Public sources / INT

OpenStreetMap

Explore a collaborative map and geographic features described by contributors.

Mapping workspace with a map, compass and illustrative coastal image.

AI-generated illustration

Read this source in practice

Is an OSM object's number a sufficient key?

OpenStreetMap nodes, ways and relations have separate ID spaces. Reference type plus number and retain the version to document the state read.

Checks to perform

  1. Include node, way or relation in the key.
  2. Keep consulted object's version and date.
  3. Read tags and geometry relevant to the question.

Interpretation limit

An ID alone may match unrelated objects. A tag alone does not certify a venue's present status.

Record to retain

Type, ID, version, selected tags, geometry and reading date.

Fictional example

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.

Provenance and evidence type

Operator or reference institution
OpenStreetMap contributors · OpenStreetMap Foundation
Result type
Geographic object or layer

Retain the layer producer, date and coordinate system. The map is a representation; inspect the underlying data.

    What this source helps you find

    Explore a collaborative map and geographic features described by contributors.

    Limit to retain in your conclusion

    Read feature history and tags; a collaborative map does not replace a field survey or cadastral document.

    Useful search anchors

    • Place / coordinates
    • Exact query

    Fields to record when citing a result

    • Document identifier
    • Version / revision
    • Access date and time zone
    • Observed passage / value

    Evidence record to retain

    Feature type and identifier, version, tags, coordinates and access date.

    Check before drawing a conclusion

    Compare the same feature version; an edit date is not necessarily a field-observation date.

    Official reference page

    Access, download and API conditions depend on the service. Consult the official documentation and the resource terms.

    Cross-check this source in a research route

    Useful methods

    Other sources in this family

    Before export or reuse

    Coverage
    INT
    Identifiers to retain
    Document identifier · Version / revision · Access date and time zone · Observed passage / value

    Licence and rights

    Inspect 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.

    Date and version

    Record consultation date, covered period, last update and version separately. For revised data, retain the file or exact extraction reference.

    What object does the result describe?

    Result unit
    Geographic layer or feature and attributes
    Time reference to retain
    Access date and displayed update date; current state does not reconstruct all history.

    Documentation and access

    The web page, export and API may differ in coverage or terms. Check pagination, filters, authentication, quotas and licence for the access method used.

    Open producer documentation

    Can a map screenshot be freely published?

    Check each layer’s terms and required attribution. Inclusion in a viewer does not automatically give identical rights for every basemap and product.

    How can a map view remain reproducible?

    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 map
    Geographic sources and observation imagery

    DOCUMENTED REFERENCE

    OpenStreetMap: a parent version does not freeze all geometry

    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.

    OpenStreetMap: a parent version does not freeze all geometry
    ReferenceValue or formWhat it identifies
    nodelat / lonA node stores a latitude and longitude position. Moving it changes the geometry of ways referencing it.
    waynd refA way is an ordered list of node references. Its version alone does not freeze all node coordinates.
    relationtype / ref / roleA relation links members by type, reference and role. Members may themselves be relations; retain the required dependencies.
    version1…nThe number increases when that object is modified. A child edit can change assembled geometry without a new parent version.
    timestampUTCThis timestamp describes the object’s modification in the database. It establishes neither the date of a real-world change nor a survey date.

    Implication for the record

    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.

    Do identical relation versions guarantee an identical 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.

    Primary documentation

    Documentation consulted on .

    DEEPER READING / PRACTICE

    Read a source profile as a starting point

    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 .

    Priority checks

    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.

    Interpretation pitfalls

    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.

    Working record to retain

    The consultation report documentes the search path, document found, useful elements and reserves. The result is included in the file with its origin.