Vector FAQ GRASS6: Difference between revisions
No edit summary |
mNo edit summary |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
'''Q''':GRASS | '''Q''':GRASS 6 vector architecture - FAQ: Why on earth a topological model!? It introduces in fact many problems. Nontopological GIS is easier to use and all popular proprietary GIS desktops like ArcView or Mapinfo use nontopological model. But there are some advantages of topological model over nontopological. In addition, OpenGIS specification is not topological, so GRASS may never conform Open GIS once topological model is used.<br> | ||
'''A''': Well | '''A''': Well, we just prefer quality. | ||
'''Q''': | '''Q''': What are the programming details?<br> | ||
'''A''': | '''A''': See here: http://grass.osgeo.org/programming7/vlibFAQ.html | ||
'''Q''': Everything is going RDBMS. The only modern and good enough solution is to store all data in relational database. Why do you spend all that time working on grass vector format if you can use PostGIS/Postgres?<br> | '''Q''': Everything is going RDBMS. The only modern and good enough solution is to store all data in relational database. Why do you spend all that time working on grass vector format if you can use PostGIS/Postgres?<br> | ||
'''A''': | '''A''': Its' a matter of choice. And GRASS GIS support [[PostGIS]]/PostgreSQL. You can choose the database backend, and in GRASS 7 a direct integration has been implemented. Note that GRASS's vector format is topological, which opens the doors to all sorts of analyses which a non-topological format (like SHAPE) does not. And you can link a vector to an external RDBMS with {{cmd|v.db.connect}} or use directly a PostGIS data source with {{cmd|v.external}}. | ||
You can choose that | |||
'''Q''': | '''Q''': Why can't I have layers called 1516?<BR> | ||
'''A''': | '''A''': The naming convention for vector maps requires that map names start with a character, not a number (map name scheme: [A-Za-z][A-Za-z0-9_]*). Reason: GRASS uses SQL which does not permit names starting with a number or symbol. | ||
'''Q''': | '''Q''': Can you save color rules in vector files?<br> | ||
'''A''': Yes. v. | '''A''': Yes, see GRASSRGB column in the {{cmd|d.vect}} manual page and {{cmd|v.colors}} | ||
'''Q''': Why do we need support for so many formats and databases? | '''Q''': It is well known that SHAPE files may contain topological errors. What can I do?<br> | ||
'''A''': Again | '''A''': GRASS helps you: the {{cmd|v.in.ogr}} import cleans most problems, furthermore there are {{cmd|v.build}} which offers an error map as well as {{cmd|v.clean}} and {{cmd|v.edit}} for special problems. | ||
'''Q''': Why do we need support for so many formats and databases? I think that one format + one database is enough.<br> | |||
'''A''': Again it is a matter of choice. What's wrong with supporting several formats? | |||
'''Q''': Is it possible to write/edit non native formats like shapefile, coverage or PostGIS?<br> | '''Q''': Is it possible to write/edit non native formats like shapefile, coverage or PostGIS?<br> | ||
'''A''': yes | '''A''': yes: {{cmd|v.out.ogr}} and from GRASS 7 onwards, {{cmd|v.external}} | ||
'''Q''': Why are two line types (line and boundary) needed? Everything is easier with just one type, otherwise thousands | '''Q''': Why are two line types (line and boundary) needed? Everything is easier with just one type, otherwise thousands of hours must be spent to assign the right type to each line.<br> | ||
'''A''': If you have lines which are part of areas and lines which are not part of | '''A''': If you have lines which are part of areas and lines which are not part of area (Example: roads, rivers etc) how could you distinguish them? | ||
area (Example: roads, rivers etc) how | |||
'''Q''': Is it possible to generate TIN from raster DEM or 3D points?<br> | '''Q''': Is it possible to generate TIN from raster DEM or 3D points?<br> | ||
'''A''': | '''A''': More or less. Not exciting yet, but TINs are also not too exciting. See also [[Addons]] | ||
'''Q''': Are there volumes or other 3D objects supported?<br> | '''Q''': Are there volumes or other 3D objects supported?<br> | ||
'''A''': 3D faces yes (e.g. CAD-style 3D buildings etc) | '''A''': 3D faces yes (e.g. CAD-style 3D buildings etc), use {{cmd|v.in.ogr}} or {{cmd|v.in.dxf}} to import or {{cmd|v.extrude}} to extrude from 2D. | ||
'''Q''': Are there multiobjects like multipoint or multiline supported?<br> | '''Q''': Are there multiobjects like multipoint or multiline supported?<br> | ||
'''A''': Yes | '''A''': Yes - {{cmd|v.build.polyline}} | ||
'''Q''': Does any support for overlay/analyses exist in GRASS | '''Q''': Does any support for overlay/analyses exist in GRASS 6?<br> | ||
'''A''': yes - v.overlay | '''A''': yes - {{cmd|v.overlay}} and {{cmd|v.select}} | ||
'''Q''': Why do we need more categories attached to one element?<br> | '''Q''': Why do we need more categories attached to one element?<br> | ||
| Line 41: | Line 42: | ||
'''Q''': Is it supported Microsoft SQL Server / Oracle / Informix?<br> | '''Q''': Is it supported Microsoft SQL Server / Oracle / Informix?<br> | ||
'''A''': Oracle via OGR | '''A''': Oracle via OGR, Microsoft via ODBC, see {{cmd|sql}} | ||
'''Q''': Are there images and other arbitrary documents supported as attributes?<br> | '''Q''': Are there images and other arbitrary documents supported as attributes?<br> | ||
'''A''': no (not yet?) | '''A''': no (not yet?). Perhaps add blob support? | ||
'''Q''': How can be nontopological formats read by topological GIS without conversion?<br> | '''Q''': How can be nontopological formats read by topological GIS without conversion?<br> | ||
'''A''': pseudotopology is built | '''A''': pseudotopology is built - {{cmd|v.external}} | ||
'''Q''': Are there routes like in ArcInfo supported?<br> | '''Q''': Are there routes like in ArcInfo supported?<br> | ||
'''A''': yes (see d.path, v.net.*) | '''A''': yes (see {{cmd|d.path}}, {{cmd|v.net}}.*, {{cmd|v.lrs}}.*) | ||
'''Q''': Will be possible to read attributes from ArcInfo coverages | '''Q''': Will be possible to read attributes from ArcInfo coverages?<br> | ||
'''A''': yes, use v.in.ogr | '''A''': yes, use {{cmd|v.in.ogr}} | ||
'''Q''': Where can I find a description of the new vector format?<br> | '''Q''': Where can I find a description of the new vector format?<br> | ||
'''A''': Try http://www.ing.unitn.it/~grass/conferences/GRASS2002/proceedings/proceedings/pdfs/Blazek_Radim.pdf | '''A''': Try http://www.ing.unitn.it/~grass/conferences/GRASS2002/proceedings/proceedings/pdfs/Blazek_Radim.pdf and http://grass.osgeo.org/programming7 ("GRASS GIS Vector Architecture") | ||
[[Category:FAQ]] | |||
[[Category:Vector]] | |||
Latest revision as of 10:17, 4 December 2018
Q:GRASS 6 vector architecture - FAQ: Why on earth a topological model!? It introduces in fact many problems. Nontopological GIS is easier to use and all popular proprietary GIS desktops like ArcView or Mapinfo use nontopological model. But there are some advantages of topological model over nontopological. In addition, OpenGIS specification is not topological, so GRASS may never conform Open GIS once topological model is used.
A: Well, we just prefer quality.
Q: What are the programming details?
A: See here: http://grass.osgeo.org/programming7/vlibFAQ.html
Q: Everything is going RDBMS. The only modern and good enough solution is to store all data in relational database. Why do you spend all that time working on grass vector format if you can use PostGIS/Postgres?
A: Its' a matter of choice. And GRASS GIS support PostGIS/PostgreSQL. You can choose the database backend, and in GRASS 7 a direct integration has been implemented. Note that GRASS's vector format is topological, which opens the doors to all sorts of analyses which a non-topological format (like SHAPE) does not. And you can link a vector to an external RDBMS with v.db.connect or use directly a PostGIS data source with v.external.
Q: Why can't I have layers called 1516?
A: The naming convention for vector maps requires that map names start with a character, not a number (map name scheme: [A-Za-z][A-Za-z0-9_]*). Reason: GRASS uses SQL which does not permit names starting with a number or symbol.
Q: Can you save color rules in vector files?
A: Yes, see GRASSRGB column in the d.vect manual page and v.colors
Q: It is well known that SHAPE files may contain topological errors. What can I do?
A: GRASS helps you: the v.in.ogr import cleans most problems, furthermore there are v.build which offers an error map as well as v.clean and v.edit for special problems.
Q: Why do we need support for so many formats and databases? I think that one format + one database is enough.
A: Again it is a matter of choice. What's wrong with supporting several formats?
Q: Is it possible to write/edit non native formats like shapefile, coverage or PostGIS?
A: yes: v.out.ogr and from GRASS 7 onwards, v.external
Q: Why are two line types (line and boundary) needed? Everything is easier with just one type, otherwise thousands of hours must be spent to assign the right type to each line.
A: If you have lines which are part of areas and lines which are not part of area (Example: roads, rivers etc) how could you distinguish them?
Q: Is it possible to generate TIN from raster DEM or 3D points?
A: More or less. Not exciting yet, but TINs are also not too exciting. See also Addons
Q: Are there volumes or other 3D objects supported?
A: 3D faces yes (e.g. CAD-style 3D buildings etc), use v.in.ogr or v.in.dxf to import or v.extrude to extrude from 2D.
Q: Are there multiobjects like multipoint or multiline supported?
A: Yes - v.build.polyline
Q: Does any support for overlay/analyses exist in GRASS 6?
A: yes - v.overlay and v.select
Q: Why do we need more categories attached to one element?
A: why not? Maybe you have different attributes to assign to one vector
Q: Is it supported Microsoft SQL Server / Oracle / Informix?
A: Oracle via OGR, Microsoft via ODBC, see sql
Q: Are there images and other arbitrary documents supported as attributes?
A: no (not yet?). Perhaps add blob support?
Q: How can be nontopological formats read by topological GIS without conversion?
A: pseudotopology is built - v.external
Q: Are there routes like in ArcInfo supported?
A: yes (see d.path, v.net.*, v.lrs.*)
Q: Will be possible to read attributes from ArcInfo coverages?
A: yes, use v.in.ogr
Q: Where can I find a description of the new vector format?
A: Try http://www.ing.unitn.it/~grass/conferences/GRASS2002/proceedings/proceedings/pdfs/Blazek_Radim.pdf and http://grass.osgeo.org/programming7 ("GRASS GIS Vector Architecture")