Open brycenesbitt opened 10 years ago
You can simply change your query to request OSM XML data (i.e. [out:xml];
or <osm-script output="xml" />
), than the export options raw data
and raw data from Overpass API
will give you the desired OSM XML. As that is only a matter of re-running a query (and implementing an on-the-fly conversion between JSON and XML output sounds cumbersome), this is a wontfix, I'm afraid.
In terms of capability, that's the right answer. In terms of usability and discover-ability, that's an unfortunate answer. Can't the GUI "do this" in the same way it fixes queries directed at JOSM that don't include "meta"?
OK, I think you have a point here. Reopening
Short remark:
I can assert that removing the first occurence of "[out:json]" from the query does the job. The only corner is an occurence in a comment.
When exporting the options I'm given now are:
Would it be possible to add an option to output as ".osm" files (e.g. OSM XML)?