Bus stops in Norway [guide for understanding current data and reporting problems]

Temporarily moved stops

Could you add something about temporarily moved bus stops? E.g., how long-lasting does it need to be for someone to report it, or to add some temporary or lifecycle tag? Do you use such tags if they are present?

The procedure is slightly diffuse because everything is a gray area. Like, “how far is too far, and is too far too far in every case”. Anyway, the practical rule of thumb is that:

  • Long term temporary stops that are far away (enough to warrant a new name): New stop is created at new location, old stop is usually disused.
  • Long term temporary stop nearby: The existing stop is moved to the new location and moved back when the situation is resolved.
  • Short term changes, long distances: Usually new stops are not created in the short term so either a different (already existing) stop is used, or the route just skips the stop.
  • Short term changes, short distance: Usually resolved by textual information in realtime deviation messages.

It should be noted here that NKA has recently modified the script so that only stops that have been out of use for 1 year are removed from OSM.

lifecycle tag

This would be difficult to implement in the source data. Stops come and go and its quite difficult for the counties to properly follow up on all stops - mostly because they dont always know if the stops will be used again later or not. The stops are versioned and the last version either has no end date, or it has an end date in the past or the future. Stops with an end date in the past are expired and should be considered “removed”.

1 Like