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.
I believe this is occurring as an older version of the segment had one end in the first area but had later been moved (when a node was added half way along)
I cant really see a decent resolution for this without splitting the two tables or making the SQL even more hideous though :(
The text was updated successfully, but these errors were encountered:
Reporter: dean[at]earlsoft.co.uk
[Submitted to the original trac issue database at 2.46pm, Friday, 23rd June 2006]
There appears to be a further problem related to the historic and current data being in the same table.
Given these two areas:
http://www.openstreetmap.org/api/0.3/map?bbox=-1.3070385371696702,50.90355331344044,-1.26940546283033,50.926855512193434
http://www.openstreetmap.org/api/0.3/map?bbox=-1.3038977738865059,50.9199261835053,-1.2662646995471656,50.94322018520521
The way 2241786 is different in each:
vs:
I believe this is occurring as an older version of the segment had one end in the first area but had later been moved (when a node was added half way along)
I cant really see a decent resolution for this without splitting the two tables or making the SQL even more hideous though :(
The text was updated successfully, but these errors were encountered: