Mapping AWS Location Service Places v2 results to GERS IDs (Roadmap / Bridge Files?)

[honeybadger93]

Hi folks,

I’m exploring ways to connect the search/autocomplete functionality to Overture data so I can leverage GERS IDs for conflation and downstream data joins.

I'm currently using AWS Location Service Places v2 (geo-places) for search. The API works great, but it returns a proprietary, temporary AWS PlaceId and abstracts away the underlying data providers. If another search API is available that can bridge to GERS IDs, I'd be open to switching.

Because AWS doesn't expose the source IDs (like OSM Node IDs or Meta Page IDs), I can't currently use the Overture Bridge files to map my search results to GERS IDs. This forces me into a custom conflation workflow (taking the lat/lng and name from AWS, doing a radius search against Overture data, fuzzy-matching the results, maybe throwing a Bedrock call on top of it to help, etc..).

Given that AWS is a founding member of Overture, I have a few questions about the roadmap:

1. Direct Integration: Are there any plans or ongoing discussions with AWS to natively return GERS IDs directly in the AWS Location Service Places v2 API responses?
2. Bridge Files: Is it technically feasible (or on the roadmap) for Overture to publish a Bridge file mapping AWS PlaceIds to GERS IDs, similar to what exists for Meta or Esri? (I assume this is tricky since AWS blends multiple closed commercial providers).
3. Best Practices: In the meantime, for developers using managed search APIs like AWS or Google Places, is spatial radius + fuzzy name matching the officially recommended approach for conflating search results to GERS?

Thanks for any guidance