NOC-ColinBell
commented
4 years ago Maybe discuss at a meeting as a lot here and people with have strong opinions. For example I always use lng for longitude (except in written documentation) but this is because as a developer, the word 'long' is a keyword in C/C++ so you can't have a variable called 'long'. Lets discuss at the end of Dave's GTM meeting if Lisa and Jill are there.
Theres a few different instances throughout the app where different notations are used to denote different pieces of information. If we want to come to an agreement on some of these to implment across the app?
Postion shorthand:
Referencing elevation values:
Referencing speed values:
Boundary Referencing:
Referncing Time Format
I feel that these should be ironed out early as users will associate the names given with the values they receive, and changing this after familiarity is established may confuse some users.