Some nitpicks about exported GPX

When looking at the GPX output from c:geo for a single cache, I found a few things which may be there for a reason I don’t know.

• the <gpx> tag contains a string xmlns:cgeo="http://www.cgeo.org/wptext/1/0" that cannot be resolved; I’d expect a XML parser to complain about this
• cache attributes do not use the same strings as GS do (e.g. “Available at all times” vs “Available 24/7”)
• log IDs: higher IDs correspond to older entries due to incrementing “down the list”, while GS hands out higher IDs for newer entries - this has only been partially handled in issue #4023
• cache placement and log dates use “midnight UTC” for the (unknown by design) time; GSAK seems to use 8 a.m. UTC - this may possily result in different dates when corrected to user time zone (for example, when using GCstatistic)

[rsudev]

The first item is not a problem. The uri denoting the namespace is not necessarily an existing web resource. It just uniquely identifies an xml namespace we use to place some extra information specific for c:geo. Regarding the attribute, there might be a change at GS we missed or it is possibly a crossover from the opencaching attrbute naming, not sure. Regarding the last point, I don’t think that we really stand a chance of sensible results if the (essentially timeless) log dates are converted to an arbitrary timezone as date-time (8 a.m. will not save you in Australia) and assigning midnight as a time value is IMO the most conventional way to display that the time doesn’t count.

[pstorch]

The xml namespace URI is just a name. It is not mandatory that there is a downloadable xsd document at that address.

From https://www.w3schools.com/xml/xml_namespaces.asp:

Note: The namespace URI is not used by the parser to look up information.

The purpose of using an URI is to give the namespace a unique name.

However, companies often use the namespace as a pointer to a web page containing namespace information.