geotagging

Should we even have this? And if so, what standards are we using.

• If we are using latitude/longitude, use decimal if possible, instead of degree/minute/second.
  • For future reference https://en.wikipedia.org/wiki/ISO_6709
• If we are using some type of code like Geohash https://en.wikipedia.org/wiki/Geohash
• The code would have to scale well from large areas to places as small as 1 meter.
• These are in consideration:
  • http://www.makaney.net/mkc_standard.html
  • https://en.wikipedia.org/wiki/Military_Grid_Reference_System
  • https://en.wikipedia.org/wiki/Postal_addresses_in_the_Republic_of_Ireland#OpenPostcode

Please do not chose:

• irregular scaling like https://en.wikipedia.org/wiki/Maidenhead_Locator_System
  • Also https://en.wikipedia.org/wiki/World_Geographic_Reference_System
  • Also https://en.wikipedia.org/wiki/C-squares
  • Also https://en.wikipedia.org/wiki/Global_Area_Reference_System
• irregular grid division (e.g. 4x5) schemes like https://plus.codes/
• irregular grid shapes like https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system
  • UTM also uses https://en.wikipedia.org/wiki/Universal_polar_stereographic_coordinate_system
  • Also https://en.wikipedia.org/wiki/Quadrilateralized_spherical_cube
    • http://www.sai.msu.su/~megera/wiki/SphereCube and http://s2geometry.io/
• proprietary english naming schemes https://what3words.com/
  • Also https://en.wikipedia.org/wiki/Natural_Area_Code
• overly large divisions like https://en.wikipedia.org/wiki/Marsden_square
  • Also https://en.wikipedia.org/wiki/World_Meteorological_Organization_squares
• Hierarchical Triangular Mesh or Quaternary Triangular Mesh
  • from https://github.com/om-henners/geogrids and http://www.what3fucks.com/
  • Side note: 45 bits for 4.78m accuracy, 47 bits for 2.39m, 49 bits for 1.19m
• text formats that contains a lot of spaces
  • https://en.wikipedia.org/wiki/LOC_record
• Low entropy formats like https://en.wikipedia.org/wiki/QDGC