Gdal.vect

gdal.vect is the part of GDAL, used to read Vector data and non-spatial data.

We test and support (options for) the following formats:

reading

Since GeoDMS 20.20.0 a table is read as one operator application (storage_read_table): the layer is opened for the attributes that are requested and no others, an IntegrityCheck on the table unit guards every attribute read from it, and SyncMode still adds the columns of the layer as attributes without reading them. See StorageManager.

Since GeoDMS 20.23.1 a Feature attribute with composition type multipoint can be read from a layer that holds other geometry types as well, such as a GeoJSON file, a csv with a WKT column or a generic PostGIS geometry column. Each feature then gives the vertices of its own geometry as stored: a point its point, a line its vertices, a polygon the vertices of its rings including each closing vertex, a curve those of its linear approximation, and a collection those of its members. Before, a line or polygon in such a layer was taken for a multipoint, which crashed the application or produced garbage.

Since GeoDMS 20.23.1 a layer whose first feature has no geometry (a GeoJSON "geometry": null, an empty WKT) is read. When a layer holds more than one geometry type and no geometry Attribute is configured, gdal.vect takes the composition type of the geometry it creates from the first feature with a geometry. Before, it took it from the first feature, and a first feature without one crashed the application with an access violation.

Since GeoDMS 20.23.1 a column that the Value type of its Attribute cannot take, such as a real column read into an int64 or bool attribute, fails only that attribute, as before 20.20.0. In 20.20.0 the one-pass read of a table failed all its other attributes and its geometry with it.

see also