Fix missing data after updating with Osm2Psql #221
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Europe import is now 4754 MB (from ~2800MB) |
|
GeoFabrik download server is unavailable, breaking CI because the OSM Berlin content is not cached anymore. |
|
#222 is a better solution |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #215
This solves part of the problem of missing track sections after updating data in the database.
Using filtered data, and touching the imported data in the Osm2Psql tables is still not supported nor correct by Osm2Psql. However without filtering the database would grow far too large to keep Europe imported and updatable for use on https://openrailwaymap.fly.dev.
Tested in Belgium with importing old OSM data, and then repeatedly updating it.
Before:
After:
