[CONSIDER] Should CMS be source of truth for facility map thumbnails

[swirtSJW]

User Story or Problem Statement

Currently for VAMC and Vet Center CMS based pages, there is a map thumbnail that is generated from a lookup of lat lon via Facility API (via VetsAPI). THe makes the Facility API the source of truth. The problem is that Facility API being the source of truth makes VAST the source of truth and sometimes VAST is delayed. (related slack thread) This sometimes creates a situation where Veterans are show a map that is not an accurate depiction of where the facility is.

The CMS contains the lat lon fields as well (also sourced from the Facility API) but there is a the allowance that if a lat lon was truly wrong and needed to be changed, we could overide it in the CMS until such time that VAST caught up. If we used the CMS facility data to pass the lat lon to mapbox we could make the change neccesary to provide Veterans with a more timely/accurate representation of where a facility is.

Risks

1. Facility Locator and CMS could disagree about the location shown. Facility locator would still show the wrong location and the CMS page would show the correct location.
2. CMS altered data could be overwitten in the CMS if something else about the facility changed in the Facility API (phone number, status, name...) Which would cause the CMS to go back to showing the incorrect VAST location for the facility.

Description or Additional Context

Steps for Implementation

Acceptance Criteria

• [ ] Change content build to use the lat lon for a facility source from the CMS rather than the Facility API.

Team

Please check the team(s) that will do this work.

• [ ] CMS Team
• [ ] Public Websites
• [x] Facilities
• [ ] Accelerated Publishing

[swirtSJW]

This is not an urgent or even a must do. Just something to ponder if the benefit is worth it for the few times we might need it.

[Agile6MSkinner]

@davidmpickett @mmiddaugh This came up in planning today. Do we want to make a call on it?