Feature request #10884
OSM data loaded with "Add Vector layer" can be incomplete
|Pull Request or Patch supplied:||No||Resolution:|
|Easy fix?:||No||Copied to github as #:||19252|
Attached is a sample of a real island with landuse polygon downloaded from the OSM API, or rather from http://gis.stackexchange.com/questions/104599/osm2pgsql-missing-coordinates. It gets loaded with the OSM plugin, but incomplete using "Add Vector Layer", as shown in the attached screenshot.
The reason is that the nodes are not sorted in the input file. No error message is given in the protocol, some nodes are silently dropped.
If I transform the file with ogr2ogr, I get the message "ERROR 1: Non increasing node id. Use OSM_USE_CUSTOM_INDEXING=NO" If I use that as environment variable (not -lco!), it works for ogr2ogr. But QGIS does not offer that method in an easy way.
So I suggest to set this variable internally when using the GDAL osm driver.
According to OSM expert Paul Norman in http://gis.stackexchange.com/questions/103547/how-to-complete-the-roads-output-of-postgis/103599#103599 the OSM API does not guarantee the nodes in an ordered way, so QGIS has to take care on its own about it.
#1 Updated by Giovanni Manghi over 8 years ago
- Category set to Vectors
- OS version deleted (
- Operating System deleted (
- Target version deleted (
Future Release - High Priority)
- Status changed from Open to Feedback
- Crashes QGIS or corrupts data changed from Yes to No