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
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: stuuf [Submitted to the original trac issue database at 5.18pm, Wednesday, 22nd April 2009]
This is a rather large problem with some annoying rendering implications that I noticed many months ago, and since it's apparently been overlooked in the recent database/api upgrade I figured I'd report it here.
When downloading map data within a bounding box, the algorithm used seems to be something like this:
select all nodes within the box
select all ways that contain nodes from 1
select any additional nodes contained by ways in 2
If you know enough about geometry, you should realize that this does NOT include the complete definition of a line segment intersecting a bounding box. Consider this situation:
The line segment obviously crosses through the box, but since neither of its endpoints (*) fall within the box the API won't select it.
Mapnik seems to use PostGIS's geometry operators to search so I don't think it's affected by this, but Osmarender will often miss ways that cross through tiles but don't have any nodes in that tile. Ways like US county lines, which usually have very long straight segments that cover many tiles, only get rendered on the corners, with spaces in between.
I've confirmed this problem still exists in api 0.6 using JOSM
The text was updated successfully, but these errors were encountered:
Reporter: stuuf
[Submitted to the original trac issue database at 5.18pm, Wednesday, 22nd April 2009]
This is a rather large problem with some annoying rendering implications that I noticed many months ago, and since it's apparently been overlooked in the recent database/api upgrade I figured I'd report it here.
When downloading map data within a bounding box, the algorithm used seems to be something like this:
If you know enough about geometry, you should realize that this does NOT include the complete definition of a line segment intersecting a bounding box. Consider this situation:
The line segment obviously crosses through the box, but since neither of its endpoints (*) fall within the box the API won't select it.
Mapnik seems to use PostGIS's geometry operators to search so I don't think it's affected by this, but Osmarender will often miss ways that cross through tiles but don't have any nodes in that tile. Ways like US county lines, which usually have very long straight segments that cover many tiles, only get rendered on the corners, with spaces in between.
I've confirmed this problem still exists in api 0.6 using JOSM
The text was updated successfully, but these errors were encountered: