Key:opening_date

Description
Expected date in the future when a construction will be finished and feature will be opened. Use YYYY-MM-DD format. Show/edit corresponding data item.
Group: properties
Used on these elements
may be used on nodesmay be used on waysmay be used on areas (and multipolygon relations)should not be used on relations (except multipolygon relations)
Useful combination
Status: de facto

An approximated date in the future when a construction will be finished and object will be opened, used for example on landuse=construction, highway=construction or building=construction. It is recommended to additionally add check_date=*, which describes the date in the past, when the value of =* was actually checked.

Format

Date format compatible with ISO 8601: YYYY-MM-DD (year-month-day).

For example: =2024-08-09 – 9 August 2024

Remember that this date should be a future date; to record when a feature was actually opened or created, use start_date=*.

Avoid combinations such as building=yes + =future as this would break lots of existing software (see trolltags). This can be avoided by using a lifecycle prefix like construction:building=yes or the specific methods established for roads and railways.

Practical use

Opening dates in the past should be resurveyed as either construction completed or opening date changed:

Opening vs completing construction

In some cases only construction end date is signed, while actual opening date may be later and unknown.

The distinction may apply in cases where there is an additional lengthy legal process of verifying and certifying construction and in cases where actual use depends on segments taking longer. For example a motorway may be completed and unusable as a motorway junction on its East end is still being constructed and for now it leads nowhere.

construction:end_date=* is in some use

See also

Possible tagging mistakes

If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
  • construction:end_date=*
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!

in the past

Once the feature opened according to schedule, you should change =* into start_date=*.

  • =2024 ‒ If the feature has opened in 2024, use start_date=2024 instead. If it's still not open, then maybe there is a newer estimate for =*?
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
  • =2023 ‒ If the feature has opened in 2023, use start_date=2023 instead. If it's still not open, then maybe there is a newer estimate for =*?
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!

start_date in the future

For features that are not yet open, you should use =* instead of start_date=*.

  • start_date=2026 ‒ If the feature is scheduled to be opened in 2026, use =2026 instead.
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!
  • start_date=2027 ‒ If the feature is scheduled to be opened in 2027, use =2027 instead.
If you know places with this tag, verify if it could be tagged with another tag.
Automated edits are strongly discouraged unless you really know what you are doing!