1. If you like. The different versions are not that different. Normaly Normally you loose lose more presission precision in the quantification of the coordinates then by using the wrong version of the datum. (And way more by using inaccurate messuring measuring devices like a GPS.) 2. The API does not have an option of specifying a datum and any coordinates will be interpreted as WGS84. If a user uploads in the wrong datum it will not be converted. This is normaly normally not a problem since any format the API supports (GPX, OSM) uses WGS84 and the error will therefore be in the converters. 3. The database stores GPX traces sepperatly separately from vector data and all conversion betwean between them is done by hand. The traces are a guide to the user when entering vector data and there are no automatic computasion computation of vector data from the traces.

1. If you like. The different versions are not that different. Normaly you loose more presission in the quantification of the coordinates then by using the wrong version of the datum. (And way more by using inaccurate messuring devices like a GPS.) 2. The API does not have an option of specifying a datum and any coordinates will be interpreted as WGS84. If a user uploads in the wrong datum it will not be converted. This is normaly not a problem since any format the API supports (GPX, OSM) uses WGS84 and the error will therefore be in the converters. 3. The database stores GPX traces sepperatly from vector data and all conversion betwean them is done by hand. The traces are a guide to the user when entering vector data and there are no automatic computasion of vector data from the traces.