← Back to the map FR · EN · dataroads-FR84

User guide

Web map of the Vaucluse (84) departmental road network. This guide covers everyday usage: showing a layer, reading the map, using the tools. CD84 prototype — local data and open sources.

General layout

The screen is split into three areas: the header (title, weather, key figures), the left sidebar (legend and tools), and the map. The legend scrolls within its column; the map fills the remaining space.

Header · weather · key figures SIDEBAR … families & layers … repo · version · Guide MAP Map tools
Overview: legend on the left, map on the right, tools at the top right of the map.

Visibility controls

Two complementary levels:

Click the family name or the chevron to expand / collapse its content in the sidebar (without changing map visibility).

The grey chips under each layer indicate data freshness (see § Freshness).

Families and layers

Factual mapping

Network, territory and basic infrastructure, mostly from OpenStreetMap.

Territory — Vaucluse boundary (84)

Always shown. Dashed outline of the department; a reference for framing.

Network hierarchy

Three levels of departmental roads, each with its own colour:

  • Red — regional-interest network (e.g. D900).
  • Orange — territorial development network.
  • Blue — local-interest network.

How: click the Network hierarchy title or each line to enable a level. Road-number shields appear at sufficient zoom. Click a segment for a card (name, surface, OSM / Wikidata links).

Cycle routes

OSM cycle itineraries (route=bicycle). Totals in kilometres: Via Rhôna (EV17), Méditerranée (EV8), Via Venaissia (V861), local routes.

How: enable via the section eye. Major cycle routes are emphasised by colour.

Roads under construction

Segments tagged construction or proposed in OSM.

How: enable the layer; the segments appear on the map. Counters in the legend.

Main towns

Sub-prefectures and large municipalities (centres + labels).

How: enable the layer for place-name markers.

Roadside areas & car-pooling

Related themes highlighting other CD84 missions along departmental roads (issue #7), sourced from OpenStreetMap:

  • Car-pooling areas 🚗 (amenity=car_pooling).
  • Rest areas 🌳 (highway=rest_area).
  • Park-and-ride 🅿️ (amenity=parking + park_ride) — parking is deliberately limited to park-and-ride sites to stay on roadside stopping areas, without showing the thousands of private car parks.

When the area is mapped as a surface in OSM, its footprint is drawn (light fill coordinated with the type colour) with a centred marker.

How: enable the “Roadside areas & car-pooling” layer; each type has its own swatch and counter in the legend. Click a marker (or the footprint) for details: type, capacity, operator, access, an OSM completeness indicator (present / missing attributes), the Wikidata link when present (otherwise flagged “no link”), and nearby street-level photos from Mapillary and Panoramax when coverage exists — click a thumbnail to open it enlarged. View / Improve links on OpenStreetMap.

Statistical data

Historical or aggregated data — loaded on demand to avoid overloading the map.

Road safety

Multi-year cloud of injury crashes (BAAC / ONISR, 2019 → 2024) geolocated across the Vaucluse. Two visual encodings:

  • Colour = recency — recent crashes appear in a vivid/saturated orange, older ones in a dark red.
  • Severity — a black ring surrounds fatal crashes and hospitalised injuries (the fatal dot being slightly larger too); slight injuries have only a thin white outline, no ring.

The legend embeds a temporal dataviz: the old → recent colour scale, a mini-histogram of crashes per year, and a year-range slider (from / to) to filter the cloud.

How: enable the layer; drag the year slider to watch the evolution over time; click a point for details (year, casualties, date, municipality, address). Note: BAAC geolocation is patchier for older years, hence a denser cloud on recent vintages.

Traffic-count stations

CD84 stations (data.gouv.fr / DataSud), classified by traffic: high (> 20k veh/day), medium, low. Each badge shows the rounded average traffic at its centre (e.g. 22k for 22,136 veh/day), readable regardless of colour.

How: enable in the legend or via the CD84 counts button on the map (both stay in sync). Click a station for a detailed card: AADT (all vehicles), HGV share and flow, and a traffic-evolution chart across every available vintage (1996–2025) with the first → last trend.

Clicking a station also highlights the matching road axis — a distinct indigo trace, separate from the round count badges — and shows the axis details (length, municipalities crossed…) in the Route information panel, without moving the view.

Real time

Recent signals: weather and announced traffic.

Weather stations

A few stations across the department (Open-Meteo). Current data: temperature, wind, humidity.

How: enable the layer; click a marker for the card. One station is also picked at random in the header.

Road events (Bison Futé)

Roadworks, congestion, ongoing crashes (DATEX II / Info Routière feed), filtered to the area.

How: enable the layer; icons on the map, popup on click.

Incubator

Experimental layers: civil-engineering structures, environment, biodiversity, listed webcams. Only the bridges layer shows a refresh chip (twice weekly, Mon. & Thu.).

Bridges layer

OSM civil-engineering structures across the department. Display adapts to zoom:

  • Far zoom — clusters (number of bridges or photos).
  • Zoom ≥ 12 — the structures' footprint on the map; clusters disappear.
  • Zoom ≥ 16 — Panoramax / Mapillary photos near the structure.

How: enable the layer then zoom in. At far zoom, click a cluster to zoom in progressively; clicking a bridge opens the full-screen 3D view.

Bridge 3D view

Clicking a bridge opens a full-screen 3D scene where the structure is rebuilt and surrounded by its photos. Orbit with the mouse, scroll to zoom.

Demo of the Bridges feature (3D view) — 18 June 2026.

Model & data sources. The model is generated on the fly from the structure type (arch, aqueduct, beam, truss, suspension), material, length, width and number of spans. Information is looked up in this order:

  1. OpenStreetMap first (bridge:structure, material, length, width… tags).
  2. Wikidata next, if the bridge is linked to it, to fill the gaps: structure type (P31), material (P186), number of spans (P1314), length (P2043), height (P2048), width (P2049). A small info card (name, image, inception, material, dimensions) then appears, with clickable links to Wikidata and OpenStreetMap.
  3. Structure name as a last resort for the arch count (e.g. "pont des 13 arches" → 13 spans).

2D map under the bridge. A basemap (CartoDB Voyager) is laid flat beneath the model, centred on the structure and north-up: it shows rivers in blue and roads. Falls back to a plain water plane if the tiles are unavailable.

Panoramax / Mapillary photos. Each photo is placed at its real capture location (provider geolocation), with a ground marker and a mast. The image faces outward (the photographer's viewpoint); the back, facing the bridge, is coloured by source — green for Mapillary, violet for Panoramax. A colour dot marks the role of the documented element (pier, abutment, deck…), using the same colour code as the map.

Navigation. Clicking a gallery thumbnail or a panel refocuses the camera on it, shows it enlarged in the centre (the other photos fade so they don't hide it) and shows a link to the source. Click empty space to deselect. Esc or × to close. If WebGL is unavailable, a 2D fallback gallery is shown.

Road signs (stop / give way)

OpenStreetMap layer: stop (red octagon) and give way (downward triangle), pre-generated by a GitHub Actions workflow (several thousand points across Vaucluse).

What data exactly? These are the OSM nodes highway=stop and highway=give_way: they mark the traffic rule at the junction (where you must stop / give way), with a direction tag for the relevant way. They are not the physical "sign" objects (which would be traffic_sign=stop / give_way, very rarely mapped in France). So we draw realistic pictograms placed on these regulatory points: coverage is far more complete, at the cost of this semantic nuance.

How: enable the layer. When zoomed out, points are grouped into clusters (red circle with the element count); clicking a cluster zooms into it. From zoom ≥ 15, the pictograms are drawn (stop octagon, give-way triangle), only for the current view. A pictogram ringed in green has a nearby Mapillary photo: click it to view.

Direction signposts

Direction masts from OpenStreetMap (information=guidepost nodes): the bladed posts pointing to hiking and cycling destinations and points of interest (several thousand across Vaucluse, including the CD84 network).

How: enable the layer. When zoomed out, points are grouped into clusters (click to zoom in); from zoom ≥ 15, a signpost pictogram (post with blue/green blades) is drawn. The popup lists the destinations. A green dot on the mast indicates a nearby Mapillary photo (click to view).

Sensitive natural areas (ENS)

CD84 polygons (DataSud). Area, municipalities, manager.

How: enable the layer; click a polygon for the card.

iNaturalist observations

Observations filtered by intersection with the 84's sensitive natural areas.

How: enable the layer; click the coloured circle (enlarged click zone) for species, date, iNaturalist link. Works alongside the ENS layer shown at the same time.

Webcams

4 CD84 traffic webcams (Bonpas) and Mont Serein (Vision-Environnement).

How: enable the layer; click a marker to start the live video feed in the popup.

Tools & meta

Search, data quality, network statistics, update calendar. No extra map layer (except the quality panel).

Search a road

Search field (e.g. D900, D4) and a filtered list. Click a road: map centring, highlight, card in Road information.

OSM / Wikidata quality

Summary in the sidebar: Wikidata coverage, OSM relations. Detailed panel button: an on-map panel (metrics, roads without Wikidata, without relation).

Network information

Counters: number of roads, OSM segments, cumulative length, AADT min/max traffic, bridges, tunnels.

Refresh formula

Calendar by source (OSM, Wikidata, external, incubator, weather, static) and status of the last refresh.

Map toolbar

At the top right of the map:

Active buttons are visually emphasised (dark background).

URL and sharing

The browser address updates as you pan or zoom the map and when you change the visible layers. Useful parameters:

Copy the URL to recover the same view after reloading.

Data freshness

Under most layers, a chip shows when the data was generated and when the next refresh is due. No indicator for sensitive natural areas, iNaturalist or webcams.

The full detail is in Tools & meta → Refresh formula.