Deep links

Blue Light Maps registers two URL schemes you can hand off to from a CAD client, a dispatch tool, or any third-party app. Use blm:// when you want fine control (vehicle type, route handoff, custom pin label); use geo: when you want the user’s chosen default mapping app to pick up the handoff.

blm:// scheme

Show a location

blm://map?v=1&ll=51.515205,-0.014115&n=Langdon%20Park

Parameter	Value
v	Scheme version. Use 1.
ll	Latitude and longitude, comma-separated, decimal degrees.
n	URL-encoded name to show on the pin. Optional.

Start a navigation

blm://nav?v=1&dll=51.515205,-0.014115&daddr=Incident%2012345&type=responsetruck

Parameter	Value
v	Scheme version. Use 1.
dll	Destination latitude and longitude, comma-separated.
daddr	URL-encoded label shown on the destination pin. Optional but recommended (e.g. the incident reference).
type	Vehicle and routing profile. See the table below.

type values

Value	Profile
vehicle	Standard car, non-emergency routing.
truck	Truck, non-emergency routing.
smoothtruck	Truck, prefers smoother roads.
largetruck	Large truck, non-emergency routing.
responsecar	Car, blue-light routing.
responsetruck	Truck, blue-light routing.
smoothresponsetruck	Truck, blue-light routing, prefers smoother roads.
largeresponsetruck	Large truck, blue-light routing.

Note

Short-form encoded blm:// URLs also appear when responders share locations from inside the app. They resolve to the same destinations as the explicit forms above; you don’t need to generate them yourself.

geo: scheme

geo:51.515205,-0.014115

geo: is the platform-neutral scheme. On Android the user’s default mapping app handles it (or the system prompts them to pick one). On iOS, Apple Maps handles it by default; Blue Light Maps is reachable via blm:// only.

Use geo: when you want the user’s choice to win. Use blm:// when you specifically want Blue Light Maps to take the handoff.