The WME URL field for Places is limited to 100 characters. I'm not really sure why!

Most URLs will fit in this area, true. But some hotels have URLs longer than this. When I try to add one to a Place, it is truncated, so the URL does not work in Waze.

A hotel in my area has this URL:

https://hamptoninn3.hilton.com/en/hotel ... index.html

WME truncates it to this when pasting into URL box:

https://hamptoninn3.hilton.com/en/hotel ... ood-clearv

To compare them:

CODE: SELECT ALL
https://hamptoninn3.hilton.com/en/hotels/louisiana/hampton-inn-and-suites-new-orleans-elmwood-clearview-parkway-area-MSYELHX/index.html

https://hamptoninn3.hilton.com/en/hotels/louisiana/hampton-inn-and-suites-new-orleans-elmwood-clearv

For a hotel in particular, websites can be difficult for searching for a particular location, and the localized names (and therefore the URLs) are really long. So, having the local URL can be very helpful to an app user. Extending the length limit will make this possible. Thanks!

by sketch
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=277350

When using the WME search box to find a road, it would be really nice if WME could leave the current zoom level well alone rather than always resetting it to level 3.

Even if it just defaulted back to level 4 that'd be an improvement, but jumping back out to 3 means we then always have to zoom back in at least one step if we want to be able to select a street segment. And even at L4, anyone looking to do some work on point places would then need to zoom in one step more before they show up... So really, not altering the zoom level at all would be the best choice IMO.

by Twister-UK
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=276683

Hi,
when saving, if the backend fails, it returns a message. But often they are not localized, and in that case we get a generic
"Please try again later" which is useless because in most case the problem will not solve and the only solution is to cancel all edits.
Here is a list of messages that are not localized and need to be displayed (maybe not exactly in the same form, but at least do not tell the user to try again if it is impossible that it works.

Invalid street 0 was set for venue ID -100
Missmatch max speed in original segments
Property toSegID of NodeConnection with ID 305118209f/-113r references Segment with no generated ID for -113
Node 282093744 is not connected to segment 356869225

There are probably many more, but it is the one I got while editing recently.

Of course it would be even better if the frontend did not generate situation causing those errors :)

By: kpouer
Link to original suggestion:https://www.waze.com/forum/viewtopic.php?f=1525&t=257666

Description: Currently when editors make most changes to a turn between two segments the segment history simply shows "Turn onto X road updated". It would be much more helpful if we could easily tell what was changed about that turn. Was is a turn instruction override (TIO)? A difficult turn? Time-based restrictions? There was a change in a value associated with the data model of that segment, so it's very much possible to have the segment history be more specific.

In this image there are three entries for turn updates to the same turn, but other than the TIO there is no way to know what exactly was done. If there's been a tile update then we only have the option to email a community manager to pull the change info for us. It'd be much quicker and more helpful to be able to get this info at a glance.

Current behavior: All changes to turn attributes are saved to segment history in a generic format.

Desired behavior: Changes to turn attributes are displayed in segment history with descriptive wording. ie - "Turn onto X road turn instruction override added/deleted", "Turn onto X road difficult turn added/deleted", etc.

By: SkiDooGuy
Link to original suggestion:https://www.waze.com/forum/viewtopic.php?f=1525&t=306811

It may be nice for us to be able to "subscribe" to a segment ID, not sure if it should be rank locked or not.

Basically, add a check box on a segments panel to subscribe to changes of the segment.

When subscribed to a segment, if a change is made to a segment the subscriber gets an email notification that their segment has had changes (and of course provide a PL)

Among other possible uses, it could be used to get notification if someone makes a change to a segment that is part of the Toll Price feature.

by jm6087
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=293706

There are many places where Lanes go one or two junctions back (H junctions for example). The editor should allow to define lanes that are not limited to the turns at the end of this segment:
Real example:
We have 3 lanes. The left lane is loaded for 1 KM. In that 1 KM there are 4 junctions ( right turns allowed).

It would be nice to be able to define 1 lane for Left turn, one for going Straight Ahead, and one for Straight Ahead or Right.And be able to do this for all 5 segments.

By: Rill
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=307279

I'm not sure if it's a minor-bug or intended, but I ask you to take a look:

Issue regarding Map Editor Beta and Production.

:arrow: When you find a new place waiting for approval, if you click on the red arrow everything runs smooth, but if you feel the need to click on the yellow arrow to check what's that place is about before approving it (sometimes you can't tell just by the name title), notice it isn't possible to change the address... well maybe it's ok at this point before approving it.

(attachment 1)

• After you Approve you can't still change it.
  (attachment 2)




• You need to click on the map background to remove selection and the click on the place again and now you can change the address. In my opinion this extra step is unnecessary.
  (attachment 3)

by KarderGomes
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=301965#p2064955

Sometimes it's necessary to select multiple segments to perform a road closure either for MTE or for a conventional closure. After you have several segments selected, you accidentally select a node and all work is lost (the section disappears). I suggest making a modification that prevents the disappearance of the selection of these segments and notifies the editor that you selected a node and it will not be possible to make the respective closure (before or at the moment of trying to save). Obviously the idea is to give you the opportunity to remove the node from the selection and continue with the work.

by kahlcolimon
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=288148

I brought this up Jan/2015
I think It should be revisited, here is the original forum post link and quote:

https://www.waze.com/forum/viewtopic.php?f=211&t=125253#p1009107

"some thoughts on Live closure implementation....Seg to Seg closure is great. But if you have a parade route (for instance) you can close an entire street for a mile (say west to east segs). Unfortunatly it has no affect on cross streets (say if you wanted to cross the closed road from north to south on a side street). So...Side streets have to be closed also if they cross your closed segment. Seems to me what's really needed is not segment closing, but node closing, and the app showing closed on segs between nodes. Unfortunatly the only way to do 'node' closing is time based turn restrictions that need to go through a tile build. I think if the live closure got re-vamped to 'node' clousure, the process would be alot more affective. Since to get to a seg you have to pass through a node anyways. Knowing waze will allow you to cross closed streets via a side street, now double or triples the amount of closures needed for just a simple one street multiple block (or whatever leangth) closure"

By: nnote
Link to the original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=168767

I tried finding a post that described this problem but I could not find it, in case there is one, it can be merged to that thread.

tl;dr Add a tag to URs when the user is not registered or not following a UR.

Not long ago ronsek57 told me that users, who just opened the app and never registered, are able to send URs but they never receive any of our messages asking for more information. I tested that on three URs (IDs 11946180, 11946458, 11946459), I am not adding permalinks because they already disappeared from WME.

I sent all three an initial message, follow up and closed them, I did not receive any messages on my test account:

Not registered - see screenshot 1
Inbox (only the welcome message) - see screenshot 2
I did not change any of the notifications on the app, I just installed the app and started driving - - see screenshot 3

I know this is not centercode, and I will post about this over there, I sent my logs on April 28th at 22:42:13 UTC / 15:40 GMT -7 hours.

We sometimes get URs with no drive or suggested route GPS traces and we will waste our time sending many messages to a user or leave the UR for more than a week or two.

Suggestion: add a "Not Following" tag for URs where the original poster is not following the UR or it comes from a Not Registered account.

This is not posted as a bug because this was WAD.

I am sure ronsek57 can give you tons of stats of how many URs are closed as Not Identified.

I know that I did not send some of those URs but I can check if there is a problem, because they are on a frequent drive and I can fix them without any messages from the OP.

By: carloslaso
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=257119