Map Editor major ver (Nov 5, 2012) Official Feedback

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby skbun » Mon Dec 17, 2012 6:57 pm

khaytsus wrote:
davipt wrote:Have you seen my post? select the segments that gives you errors, click on permalink, and go to waze.com/support, write ghost segments and post the permalink asking waze to remove those broken segments.

I've done this now myself, but I'm finding them all over.. I think it's a a larger problem than a random ghost segment.


This is a fairly huge problem. It may be serverwide. FWIW, I created a post on this and submitted its contents to support, but people are finding these all over.

(My post: viewtopic.php?f=10&t=34676 )
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby skbun » Sun Dec 02, 2012 2:45 am

Speaking of ads...it would appear that advertisement landmarks (probably on a hidden layer) are coming up in WME.

Put in 'Seattle, WA' into the search box, and you'll get two results:
'Seattle, WA'
'LIVE HERE! - ...(address)'

If you go into the Waze client, you'll see that this is a advertising popup for a location. I'm thrilled actually that Waze is getting more sources for these! - but my guess is that these aren't meant to be a searchable layer in WME?
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby skbun » Sun Dec 02, 2012 12:29 am

Kuhlkatz wrote:The intention is not say anyone is incompetent. We all strive to better the maps in our area, AND we all make mistakes - it's part of the game, especially since we all tend to spend late nights editing. I get annoyed with myself too. After completing an area and looking at it weeks later, I still find some obvious mistakes.


No, though...we don't have nearly enough editors in number to cover say, the United States, and some localities just don't have the numbers they need.

I know Waze can turn on ads encouraging people who have the app to join, say, a local TV traffic group (I've seen this in the California Bay Area, and Portland). We'd have a big influx of people, potentially, but would it be worth it to have an ad for a week or so - if you're not in one of those areas - that says something like 'Fixes needed where you drive? Become an editor!', which links to the video...might get people involved. We'd have a lot of basic stuff to teach on, but the overall effect might be a positive. Curious what people think about that idea.
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby skbun » Thu Nov 29, 2012 5:20 am

PhantomSoul wrote:I'm sure that the use, in the US, anyway, of Bing for street address resolution, as well as Bing, Google, Yelp, et. al., for POI resolution is just a temporary stopgap until until Waze's own house number and landmark databases are more complete and accurate.


It's my understanding that we already have a standing soft policy in the U.S. of not creating landmarks for every business/address/thing because of the clutter and sheer difficulty maintaining all of that. If we lose the (Bing Google Yelp etc.) resolutions, we lose the ability to search by things like business names. This is something that say, Google Maps has as a baseline feature. This strikes me as a Bad Thing?
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby skbun » Tue Nov 27, 2012 7:38 am

The 'Landmarks causes segment selection' crashes continue, FWIW. I'd still recommend keeping the landmarks layer disabled. I've found a different predictable use case and will forward it to nanorep support tonight.
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Road direction picking changed

Postby skbun » Thu Nov 22, 2012 8:59 pm

bz2012 wrote:something strange is going on around there. To the south and east, I see the symptoms you are reporting. To the west, segments act normally.
I don't know how far the 'three directions only' region extends.


I do see this 'three directions only' as far south as rural central California, and the Bay Area (San Jose, CA, etc.) Seems to be a pretty big area in that sense, but yeah, further west than my permalink, it DOES act how it used to.
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Road direction picking changed

Postby skbun » Thu Nov 22, 2012 7:46 pm

Something oddball in the way of a change has happened at least on the NA editor, and I can't put my finger on what it is.

Consider permalink https://www.waze.com/editor/?zoom=7&lat ... s=54685761

My attention was brought to this area because there's an automated report saying 'restricted turn might be allowed'. The thing is (as this is an express lane interchange) both ramps had direction 'Unknown' on them. However...if you look at streets in this area, you'll see that you're now only given three choices for directionals: One way A-B, One way B-A, and Two Way. Even the sister ramp attached to the one I saved as two way (I had no other choice!), shows the Xs I would associate with an 'Unknown direction' road, but I can't select it in the dropdowns.

Tried basic things to reset the segment like pulling its endnodes away from either side, saving, putting back...no go. I don't want to lose speed data for the segment, so I haven't done more than that and figured I'd put it out there to be investigated.

If I type 'R' to change the directions with the keyboard, 'Two Way' stays on screen for two keypresses. So it's like it is aware Unknown is kind-of-sort-of there, but isn't offering it as a choice; that the directional picker has gotten somehow broken - at the very least changed - and I don't understand the rationale of why. We do USE 'unknown' type designations for streets in situations like short to mid-term road construction, and to explicitly prevent routing on street types that otherwise allow it (like ramps) so...
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby skbun » Tue Nov 20, 2012 9:27 pm

Timbones wrote:Skbun, you might want to send these issues directly to Waze Support...


I took your suggestion and did so. Thank you!
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Too little error checking on cities

Postby skbun » Tue Nov 20, 2012 8:18 pm

This has been being discussed in various ways in other threads, but I wanted to put this here, so there's one place for Waze/the developers to look. (As a suffix to this, I'm not just putting these down as 'Look at how I can break the editor! I've actually had to fix real world cases of these problems.)

* City names with less than three characters are not rejected (Real world cases of such short names are exceedingly rare, but we get city smears all the time when people believe they've autocompleted a longer city name and haven't. See viewtopic.php?p=293748#p293748 (the problem) and viewtopic.php?p=295180#p295180 (possible solutions) for more on this.
* When the number of a city's streets is zero, a cityID is not deleted from the database (Related to above. If these don't get cleaned out, fat-finger errors can be reintroduced 'because that city DOES exist'.
* Spaces are not chopped from the middle of a city string (In other words, 'Federal Way' is not equal to 'Federal Way', but I can create a city with that name, and saving the latter will create a new CityID if it does not exist)
* Special characters are allowed in city names (e.g. $%,; ...) I suspect a couple select ones would want to be allowed like apostrophe, dashes...but as it is it looks like anything goes right now.
* 'The highlighted road is too far from the city it was added to' does not check altStreets for their cityIDs. I can add an alt street from anywhere in a state or country, in an alt street.
* In the United States, the state that the editor believes you are in is offered as a possible city. If I am in Washington, and start a city name with 'S', 'Washington' is given as an autocomplete. If I accept that, the cityID assigned is 100000040. I have to assume this is not what's wanted. (I've seen this sometimes, probably where a user was quickly tabbing around and didn't realize what they'd filled.) If there's a similar problem with countries on World, I can't see it because the infrastructure is being moved at the moment.
* I don't know how they got there, but there exist 'cities' in the database city names whose name is NULL or empty. I discovered this with the highlighter tool, when I saw two identical 'No City, State' entries in an area. One example is the altStreet on https://www.waze.com/editor/?zoom=7&lat ... s=61284239 whose cityID is 47991, not 999953. My guess is there are others on NA or world. I don't know if that might cause weird pollution behind the scenes.
* Please add more than six colors to the 'Cities' layer pallette. See viewtopic.php?p=293719#p293719 for more information.
* The Javascript console tells me when a new city has to be created. Can the user be alerted to it too, so they can be sure that they wanted to do that?

As always, thank you so much for reading!
Last edited by skbun on Tue Nov 20, 2012 8:44 pm, edited 1 time in total.
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Map Editor major ver (Nov 5, 2012) Official Feedback

Postby skbun » Wed Nov 14, 2012 10:05 pm

davipt wrote:In my case zooming out or in or taking layers out doesn't solve it. And it's no extra script either. There is a javascript error (I've posted both on Firefox and Safari) and from that point on the javascript login is broken and only a refresh will solve it. I'm sure with the javascript error lines they can easily solve this. And I'm pretty sure this is a bug introduced days after the launch of the new version.


I myself am on Chrome, so maybe I'm getting a different error based on a different condition.
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 850
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: kelvinkuok