search

PoseiDAT / schemas

The core schemas for the PoseiDAT data interchange formats
MIT License
1 stars 5 forks source link

further lat lon specs #2

Closed Friskfisk closed 3 years ago

Friskfisk commented 4 years ago

questions about specifying the lat lons +/- 180 E W rather than 0-360 and decimal degree

Qwerios commented 4 years ago

There are various ways to store geospatial data and I do have a technical reason specifically for positions to store them as 2 decimal values (lat/lon).

The reason is that we've seen people input degree characters from evil unicode sets. Also N/E/S/W variants with casing issues. Ultimately a numerical value with only a dot (.) is a transport safe way of declaring the position. It is also very efficient for database storage and indexing.

Front-end applications can present positions as needed and convert as long as we're all using the same input format.

The heading and velocity were an after thought and if a more current value type should be used I'm all ears

Qwerios commented 3 years ago

@Friskfisk could you please update or close this issue? We've recently updated the position schema:

https://github.com/PoseiDAT/schemas/blob/master/src/schema/core/measurement/position.json

Please let us know if you still have suggestions

Qwerios commented 3 years ago

Closing this due to inactivity