Real time closures on Turns for All Environments.[/size][/i][/b]
These features will be available to you shortly after the production release.
Stay tuned for announcements, and we warmly welcome your feedback! Below you can find a summary of the release. Known issue:
Lanes width: Apply button should be disabled after applying and becomes active with any new change.
New features/enhancements:
Permanent Hazard: Add visual indication for Topes/Speed bumps - enabled.
Closure Status: Add vertical scroll to reveal the full Closure Status List - enabled
The “Show my location” button functionality now also includes adjusting the zoom level. When users try to locate their own position on the map, the zoom level automatically adjusts to level 17.
Suggest an edit: The message alert limit has been removed, allowing up to 80 characters to be displayed, ensuring the full text is visible.
Suggest an edit: show the suggested edit after submit - enabled.
Suggest an edit: editors should be allowed to add suggestions to segments that exceed 1.5 km - enabled.
Suggest an edit: We removed the ‘1 segment + ID’ header element from the left panel for cases when a segment is opened solely for suggestion. Bug fixes:
We’ve released 10 bug fixes.
Suggest an edit: Changes failed to apply - fixed
Suggest an edit: Text on the issue card is not updated after Save - fixed.
Suggest an edit: The front-end interface incorrectly displays changes as already applied to the map - fixed.
Suggest an edit: Suggesters should have the possibility to view their own suggestion - fixed.
Suggest an edit: Alternative / Primary address is not displaying under suggestion - fixed.
Turn arrows appear too close when they are part of a Path - fixed
Unable to move a virtual node - fixed.
Safari: No left panel and Layers panel displayed - fixed.
Editor is sometimes stuck on the loading screen - fixed.
Can’t update lane width/number of lanes - apply button grayed out - fixed.
When approving a Suggested edit, moving to the next suggestion does’t allow to approve or disapprove until the previous has been saved.
Is this WAS or a BUG?
I don’t know if this is a BUG or a WAD, but when I close a turn, the next segment affected by the real time closure on turn, is also locked for editing as is the original segment the turn belongs to.
I suggest that the next segment be editable since sometimes a turn closure is performed because the next segment changes direction. What is sought is to be able to change direction in real time through this functionality.
It’s almost impossible to see the current location and suggested location markers on the map from a PUR, looks like the background “vanished”.
No scripts were running, TM disabled, running on MIcrosoft Edge
After rechecking with the team, we found that the current behaviour is as expected. The reasons behind are technical limitations and additional code checks, so editors can only accept or reject one suggestion at a time.
Right now the team discusses possible solutions to confusion.
