The simulation selects a random address ID during event generation under certain parameters. These are the same address data that are also available via the API or selection fields, for example in the deployment mask or administration area. This is therefore a shared address data pool.
The address data is structured (country, state, district, etc.), but not georeferenced, meaning without stored latitude and longitude values. When an address is needed on the map, the coordinates are only resolved at that moment via an external interface. This works without problems in most cases.
When coordinate resolution fails
If resolution fails, the generated event lands at incorrect coordinates, as seen in the screenshots from @ibuprofönix. This doesn’t only affect the map display: the simulation mechanics also receive incorrect coordinates, so the event may end up several (hundred) kilometers away from the actual deployment location.
Now the rescue resource must be considered: it doesn’t know which simulated event you want it to have. It behaves as it would in reality. The dispatch center alerts it with an address, and it drives there. Upon arrival, it searches for the event. However, if the event was generated with incorrect coordinates, the rescue resource finds nothing at the destination (“spawned incorrectly on the map”).
Correcting coordinates retroactively
Using the “Change coordinates” function, multiple interfaces are queried for the coordinates of the address in question. The correct coordinate can then be selected manually. This selection is permanently linked to the address. All future queries for this address, including in the simulation background, will use the selected coordinates from then on.
This also makes it possible to correct an event that was already incorrectly located retroactively: if the coordinates of the address are updated, the ongoing simulated event also refers to the new location.
Important: The correction only takes effect if the address matches exactly. If the event was generated for “Bahnhofstraße 3” but the coordinates were changed for “Bahnhofstraße” or “Bahnhofstraße 30”, there is no connection. The event then remains at the wrong location, and while the rescue resource may drive to the newly selected address, it will find no event in the vicinity.