Opened 11 years ago
Closed 11 years ago
#5055 closed defect (fixed)
OSM Driver: Too many members referenced
Reported by: | dengo | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | 1.10.0 |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | OSM |
Cc: |
Description
I've already posted this on the mailing list:
The issue I’m having is that I sometimes get a Failure on GetNextFeature like “Too many members referenced in relation 32572”. What consequences does this failure have?
If I just continue with the next layer in the interleaved reading scheme I get more features, but did I miss some features because of the failure?
Here is what Even said:
Interesting. This means that your OSM file has a <relation> with more than 2000 <member> in it, which is documented as something that should be avoided (http://wiki.openstreetmap.org/wiki/Relation indicates 300 as the recommanded max size, and the OSM XML parser currently implements a limit of 2000). How was that OSM file generated ? Could you create a Trac ticket and share it ? Anyway, I'll try to see if the limit can be dynamically increased.
A file where this problem occurs can be created with:
http://www.overpass-api.de/api/xapi?map?bbox=8.6088,48.2827,8.7268,48.3336
or
http://api.openstreetmap.org/api/0.6/map?bbox=8.6088,48.2827,8.7268,48.3336
I've also attached the the file.
Attachments (1)
Change History (2)
by , 11 years ago
Attachment: | problem.osm.zip added |
---|
comment:1 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in trunk (r25925) and branches/1.10 (r25926)