The OGR spatial engine provides support for additional formats not directly supported by Weave based on the OGR GDAL library. A list of the available formats is available here. Note, that link provides a list of the latest supported formats which may include newer ones than those supported by Weave or newer parameters than are supported by Weave.
| Note |
|---|
The OGR driver requires the installation of the Microsoft Visual C++ 2013 Redistributable libraries. They can be downloaded from Microsoft from here. |
Different OGR drivers require different parameters, documented at the link above, but each spatial engine should have dbtype set to "ogr", and a driverName corresponding to the OGR driver, or the dbtype set to the factory name of the driver. A list of the available OGR driver names is output to the weave.log file when Weave starts (at log level INFO), e.g.
...
Some OGR drivers only support a single table whereas others can be pointed to a source that contains multiple tables, e.g. you can point to a GeoJSON file that will only have one listed table, or a directory or MapInfo files that will list one table per file.
...
The OGR driver requires the installation of the Microsoft Visual C++ 2013 Redistributable libraries.
...
.
Namespace
urn:com.cohga.server.spatial.geotools#1.0
...