Opened 14 years ago
Closed 5 years ago
#6689 closed defect (irreproducible)
Ways downloaded through "Download parent ways/relations" sometimes have some nodes not loaded
Reported by: | kolen | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | tested |
Keywords: | download, parent, ways, nodes, appearance | Cc: |
Description (last modified by )
JOSM version 4279
How to reproduce (hope that data in that area will not changed noticeably):
Start with no data layers.
- Download area:
lat 56.6444066 - 56.6451794
lon 47.8568101 - 47.8582
(Can be done using remote control http://127.0.0.1:8111/load_and_zoom?left=47.8568101&bottom=56.6444066&right=47.8582&top=56.6451794 )
- Select east-most node of road, where two links to roundabout join (node 637694461)
- Select "Download parent ways/relations" from menu (Ctrl+Alt+D)
- After way adjacent to that node (way 48522817) is downloaded, some nodes of it have strange appearance in josm view (styled view shows no line of way, just nodes, wireframe view shows lines to far outside (to infinity).
- When saving this dataset to .osm xml file (test2.osm) and opening again, it shows the same. However, coordinates of nodes in .osm file look correct, and it opens without errors, and 'status report' shows "Dataset consistency test: No problems found".
Just starting josm and opening (test2.osm) also causes this problem for me to appear.
Update: found that resulting xml does not have two of nodes: 1365747928 and 1365747989 referenced in way 48522817, these nodes are displayed as far away. Seems that they are not loaded by "Download parent ways/relations". But status report shows that data consistency test passes (it allows not loaded nodes of ways?).
Attachments (4)
Change History (11)
by , 14 years ago
Attachment: | josm-strange-points-in-ways-mode1.png added |
---|
by , 14 years ago
Dataset loaded when doing things described in how to reproduce
comment:1 by , 14 years ago
Description: | modified (diff) |
---|
comment:2 by , 14 years ago
Description: | modified (diff) |
---|
comment:3 by , 14 years ago
Summary: | Ways downloaded through "Download parent ways/relations" have strange appearance/behavior → Ways downloaded through "Download parent ways/relations" sometimes have some nodes not loaded |
---|
comment:4 by , 14 years ago
Recorded traffic, first josm gets /api/0.6/node/637694461/ways and it returns correct list of nodes in way. But then when doing /api/0.6/nodes josm skips some nodes:
http://api.openstreetmap.org/api/0.6/nodes?nodes=639251730,639251731,324379478,324163048,1365747926,416636331,705416990,413411505,323904576,649176539,613061428,413410370
It skips 1365747928 and 1365747989, other nodes of way 48522817 are downloaded.
And should "data consistency test" complain about ways containing not loaded nodes?
comment:6 by , 5 years ago
Description: | modified (diff) |
---|
I cannot reproduce the problem with the current tested version (r15629). I think this can be closed. This is what happens now:
2020-01-23 09:06:19.593 INFO: GET https://api.openstreetmap.org/api/0.6/node/637694461/ways -> HTTP_1 200 (659 B) 2020-01-23 09:06:19.603 INFO: Way 50163903 with 7 nodes is incomplete because at least one node was missing in the loaded data. 2020-01-23 09:06:19.603 INFO: Way 50163902 with 4 nodes is incomplete because at least one node was missing in the loaded data. 2020-01-23 09:06:19.603 INFO: Way 48522817 with 15 nodes is incomplete because at least one node was missing in the loaded data. 2020-01-23 09:06:19.693 INFO: GET https://api.openstreetmap.org/api/0.6/node/637694461/relations -> HTTP_1 200 (380 B) 2020-01-23 09:06:19.763 INFO: GET https://api.openstreetmap.org/api/0.6/way/50163903/full -> HTTP_1 200 2020-01-23 09:06:19.833 INFO: GET https://api.openstreetmap.org/api/0.6/way/50163902/full -> HTTP_1 200 2020-01-23 09:06:19.903 INFO: GET https://api.openstreetmap.org/api/0.6/way/48522817/full -> HTTP_1 200 2020-01-23 09:06:19.973 INFO: GET https://api.openstreetmap.org/api/0.6/nodes?nodes=1403393527,1406496787,1797449460,1403393537,1408477674,1403466219,1403393530,1403393529 -> HTTP_1 200
comment:7 by , 5 years ago
Resolution: | → irreproducible |
---|---|
Status: | new → closed |
Screenshot (wireframe view)