| 66 | |
| 67 | == Report 2 == |
| 68 | |
| 69 | Hi All, |
| 70 | |
| 71 | apologize me for the gap time :-/ |
| 72 | |
| 73 | the "duplicate grass installation" gived me some problems. |
| 74 | Fixed the gdal-grass driver problems (thanks to William!!!) when multiple grass installation are finded |
| 75 | now the problem come up with subprocess when i use the grass.py function |
| 76 | |
| 77 | the error is a bit weird beacouse it sometimes works and sometimes get me a subprocess error |
| 78 | |
| 79 | ^^^ this only on Osx ... on linux all goes fine. |
| 80 | |
| 81 | |
| 82 | ... so : hard solution, i erased an exrternal hd and installed osx from scratch with only one grass version(7) i haven't finished to reinstall all the needed SW |
| 83 | |
| 84 | |
| 85 | back to coding ... |
| 86 | |
| 87 | going ahed with my coding ... what i do this week : |
| 88 | |
| 89 | - worked a lot to have a better gui. |
| 90 | to have a more usable app. i switched from Qwidjet() to Qmainwindow() so now i'm able to use more widjet like menubar etc... (i know this are cosmetics things ;-) |
| 91 | |
| 92 | - worked on the kml export, not uploaded yet into the svn |
| 93 | i have kml export working for point line and polygon, but i haven't yet it working on polygon that has inner+outher boundaries. |
| 94 | it use py-gdal to have acces to the layer feature |
| 95 | |
| 96 | the export parameters are : |
| 97 | |
| 98 | colors (line,label,polygon) |
| 99 | alpha-chanell(colors) |
| 100 | line width |
| 101 | altitude mode |
| 102 | icons |
| 103 | |
| 104 | label name and height can be setted from a field attribute |
| 105 | |
| 106 | (studing the kml standard) |
| 107 | |
| 108 | i'm including the layer attributes in the "kml data description", but my plain is to insert , in the kml attribute data, |
| 109 | the results of v.what + r.what (for points and/or polygon's centroid) |
| 110 | for line i think is not usefull .. maybe leght and layer attributes can be good as information. |
| 111 | |
| 112 | the layers to be queried are the layer in the active mapset |
| 113 | (in the gui i'm adding a tree with layer's names, each layer will be checkable so all the checked layer will be passed to the query) |
| 114 | |
| 115 | i need to add yet the capabilites to create png file for raster legend so we can the kml export to create "kml screen overlay" |
| 116 | i think to use the png monitor in grass to produce the image or other solution .. i need to investigate |
| 117 | |
| 118 | - wrotin build documentation about my linux environment. |
| 119 | starting from a linux live cd distro (sidux) i done an "how to install" (apt-get & configure notes) for all the sw i'm using |
| 120 | so i create a virtualcd based on virtualbox i can distribuite to every one want help me to test the project |
| 121 | (the project has immense options of development so suggestions on which feature is to prefer to an other one |
| 122 | or you have a feature that is possible to include in it and and i haven't tinked yet) |
| 123 | |
| 124 | - On the next week the OssimDev Team will have a meeting, so i'm preparing a report with case-test to face the ossm-gdal-grass raster rendering. |
| 125 | |
| 126 | == == |
| 127 | |
| 128 | == Report 3 == |
| 129 | |
| 130 | Little notes : |
| 131 | |
| 132 | Restored my OS, |
| 133 | |
| 134 | for grass on osx i'm using version 6.4 |
| 135 | (the 7 can works, but some time the build fais, so to have a more stable development |
| 136 | i'm switching to 6,4 binary version, so it is more easy for osx user to test the code) |
| 137 | |
| 138 | on linux i'using grass7 (there are difference in the module import for grass, so i'll use "try: except" |
| 139 | to get the code running for grss 6.4 and 7) |
| 140 | |
| 141 | |
| 142 | Coded : |
| 143 | |
| 144 | fixed the polygons exporte to kml so now hole in polygons hare andled |
| 145 | firex some gui behavioure .. a window too much big, so i done a recode of the gui code |
| 146 | |
| 147 | - preparing a different web-map widjet, based on ka-map2 |
| 148 | this can give some enanchement like : |
| 149 | - ability to crteate a mapfile on the fly, generated reading the grass mapset layers |
| 150 | - better refresh of gps signal |
| 151 | |
| 152 | - done a report about the grass-raster rendering, this tasks will be faced the next week, |
| 153 | i have exam on 16 june so the incoming week my Soc works will be slowly |
| 154 | (i hope all goes well) then i'm planning to go to bolsena meeting where i'll spend |
| 155 | a full dept week to code. |
| 156 | |
| 157 | here some screenshoot of the gui (yet prototipe) : |
| 158 | |
| 159 | http://www.geofemengineering.it/data/view.png |
| 160 | http://www.geofemengineering.it/data/data.png |
| 161 | http://www.geofemengineering.it/data/gps.png |
| 162 | |
| 163 | for who is intersted in testing, debug : |
| 164 | |
| 165 | - notes about the installation of the needed software can be etracted from : |
| 166 | |
| 167 | http://wiki.osgeo.org/wiki/GFOSS.it_Live_DVD_Install |
| 168 | |
| 169 | |
| 170 | done a virtual machine with needed sw, |
| 171 | but my ftp reject it :-( |
| 172 | so i don't know where to upload it |
| 173 | (this is for who is intersted in testing purpose, but has problems / or do not want touch his system) |
| 174 | |
| 175 | == == |
| 176 | |
| 177 | == Report 4 == |
| 178 | |
| 179 | Hi All, |
| 180 | |
| 181 | here the 4-th report for my project : |
| 182 | |
| 183 | In the last week, after some coding i can see that he main-app file was too much long |
| 184 | that is no good beacouse the code is not easy readable. |
| 185 | |
| 186 | doing some test, i can see the threaded class "joystick and gps tools" |
| 187 | consume a lot of cpu-resource |
| 188 | |
| 189 | i decided to do a complete revision on the code : |
| 190 | |
| 191 | - extracted some function and class from the main file |
| 192 | and store it in separate files (the code results more readable, |
| 193 | and each tools can be easy re-used out-side the main app) |
| 194 | |
| 195 | - done a complete revision on the trheaded class, |
| 196 | now the trhead are colled only when they really needs |
| 197 | i also added in the joystick code a line used in pygame |
| 198 | to reduce cpu usage when possible. |
| 199 | |
| 200 | |
| 201 | The results code is more fast and readable. |
| 202 | |
| 203 | In the last week i also worked on : |
| 204 | |
| 205 | - a query tool to ask information on grass layer (both raster and vector) |
| 206 | it runs r.what + v.what on a list of selectable layers avaiable in the active grass-mapset. |
| 207 | |
| 208 | - initial test about the grass code to produce "legend images" for raster layers |
| 209 | this is needed to produce kml screen overlay |
| 210 | |
| 211 | - create a blog page for the project to describe the project |
| 212 | |
| 213 | |
| 214 | what to do the next week : |
| 215 | |
| 216 | - separate each tool in separate files produce some (minor) code issue, i need to learn how to send |
| 217 | a message from one widget to an other one (e.g. create connections bettween different tools) |
| 218 | if some one has pyqt knowledge i have some questions for him ;-) |
| 219 | |
| 220 | - rework the web-map based tool using kamap2 (it will consists in a web-gis based on a mapfile produced on the fly, it read the layer to render from a list of grass layer, so i'm coding an interface to produce it) |
| 221 | |
| 222 | - i'll be in Bolsena for the osgeo hacking event i'll try to receive feedback, suggestion for a full coding-week |
| 223 | |
| 224 | == == |