-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Low zoom (NE) roads missing segments #204
Comments
zerebubuth
added a commit
to tilezen/TileStache
that referenced
this issue
Sep 16, 2015
Previously, the comparison had been on Python type. This seemed to work most of the time, but there were some odd instances of things claiming to be of `MultiLineString` type, but where `isinstance(obj, BaseMultipartGeometry)` was `False`. I have a feeling it might be something `ctypes` related. It turns out that Shapely doesn't expose the geometry type ID, so we still have to do a stringly comparison, but I've tried to make it as simple as possible and do it only once. This is the base cause of tilezen/vector-datasource#204: Objects were returned from the intercut algorithm which were MultiLineStrings, but which were not being detected as such in the `isinstance` test. This led to some road segments being dropped from the tile.
After tilezen/TileStache#52: |
@nvkelso looks good? |
Yes, looks good. I see a few gaps in the road network, but those were there before and look to be a Natural Earth road bug: nvkelso/natural-earth-vector#147 |
Fixed in tilezen/TileStache#52. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've regressed the low zoom roads:
Probably related:
We've ignored the issue for now by turning off updates on zooms 0-8.
The text was updated successfully, but these errors were encountered: