add scenario to fix bug in GeoPackage exports in OSM Schema #5765
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
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.
there was a bug in Hoot's node export server that if a user requested an export for a GeoPackage in OSM Schema, the user would get an error about an invalid writer.
I found the bug was caused because the export command wasn't appending the translation script option. I added a new scenario check that if the schema is OSM and format is GeoPackage to add all necessary params to the command
I have this deployed in testing if you want to test:
https://testing.vgihub.geointservices.io/export#map=17/38.81165/-77.62058