I really don't see a big need for this new feature indicating levels. Other than railroads, and the occasional overpass that is set to the wrong level, what is it's use? This would/will be kept turned off as I want to see lock level issues and other real problems on the roads that most commonly need to use elevations (freeways), not levels. Levels only really affect how the map is drawn, two segments can cross at the same level, abd two segments at widely carried levels can be connected and neither situation will effect the routing.

Tapatalking via my Galaxy S4

jondrush wrote:Because levels now matters on the livemap.

Oh gee, yet another link to private information that most editors have no access to, even some level 6 editors.

Edited to remove private link.

Tapatalking via my Galaxy S4

sketch wrote:

daknife wrote:Oh gee, yet another link to private information that most editors have no access to, even some level 6 editors.

Edited to remove private link.

Tapatalking via my Galaxy S4

And so? As a mentor, you also have access to at least one private forum that most editors have no access to, even some level 6 editors.

But I have yet to toss out such a link as proof of some concept. Time and again Champs cite some new law from above, and when questioned, a link to the private forum is shared, which nobody but the champs can read.
If it hasn't been published to he general community it is not a standard, no matter how many champs agree with it.

I don't like private channels, I grant some use of them for discussing how to deal with problem editors. But any and all discussions as to how the map system works must be at least readable by all editors, limit comments by non champs, but stop hiding new details from us.
Tapatalking via my Galaxy S4

Drkorb, Then don't yell at me when I call you chumps out for linking to private info as if we ALL have access to it. I got upset when Sketch came down on me.

You have your private forum, just don't cite it in response to the vast majority of us who are not as special as you.

Tapatalking via my Galaxy S4

Timbones wrote:I see that fwdSpeed and revSpeed have both been removed from the segment attributes, presumably because they deemed to be not useful by HQ. I don't see any 'averageSpeed' attribute though, or anything else that indicates speed. I shall have to remove this feature.

Thanks Timbones. Here is a link to qwaletee's original thread with a little more background on where I saw averageSpeed. As mentioned though, it was just a quick glance at the JS file, and since I don't work with JavaScript or know detail on how such scripts interact with the Waze object model, I don't have the expertise to know if this is useful or not.

From WME-f3bf976b.js:
getAverageSpeed:function(){return this.averageSpeed||(this.averageSpeed=3600*(this.totalRoadMeters/(this.endTime-this.startTime))),this.averageSpeed}

okladriver wrote:

sketch wrote:But a lot – A LOT – of the imported house number data is wrong, very wrong.

This is where I think this type of highlighting could be useful. I started going through my area, block by block, to check street names and house numbers. It became almost impossible to keep track of what streets I had verified the house numbers on. If there was some way to highlight the streets that had any non-bumped addresses, or even better highlight the non-bumped ones in the house number manager, then I'd have a way to keep track of what I've fixed and haven't.

Not sure if this is even remotely possible through the Waze API though. Just wishful thinking.

Waze doesn't get the house number data until you select the segment and manually hit the Edit House Numbers button. At that point, it queries based on the segment selected (and neighboring segments similar to "select entire street")

For example: https://www.waze.com/Descartes-live/app ... s=23641491

From there though, it is easy to tell which numbers have or have not been "bumped". Anything with "updatedBy":null has not been touched. To make that request for every segment in view would be returning a lot of data though, which is probably one reason Waze isn't doing this by default in WME. WMECH doesn't currently make any extra requests like that, so if it ever does, it should be an "opt in" feature in WMECH. It could be done, but it would make the script a lot less light-weight.

Olestas wrote:Ok, here it is:
https://www.waze.com/editor/?env=row&lo ... 413&zoom=6

I have Highlighting Recently Edited (Green) 30 days turned on.. and only 3 segments show up.. others don't react. Also tried 365 days...

Is your filter by city also enabled at the same time? When applying the Recently Edited and Filter by City simultaneously, I've noticed that it changes the Recently Edited to an "AND" condition that matches the city selection.

Timbones, have you considered highlights for Preferred or Unfavored routing road types, and if so, what do you think is the best way to visually represent these? WMECH seems to be the most appropriate tool to deliver this, but I suppose that it could be an option in our Toolbox highlights if you are not planning it for WMECH.

Timbones wrote:

davielde wrote:Timbones, have you considered highlights for Preferred or Unfavored routing road types, and if so, what do you think is the best way to visually represent these?

Not sure. I'll have to think about it...

Thanks. There are no immediate plans to add this to Toolbox, and it is not something that our dev team has discussed yet. The question just came up.

ranttine wrote:Feature request: highlight road segments with an elevation that differs from ground level. Even better if its different color for negative levels and positive levels.

Are you using WME Toolbox? That highlight exists there in the exact manner you mention.