Add support to support input coordinates in AVD for locations in pathfinder solution

[mansihanda]

Enhancement summary

The user can not input coordinates in AVD. Only the "address" which will be resolved to coordinates by CV.

This requirement is coming from the limitation that Mapbox API is running on onprem but you would have to get a mapbox token and add it to CV but there is no first class support for this yet on prem ,

We don't claim support for geographical view on onprem because there is no straightforward way currently to supply the mapbox token.

latitude and longitude for locations for sites on topology page provisioned via AVD is all 0 ,0.

https://venom.sjc.aristanetworks.com/cv/topology?studio=studio-avd-pathfinder-metadata&fromOffset=58424549&buildId=d97f044b-68e8-4913-848e-a71da5b06fbb&ws=9f1b9518-466e-46ab-a9e1-ec924ef46bfb&activeFilters=%5B%22deviceType%22%5D&activeNode=e93ce95&geoMode=true

https://venom.sjc.aristanetworks.com/cv/settings/aeris-browser?studio=studio-avd-pathfinder-metadata&fromOffset=58424549&buildId=d97f044b-68e8-4913-848e-a71da5b06fbb&ws=9f1b9518-466e-46ab-a9e1-ec924ef46bfb&datasetId=cvp&path=xx8Ak8QIbG9jYXRpb27ECmFzc2lnbm1lbnTEBmNvbmZpZw%3D%3D

Mapbox API is running on onprem but you would have to get a mapbox token and add it to CV but there is no first class support for this yet.

We don't claim support for geographical view on onprem because there is no straightforward way currently to supply the mapbox token.

Which component of AVD is impacted

eos_designs

Use case example

Mapbox API is running on onprem but you would have to get a mapbox token and add it to CV but there is no first class support for this yet.
We don't claim support for geographical view on onprem because there is no straightforward way currently to supply the mapbox token.
We need to prioritise coordinates to be inputed via AVD directly , two of our on-prem customers are planning to use AVD for provisioning.

Describe the solution you would like

The user can not input coordinates in AVD. Only the "address" which will be resolved to coordinates by CV.

To support coordinates we would also need input fields in the metadata studio.

Describe alternatives you have considered

No response

Additional context

No response

Contributing Guide

• I agree to follow this project's Code of Conduct