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

osm2pgsql in slim mode fails to handle out-of-sequence nodes #1058

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

osm2pgsql in slim mode fails to handle out-of-sequence nodes #1058

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: utils Priority: major Resolution: fixed Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: jburgess[at]uklinux.net
[Submitted to the original trac issue database at 11.18pm, Tuesday, 22nd July 2008]

The current slim mode code in osm2pgsql assumes that the nodes will be seen in ascending order. This is often not the case, e.g. files saved by Josm. This makes it much harder to test the operation of slim mode on a small subset of downloaded data.
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: jonb
[Added to the original trac issue at 12.31am, Wednesday, 23rd July 2008]

(In [9251]) osm2pgsql: reduce frequency of out-of-order node warning. Turns out this just effects the cache efficiency not the operation of the overall processing. This is fine for small files like the ones from Josm. Closes #1058

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: utils Priority: major Resolution: fixed Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac