You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, if an area way(e.g. amenity=place_of_worship, amenity=school, etc.) has an extra barrier=fence tag onto it, the openstreetmap plugin fails to import that way into a polygon. This got me scratching my head for a little while as to why a few school grounds were not imported.
I'm attaching a .osm that shows both area ways with amenity=place_of_worship with and without the barrier=fence to test out.
With your test case, you are confusing the importer: amenity=school can be an area (or a point), but barrier=fence is more likely a line. To avoid such pitfalls, you can add area=yes to your object.
Or use Add Vector Layer. The GDAL OSM driver seems to handle your case correctly.
Author Name: Mathieu Pellerin - nIRV (Mathieu Pellerin - nIRV)
Original Redmine Issue: 8037
Affected QGIS version: master
Assignee: Martin Dobias
Basically, if an area way(e.g. amenity=place_of_worship, amenity=school, etc.) has an extra barrier=fence tag onto it, the openstreetmap plugin fails to import that way into a polygon. This got me scratching my head for a little while as to why a few school grounds were not imported.
I'm attaching a .osm that shows both area ways with amenity=place_of_worship with and without the barrier=fence to test out.
The text was updated successfully, but these errors were encountered: