| 05:21:53 | lee54: | anyone awake that can help with r.colors from the grass wiki? |
| 05:22:12 | yarma: | what's the problem? |
| 05:23:39 | lee54: | good morning yarma = ) i've been stepping through the grass wiki on modis ssts.. i'm new to grass but fairly fluent with gdal, last night i got the converted geotiff into grass and displayed, then goto run r.colors "${map}.degC" rules=palette_sst.gcolors and receive the Error: value out of range for parameter rules |
| 05:24:01 | lee54: | everything before that seemed to be ok |
| 05:24:47 | lee54: | fyi referencing this http://grass.osgeo.org/wiki/MODIS under Apply color rules to imported maps |
| 05:24:51 | sigq: | Title: MODIS - GRASS-Wiki ( at grass.osgeo.org ) |
| 05:29:19 | yarma: | I suggest to run `r.info "${map}.degC"` |
| 05:29:41 | yarma: | so you can see the min/max values in your modis file |
| 05:30:10 | lee54: | cool |
| 05:30:23 | yarma: | it must be between the min and max in your color rules file |
| 05:30:25 | lee54: | shows the values of -1.87 - 31.45 |
| 05:31:03 | lee54: | values in .gcolors runs from -3 to 45 |
| 05:31:43 | yarma: | just to be sure: have you run the entire for loop, or just the r.colors command ? |
| 05:32:45 | lee54: | i stepped through each stage of the wiki individually, after opening the image started teh apply colors processes by first recalculating via slope and intercept which seems to have worked |
| 05:33:00 | lee54: | i wonder is it possible the format of gcolors is an issue? |
| 05:33:32 | lee54: | to be sure i did it correctly i downloaded the version from the site |
| 05:33:39 | yarma: | if you copy it from the wiki it shouldn't |
| 05:34:07 | lee54: | yah did direct |
| 05:34:17 | lee54: | r.info is cool heh |
| 05:34:17 | yarma: | and you run the following commandss ? |
| 05:34:20 | lee54: | <~~ noob |
| 05:34:29 | lee54: | = ) |
| 05:34:39 | yarma: | for map in `g.mlist rast pat=*SST_4` ; do |
| 05:34:40 | yarma: | r.colors "${map}.degC" rules=palette_sst.gcolors |
| 05:34:40 | yarma: | done |
| 05:35:00 | yarma: | or just the `r.colors "${map}.degC" rules=palette_sst.gcolors` ? |
| 05:36:11 | lee54: | i tried the just r.colors trying other now |
| 05:36:58 | yarma: | ok |
| 05:37:21 | yarma: | so you have to replace "${map}.degC" by the full name of your map |
| 05:38:07 | yarma: | the ${map} is a variable that is populate by the for loop with the result of `g.mlist rast pat=*SST_4` |
| 05:38:35 | yarma: | it's very useful if you have dozens of maps, but in your case not ... |
| 05:38:42 | lee54: | looks like that version ran, going to disply now to be sure |
| 05:41:27 | lee54: | ok now that is awesome lol.. now to export and figure out how to automate with a batch script = ) |
| 05:41:34 | lee54: | ty yarma! |
| 05:43:05 | lee54: | actually the colors are off lol |
| 06:33:17 | td123: | anyone know how I can assign a vector network of some roads, speeds taken at different points along the network? It would have to only assign the speed to sections of the road, not just the whole road. Any ideas? |
| 06:34:53 | yarma: | I dno't think you can assign multiple values to 1 element |
| 06:35:44 | yarma: | i think you would have to split your vector into sections of road |
| 06:37:08 | td123: | yarma: ya, " It would have to only assign the speed to sections of the road" sorry if I was unclear : ) |
| 06:38:41 | td123: | is there a way to split a vector given a point on the vector and a distance? |
| 06:41:28 | td123: | v.net.iso looks kind of promising |
| 06:42:49 | td123: | if it splits up a vector at the boundaries, then that's what I'm looking for ^^, any thoughts? |
| 10:08:36 | gioman: | Hi all, one question: how it is supposed to work the command "v.in.ogr" when pointing to a folder containing more than one shapefile? for example a folder containing two simple shapefiles each with one polygon partially overlapping with the one in the other shape. I was expecting the module to import the vectors as they are in origin, instead I obtain two GRASS vectors each containing two features ( the extra feature is the overlapping portion ). Is |
| 10:49:30 | sigq: | grassfeed: Ticket #829 ( defect created ): v.in.ogr: when pointing to a folder import of vectors can produce wrong results <https://trac.osgeo.org/grass/ticket/829> |
| 19:41:52 | CIA-64: | cmbarton * r39860 /grass/branches/releasebranch_6_4/gui/wxpython/xml/menudata.xml: Update menus |
| 19:42:11 | sigq: | grassfeed: Changeset [39860]: Update menus <https://trac.osgeo.org/grass/changeset/39860> |
| 19:55:18 | CIA-64: | cmbarton * r39861 /grass/branches/develbranch_6/gui/wxpython/xml/menudata.xml: Update menus with modules and scripts. Backport from releasebranch_6_4 r39860 |
| 20:31:32 | CIA-64: | cmbarton * r39862 /grass/trunk/gui/wxpython/xml/menudata.xml: Menu update with modules and scripts |
| 20:31:37 | sigq: | grassfeed: Changeset [39862]: Menu update with modules and scripts <https://trac.osgeo.org/grass/changeset/39862> |
| 20:43:16 | sigq: | grassfeed: Changeset [39863]: More updates to menu <https://trac.osgeo.org/grass/changeset/39863> |
| 20:43:25 | CIA-64: | cmbarton * r39863 /grass/branches/develbranch_6/gui/wxpython/xml/menudata.xml: More updates to menu |
| 20:45:28 | CIA-64: | cmbarton * r39864 /grass/branches/releasebranch_6_4/gui/wxpython/xml/menudata.xml: More updates to menus |
| 20:47:07 | sigq: | grassfeed: Changeset [39864]: More updates to menus <https://trac.osgeo.org/grass/changeset/39864> |
| 21:26:33 | CIA-64: | cmbarton * r39865 /grass/trunk/scripts/v.db.univar/v.db.univar.py: GUI enhancements and formatting. |
| 21:26:36 | sigq: | grassfeed: Changeset [39865]: GUI enhancements and formatting. <https://trac.osgeo.org/grass/changeset/39865> |
| 21:36:07 | StewieGriffen: | Hello |