Skip to main content

Mobility and live data

OpenMapX can show places and vehicles with current information, such as charger availability, fuel prices, parking occupancy, or available shared bikes. The sources enabled by the instance operator determine coverage and which categories appear. A location without a live value is not a promise of availability.

Find a service nearby​

Choose a category in the bar above the map to search the visible area. Select a marker to open its details. After moving the map, use Search this area to request results for the new view.

CategoryAvailable details depend on the source
EV chargingConnectors, power, operational status, tariffs, and live charge-point availability
FuelStation information and prices by fuel grade
ParkingFacilities, Park & Ride sites, and free-space counts
Bike sharingDocked or free-floating bikes, available bikes, and free docks
Car sharingStations or vehicles, availability, and published pricing
E-scootersAvailable vehicles and operator no-ride, no-parking, or slow zones
WebcamsTraffic or scenic still images and, where offered, video

An open panel uses the same place information as other map results, with additional details for that category. Filters depend on the selected source; charging can expose connector, speed, or available-now filters, for example.

A webcam can have several views. Stills refresh while the panel is open; external streams and players load only after you allow external media. Offline or outdated cameras appear dimmed. External media has a different privacy boundary from an image fetched through the OpenMapX API.

Read road information​

The Road conditions overlay includes information about the road itself, alongside incidents:

  • Message signs show their current pages and publication time. A blank or failed sign is marked accordingly.
  • Road-weather stations show available surface and air observations. Check the measurement time and any offline, stale, or suspected-fault notice.
  • Maintenance vehicles can show their current task and a short recent trail. Coverage and reporting frequency depend on the source.
  • Border crossings can show queues by direction and vehicle class, with reported waiting times, open lanes, and observation times.

Use each layer's legend to interpret its symbols. A missing observation, an empty viewport, and a source failure are different states; none establishes that a road is clear or a service is available.

Sources and freshness​

A category can combine several providers. Results carry source credits and freshness information so you can check who supplied a value and when it was reported. The displayed source time can differ from the time OpenMapX fetched the response. Cached or delayed observations can remain useful, but should not be read as a live guarantee.

Where the data lives​

Shared-mobility integrations use feeds such as GBFS and regional operator APIs. Charging, fuel, parking, cameras, message signs, road weather, maintenance vehicles, and border crossings can be supplied by OpenConditions. OpenConditions ingests and links its own datasets; OpenMapX reads its provider responses for the requested area.

Available sources​

There is no single worldwide coverage guarantee. Sources differ by country, operator, licence, credentials, and whether they publish locations, live values, or both. OpenStreetMap-backed location data does not by itself provide live availability or prices.

Check the credits on a result and the instance's privacy information for the sources actually in use. OpenConditions' feed catalogue is the detailed inventory for its datasets. For freshness and coverage diagnostics, operators should use Coverage and freshness.

Enabling and configuring​

Operators manage categories and providers in Admin → Integrations. The category integration and its provider must both be available. For example, the charging and fuel categories are unavailable when they have no registered site provider; enabling their UI integration alone does not supply data.

To use OpenConditions, install and configure its companion services and the built-in adapter as described in Community extensions. Configure upstream ingest credentials on the OpenConditions service that owns those feeds. Restricted sources additionally need the operator token on both sides. A token controls access; it does not grant additional data rights.

Provider acquisition follows source policy and attribution requirements. The backend provider requests normally pass through OpenMapX's server. External links and consented media players contact their destination directly.

Developers adding a category or provider should read Data-source integrations for search, detail, filtering, attribution, and freshness contracts.