Hi,
What, if any, significance is there to these “equals” signs on the roundabouts??
Sod it! I’m deleting those roundabouts and redoing them without those stoopid Y entrance/exits…
They’d be fine if your navigation software understood them, but a complete waste of time if it doesn’t. Obviously Waze doesn’t!
Des. . . 
They show which segments belong to a roundabout. You can only delete all of them at the same time, or none of them. This can also serve as a handy way to spot roundabouts that aren’t proper ones, and need to be rebuilt.
Edit: I just found a roundabout where only half the segments has ==s. I deleted and rebuilt it just in case.
Yeap it is quite important though. After a base map update and some very old roundabout, they were built by normal segments and no roundabout properties. Now it is very easy to point out which one is a proper around.
After redoing them from scratch using papyrus they seem to be working, so hopefully the new roundabout tool is better that the old cartouche one.
I’ll give it a week to try as many different approaches as possible and then hopefully all will be well!
I’ve found that Papyrus is way better for roundabouts in general. Some in my area that I’d been having continuous problems with seem to have settled down once they’ve been either fixed or remade using it.
We can but wait, and see how it goes. I am feeling optimistic though!
Hi,
Does anyone know who “-1” is.
Whoever he is he seems to be bastardising some roundabouts I KNOW I have fixed in the past…
This one.… As an example…
Des. . .
Is ‘The Past’ before or after the Live Map…
Normally editor -1 is the basemap import.
Hi,
Somebody reverting them maybe??
Just checked the routing on that roundabout:
Talk about long way round! Fixed for now…
Des. . .
I found many similar situations. I believe ‘-1’ is a kind of automatic continuous map update. Quite annoying though as it mostly messying up what we have done rather than helping us. Well I have not got any official response from waze about ‘-1’.
Here -1 edited roads come from users gps-points, usually in areas with poor or no maps.
Sent from this Galaxy
The problem is it often messes up where it has been well mapped, not only in areas with poor or no maps. That’s why I always lock the road I’ve done and hope ‘-1’ will not unlock it and mess them up again. :x
Well they are officially working. I’ve now decided to redo every roundabout that I work past whilst editing just to be sure they work … if it’s already been done it’s just 2 mins work to delete and re-do with the new tool.
Started off today working my way along the A5 from Telford to the M42, all stuff I’ve done before but is still a little messed up from the basemap import.
Gentlefolk, much as I hate to do this I’m afraid that I’m forced to mess with our variously addled brains when it comes to 0 exit rb’s, for which I apologise profusely.
It has come to my attention that some of these 0 exit reports may be software errors and not errors with the rb geo at all.
The proof
Several times yesterday, whilst driving with a fellow wazer in the car and us both having waze on (obviously), my phone reported a 0 exit rb whilst my mates gave the correct number and unfortunately the converse is true, I got correct routing whilst he got a 0.
The rb’s in question are in my AOR and are locked and haven’t been edited since I ’ fixed’ them after basemapgate.
On that note, discuss!
You’re not giving us a lot to discuss. Permalinks would be a start but I think HQ (or Gerben) will need to pass this through the route server for some analysis!
Haven’t posted permalinks to the rb’s concerned as I checked them thoroughly on my return home, and only found an error on one of them and that was unrelated.
I could find no invisible(sic) nodes and connectivity/directionality was all fine.
One of the rb’s in question I rebuilt some time ago after it started with the 0 shenanigans and then it worked fine.
It also started with the 0 exit thing again recently but then worked fine again, so I put it down to a temp glitch.
However it is now as of yesterday reporting 0 for me and correctly for at least one other.
Granted ’ discuss’ was a glib comment, but I was merely inviting opinions
And the option is for the route and server output to be analysed by the folk with the tools!
Different client versions?
Sent from my Nexus S using Tapatalk
That would lend weight to it being a software issue then, no?
As I say rb’s this occurred on haven’t been toyed with since base map corrections were made by me, so the map info you have to assume is the same on both our client phones?
Well judging by what you’ve said Seasider, I would assume that the map data on both devices are current (as literal as we all know), and that both devices are connected and working as intended. If that is the case then it’s definitely not the map, but either A - the client version as faitaru said or B - the routing server/phone network sending a dodgy data packet to the device. I can’t think of anything else in the middle that could cause it.
And therein lies the problem, does it not? Both our client phones were showing the same date on my secret benchmark road, so map versions most definitely were the same.
My nagging doubt is this, what if I’ve been fixing rb’s that there is jack all wrong with? Just because my client says 0 it now doesn’t mean that everybodies will?
Surely the same applies to each one of us that’s fixed an rb based solely on our own phone. Is it then plausible that no other wazer has posted an update request for some (most) of our 0 rb’s, because to everyone else the y work fine?
I will post a permalink to the most contentious of my rb’s, purely because I KNOW that thurs morning it was routing fine and friday it was a 0, but it’ll have to wait till tomorrow as up for work at 0430.