CommuteTour factual baseline / 7 October 2026

source-facts.json retains compact code, heading, named-place and editorial/capture facts, with original ordinals and source-file hashes. Lists are publisher presentation order; omitted ordinals indicate bounded samples. Source headings are joined to lists only where independently witnessed. No reverse is generated. Source publication/edit dates are not service dates.

osm-platform-context.json retains exact separately acquired native point objects and reviewed fact-to-point associations. The marker denotes a named OSM platform context, not a building centroid, gate, boarding right or CommuteTour-supplied coordinate. Repeated source occurrences remain; map markers may combine matching native IDs while naming every source ordinal. Nothing connects the markers by a line.

Method: normalize each released factual JSON into records and sections, preserving literal names, source ordinals, locators and explicit heading-binding state. Attach only independently reviewed exact native identities using code/source ID/fact-file hash/section/ordinal/label; unmatched facts remain text. Read node version, timestamp, tags and coordinates from the frozen City native body, without geocoding, snapping, joining or reversing. No private publisher HTML, media, embedded maps, Google Directions, inferred schedules or passenger approvals are conveyed.

Same-version native OSM body is publicly available in /transport/osm/2026-10-07-v2/osm-derived-database.json, sourceNativeData.citySnapshot. The old v2 is unchanged. This compact offer contains every newly compiled factual record and point binding. Existing native road traces retain their separate identities and sources and are not declared equivalent to publisher lists.