Hard to tell exactly - they mostly rely on local knowledge of the emergency staff, with various other sources, OSM among others, as helpful (visual) background. We have talked to some of the people in the regional organisations (“Veiligheidsregio’s”) and learned that the organisations are all different in what digital tools they choose, so some do not use OSM at all, while others are using tools provided by a company using some OSM data in their emergency support systems. Their emergency navigation tool needs reliable data from other detailed sources, e.g. how to approach special objects such as parks and building compounds in case of emergency; how to pass barriers; whether fields can be crossed, that kind of thing. Then all of that is mixed into a routing/navigation system; but whatever the system says, it’s the driver who decides where to go.
Nevertheless, they want OSM highway and barrier data to be as accurate and reliable as possible. They agreed that the regular access is bypassed anyway, and their main wish is that data from their regular inspections of road accessibility can be recorded properly. Which is more of a workflow thing than an access thing, so recording inspection date and physical road characteristics/type is more important than assigning emergency access.
(Sorry about the logorrhoea, bad habit, I know.)
Circling back to this case, the emergency people would rather see this tagged and displayed as a service road than as a path, so they do not need to check physical characteristics. Service and maintenance personnel usually know the situation, so they wouldn’t care about these OSM worries.
1 Like