May I report a possible bug on international version of WME. It looks that it is not possible to delete a node between two adjacent segments that have corresponding different speed limits on their sides.
Here is a permalink to such node: https://www.waze.com/editor/?env=row&lo ... =256108104

matsalka wrote:

WazingArch wrote:May I report a possible bug on international version of WME. It looks that it is not possible to delete a node between two adjacent segments that have corresponding different speed limits on their sides.
Here is a permalink to such node: https://www.waze.com/editor/?env=row&lo ... =256108104

It's more like a feature and has always been this way.

It doesn't make sense. All speed limits are same and this node is redundant but I can't remove it.


Sent from my iPhone using Tapatalk

BellHouse wrote:

WazingArch wrote:May I report a possible bug on international version of WME. It looks that it is not possible to delete a node between two adjacent segments that have corresponding different speed limits on their sides.
Here is a permalink to such node: https://www.waze.com/editor/?env=row&lo ... =256108104

This WME bug has already been reported many times (in the WME beta forum part), but Waze is ignoring it since more than a year. Very sad.

My community manager forwarded this issue to the devs earlier this week, so there is some hope.

While we are on this subject I would like to mention a similar issue that goes the opposite way. It is possible to delete the node between two adjacent segments that have different road type options enabled (unpaved/tunnel/toll road). That is especially dangerous for "unpaved" option because there is no visible indication on map where this option is in effect and a user may want to purge the "unnecessary" node between these segments thus removing important route information.

Hello,
I would like to report an issue with closures. This problem appears when driver closes segment on app. Web editor incorrectly sets start date too far in the past - usually in 1970.
Apart from being incorrect information, this makes difficult to edit times of closure.

Please take time to fix it.

vince1612 wrote:As far as I know that was always like this with closures from the app. It's not an error.

Hello Vince,
it took me quite a time to figure out that this is closure from app and not a small bug. I never thought this was an intended behaviour of web editor. It really makes little sense and causes more confusion than help when dealing with closures. Also it is difficult to edit such closure in order to extend or shorten it. It would be a good idea to fix it although we can live with it.

This isn't good...
With this update, I can no longer select "View House Numbers" when selecting any segment that is not editable to me - either outside my EA or in my EA but above my lock level. Similarly, the "View Restrictions" button is not working. Viewing HNs, even without edit privileges, can be very helpful. Please bring it back/fix!

Eagles1181 wrote:It appears that users can no longer use the "Select Entire Street" option for roads that are above their lock level. Not sure if this was intentionally removed, or was simply broken with the new release. Either way, this feature is very handy when submitting unlock request for a long segment of road (think SL). Please bring this feature back.

Thanks,
Philip

+1, in addition to the above.

Twister-UK wrote:, I can't think of any good reason why app-submitted closures couldn't instead default to the date/time at which the closure was submitted from the app - since Waze doesn't offer a time-travel facility there's no real benefit in setting the closure start time to anything earlier than right now...

Do you know of another way to distinguish between WME and App closures?
App closures are monitored and worked with extensively in the Benelux community. Until now this timestamp is the only known way to identify App closures. So losing that functionally would be a bad thing.

Sent from my Nexus 6P using Tapatalk

Olestas wrote:Well.. waze could add flag -"from app" instead of 1970... not everyone knows what 1970 means.

They could. But I'm not sure they would.
Adding a flag has an impact on the needed processing power and database capacity. They would have to weigh this impact against the problems editors have with the 1970 date. Which is a way to achieve the same result without impact (for free). Only editors will ever see that date and only editors with closure rights have technical issues with that date.

One thing that could be done is visualize the 1970 date differently in WME.

Sent from my Nexus 6P using Tapatalk