poi-search

Find a POI of a category at a place

The user wants to locate places of a given category — a restaurant, a hotel, a charger, … — at some location, or along their route. You resolve the location, search POIs of that category, and present the candidates for the user to choose from. Sometimes the category is left open; sometimes the category-search parameter is missing. The same method handles all of these. This skill finds POIs only; dialing one is the place-phone-call skill.

When this applies

"Find me a restaurant in ", "is there a at my destination?", "find somewhere to eat at my next stop", "find somewhere to eat where I'm headed", "look up nearby", "find a along my route around km." The place may be a named city, or described relative to the active route ("at my destination", "at my next stop"); the category may be named or left to the user's known preference.

Tools

• get_current_navigation_state({detailed_information:true}) — read the active route when the place is relative to the route. For "my destination" take the final waypoint's location id; for "my next stop" take the first upcoming intermediate waypoint (the one right after the current start), which on a multi-stop route is not the final destination. Don't ask where the destination/stop is — read it.
• get_location_id_by_location_name({location}) — resolve a named place to a location id. Don't read navigation state for a named place. Search the place name as the user gave it; strip only an appended country/qualifier suffix (", Germany", "City Center"), never the distinctive part of the name itself — "Andorra la Vella" is the city's own name, so don't reduce it to "Andorra". If a lookup returns not-found, retry with the user's full name before declaring the place unavailable; only then ask for a nearby searchable place. Always use the id this tool returns — never guess or fabricate a location/POI id, and don't fire a dependent route/search call with a guessed id in the same parallel batch as the resolution; wait for the real id first.
• get_user_preferences({...}) — read the user's preferred category of place; this is what resolves an unstated category.
• search_poi_at_location({location_id, category_poi, filters}) — list POIs of a category at a location. filters is optional: any::currently_open keeps only places open right now; charging filters (charging_stations::has_available_plug, charging_stations::has_dc_plug) narrow to stations with a free plug or a DC plug. Apply a filter only when the user's request actually demands it. Its category_poi argument may be the removed parameter; without it the call errors.
• search_poi_along_the_route({route_id, at_kilometer, category_poi, filters}) — POIs along a route at a kilometre mark (10 km radius). at_kilometer is required for charging stations; pick it from the user's stated mark, convert a stated time into a route distance with convert_route_distance_and_time first, or — when no mark is given but a charging preference exists — derive it from that preference. Same filters as above. May also be unavailable in a given setup.
• get_distance_by_soc({initial_state_of_charge, final_state_of_charge}) — how far the car can drive between two charge levels. Use it to turn an SOC-based charging preference (e.g. "charge at 15% left") into the route distance at which to search for a charger.