GrowLeafy ONE IDENTITY. PROTECT EVERYTHING.

GEO

See what’s connected.

A spatial layer for people, assets, places, businesses and services — the ground an identity sits on, and the boundaries it is inside.

What the layer holds

Geography is where an identity layer becomes useful beyond the object itself. A GrowLeafy asset already knows what it is; GEO is how the platform answers where — which place, which boundary, which nearby service, which route between two of them.

Places
A place hierarchy, addressable by level and code. Each place is a real record with real boundaries, not a label typed into a text field.
Geometry
Points, lines, polygons and multi-surfaces, with the geodesy to measure them. Distance, area and intersection are computed on the spheroid rather than on a flat grid.
Boundaries
Administrative areas that nest, with topology between them. A place can be asked what contains it and what it contains.
Geofences
Areas that answer a containment question about a position. Included, excluded, or genuinely undecidable — the three are kept apart.
Identifiers
Codes from outside GrowLeafy are linked to places, not copied into them. External registries are referenced and dated, so a change upstream is visible rather than silently absorbed.
Routing
A swappable routing seam, with a straight-line fallback that says it is one. A provider is optional; an honest answer is not.
Maps and tiles
Basemaps delivered through a provider seam, keyless by default. Swapping the provider does not change what the layer knows.
Coverage
The layer reports which ground it actually covers. An uncovered area is reported as uncovered, never extrapolated into an answer.

Answers, and refusals, with the same precision

Most spatial APIs lose their honesty at the boundary: a null becomes zero, an undecidable containment becomes false, a straight line becomes a journey. Each of those turns a gap in the data into a claim about the world. GEO refuses to do it, and says so in public.

A verdict, not a boolean
A containment question answers included, excluded or undefined. Collapsing the third into "not there" would be a statement the data cannot support.
A null with a reason
A straight-line route reports no duration and names the basis. An absent field is invisible to a client; an explained null is actionable.
Published limits
The layer can be asked what it cannot do. So a product chooses what to render before it renders something untrue.

Two of these surfaces are live

The map is not a promise. Nearby answers what GrowLeafy knows is around a position, and every place has its own addressable page. Both are public and both are open right now.

Places and nearby are public; the writing side is not. Declaring boundaries, linking external identifiers and defining geofences are administrative capabilities — they are reached through the platform API with the right authority, not from this page. What is open to a visitor is reading the ground the platform already knows.

Everything has a place.

Places · Boundaries · Fences · Routes