Source and derivative errors
Corrections
Camera records begin in OpenStreetMap, while country assignment and format conversion happen in this site's pipeline. Correct the layer that is actually wrong; do not change good OSM data to work around a SpeedCams.world processing error.
Public contact status
There is currently no verified public SpeedCams.world inbox or correction form. No email address on this page is implied, and the site does not simulate a successful submission. The steps below are the only currently available correction path for source-data errors.
First, identify the error layer
The OSM location or tags are wrong
Examples: the camera no longer exists, the coordinate is misplaced, the object is not a speed camera, or a supported speed/type tag is wrong. Correct OpenStreetMap using local knowledge and its contributor guidelines.
OSM is right, but this site is wrong
Examples: the country assignment is wrong, a valid unit was transformed incorrectly, a duplicate was handled badly, or an export differs from the page. This is a derived-data issue. Do not move or retag the OSM object to compensate.
Correct an underlying OSM record
Find the OSM node ID
Camera listings and map popups show an OSM numeric ID where available. Record the ID and the coordinate before editing.
Inspect the source object
Open
https://www.openstreetmap.org/node/OSM_ID, replacingOSM_IDwith the numeric value. Review the current coordinate, tags, history, and nearby map context.Edit only with evidence
Use personal local knowledge, permitted imagery, or another acceptable source. Follow OSM's tagging and changeset-comment guidance. If unsure, leave an OSM note instead of guessing.
Wait for a new site snapshot
An OSM edit does not update SpeedCams.world immediately. It can appear only after a later OSM snapshot is fetched, validated, processed, and published. No regular refresh interval is promised.
When the derived output is wrong
The site currently has no verified public channel for a derivative-only report. That is a service limitation, not a reason to alter correct OpenStreetMap data. A future channel should request only the OSM node ID, affected page, observed output, and expected processing result—never unnecessary personal information.
The pipeline is designed to quarantine ambiguous boundary and coastline records and to publish rejection ledgers. Review the methodology for what is accepted, rejected, or left unassigned.
Review methodology and rejection rules