Interpretation limit
An ID alone may match unrelated objects. A tag alone does not certify a venue's present status.
Public sources / INT
Explore a collaborative map and geographic features described by contributors.

AI-generated illustration
Read this source in practice
OpenStreetMap nodes, ways and relations have separate ID spaces. Reference type plus number and retain the version to document the state read.
An ID alone may match unrelated objects. A tag alone does not certify a venue's present status.
Type, ID, version, selected tags, geometry and reading date.
A fictional extract contains node/100 and way/100. Deduplicating by 100 alone wrongly removes one object.
Consulted reference : OpenStreetMap — Elements · Consulted on
Updated on :
The reference documents the reading method. The example is fictional; this note does not attest a portal test today or a mission outcome.
Retain the layer producer, date and coordinate system. The map is a representation; inspect the underlying data.
Explore a collaborative map and geographic features described by contributors.
Read feature history and tags; a collaborative map does not replace a field survey or cadastral document.
Feature type and identifier, version, tags, coordinates and access date.
Compare the same feature version; an edit date is not necessarily a field-observation date.
Access, download and API conditions depend on the service. Consult the official documentation and the resource terms.
Identify the feature and coordinates, compare public layers and select a satellite acquisition for the relevant date.
Coordinates, map update and acquisition are different references; record their respective precision.
Compare sourcesInspect the exact resource and its terms. Being viewable does not authorise redistribution; retain the resource licence and restrictions instead of inferring them from the portal.
Record consultation date, covered period, last update and version separately. For revised data, retain the file or exact extraction reference.
The web page, export and API may differ in coverage or terms. Check pagination, filters, authentication, quotas and licence for the access method used.
Check each layer’s terms and required attribution. Inclusion in a viewer does not automatically give identical rights for every basemap and product.
Record layers, producer, extent, zoom and data date. Separate an entered point from the described object; markers and administrative boundaries have different scope.
Check coordinates before placing them on a mapDOCUMENTED REFERENCE
Type plus identifier distinguishes OSM objects. Reconstructing a boundary at a given date requires more: geometry may depend on references to other objects whose versions evolve separately.
| Reference | Value or form | What it identifies |
|---|---|---|
| node | lat / lon | A node stores a latitude and longitude position. Moving it changes the geometry of ways referencing it. |
| way | nd ref | A way is an ordered list of node references. Its version alone does not freeze all node coordinates. |
| relation | type / ref / role | A relation links members by type, reference and role. Members may themselves be relations; retain the required dependencies. |
| version | 1…n | The number increases when that object is modified. A child edit can change assembled geometry without a new parent version. |
| timestamp | UTC | This timestamp describes the object’s modification in the database. It establishes neither the date of a real-world change nor a survey date. |
For historical comparison, retain a coherent dated state of objects and dependencies, relevant tags and assembly rules. Do not combine an old parent with current child coordinates and present it as a verified historical boundary.
No. A member way or node may have changed separately. Check dependency versions or use a coherent time snapshot; the relation version alone is insufficient.
Documentation consulted on .
DEEPER READING / PRACTICE
A list indicates where to look for and what limits to keep in mind. It helps to prepare a consultation but does not replace the reading of the obtained document.
Updated on .
Select a precise question, open the source and raise the request, result and date. Compare the possibilities announced with the information actually available at the time of the consultation.
The availability of a service and its content may vary. The directory does not turn an absent, partial or ambiguous result into a definitive response.
The consultation report documentes the search path, document found, useful elements and reserves. The result is included in the file with its origin.