Open swirtSJW opened 2 years ago
On running the bulk save for these, there are 8 CAPS with addresses that are failing geocoding
Unable to geocode 'Barrio Santa Rosa, Km 1.7 LAJAS, PR 00667 US'.
Unable to geocode 'Carretera 704, Km. 1.6 Interior Barrio Cuyón COAMO, PR 00769 US'.
Unable to geocode 'Callejon Los Fas Casa 9 CABO ROJO, PR 00623 US'.
Unable to geocode 'Urb. Villa del Rosario 6 Street A VEGA BAJA, PR 00693 US'.
Unable to geocode '1 Herrera St. UTUADO, PR 00641 US'.
Unable to geocode 'Pr-3, Kilometers 54.9, Lot 3 Pueblo Ward CEIBA , PR 00735 US'.
Unable to geocode '1000 Recreational Drive MINDEN, LA 71055 US'.
Unable to geocode 'Bldg. 312 on 9th Street DUBLIN, CA 94568 US'.
User Story or Problem Statement
As a Vet Center CAP editor, If I add an address that does not geocode, I see a notification But I am helpless to do anything about it, and the lat lon fields remain empty (not able to push to Facility API)
As a Vet Center CAP editor, If I change the address from a "good" address to an address that can not be geocoded, the old lat lon remains in the system so the cms will push the right address but the wrong lat lon to the Facility API, AND I do not know it is happening, AND I am helpless to do anything about it.
Possibile solutions to explore
A) In the event of geocode failure, blank out the lat lon values so we are not pushing incorrect values to Lighthouse. B) In the event of gecode failure, prevent node save??? Given the order of operations, this might not be possible. C) Reveal to editors the map on node View so they can at least see that something is wonky and raise it with cms support. D) compare the address as input by the editor to a database of known, geolocatabale addresses, and offer it as an alternative.
This was uncovered as an issue in https://github.com/department-of-veterans-affairs/va.gov-cms/pull/9584#pullrequestreview-1023467359
Acceptance Criteria
Implementation steps