Prepare a bounded extract
The importer accepts standard Overpass JSON with an elements array, up to 5 MiB and 10,000 elements. Nodes require latitude and longitude; ways and relations require center coordinates. A response carrying an error remark is rejected because it can be incomplete.
Use a regional data source or a modest manual query appropriate to your need. This site does not send visitor searches to public Overpass instances. The published city extracts are static files, so a busy page does not repeat the same upstream query for every visitor.
Understand which records survive
The parser keeps explicit drinking-water or free-refill candidates and rejects explicit drinking_water=no. It removes inactive and explicitly private/no-access entries, validates coordinates and deduplicates OSM type/id pairs. Optional fee and bottle filters apply afterward.
A way or relation can describe an area instead of an exact tap. Its supplied center is marked approximate. Imported provenance and completeness are not independently verified, even if the file includes a source timestamp. Review the resulting coordinates before using them outside.
Move selected waypoints to another tool
Add up to twenty candidates and order them yourself. The GPX export uses waypoint records, not a route or track. Your navigation application may let you plan paths between them, but those paths are not part of this file and need their own review.
Keep the JSON record or full source extract alongside the GPX. It preserves the filters, dates, attribution and limitations that a map application might not display prominently. Offline files remain tied to their original snapshot and do not become current simply by reopening them.