Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make XML Response deserializable with OsmSharp #533

Closed
blackboxlogic opened this issue Jul 26, 2019 · 2 comments
Closed

Make XML Response deserializable with OsmSharp #533

blackboxlogic opened this issue Jul 26, 2019 · 2 comments

Comments

@blackboxlogic
Copy link

blackboxlogic commented Jul 26, 2019

OsmSharp can't parse XML responses from Overpass-API because of the "note", "meta" or any other XmlElements which are not part of the OsmApi's XML format.

Could there be (or is there already) a feature to either

  • Omit non-conformant XML elements from the XML response, or
  • Move non-conformant elements to be the last XML Elements within the "osm" XmlElement.

Related: OsmSharp/core#76

@blackboxlogic blackboxlogic changed the title Make response deserializable with OsmSharp Make XML Response deserializable with OsmSharp Jul 26, 2019
@mmd-osm
Copy link
Contributor

mmd-osm commented Jul 26, 2019

As of now, there's no option to remove those extra tags. At least for the copyright notice, I doubt that this kind of information could be easily dropped without further discussion.

Let’s see if this could be possibly fixed in OsmSharp, as this turns out to be the only tool affected by this issue. By the way, those extra tags are documented here: http://overpass-api.de/output_formats.html

@blackboxlogic
Copy link
Author

Yep, looks like I solve this by changing how I use osmSharp or my making a pull request there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants