There is no reason why a technical event (aka server crash etc) would require a renumbering of OSM objects, the ids are one of the objects attributes and not a transient database row id or similar. Naturally some of the data model changes that are in discussion (area types, doing away with way nodes and similar) could potentially lead to a large number of objects being removed and new ones with different ids id being created, however any such change would be discussed and prepared well in advance. So to answer your question, the likelihood of any such change happening before 2020 is minimal. Note: none of the above makes relying on stable OSM ids less technical technically defective.

There is no reason why a technical event (aka server crash etc) would require a renumbering of OSM objects, the ids are one of the objects attributes and not a transient database row id or similar. Naturally some of the data model changes that are in discussion (area types, doing away with way nodes and similar) could potentially lead to a large number of objects being removed and new ones with different id ids being created, however any such change would be discussed and prepared well in advance. So to answer your question, the likelihood of any such change happening before 2020 is minimal. Note: none of the above makes relying on stable OSM ids less technical defective.

There is no reason why a technical event (aka server crash etc) would require a renumbering of OSM objects, the ids are one of the objects attributes and not a transient database row id or similar. Naturally some of the data model changes that are in discussion (area types, doing away with way nodes and similar) could potentially lead to a large number of objects being removed and new ones with different id being created, however any such change would be discussed and prepared well in advance.advance. So to answer your question, the likelihood of any such change happening before 2020 is minimal. Note: none of the above makes relying on stable OSM ids less technical defective.

There is no reason why a technical event (aka server crash etc) would require a renumbering of OSM objects, the ids are one of the objects attributes and not a transient database row id or similar.similar. Naturally some of the data model changes that are in discussion (area types, doing away with way nodes and similar) could potentially lead to a large number of objects being removed and new ones with different id being created, however any such change would be discussed and prepared well in advance.

There is no reason why a technical event (aka server crash etc) would require a renumbering of OSM objects, the ids are one of the objects attributes and not a transient database row id or similar.