← Marketplace

Commons signalFree

Places & Geo Context

OpenStreetMap and Census context for every site you run: what is there, and what is around it.

Ask how Places & Geo Context fits what you run.

Answers are based on this listing. For anything it can't answer, our team can.

For anything this page can't answer, talk to us.

About

This Commons feed reads place and boundary context from OpenStreetMap's Overpass API and the US Census APIs: what surrounds a site, which administrative areas contain it, and coarse demographic context for the area a site serves. It is the difference between dispatching to an address and dispatching to a place you understand.

Both upstreams are free and public. Lookups are cached and rate-respectful, and every derived fact carries its source, so a routing decision can cite the map data it stood on.

Highlights

  • Free public sources, no key required
  • Every derived fact cites its map or Census source
  • Site context for dispatch and routing decisions
Kind
Commons signal
Category
Commons signals
Publisher
Fibric Commons
Upstream
OpenStreetMap Overpass / US Census (overpass-api.de, api.census.gov)
Feed health
Feed live, data flowing (9086ms, checked 2026-07-06T23:28Z)
Availability
Early access
Delivery
Managed by Fibric; nothing to install
Data direction
Read-only
Pricing
Free
Sold by
Fibric
Support
Developed and supported by Fibric
Tags
geo, places, commons, free

Authentication

None. Overpass and Census APIs are free and public; Fibric respects their published rate limits.

What it reads

  • Nearby places and infrastructure around each site from OpenStreetMap
  • Administrative boundaries and containment for each site
  • Census area context for the regions your sites serve

What it can do

This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.

How it works

1

Sense

Nearby places and infrastructure around each site from OpenStreetMap.

2

Reason

Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.

3

Act

Nothing. This is a sensing source; operators act through the write-capable connectors alongside it.

Pricing

Public upstream feed · managed deployment terms

The upstream signal may be publicly accessible, but no public Fibric plan or hosted feed is offered here. Integration, validation, limits, and support are scoped in writing for a managed deployment.

Deployment engineer
Wires and verifies the integration with you during onboarding
Managed validation
Review maturity, authority, supported records, and deployment boundaries before go-live
Execution records
Supported reads, proposals, policy decisions, and reported outcomes kept for review
Support from the builders
Developed, run, and supported directly by Fibric

Requirements

System requirements
  • Your site locations

Your deployment engineer verifies each line with you during onboarding.

Support and resources

Supported by the people who built it

This signal feed is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.

Works with

Listings this is designed to pair with. Each listing has its own live or managed early-access state.

Operator by Fibric

Field Dispatch

A managed early-access pattern for matching supported field signals to a reviewed route and dispatch proposal.

View details

Operator by Fibric

Exception Routing

A managed early-access pattern for identifying line exceptions and proposing reroutes, reschedules, or reviewed dispatches.

View details

Data & events connector

PostgreSQL

Reads your operational tables under row-level tenant isolation, the same wall that keeps tenants out of each other's data.

View details

Bring Places & Geo Context into your early-access deployment

Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.