Skip to main content
Geographic Information Systems

Return to Answer

replaced http://gis.stackexchange.com/ with https://gis.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

You are confusing two different issues: the Grass plugin (Joseph answer and the new GRASS Plugin ready) and Grass in the Processing Toolbox:

  1. with the GRASS plugin, you work in GRASS GIS and you must use v.in.ogr to import your shapefile in the original GRASS GISDBASE (locations, mapset) -> The Joseph answer
  2. a GRASS script in the processing toolbox creates first a temporary GRASS GISDBASE, import the layer with v.in.ogr, do the work and finally destroy this temporary folder (see How to modify existing grass gis tools and run them in QGIS?How to modify existing grass gis tools and run them in QGIS?)

In theory, These GISDBASEs have nothing to do with each other but if you know Python, you can modify the procedure.

You are confusing two different issues: the Grass plugin (Joseph answer and the new GRASS Plugin ready) and Grass in the Processing Toolbox:

  1. with the GRASS plugin, you work in GRASS GIS and you must use v.in.ogr to import your shapefile in the original GRASS GISDBASE (locations, mapset) -> The Joseph answer
  2. a GRASS script in the processing toolbox creates first a temporary GRASS GISDBASE, import the layer with v.in.ogr, do the work and finally destroy this temporary folder (see How to modify existing grass gis tools and run them in QGIS?)

In theory, These GISDBASEs have nothing to do with each other but if you know Python, you can modify the procedure.

You are confusing two different issues: the Grass plugin (Joseph answer and the new GRASS Plugin ready) and Grass in the Processing Toolbox:

  1. with the GRASS plugin, you work in GRASS GIS and you must use v.in.ogr to import your shapefile in the original GRASS GISDBASE (locations, mapset) -> The Joseph answer
  2. a GRASS script in the processing toolbox creates first a temporary GRASS GISDBASE, import the layer with v.in.ogr, do the work and finally destroy this temporary folder (see How to modify existing grass gis tools and run them in QGIS?)

In theory, These GISDBASEs have nothing to do with each other but if you know Python, you can modify the procedure.

added 36 characters in body
Source Link
gene
gene
  • 55.4k
  • 3
  • 113
  • 191

You are confusing two different issues: the Grass plugin (Joseph answer and the new GRASS Plugin ready) and Grass in the Processing Toolbox:

  1. with the GRASS plugin, you work in GRASS GIS and you must use v.in.ogr to import your shapefile in the original GRASS GISDBASE (locations, mapset) -> The Joseph answer
  2. a GRASS script in the processing toolbox creates first a temporary GRASS GISDBASE, import the layer with v.in.ogr, do the work and finally destroy this temporary folder (see How to modify existing grass gis tools and run them in QGIS?)

In theory, These GISDBASEs have nothing to do with each other but if you know Python, you can modify the procedure.

You are confusing two different issues: the Grass plugin (Joseph answer) and Grass in the Processing Toolbox:

  1. with the GRASS plugin, you work in GRASS GIS and you must use v.in.ogr to import your shapefile in the original GRASS GISDBASE (locations, mapset) -> The Joseph answer
  2. a GRASS script in the processing toolbox creates first a temporary GRASS GISDBASE, import the layer with v.in.ogr, do the work and finally destroy this temporary folder (see How to modify existing grass gis tools and run them in QGIS?)

In theory, These GISDBASEs have nothing to do with each other but if you know Python, you can modify the procedure.

You are confusing two different issues: the Grass plugin (Joseph answer and the new GRASS Plugin ready) and Grass in the Processing Toolbox:

  1. with the GRASS plugin, you work in GRASS GIS and you must use v.in.ogr to import your shapefile in the original GRASS GISDBASE (locations, mapset) -> The Joseph answer
  2. a GRASS script in the processing toolbox creates first a temporary GRASS GISDBASE, import the layer with v.in.ogr, do the work and finally destroy this temporary folder (see How to modify existing grass gis tools and run them in QGIS?)

In theory, These GISDBASEs have nothing to do with each other but if you know Python, you can modify the procedure.

Source Link
gene
gene
  • 55.4k
  • 3
  • 113
  • 191

You are confusing two different issues: the Grass plugin (Joseph answer) and Grass in the Processing Toolbox:

  1. with the GRASS plugin, you work in GRASS GIS and you must use v.in.ogr to import your shapefile in the original GRASS GISDBASE (locations, mapset) -> The Joseph answer
  2. a GRASS script in the processing toolbox creates first a temporary GRASS GISDBASE, import the layer with v.in.ogr, do the work and finally destroy this temporary folder (see How to modify existing grass gis tools and run them in QGIS?)

In theory, These GISDBASEs have nothing to do with each other but if you know Python, you can modify the procedure.