Build a reproducible export
Download the deduplicated public record that underlies the map, list, and analysis. Filters, provenance, precision, and derived segment metadata travel with the data.
Choose the records
“Mapped” requires a qualifying match to the active road network and a usable reference point. A source coordinate by itself is not enough. All other reports remain available under “Unmapped”; this means unresolved by the current evidence and road model, not inherently unlocatable. The export never invents a point for them.
Field dictionary
CSV uses snake_case column names. JSON groups exact coordinates and matched-segment fields into objects and adds the selection, generation time, schema/method version, and a SHA-256 hash of the incidents array.
| Field | Meaning |
|---|---|
| id | Stable public incident or observation identifier. |
| reported_at_utc / reportedAt | Source publication time as a UTC instant. |
| reported_at_sgt / reportedAtSgt | The same publication time rendered in Singapore time. |
| time_precision | Whether time is minute-precise, a post-time proxy, or unknown. |
| road_name, direction, relation, landmark | Best-effort fields parsed from the source message. |
| location_precision | Original record or event location classification; this does not by itself mean mapped=true. |
| sources / provenance | Source-family audit set and its readable API, X, or both label. |
| exact_longitude / exact_latitude | Source-supplied coordinate only; blank when absent. |
| mapped | True only when a qualifying active-network segment has a reference point. |
| segment_* / segment.referenceCoordinate / segment.geometry | Derived segment id, network version, edge, reference coordinate, GeoJSON geometry, method, confidence, bounded extent, approximation flag, matcher version, and matching evidence; CSV uses segment_reference_longitude, segment_reference_latitude, segment_geometry_geojson, segment_geometry_attribution, and segment_geometry_licence. Fields are blank when unmapped. |
| segmentGeometrySource | JSON-level OpenStreetMap source, attribution, and licence metadata for the derived segment geometry. |
| message | The verbatim source message retained for audit. |
Using the export responsibly
Provenance
These are reports LTA published through DataMall and @LTATrafficNews. They are not the complete Traffic Police accident registry. Publication time is not collision time.
Location
Exact coordinates are source-supplied and preserved unchanged. Text-derived segment matches are bounded 20–250 m estimates; capped extents are marked approximate. Exit anchors can carry explicit OpenStreetMap destination-tag provenance. Explicit tunnel reports can also record a verified same-road connector of up to 1 km from the landmark anchor to the first tunnel edge; that connector is evidence for the bounded segment and is not itself the displayed extent. A source coordinate and a derived extent remain separate fields when text evidence is used after an ambiguous coordinate match. The derived reference coordinate and segment GeoJSON support spatial analysis without replacing the original source coordinate. Blank coordinates are meaningful missing data, not an export error.
Comparison
Counts reflect source publication, road length, traffic volume, and collection coverage. They are reported-incident counts, not severity or risk rates.
Source terms
Source material is linked under the Singapore Open Data Licence. Derived road geometry and exit-anchor evidence use OpenStreetMap data; see the OpenStreetMap copyright and licence notice. Refer to those notices for their terms.
Citation and reproducibility
Suggested citation: accidents.sg, “LTA-published traffic incident record”, generated on the export’s timestamp, filtered as recorded in its query metadata. Include the methodology version and JSON content SHA-256 when available, and link to accidents.sg/methodology.