This repository was archived by the owner on May 5, 2022. It is now read-only.
When processing GML, allow .xml file ending #523
Conversation
This file contains hidden or 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
Member
|
I think there might be some .xml data hanging out in one of the Japanese tests. |
Member
|
Hey Ian, any further thoughts on getting this completed? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In openaddresses/openaddresses#1898 we're trying to download a GML dump from a WFS server. The server responds with a
Content-Type: text/xmlheader, so the cacher saves the file with a.xmlsuffix, but the subsequent steps only look for.gmlwhen processing a source withtype: xmlset.This change makes it so we look for
.xmlAND.gml.