Xenon32 Waze
My feedback
17 results found
-
119 votes
An error occurred while saving the comment Xenon32 Waze supported this idea ·
-
238 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.
Xenon32 Waze supported this idea ·
-
10 votes
Xenon32 Waze supported this idea ·
-
9 votes
Xenon32 Waze shared this idea ·
-
390 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.
Xenon32 Waze supported this idea ·
-
40 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.
Xenon32 Waze supported this idea ·
-
3 votes
Xenon32 Waze supported this idea ·
Xenon32 Waze shared this idea ·
-
30 votes
Xenon32 Waze supported this idea ·
-
277 votes
Hey,
Please note we're changing the status of this suggestion to Not right now, since we finalized our plans for 2023 and this idea won't be implemented this year.
We hope to have it included in our plans for later years and will keep you posted.
Thanks!Xenon32 Waze supported this idea ·
-
96 votes
Hey,
Please note we're changing the status of this suggestion to Currently Not Planned, since we finalized our plans for 2024 and this idea won't be implemented this year.
We hope to include it in our plans for later down the line.
Thanks!
Xenon32 Waze supported this idea ·
-
3 votes
Xenon32 Waze supported this idea ·
-
5 votes
Xenon32 Waze supported this idea ·
-
4,110 votes
Xenon32 Waze supported this idea ·
-
7,392 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.
Xenon32 Waze supported this idea ·
-
11 votes
Xenon32 Waze supported this idea ·
-
55 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.
Xenon32 Waze supported this idea ·
-
144 votes
Xenon32 Waze supported this idea ·
I fully support this proposal.
The data and mapping needs have already been explained very well. I would mainly add the operational value of such a feature.
Allowing a level crossing to be identified and searched by its official number or ID would be very useful in both WME and Waze, especially for crossings located in isolated areas or places that are difficult to find using a normal street address.
As a track maintenance employee for SNCF Réseau, I regularly use Waze during interventions to obtain a reliable ETA that I can communicate to our supervision team. Being able to search directly for a level crossing by its number would make it easier to reach the correct location quickly and reduce the risk of locating the wrong crossing.
Today, some editors, myself included, create POIs next to level crossings simply to make their numbers searchable. This clearly shows that the need already exists, but storing this information directly on the railroad crossing permanent hazard would be much more logical and reliable.
Adding the crossing number/ID and, where available, the emergency contact phone number would also be useful for drivers and emergency services in the event of an incident.
The minimum information could be:
* official crossing number or ID;
* municipality / locality;
* railway line identifier where needed to avoid ambiguity;
* emergency contact phone number where available.
Ideally, this information should be editable in WME and searchable in Waze.
Finally, this is not only a French or US need: it could be useful anywhere in the world where level crossings exist, with each community using the official identifiers of its own railway network.