Skip to content
supercarto
Esc
↑↓navigate↵open⌘Jpreview
On this page

get_maplet

The core call — a walkable, token-budgeted topological graph of any coordinate.

always advertised

get_maplet(lat, lon, radius, layers, budget) — the single call that produces the product. Fetches real geodata around a coordinate, compiles a topological graph, cuts it to your budget, and emits YAML.

PropType
latnumber

Latitude in [-90, 90].

Typenumber
lonnumber

Longitude in [-180, 180].

Typenumber
radius?number

Radius in metres. Kept sane at the interface.

Typenumber
budget?number

Token budget for the emitted YAML.

Typenumber
layers?string[]

Layer filter. Raw OSM tag selectors are also taken; anything else is rejected rather than silently returning nothing.

Typestring[]

The output

Nodes, edges, and — this is the part that makes it honest — omissions:

map:
  center: "35.6833, 139.762"
  radius: 400m
nodes:
  n186: {type: transit, name: 新橋駅(3), tags: [subway_entrance]}
edges:
  n1->n2: {dist: 120m, dir: east, path: road}
omitted:
  - {layer: feature, count: 1754}
tools:
  - expand_feature(id)

What a node can carry

Beyond topology: hours (evaluated in the map’s timezone — a known-closed shop at 04:00 reads closed, a bench with no recorded hours emits no hours at all), sun and twilight in the map header, transit nodes, indoor floors, and the tools: list at the foot.

The omitted: section exists so the model can tell not there from not shown. An agent reading only this block still knows the map is an excerpt.

Last updated on

Was this page helpful?