[GRASS-user] setting snap an min_area for v.in.ogr

Hello List,

why are there no input boxes for snap threshold and min_area in the v.in.ogr menu in GRASS 7.0.3? I think those values are important to control the process. On the command line, the values can be entered.

Greets, Uwe

On 09/06/16 10:47, Uwe Fischer wrote:

Hello List,

why are there no input boxes for snap threshold and min_area in the
v.in.ogr menu in GRASS 7.0.3? I think those values are important to
control the process. On the command line, the values can be entered.

This is an old discussion. See [1] for example.

The menu entry File->Import vector data->Common import formats actually does not launch v.in.ogr as such, but a GUI import wizard which launches v.in.ogr.

The general gist of those in favor of simple versions of the wizard is that the wizard should only show the basic functionality to ease use.

Those who want to use the full-power v.in.ogr can launch it using v.in.ogr --ui in the console.

In GRASS7.2 the main import wizard actually uses v.import which allows reprojection during the import. It also gives access to the more detailed parameters. However, v.import does not provde min_area. If this is considered necessary, then a ticket should be opened.

Moritz

[1] https://trac.osgeo.org/grass/ticket/2042

Moritz,

thank you very much for your help. I understand so far whats going on. But I did not choose any menu items; I typed v.in.ogr in the console window, and then the reduced wizard showed up. So the flag --ui is what I need.

Is --ui available for every GRASS command? Or is there a way for the user to see/to learn if 2 wizards for the same command are existing?

In most cases, I'd love to see all options available because my input datasets often require filtering, selecting or setting tolerances.

Thank you once more.

Mit freundlichen Grüßen,

UWE FISCHER

-----Ursprüngliche Nachricht-----
Von: Moritz Lennert [mailto:mlennert@club.worldonline.be]
Gesendet: Donnerstag, 9. Juni 2016 11:27
An: Uwe Fischer <gisfisch@t-online.de>; grass-user@lists.osgeo.org
Betreff: Re: [GRASS-user] setting snap an min_area for v.in.ogr

On 09/06/16 10:47, Uwe Fischer wrote:

Hello List,

why are there no input boxes for snap threshold and min_area in the
v.in.ogr menu in GRASS 7.0.3? I think those values are important to
control the process. On the command line, the values can be entered.

This is an old discussion. See [1] for example.

The menu entry File->Import vector data->Common import formats actually does not launch v.in.ogr as such, but a GUI import wizard which launches v.in.ogr.

The general gist of those in favor of simple versions of the wizard is that the wizard should only show the basic functionality to ease use.

Those who want to use the full-power v.in.ogr can launch it using v.in.ogr --ui in the console.

In GRASS7.2 the main import wizard actually uses v.import which allows reprojection during the import. It also gives access to the more detailed parameters. However, v.import does not provde min_area. If this is considered necessary, then a ticket should be opened.

Moritz

[1] https://trac.osgeo.org/grass/ticket/2042

On 09/06/16 12:55, Uwe Fischer wrote:

Moritz,

thank you very much for your help. I understand so far whats going on. But I did not choose any menu items; I typed v.in.ogr in the console window, and then the reduced wizard showed up. So the flag --ui is what I need.

Is --ui available for every GRASS command?

Yes. You can see it if you la

Or is there a way for the user to see/to learn if 2 wizards for the same command are existing?

Not really, AFAIK. --ui _always_ brings up the actual module GUI. Normally, launching a module with just its name does the same, but for the import and export modules special treatments have been decided within the wxGUI. If you launch the same module in a terminal, you get the original (--ui) GUI.

I personally find this confusing and would have prefered a separate "Import wizard" entry in the GUI menu (with possible g.gui.vimport/rimport modules), but others have the feeling that this makes life easier for newcomers...

In most cases, I'd love to see all options available because my input datasets often require filtering, selecting or setting tolerances.

+1.

You will always get all options using --ui.

Moritz