Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPIKE: Understand Data Journey to Google Maps #20080

Open
9 tasks
Agile6MSkinner opened this issue Dec 11, 2024 · 1 comment
Open
9 tasks

SPIKE: Understand Data Journey to Google Maps #20080

Agile6MSkinner opened this issue Dec 11, 2024 · 1 comment
Assignees
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Facility Locator product owned by Facilities team Regional office CMS managed VBA product owned by the Facilities team sitewide SPIKE VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team

Comments

@Agile6MSkinner
Copy link

Agile6MSkinner commented Dec 11, 2024

Description

We would like to understand how an address gets from it's source of record to displaying in Google Map. In this spike we will need to investigate all avenues that lead to google maps so that we can better troubleshoot issues and potentially design better systems.

In short: How does data get from source to GMaps URL. How to we transform along the way. Makes sense to organize by facility type.

Associated Issues

#12072
#19379

Existing Resources


Facility type Source
VA health (VAMCs, CBOCs, etc) VAST -> VSSC -> BISL - > CDW -> Lighthouse
Vet Centers and Outstations VAST -> VSSC -> BISL - > CDW -> Lighthouse
Vet Center CAPs Editor created in Drupal - no presence in VAST
VBA (Region offices, Satellites and other benefit location types) Sandy's DB - > CDW -> Lighthouse
NCA - national cemeteries name and website from NCA XML - all other data from CDW XML file
NCA - state cemeteries NCA XML file

Other relevant processes

  • new stations in VAST get a preliminary lat/long but the official geocoded attributes come from GSSC on monthly basis
  • Lighthouse does daily validation on (mailing) address (using "VA address validator")

Acceptance Criteria

  • List sources of address data for each facility type.
  • Find any intermediary steps/platforms/systems that are involved
  • Describe how that data is transformed into "Get Directions on Google Maps" link in Facility Locator search results (All listed in dropdown)
  • Describe how that data is transformed into "Get Directions on Google Maps" link in modernized facility sites
    • And any subpages, etc
  • Describe how that data is transformed into "Get Directions on Google Maps" link in facility detail page (FL-generated)
  • Event listing pages
  • Include explanation of URL parameters that are used
  • Create visual diagram artifact
@Agile6MSkinner Agile6MSkinner added Needs refining Issue status sitewide Facilities Facilities products (VAMC, Vet Center, etc) labels Dec 11, 2024
@randimays randimays added Facilities Facilities products (VAMC, Vet Center, etc) and removed Facilities Facilities products (VAMC, Vet Center, etc) labels Dec 11, 2024
@Agile6MSkinner Agile6MSkinner changed the title Special Characters in Google Maps URLs "saddr" is passed as "undefined" in Google Maps URLs Dec 11, 2024
@Agile6MSkinner Agile6MSkinner changed the title "saddr" is passed as "undefined" in Google Maps URLs SPIKE: "saddr" is passed as "undefined" in Google Maps URLs Jan 28, 2025
@Agile6MSkinner Agile6MSkinner changed the title SPIKE: "saddr" is passed as "undefined" in Google Maps URLs SPIKE: Understand Data Journey to Google Maps Jan 28, 2025
@Agile6MSkinner Agile6MSkinner added SPIKE and removed Needs refining Issue status labels Jan 29, 2025
@jilladams jilladams added VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Regional office CMS managed VBA product owned by the Facilities team Vet Center CMS managed product owned by Facilities team Facility Locator product owned by Facilities team labels Feb 4, 2025
@jilladams
Copy link
Contributor

From 23 planning: we are also looking into Mapbox static image calls and whether that will affect scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc) Facility Locator product owned by Facilities team Regional office CMS managed VBA product owned by the Facilities team sitewide SPIKE VA.gov frontend CMS team practice area VAMC CMS managed product owned by Facilities team Vet Center CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

3 participants