Re: [OSM-dev] Malformed API results
On 2020-01-04 21:38, Mike Parfitt wrote: > What does curl and wget return for you ? Here's the result I got when running: curl https://api.openstreetmap.org/api/0.6/user/gpx_files -u "some_osm_user_name" http://www.openstreetmap.org/copyright; license="http://opendatacommons.org/licenses/odbl/1-0/;> ... ... ... ... You need to replace the user name with your own here, and provide a password when curl asks you to. The result is an XML document with a number of gpx_file elements. Note that I replaced some of the field contents with dummy values above. -- ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Malformed API results
Hi, thanks for the reply. On my android tablet :- . . the following browsers exhibit the same problem :- . . . . Chrome . . . . Opera . . . . Samsung's basic offering . . so does the http shortcuts app I am not an Android/Linux command line user. I did install a command line app and executed the curl command prepared by the http shortcuts app, but all I got was "not found". The same stream of description tags values precedes the desired xml on a Windows 10 Home PC using the Edge and Chrome browsers. My conclusion is that it isn't a browser artifact. Have you uploaded any gpx files ? What does curl and wget return for you ? From: mmd Sent: 04 January 2020 11:31:15 To: dev@openstreetmap.org Subject: Re: [OSM-dev] Malformed API results On 2019-12-13 19:09, Mike Parfitt wrote: > The https://api.openstreetmap.org/api/0.6/user/gpx_files call returns a > long stream of tag values before the xml that it is > supposed to return. That's most likely a browser artifact and has nothing to do with the actual data returned by the API. Try curl or wget instead and inspect the resulting XML file in a text editor. -- ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Malformed API results
On 2019-12-13 19:09, Mike Parfitt wrote: > The https://api.openstreetmap.org/api/0.6/user/gpx_files call returns a > long stream of tag values before the xml that it is > supposed to return. That's most likely a browser artifact and has nothing to do with the actual data returned by the API. Try curl or wget instead and inspect the resulting XML file in a text editor. -- ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Malformed API results
The https://api.openstreetmap.org/api/0.6/user/gpx_files call returns a long stream of tag values before the xml that it is supposed to return. See below for an extract :- by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle Exploring roads by vehicle This XML file does not appear to have any style information associated with it. The document tree is shown below. http://www.openstreetmap.org/copyright; license="http://opendatacommons.org/licenses/odbl/1-0/;> Exploring roads by vehicle ... Exploring roads by vehicle ... Exploring roads by vehicle ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
