render_map_tool: click a place to ask the model about it #284

Activity

1. mattpodwysocki

   added

   enhancementNew feature or requestNew feature or request

   on Oct 16, 2026
2. mattpodwysocki commented on Oct 19, 2026

   

   mattpodwysocki

   on Oct 19, 2026

   ContributorAuthor

   More actions

   How to do the "basemap POI" part: feature querying in GL JS.

   • Use Standard featuresets. We're on Standard, so use map.addInteraction with the built-in poi, buildings and place-labels featuresets instead of raw queryRenderedFeatures against layer ids, which change between style versions. A click on any café gives its name, class and coordinates. Check whether the POI carries an id place_details_tool accepts. If it doesn't, fall back to a search by name and coordinates.
   • Hover highlight. Featuresets support feature state, so hovering a POI or building can highlight it. That shows people the map is clickable.
   • Report a problem. The same click can pre-fill a feedback report (feedback_tool: submit map/route feedback via the Feedback API #290).

   Optional extras that use the same mechanism:

   • Traffic popup. Clicking a traffic line shows the congestion level and road name (follow-up to render_map_tool: live traffic overlay and in-map Satellite/Traffic toggles #277 / feat(render_map_tool): live traffic and Satellite/Traffic buttons on the map #278).
   • What's in view. Query the rendered POIs or roads in the viewport and send a short summary as model context (render_map_tool: tell the model what the user did on the map #287), e.g. "map shows downtown Oakland, 14 cafés visible". Keep it small: counts and a few names, never geometry.

   Feature querying only sees what's rendered. For questions about places off screen or not loaded, tilequery (#289) is the server-side option.