Hi Twister,
Is there any way to distinguish the URs reported from private car and taxi.
Cheers,
Leo
Is there any way to distinguish the URs reported from private car and taxi.
Cheers,
Leo
This one should be reported in Taxi mode except the reporter has made mistakedTwister-UK wrote:Do you have any examples of URs that were *definitely* submitted by someone running in taxi mode? If not I'll try dropping a few on my way home tonight.leocylau wrote:Hi Twister,
Is there any way to distinguish the URs reported from private car and taxi.
Cheers,
Leo
In the second screenshot you can see that I am not allowed to edit the closure.Wed Jul 31 2019, 11:15 by VRFR-KHamstra(1)
Multiple changes
Road closure: added
ID: 3998228.40244427.20443442
Reason: Reconstructie
MTE: not provided
From: 2019-08-19 07:00
To: 2019-12-19 16:00
Direction: A-B
Ignore traffic: false
Road closure: added
ID: 3998228.40244427.20443342
Reason: Reconstructie
MTE: not provided
From: 2019-08-19 07:00
To: 2019-12-19 16:00
Direction: B-A
Ignore traffic: false
Thanks for looking out. Wasn't aware of that issue.Twister-UK wrote:Having now looked at the RTC data, the missing ID bug does seem to be the reason for this one being flagged as an in-app RTC as well.
I still have this BUG in the latest beta WME.Twister-UK wrote:This is related to a bug in WME which is causing it to forget the data associated with segments after certain operations - if you've got segment popups enabled and they start showing "non-existent streetID" instead of the actual segment name, or if you click on a segment and it shows "No address" in the left-hand side panel instead of the actual name, then it indicates WME has lost the data.
At this point, any closures added to segments will be generated with blank location data - WME knows which *segment* the closures are being added to, but not which *streets* those segments relate to. Unfortunately, blank location data is also a trait of closures generated from the Waze app and, until this WME bug surfaced, was the only way to differentiate an in-app closure from a WME one...
Waze staff have now informed us that this bug has been fixed, though at present there's no indication when this fix will turn up in the production version of WME, so until this happens please be patient and pay attention to any unexpected loss of street names.
Isn't working for me neither.taco909 wrote: ↑Wed Aug 23, 2023 4:39 pmThat's not working for me.Webs101 wrote: ↑Tue Aug 22, 2023 2:49 pmThis was the case for me at first. Now it's working for me without crashing the sidebar (so far).
1) I disabled URO+ in Tampermonkey.
2) I reloaded WME.
3) I re-enabled URO+ in Tampermonkey.
4) I clicked the "Enable" box in URO+ in the WME Scripts panel.
It's been working fine* for me since.
* "Fine" as in only periodic sidebar crashes rather than 100% of the time.
I can disable it in TM and reload WME.
When reenabling URO+ in TM, I have to reload WME again (URO does not show in the scripts box), and after the reload, the sidebar is solid white.
Disable in TM and reload WME, everything is back to the current "normal"
Re: [Script] UROverview Plus v3.73 (20160215)