`GET /v1/places/in-view` (see module docs).
Request
- Base URL: https://api.mapmap.ai
- URL: https://api.mapmap.ai/v1/places/in-view
- Auth: one of:
- HTTP bearer
- API key in query parameter api_key
Query parameters
Observer latitude in decimal degrees
Observer longitude in decimal degrees
Direction the observer is facing, degrees CLOCKWISE FROM TRUE NORTH (0 = north, 90 = east). Magnetic bearings must be converted by the caller; nothing here corrects for declination
FULL width of the cone in degrees (1–360, default 60, so 30 degrees either side of the bearing). The same meaning fov_deg has on the nearby_places MCP tool
Maximum straight-line range in metres (1–5000, default 1000)
Comma-separated place categories, normalised through the same vocabulary GET /geocode/reverse accepts (cafe, pub, fuel, charging_station, …; coffee → cafe, petrol → fuel). categories=building reaches named buildings, which is how to ask "what is that building over there". At least one of categories and name is required
Place name or brand filter, matched exactly as GET /geocode/reverse's name matches it. At least one of categories and name is required
Results to return (1–25, default 5)
Height of the observer's eye above the ground in metres (0–500, default 1.6, a standing adult). A driver's eye is nearer 1.2 m; a first-floor window is nearer 4 m
Height above its own ground at which each place is tested (0–500, default 0, the place's door). Raise it to ask about rooflines, spires or masts
When true, drop everything whose verdict is not clear. Default false: an occluded or unchecked place is returned WITH its verdict, because dropping it would be a visibility claim made silently
Response
Places in the cone, each with distance_m, bearing_deg, angular_offset_deg and a visibility report naming exactly what was checked; plus an observer echo, an excluded count, a coverage block naming the datasets that answered, and the standing caveat
Changes
No recorded changes to this operation across all 1 revision of this API.