YUL_
My feedback
52 results found
-
132 votesYUL_
supported this idea
·
-
13 votes
An error occurred while saving the comment YUL_
supported this idea
·
-
101 votes
An error occurred while saving the comment YUL_
commented
I support this! A simple button to expire the closure "soon", i.e. "now" would be very convenient. If we want to do it in an elegant way right now, we have to manually change the end date/time, which is time-consuming.
YUL_
supported this idea
·
-
71 votes
An error occurred while saving the comment YUL_
commented
This would be extremely useful! We often have repeated nighttime closures on various roads, and right now we have to re-create the closures manually. Being able to duplicate them would be very convenient indeed.
Also, being able to re-select all the segments that were included in the expired closure would be a real bonus!
YUL_
supported this idea
·
-
36 votes
Hey!
Thank you for the suggestion.
In order to check this suggestion, we would like you to share some more examples with us.
We aim to get the understanding of how often this is an issue.Best,
Hezi.An error occurred while saving the comment YUL_
commented
Here is an example:
There is a long-term closure already in place on several segments of a highway, but which has not yet started. Call it 23:00 on a given day and lasting several months.
A new closure is to be put in place for installation of warning signs, etc., say 19:00-05:00 next day. This closure includes one of the segments which already has the closure mentioned above, but also several others.
Since it overlapping closures are not allowed, the entire new closure cannot be placed, and there is no easy way to figure out what the issue is without looking at all the individual segments. Once you've done that, you either have to make a partial closure 19:00-22:59 to avoid overlap, or reduce the size of the new closure so there are no overlapping segments. Either way, it adds complexity and work.
YUL_
supported this idea
·
-
51 votesYUL_
supported this idea
·
-
21 votesYUL_
supported this idea
·
-
27 votesYUL_
supported this idea
·
-
7 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
YUL_
supported this idea
·
-
19 votesYUL_
supported this idea
·
-
125 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
YUL_
supported this idea
·
-
336 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
YUL_
supported this idea
·
-
3 votesYUL_
supported this idea
·
-
67 votesYUL_
supported this idea
·
-
359 votesYUL_
supported this idea
·
-
68 votes
An error occurred while saving the comment YUL_
commented
I agree that excessive info should be trimmed / collapsed, but certain information should still be shown, such as the user's language setting, type of vehicle, avoid preferences, etc.
YUL_
supported this idea
·
-
111 votesYUL_
supported this idea
·
-
145 votes
Thank you for this suggestion.
We are looking into its feasibility on our end, and will update accordingly
Best,
YUL_
supported this idea
·
-
158 votesYUL_
supported this idea
·
-
165 votes
Thanks all! We're researching this further and will come back with follow up questions shortly.
YUL_
supported this idea
·
I definitely support this suggestion.
For example, we frequently have larger-scale highway closures due to weather, and when these have to be extended (or re-applied in the case of an expired closure -- see other suggestion), having to re-select everything is very tedious!