Simplifying coordinates attribute in the Geo Location object

[floydtree]

Today, our geolocation object contains a coordinates array which is intended to house lon, lat in decimal degrees. As one can imagine, order of the elements in this array would be very important to convey the geo coordinates accurately. There in lies the issue, since it is an array we cannot really prescribe what the order should be. Additionally, there is no single, universally followed convention, MaxMind, Google Maps both follow lat, lon however, GeoJson standard, that OCSF's description refers to, follows lon, lat standard. I think we are adding unnecessary ambiguity for producers, mappers and consumers of OCSF data.

The simple solution to alleviate this ambiguity is to introduce explicit attributes in the object. Two new attributes should be added to the geolocation object - lat, long and the existing coordinates array attribute should be deprecated. Happy to discuss further.

This was discussed amongst a few community members in Feb 8th, 2024 Mapping work-stream call.

[query-jeremy]

If we're adding to the geolocation object, we should consider an optional geohash property. Geohashes are information dense, searchable, and flexible in precision.

I can't represent a current need for them but they can be very useful for certain location informed analytics.