New answers tagged ogr2ogr
Again I answer my own question. See the ticket at https://trac.osgeo.org/gdal/ticket/6597
The admin is another user. Privileges allow access to system-resources and tasks. They allow you to change time and shutdown and such things. That is needed when programs need to use those functions or alter something system wise like setting path variables or registry entries. Access rights allow access to objects, like folders and processes. The admin ...
The GeoJSON format and the ArcGIS Server JSON format (ArcGIS Server REST API:geometry) are simple Python dictionaries There are many Python spatial modules which have the Geo_interface protocol (GeoJSON like)(list of modules with examples). For example with Fiona import fiona lines = fiona.open("a_shapefile.shp") # first feature of the shapefile line = ...
From the ogr2ogr page: -a_srs srs_def: Assign an output SRS -t_srs srs_def: Reproject/transform to this SRS on output -s_srs srs_def: Override source SRS So we can see they have very different functions. -s_srs tells OGR to ignore the SRS that the input source claims to have and use the one provided. This is useful when OGR is unable to determine the SRS ...
I tried to approach this from as many angles as possible, and I finally found something that worked. Instead of converting the .shp to .geojson using ogr2ogr, I loaded the .shp into QGIS and then saved it as .geojson. Like stated previously, this file itself cannot be loaded into mongodb directly, so I used $ jq --compact-output ".features" counties....
I have just now developed a fairly full featured program that simplifies kml files. As well as gpx and tcx ones. It supports a number of techniques that make the file smaller, many are essentially loss-less, others reduce the precision of the path.
I didn't work through the issue with your data but my perspective is that the error comes down to a limitation of shapefile format. Topological consistency is not enforced/inherent in the shapefile format (esri's explanation here). The Mongo spatial indexing system does require topological consistency. Lacking the enforcement of consistency in the source ...
FROM should contain table names, not column names (and 100 is missing here in the table name) The ON part should connect columns from both tables, but you have specified the same table on both sides. I suggest to put the whole sql statement in quotation marks, single ones for Linux and double for Windows. The roles of dst_datasource_name and ...
Top 50 recent answers are included