Let's say the user, to save valuable battery, just makes waypoints every time he is in front of a statue.
There is no reason for him to make loads and loads of trackpoints for an area where the roads are very simple and able to be seen from a satellite image.
He merely just wants to make a lot of waypoints, however for no good reason he must have some track points also for his waypoints to be recognized as a valid GPX file. Jidanni (talk) 11:26, 21 October 2019 (UTC)
Bounds metadata ignored
The OpenStreetMap GPX file import function ignores <bounds></bounds> and <bounds ... /> tags entirely. Moreover, it has the ability to calculate latitude and longitude minima and maxima while parsing trace data, effectively discovering the bounds coordinates on its own, but it doesn't do that either. When one opens a trace under My GPS Traces with the Edit Map link, the lower left extreme point of the trace or family of traces appears in the center of the map window at some arbitrary scaling factor that has most of the trace(s) trailing off-screen and requiring the user to fiddle with zooming and panning every time a new trace is uploaded. This feature in OpenStreetMap is obviously broken and needs to be fixed. — User8192T @ 00:30, 21 September 2022 (UTC)