"Coordinates" property

[joshreisner]

I think we should add support for a new field called coordinates that could be used instead of latitude, longitude, and approximate.

When the location is a point, such as an address or intersection, coordinates would be the latitude and longitude concatenated as a string (latitude goes first):

  'coordinates': '37.33296,-121.90200',

When the location is approximate, such as a city, coordinates would be the concatenated latitudes and longitudes of the northeast and southwest coordinates, eg this response from Google:

  [formatted_address] => San Jose, CA, USA
  [geometry] => Array
    (
      [bounds] => Array
        (
          [northeast] => Array
            (
              [lat] => 37.4692304
              [lng] => -121.589154
            )
          [southwest] => Array
            (
              [lat] => 37.124493
              [lng] => -122.0456719
            )
          )

would become:

  'coordinates': '37.46923,-121.58915,37.12449,-122.04567',

the advantages of this scheme are that it's more concise (replaces three fields with one) while adding more information (it now conveys the boundary).

having the boundary could be useful in cases where we want to show an area (like still displaying a map on an online meeting listing) or tracking other info (such as a service entity)

[FlipperPA]

I love it. I suspect this is for virtual-only meetings that still want to be part of an intergroup, and it would certainly work great for us in that capacity.