Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

api/0.3/map and api/0.3/way return different results #214

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments
Closed

api/0.3/map and api/0.3/way return different results #214

openstreetmap-trac opened this issue Jul 23, 2021 · 5 comments
Assignees
@openstreetmap-trac
Labels
Component: api Priority: blocker Resolution: fixed Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: ge[at]gabrielebner.at
[Submitted to the original trac issue database at 7.52pm, Monday, 8th May 2006]

Way 275733 is missing segment 350430 just when requesting http://www.openstreetmap.org/api/0.3/map?bbox=16.21,48.2,16.23,48.21

However if I request http://www.openstreetmap.org/api/0.3/way/275733 it's there...

--- a1-map.osm  2006-05-08 22:02:53.000000000 +0200
+++ a1-way.osm  2006-05-08 22:02:44.000000000 +0200
@@ -1,4 +1,5 @
   <way id="275733" timestamp="2006-05-08 20:38:51">
+    <seg id="1389817"/>
     <seg id="1390236"/>
     <seg id="1390324"/>
     <seg id="1390500"/>
@@ -86,6 +87,9 @
     <seg id="1659610"/>
     <seg id="1659612"/>
     <seg id="1834145"/>
+    <seg id="1981146"/>
+    <seg id="350430"/>
+    <seg id="350434"/>
     <seg id="351777"/>
     <seg id="351778"/>
     <seg id="351779"/>
@@ -133,6 +137,8 @
     <seg id="351994"/>
     <seg id="351995"/>
     <seg id="351996"/>
+    <seg id="466126"/>
+    <seg id="466127"/>
     <tag k="oneway" v="yes"/>
     <tag k="highway" v="motorway"/>
     <tag k="name" v="A1"/>
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: dean[at]earlsoft.co.uk
[Added to the original trac issue at 4.12pm, Friday, 19th May 2006]

This also happens with way 485136 (M27 eastbound).

http://www.openstreetmap.org/api/0.3/way/485136 shows the correct 199 items but that way listing in http://www.openstreetmap.org/api/0.3/map?bbox=-1.35,50.86,-1.24,50.97 misses about a quarter and has the remaining ones in the wrong order.

@openstreetmap-trac
Copy link
Author

Author: immanuel.scholz[at]gmx.de
[Added to the original trac issue at 9.48am, Friday, 2nd June 2006]

OMFG!

@openstreetmap-trac
Copy link
Author

Author: steve[at]fractalus.com
[Added to the original trac issue at 2.54pm, Sunday, 9th July 2006]

fixed with new way code and SET GLOBAL group_concat_max_len = 1048576; on the server

@openstreetmap-trac
Copy link
Author

Author: immanuel.scholz[at]gmx.de
[Added to the original trac issue at 12.40pm, Friday, 21st July 2006]

the problem seems to still exist. look #255

@openstreetmap-trac
Copy link
Author

Author: dean[at]earlsoft.co.uk
[Added to the original trac issue at 11.03am, Friday, 11th August 2006]

Copied from my email to the dev list:

Is it just me or is something very similar to bug 214 back again?
My local Motorway has huge chunks missing...
Strangely, these are also missing from the individual way request but were in exactly the same place as the results of 214.

The two ways in question are:
http://www.openstreetmap.org/api/0.3/way/485136
http://www.openstreetmap.org/api/0.3/way/485137

Additionally, the timestamp is from roughly whan I last changed it and it has been correct between than and now.

This was referenced Jul 23, 2021
Closed
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: api Priority: blocker Resolution: fixed Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac