Hi Helena, On Thu, Sep 20, 2012 at 5:37 AM, Helena Mitasova <[email protected]> wrote: > It appears that d.his does not work when the map layers are from different > mapsets, > the following command which has the first map in PERMANENT and the second one > in mea582f2012 > expects both maps in PERMANENT > d.his i_map=elevation_shade h_map=noise bright=30 > Command 'd.his bright=30 i_map=elevation_shade@PERMANENT > h_map=noise@PERMANENT' failed > Details: Raster map <noise@PERMANENT> not found
I hopefully fixed it in r53241. Please test also other similar commands like d.rgb if I didn't forget about something. > adding the mapset to the name did not help, I was still getting the error for > the following: > d.his h_map=noise@mea582f2012 i_map=elevation_shade@PERMANENT bright=30 > d.his i_map=elevation_shade@PERMANENT h_map=noise@mea582f2012 bright=30 This should work (also before the fix). Maybe you could get confused because the error message appears again after re-rendering. To avoid this you must remove the layer or double click to open properties dialog and fix it there. > > It runs OK from GUI. > Can somebody try this out independently? > I can file a bug report but I would like to make sure that this is not my > local problem, > > Thanks, Helena Best, Anna > > > Helena Mitasova > Associate Professor > Department of Marine, Earth, and Atmospheric Sciences > 2800 Faucette Drive, Rm. 1125 Jordan Hall > North Carolina State University > Raleigh, NC 27695-8208 > [email protected] > > "All electronic mail messages in connection with State business which are > sent to or received by this account are subject to the NC Public Records Law > and may be disclosed to third parties.” > > On Sep 19, 2012, at 3:02 AM, Anna Kratochvílová wrote: > >> Hi, >> >> sorry for the late answer, >> >> On Tue, Sep 11, 2012 at 4:26 AM, Helena Mitasova <[email protected]> wrote: >>> Anna, >>> >>> here is a more complete information: >>> >>> this is what I typed in and running it resulted in the error message below >>> d.vect -c basin_50Kval >>> >> >> for me it works. I try for example >> >> d.vect -c railroads >> >> and the layer is added correctly and arrow up shows you >> >> d.vect -c map=railroads@PERMANENT >> >> There shouldn't be any platform specific code so I don't understand >> why it's not working. I tested it for both grass 6.4 and 7. Is it >> still an issue? >> >> Anna >> >>> if you try to rerun it by retrieving it from history using up arrow it >>> shows this (apparently that is what I sent without checking it) >>> d.vect map=-c basin_50Kval >>> >>> it works with the word map >>> d.vect -c map=basin_50Kval >>> >>> or if -c is at the end >>> d.vect map=basin_50Kval -c >>> >>> so it unfortunately does the same thing as d.rast, >>> >>> Helena >>> >>> >>> On Sep 10, 2012, at 3:17 AM, Anna Kratochvílová wrote: >>> >>>> On Mon, Sep 10, 2012 at 3:09 AM, Helena Mitasova <[email protected]> wrote: >>>>>> >>>>>> >>>>>>> >>>>>>> d.rast -o landuse96_28m cat=1,2 >>>>>>> run in command console is interpreted as follows: >>>>>>> Command 'd.rast -l -a -n -d -u -s -e -9 -6 -_ -2 -8 -m >>>>>>> map=-o cat=1,2' failed >>>>>>> Details: Sorry, <l> is not a valid flag >>>>>>> Sorry, <a> is not a valid flag >>>>>>> Sorry, <n> is not a valid flag >>>>>>> Sorry, <d> is not a valid flag >>>>>>> Sorry, <u> is not a valid flag >>>>>>> Sorry, <s> is not a valid flag >>>>>>> Sorry, <e> is not a valid flag >>>>>>> Sorry, <9> is not a valid flag >>>>>>> Sorry, <6> is not a valid flag >>>>>>> Sorry, <_> is not a valid flag >>>>>>> Sorry, <2> is not a valid flag >>>>>>> Sorry, <8> is not a valid flag >>>>>>> Sorry, <m> is not a valid flag >>>>>>> >>>>>>> d.rast landuse96_28m cat=1,2 -o works fine. >>>>>> >>>>>> I tried to fix it so it should work now. I hope I didn't break >>>>>> something else, this is quite difficult to test. >>>>> >>>>> does this fix solve also the flags with d.vect? For example I get >>>>> d.vect map=-c basin_50Kval >>>> >>>> This should probably be d.vect -c map=basin_50Kval? This case works. >>>> "d.vect map=-c basin_50Kval" is bad input and it would be difficult to >>>> handle all wrong inputs. >>>> >>>>> >>>>>> Command 'd.vect -b -a -s -i -n -_ -5 -0 -K -v -a -l map=-c' >>>>>> failed >>>>>> Details: Sorry, <b> is not a valid flag >>>>>> Sorry, <s> is not a valid flag >>>>>> Sorry, <n> is not a valid flag >>>>>> Sorry, <_> is not a valid flag >>>>>> Sorry, <5> is not a valid flag >>>>>> Sorry, <0> is not a valid flag >>>>>> Sorry, <K> is not a valid flag >>>>>> Sorry, <l> is not a valid flag >>>>> >>>>> Thanks a lot. >>>>> >>>>> I think I have written that the color fill on cutting planes does not >>>>> work on windows - I tried it again and it works great, >>>>> We just worked in class with wxnviz last week and we did not have any >>>>> problems on 20+ computers and laptops >>>>> running windows and Mac OSX, so that is fantastic, given how new the GUI >>>>> is. >>>>> >>>> >>>> I'm glad to hear that. >>>> >>>>> Also, this is the first year that I haven't seen many complaints about >>>>> import/export of raster and vector data, >>>>> so that is a great improvement too. >>>>> The only comment I have seen so far was lack of Browse button when >>>>> selecting the directory for v.out.ogr output, >>>>> I am wondering whether it is intentional due to some technical issues or >>>>> just an oversight, >>>>> given that r.out.gdal has such option. >>>> >>>> I don't know, the gui respects that the dsn option is string and not >>>> file. There is probably some difference but someone would know this >>>> better. >>>> >>>> Anna >>>> >>>>> >>>>> Helena >>>>> >>>>>>> >>>>>>> add volume still does not open dialog >>>>>> >>>>>> Maybe someone else (who is more familiar with PATH and Makefiles) could >>>>>> help? >>>>>> >>>>>> Anna >>>>>> >>>>>>> >>>>>>> I am running Michaels Mac binary, >>>>>>> >>>>>>> Helena >>>>>>> >>>>>>> >>>>>>> >>>>>>> Helena Mitasova >>>>>>> Associate Professor >>>>>>> Department of Marine, Earth, and Atmospheric Sciences >>>>>>> 2800 Faucette Drive, Rm. 1125 Jordan Hall >>>>>>> North Carolina State University >>>>>>> Raleigh, NC 27695-8208 >>>>>>> [email protected] >>>>>>> >>>>>>> "All electronic mail messages in connection with State business which >>>>>>> are sent to or received by this account are subject to the NC Public >>>>>>> Records Law and may be disclosed to third parties.” >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> grass-dev mailing list >>>>>>> [email protected] >>>>>>> http://lists.osgeo.org/mailman/listinfo/grass-dev >>>>> >>> > _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
