Looking at some changesets I find odd information regarding coordinates and objects version. For instance, in changeset 420453 one can find ...
Does anybody can provide me with some historical context/explanation how such data appeared in the database? Is it still possible it happens again? Cheers! asked 10 Nov '14, 19:28 jfd553 |
All the comments make sense... I missed the point about multiple versions of an object in a changeset - It's certainly possible! Concerning the erroneous coordinate, I'm happy it is not possible anymore! Thanks answered 15 Nov '14, 03:50 jfd553 |
For the curious: It isn't possible to upload a node with this longitude any longer. The server responds with error 400 and "The node is outside this world".
Regarding your observation in list member two: "One element can be updated multiple times during one changeset and its version number is increased each time so there can be multiple history versions of a single element for one changeset." (API 0.6). So this is nothing unexpected.
The linked changeset was created at the time when API 0.5 was active. Maybe the coordinates were not enforced to be in the range [-180 -90, 180 90] at this time.
Possibly, although the API changes between v0.5 and v0.6 don't mention the introduction of such checks.