This question is **not** about "natural changes" (e. g. user editions deleting something), is about system-maintenance events that changed (or will change) the value of the `osm_id`. ----- Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. As we can check, some `osm_id` was preserved, the element's `osm_id` value stay unchanged many years: [node 1 is there!](https://www.openstreetmap.org/node/1/history) ... But "all OSM people" say that a maintenance event can change `osm_id` values, the system can rebuild it. Therea are a "risk of change". The focus here is this kind of "unsolicited changes" of the maintenance/recovery events, and **the risk of `osm_id` change its an event changing the `osm_id` value whitout editions**. (whitout editions)**. **NOTE**: is natural to change, the reality is dynamic (an earthquake destroys map features) and the community enhance map features editing it (e. g. a node is deleted to become a complete relation)... But the focus here is not the "natural changes".<br/>A crash in the OSM servers or a big technical change can enforce the system to *rebuild* `osm_id`'s (some or all). Whe can label this kind of changes as **unsolicited changes**. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, the "risk of `osm_id` change" exists. In a perspective of 10 years, the change will occur... Is it? ## Where the information about unsolicited changes of osm_id? With some basic information we can ask any question about "unsolicited changes of `osm_id`". How many times the `osm_id` changed for all elements [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? A specific group of elements (how many?) suffered a technical maintenance that affected its `osm_id`? What the risk that an element created today experiencing unsolicitedly-change of its `osm_id` before 2020?

This question is not **not** about "natural changes" and (e. g. user editions. editions deleting something), is about system-maintenance events that changed (or will change) the value of the `osm_id`. ----- Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. As we can check, some `osm_id` was preserved, the element's `osm_id` value stay unchanged many years: [node 1 is there!](https://www.openstreetmap.org/node/1/history) ... But "all OSM people" say that a maintenance event can change `osm_id` values, the system can rebuild it. Therea are a "risk of change". The focus here is this kind of "unsolicited changes" of maintenance/recovery events, and **the risk of `osm_id` change its value whitout editions**. **NOTE**: is natural to change, the reality is dynamic (an earthquake destroys map features) and the community enhance map features editing it (e. g. a node is deleted to become a complete relation)... But the focus here is not the "natural changes".<br/>A crash in the OSM servers or a big technical change can enforce the system to *rebuild* `osm_id`'s (some or all). Whe can label this kind of changes as **unsolicited changes**. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, the "risk of `osm_id` change" exists. In a perspective of 10 years, the change will occur... Is it? ## Where the information about unsolicited changes of osm_id? With some basic information we can ask any question about "unsolicited changes of `osm_id`". How many times the `osm_id` changed for all elements [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? A specific group of elements (how many?) suffered a technical maintenance that affected its `osm_id`? What the risk that an element created today experiencing unsolicitedly-change of its `osm_id` before 2020?

This question is not about "natural changes" and user editions. Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. Is As we can check, some `osm_id` was preserved, the element's `osm_id` value stay unchanged many years: [node 1 is there!](https://www.openstreetmap.org/node/1/history) ... But "all OSM people" say that a maintenance event can change `osm_id` values, the system can rebuild it. Therea are a "risk of change". The focus here is this kind of "unsolicited changes" of maintenance/recovery events, and **the risk of `osm_id` change its value whitout editions**. **NOTE**: is natural to change, the reality is dynamic (an earthquake destroys map features) and the community enhance map features editing it (e. g. a node is deleted to become a complete relation)... But the focus here is not the "natural changes". A changes".<br/>A crash in the OSM servers or a big technical change can enforce the system to *rebuild* `osm_id`'s (some or all). Whe can label this kind of changes as **unsolicited changes**. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, the "risk of `osm_id` change" exists. In a perspective of 10 years, the change will occur... Is it? ## Where the information about unsolicited changes of osm_id? With some basic information we can ask any question about "unsolicited changes of `osm_id`". How many times the `osm_id` changed for all elements [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? A specific group of elements (how many?) suffered a technical maintenance that affected its `osm_id`? What the risk that an element created today experiencing unsolicitedly-change of its `osm_id` before 2020?

This question is not about "natural changes" and user editions. Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. Is natural to change, the reality is dynamic (an earthquake destroys map features) and the community enhance map features editing it (e. g. a node is deleted to become a complete relation)... But the focus here is not the "natural changes". A crash in the OSM servers or a big technical change can enforce the system to *rebuild* `osm_id`'s (some or all). Whe can label this kind of changes as **unsolicited changes**. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, the "risk of `osm_id` change" exists. In a perspective of 10 years, the change will occur... Is it? ## Where the information about unsolicited changes of osm_id? With some basic information we can ask any question about "unsolicited changes of `osm_id`". How many times the `osm_id` changed for all elements [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? A specific group of elements (how many?) suffered a technical maintenance that affected its `osm_id`? What the risk that a an element created in 2009 changes today experiencing unsolicitedly-change of its `osm_id` in before 2020?

This question is not about "natural changes" and user editions. Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. Is natural to change, the reality is dynamic (an earthquake destroys map features) and the community enhance map features editing it (e. g. a node is deleted to become a complete relation)... But the focus here is not the "natural changes". A crash in the OSM servers or a big technical change can enforce the system to *rebuild* `osm_id`'s (some or all). Whe can label this kind of changes as **unsolicited changes**. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, the "risk of `osm_id` change" exists. In a perspective of 10 years, the change will occur... Is it? How many times the `osm_id` changed [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? What the risk that a element created in 2009 changes its `osm_id` in 2020?

This question is not about "natural changes" and user editions. Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. Is natural to change, the reality is dynamic (an earthquake destroys map features) and the community enhance map features editing it (e. g. a node is deleted to become a complete relation)... But the focus here is not the "natural changes". A crash in the OSM servers or a big technical change can enforce the system to rebuild *rebuild* `osm_id`'s (some or all) `osm_id`s. all). Whe can label this kind of changes as **unsolicited changes**. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, there are a the "risk of `osm_id` change". change" exists. In a perspective of 10 years, the change will occur... Is it? How many times the `osm_id` changed [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? What the risk of change that a element created in 2009 changes its `osm_id` in 2020?

This question is not about "natural changes" and user editions. Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. A crash in the OSM servers or a big technical change can enforce the system to rebuild (some or all) `osm_id`s. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, there are a "risk of `osm_id` change". In a perspective of 10 years, the change will occur... Is it? How many times the `osm_id` changed [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? What the risk of change in 2020?

This question is not about "natural changes" and user editions. Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, there are a "risk of `osm_id` change". In a perspective of 10 years, the change will occur... Is it? How many times the `osm_id` changed [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? What the risk of change in 2020?

Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, there are a "risk of `osm_id` change". In a perspective of 10 years, the change will occur... Is it? How many times the `osm_id` changed [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? What the risk of change in 2020?

Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, there are a "risk of `osm_id` change". In a perspective of 10 years, the change will occur... Is it? How many times the `osm_id` changed since 2009? [since 2009](https://wiki.openstreetmap.org/wiki/API_v0.6)? What the risk of change in 2020?

Any relation have an unique ID, the so-called `osm_id`, as in an XML element, &lt;relation id="123"&gt;. Ways and nodes also have respectives `osm_id`s. The `osm_id` is also used in SQL data dumps, etc. URLs use the notation `relation/123` or `way/123` or `node/123`. For many applications is possible to suppose that, **in the application's "time perspective", the `osm_id` not changes**. But in a *digital preservation* perspective, and other more specific applications, there are a "risk of `osm_id` change". In a perspective of 10 years, the change will occur... Is it? How many times the `osm_id` changed since 2009? What the risk of change in 2020?