[GRASS-dev] [GRASS GIS] #3890: Extend v.in.ogr to use GDAL/OGR-GMLAS driver

[GRASS GIS]

#3890: Extend v.in.ogr to use GDAL/OGR-GMLAS driver
--------------------------+-------------------------
  Reporter:  gisix        |      Owner:  grass-dev@…
      Type:  enhancement  |     Status:  closed
  Priority:  normal       |  Milestone:
 Component:  Vector       |    Version:  svn-trunk
Resolution:  invalid      |   Keywords:
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------

Comment (by gisix):

 Please reopen this ticket and reconsider whether this is really invalid
 for GIS users wanting to work with nontrivial contemporary 3D GML in GRASS
 GIS:

 1) GDAL as it is currently configured in GRASS 7.6.1 does *NOT* include
 the GMLAS driver for nontrivial GML/XML. So v.in.ogr currently does *NOT*
 import nontrivial GML/XML: Opening a complex GML-based file like european
 CityGML datasets by explicitly choosing the advanced GMLAS driver instead
 of the default GML driver throws an error message. If folks want to work
 with complex 3D GML, they will need to do so outside a GRASS environment.
 2) The GMLAS driver of GDAL/OGR would allow to work in GRASS with 3D
 PolyhedralSurfaces encoded as nontrivial GML.
 3)3D PolyhedralSurfaces will either either require functionality for the
 users on the GRASS module level (i.e. a flag or similar for v.in.ogr) to
 flatten 3D polyhedral surfaces into a GRASS 2D vector topology,
 4) or a means to provide additional parameters to the underlying GDAL/OGR
 environment, similar to the query_layer parameter of v.to.db
 (https://grass.osgeo.org/grass70/manuals/v.to.db.html)

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3890#comment:2>
GRASS GIS <https://grass.osgeo.org>