Add a Plus Code field as an alternative to the longitude, latitude fields

[MediumBrownToast]

As ...

Nelly - Network Engineer

I want ...

Add support for Google Plus Code fields in objects that record longitude and latitude information. e.g. Locations (I'm not sure if there are others).
https://maps.google.com/pluscodes/

So that ...

When I'm adding location info, I'm currently going to Google Maps to find the place and then placing a pin next to that place which then shows the lat long in minutes (not compatible with the Nautobot lat long field). To get around that, I copy the lat long (in decimal) from the address bar (example link below) and paste it into Nautobot but I often need to shorten the lat/long value by a few digits because Nautobot rejects the length. Plus codes makes it easier to copy and paste the info into Nautobot (there's a "Copy" icon in maps).

https://www.google.com/maps/place/29%C2%B040'36.3%22S+111%C2%B020'40.1%22E/@-29.6767353,111.3418951,17z

I know this is done when...

-I can create/edit a Location object and instead of recording lat/long values, I can record a Plus Code.

-When the Plus Code is recorded and I view the Location object, I can click the "Map It" icon and the correct location opens in Google Maps.

-Bonus points: lat/long values can be converted to Plus Codes so existing Location objects with lat/long values could have a Plus Code field automatically populated.

Optional - Feature groups this request pertains to.

• Automation
• Circuits
• DCIM
• IPAM
• Misc (including Data Sources)
• Organization
• Apps (and other Extensibility)
• Security (Secrets, etc)
• Image Management
• UI/UX
• Documentation
• Other (not directly a platform feature)

Database Changes

Additional fields on existing models?

External Dependencies

Not sure what exactly but it looks like there are libraries in multiple languages https://github.com/google/open-location-code

[glennmatthews]

Seems like an interesting idea to me. We should also consider increasing the number of decimal places supported in the lat/long fields to make the above workflow easier - IIRC the current limits were chosen because they provide sufficient resolution to locate something down to the nearest meter as it is, but there shouldn't be any harm in allowing arbitrarily more precise values.