Has any thought been put into the fragility of the current setup of associating toll pricing with segment IDs :?: If a segment that is used for toll pricing is changed enough to alter its ID number then the toll price will no longer be calculated for a journey that pass through that section of road :!:
Covering each segment that is associated with a toll price with a Map Comment would alert those editors who work with the layer turned on. Locking them all to L6 would stop most, except for visiting editors and staff.
Segments currently retain their speed data when their segment IDs are changed so it is possible for some sort of memory. An easier solution might be an additional level of warning when such a segment is being edited in WME.
It is actually the Junction Node ID’s that are vital to the operation of the toll prices. If a L5+ (visiting editor/staff) comes in, I would hope and trust that they would read the map comment and not make any changes with proper notification. From personal experience, I have had editors contact me to verify if making changes to the segment would be problematic.
I would hope (and expect) that any L4+ editors have their MC layer turned on.
Also, to the best of my knowledge, speed data is not retained with segment IDs change either but depending on the traffic on the segment, the speed data will rebuild pretty quickly.
Using node IDs doesn’t make the system any more stable as splitting a segment that is matched to toll pricing will generate a new node ID at at least one end therefore breaking the toll price calculation.
I highlighted this observation as this forum was supposed to monitored by Staff and it seems that however much we try to protect our work it can easily be undone. But I guess that is no different to all Waze mapping.