On Tue, Mar 7, 2017 at 7:41 AM, Ken Mankoff <[email protected]> wrote: > > On Tue, Mar 7, 2017 at 4:11 AM, Moritz Lennert > <[email protected]> wrote: >> >> AFAIK, d.where does not allow direct interaction with the display anymore. >> It "just" takes screen coordinates and outputs them as map coordinates. In >> GRASS 6 you could get the screen coordinates by clicking on the d.mon >> display, but in GRASS 7 this is handled by the GUI (g.gui or d.mon wx*). In >> other words you chose the GUI interrogation tool and when you click on the >> monitor, it launches d.where and you get the coordinates. You can ask for >> these coordinates to be redirected to the console. >> >> I agree that the current solution is not ideal. For example, it is not >> straightforward how to collect the info into a file. Also: the output is not >> really as machine-parsing friendly as it could. >> >> See https://trac.osgeo.org/grass/ticket/3310 and add to it if you think >> something is missing. > > > Thanks for the reply. I will think about and add suggestions to the ticket. > Let me know if I can help debug the "ERROR: Vector digitizer not available. > cannot import name GV_LINES" issue. >
That seems to be problem with ctypes, I've seen this on Mac before. Do you compile grass on your own, or use homebrew? I know some students used osgeo4mac and they couldn't use digitizer, 3D view and pygrass at all. But when I compile GRASS myself, it works. Anna > -k. > > _______________________________________________ > grass-user mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/grass-user _______________________________________________ grass-user mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-user
