MapsBox

Solutions

For the teams responsible for the road

Agencies and operators work with the same live incident record, set up for the way their organization runs.

State DOTs

Statewide incident visibility without waiting for the phone tree.

Information about a crash on an interstate often lives in several places at once: a trooper radio call, a maintenance supervisor text, a district spreadsheet. The traffic management center ends up reconciling them by hand while drivers are already in the queue.

MapsBox gives every district one live record of incidents. Operators confirm what comes in, and the same record drives the map, the driver app and your public feeds.

  1. Intake from any sourcePaste a trooper or patrol message into AI intake and confirm the road, direction, lanes and severity.
  2. Per-direction statusClose the southbound lanes of an interstate without marking the northbound side affected.
  3. Role-based districtsGive district staff operator access and leadership viewer access to the same workspace.
  4. Publish downstreamPull active incidents as GeoJSON into your own traveler-information map through the API.
Start free trial Talk to sales

Cities & counties

One place for closures, events and roadwork on local streets.

City streets are affected by parades, water main breaks, utility work and school events, and each is owned by a different department. Residents hear about them late, if at all.

Public works, traffic engineering and police share one incident list. Planned work is entered ahead of time and cleared when the crew leaves.

  1. Roadwork trackingRecord construction with the lanes affected, update it as the work moves and clear it when finished.
  2. Event closuresAdd a closure for a street festival or marathon route and clear it afterward.
  3. Shared viewLet the 311 desk, public works and police look at the same map.
  4. Invite partnersSend an invite link with a viewer or operator role to a utility contractor or neighboring jurisdiction.
Start free trial Talk to sales

Fleets & logistics

Route-level closures and delays, available to dispatch.

A driver learns about a closure when they reach it. Dispatchers learn about it from the driver. The load is late before anyone can reroute.

Your operations team keeps a workspace for the corridors you run, and the API feeds incidents into the dispatch and routing tools you already use.

  1. Bounding-box feedsRequest only the incidents inside your service area with a bbox query.
  2. Incremental syncPoll with the since parameter and receive only incidents updated after your last call.
  3. Driver reports backDrivers report what they see; an operator confirms it and every other driver gets the update.
  4. Scoped tokensIssue a read-only token to the routing service and a separate write token to the reporting tool.
Start free trial Talk to sales

Emergency management

Road status you can trust during storms, floods and evacuations.

During an event, road status changes by the hour and comes from many agencies. A closure that is lifted but not recorded sends evacuees the wrong way.

The emergency operations center keeps one authoritative list of closures and hazards, updated by operators across agencies and visible to responders.

  1. Hazard and closure entriesLog flooded roads, downed lines and debris with severity and location.
  2. Multi-agency rolesInvite fire, police and public works staff as operators and give elected officials viewer access.
  3. Activity logSee who changed which road status and when, for after-action review.
  4. Offline reportingField reports from the driver app queue on the device when networks go down and sync later.
Start free trial Talk to sales

Transit agencies

Know which incidents affect routes and stops before service is hit.

A blocked street can strand a bus route or a stop. Supervisors usually learn about it from an operator on the radio, and passengers learn from the delay.

Control center staff watch the incident map for the streets their routes use, and the API supplies incident data to internal dashboards.

  1. Route corridorsFilter incidents by road and area to match the corridors your routes run on.
  2. Detour planningCheck closures and construction before approving a detour.
  3. Dashboard feedBring active incidents into an internal service-status dashboard through the API.
  4. Shared with citiesReceive incident updates from the city workspace through an invite or the API.
Start free trial Talk to sales