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

osm2pgsql produces different output in non slim mode between -l and -m #4553

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

osm2pgsql produces different output in non slim mode between -l and -m #4553

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

Comments

@openstreetmap-trac
Copy link

Reporter: amm
[Submitted to the original trac issue database at 2.58pm, Tuesday, 4th September 2012]

Caught by the regression tests, it appears that "osm2pgsql -l" and "osm2pgsql" produced different outputs (different number of entries in the planet_line and planet_roads table).

I haven't investigated any further yet to see what is causing this issue. I have also not yet checked to see if only these two options are effected, or if it is more wide spread. Currently I am putting this bug report in as a reminder.
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: pnorman
[Added to the original trac issue at 10.41am, Tuesday, 3rd January 2017]

Geometry validity can differ depending on projection and floating point issues, and all cases I've seen of this boil down to that.

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

@openstreetmap-trac openstreetmap-trac

Labels
Component: osm2pgsql Priority: minor Resolution: fixed Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac