Hi team,
Can I just say how super impressed I was to see that Waze has started to roll out the new “monster truck” vehicle type to Waze app users? I know driving on roads can be so… limiting… and of course is the primary reason drivers are slowed down by traffic. Instead, bulldozing over innocent homes in a race to deliver the fastest route to drivers ever is some pretty out of the box thinking. I can’t believe someone hasn’t thought of this idea before.
What am I talking about? @kambingtinggi spotted this amazing route on Live Map where the route offered suggests driving where no road exists. The driver would drive over the top of not just one or two but… seven homes and a private girls’ college. No road appears on the Waze map in either snapshot mode or the current map view.
I realise Waze hasn’t announced this feature get, and I hope I haven’t spoiled any big marketing launch, but I’ve gone ahead and named it on your behalf. Yes, I decided “moster truck” was the most applicable name for the new vehicle type. I checked the vehicle types available in my app and despite running the latest beta it didn’t appear yet:
Knowing how busy the graphics team have been, I’ve gone ahead and developed a preliminary image to take a load off their shoulders. The cat’s name is Princess Monster Truck which I thought was inspiring:
The Waze team constantly surprises me with your creative ideas. Let’s see Google steal this idea from us! 
Edit: We were unable to replicate this in the app, it only appears on Live Map (thanks @numbermaniac).
8 Likes
The way I was told routing works once is that Waze routing relies on node-to-node logic to determine if routing is possible or not.
That was back when we tried to understand why two-segment-loops were problematic because they could cause Waze to pick the wrong path of the two possible ones to go from a node to another. Basically if routing sees a “TRUE” value for routing between nodes 1234 and 4321 it will route to it and if two segments (instead of three) form a loop to get there, it could pick either segment indifferently.
It’s the first time that I see a case where no connection exists at all, but it would be interesting to know if somehow in the livemap routing there is a glitch somewhere showing a “green light” to navigate from those two node IDs and why. If that’s even the reason that it happened.
Maybe the nodes have been connected before by a deleted or re-used segment and some =true value didn’t get updated correctly to =false somewhere. Which could explain the straight line even though a segment is not there.
Thanks for sharing this interesting case and I hope we’ll have some insights because I’m curious 
3 Likes
Hi LostInMyMaps,
Thank you for the report and for the suggestion about this special “monster truck”! The image and idea really look great, I will share it with Anat, maybe she will use it for future Copilot projects.
As about the issue, could you please open a bug in Centercode for it. Sorry for asking this, we have a dedicated component there for such bugs, it will be easier to handle similar cases and other users can upvote it or leave comments.
Many thanks in advance and once again BIG Thanks for the idea with the Monster Truck. :geek:
Best,
Nataliia
1 Like
I know it’s supposed to go on Centercode, but just wanted to share that it’s replicable and I think it’s not a BETA WME issue.
It’s a common case when a JB only permits one path, in this case a roundabout with a sliplane, but the sliplane is closed rn.
PL to the testarea
And here’s an example on a real road in Germany, that’s how routing went for a while when the sliplane was closed:
The monster truck roads only appear in the livemap, not in the app.
It would be nice if there were an override in the routing algorithm if a closure won’t allow the standard path.
Best regards
2 Likes
Hi @LostInMyMaps,
We apologize for taking a while responding to this issue.
Since this case doesn’t seem to be very common and is getting outdated, we will automatically close this bug now.
If this issue is still occurring please submit a new bug with all the relevant information and we’ll make sure to fully revisit it again.
We apologize for the inconvenience.
Thanks and have a great day.
If you click the link to the livemap in the original post, the bug still occurs:
Hi @numbermaniac,
Sorry for the wrongly changed obsolete status of the following issue, as this was part of the clean-up process.
Thank you for reporting that the following bug is still reproducible. I’ve logged an internal ticket, and our team will take another look. I will keep you posted here.
Regards,
Vladyslav
1 Like
