Hey for everyone in the Twin Cities Metro and surrounding area, I’m Lemon one of the area managers for this area. I know people have been asking for a better way to try to get a hold of their area managers in order to make changes to the map and that not a lot has been done yet.
Currently, reporting errors from the client doesn’t always get resolved in the most timely manner and they are hard to see unless you are looking at that area of the map. To resolve some of these issues, I created an email address: lemon.atWaze@gmail.com. The goal is for people in this area to directly send Waze related map problems for what I hope is a more immediate and direct response to your problems when using the map in the Twin Cities Metro area. I guess you could kind of think of it as a help desk for Waze in the Twin Cities.
Just a few things to keep in mind:
Try to be as descriptive as possible when explaining the problem (time, location, situation details, etc).
Screen shots from your client while experiencing the problem or Cartouche screen shots/perma-links are extremely helpful.
I do have a job but would be more than willing to help you out when i’m free in the evening so email me your issues Twin Cities Wazers
Hey Twin Cities, i just got a request for a user to edit the major highway on their commute. Took a couple hours but i hope everything should be solved now. When you email me i can get a sense of where people need more help with the maps sooner than if you were to report a problem via your mobile device.
The email thing i’ve set up actually worked well in this case. Again, don’t feel awkward about emailing me. I’d love you help you out
Hi Lemon. I just was given area manager privs for edina area. Looking forward to working with you on getting the maps right. Exchanged a little emails with sota767 about the 280/Midway area. It seems like a very good group of people with a common goal.
Perhaps you’ve got some ideas on the issue I’ve seen with my I-94 routes. I posted in the Bugs area under the topic "Met the enemy and think it is me… ". A pretty lively discussion.
Any advice on if my editing might be causing the issue and how to avoid it would be greatly appreciated.
Hi Lemon:
I was doing some clean up around south mpls last night and ran into something really odd.
Take a close in look at 35W going south (and North) between the 62 cross town and I-94.
It’s weird. Going North, there was some odd stuff that used to take you off an off ramp and back one again but the segement of 35W between the two ramps was missing. I drew in a road to try to connect things up but it probably is still not right.
Also going south we’ve got TWO roads that are suppose to be 35W. I was nervous about removing one of them so I left them. What do you thing we should do the correct that problem.
I do that the 35w south route home and I noted that waze seemed to get very confused about where I was (ie which road I was on) as the travel that segment. I assume we want it to be one road going south (since I don’t think waze can handle modelling a 4 lane freeway just yet).
Hi got an odd one. I have Restricted Turns on and Connectivity checked.
I can’t figure out how to fix it. The connectivity shows that waze thinks the north south roads are linked?? And there are turn issues up the ying / yang, probably caused by the poor connectivity?
I thought perhaps one could just delete the bad roads and then re add them but I doubt I have permissions in the midway.
You are getting bad directions driving out that way or just based on the turn restrictions shown?
That mess of turn restrictions is from a mess that I cleaned up a while ago and those turn restrictions won’t go away, they’re kind of “phantom turn restrictions” of junctions I deleted. I believe it’s a known bug.
I’ll drive around out there and see what it does at my lunch hour.
well it seemed to route correctly for me, but it did want me to make a U-turn at the ends of the split which I saw was not really possible so I restricted those turns in Cartouche so it won’t do that again.
Hey Lemon. This is a follow up to my earlier post on this,
I think you and I are area managers for this tough piece of real estate.
The issue is the aerial maps are out of date. You can see this when you turn on ‘recent gps points’.
It will take a lot of work to clean it up ‘blind’. But as a major freeway, folks will be getting pretty frustrated if it stays in current condition. Based on info I can find the project will not be completed until 12/2010.
I also worry about fixing it and then having a newbie wazer go changing the road layout. I suppose if we do it pretty well, they at least won’t be able to delete the roads we set up, they’ll just move them and we can change them back. Do you think we could temporarily label them ‘135 const zone pls don’t change’
I was scanning the web and found a couple map PDFs from the DOT that show the final layout and even the status of work as of Feb 2010.
I’d propose whoever does this should set up the current map as best we can to match the future layout, using recent GPS points and the DOT map to get the roads ‘close’.
Re. edit to W 28th St in St Louis Park.
I just made an edit (now pending), and wanted to leave a note for the area manager.
I removed the stretch of w28th St from Xenwood to Yosemite Ave’s - it is a footpath. Also, Yosemite is no drivable from a point ~20’ S of the footpath for a distance of about 40’ (There is a 20’ berm!) but I could not find a way to delete that section.
I just submitted some deletions in EP, but do not have permission for additions - there is a development bounded by Prairie Center Drive, Prairie Lakes Drive and Lexington Drive which is severely messed up!
Lemon: Got another tangle. I was driving from roseville to mpls on 36 to 35w and had some minor issues. But started looking North of the Cleveland, 36, I 35 intersections and found this one.
Yea, i last looked at this mess a few months ago. I had just avoided it for these reasons though this pdf will really help us ultimately line up roads with GPS. I thought i might drive drive all of the new roads and just look at my GPS tracks to line up the roads (when i have some free time). I got a Nexus One and from what i’ve heard and experienced with this so far i haven’t jumped around on the map b/c the GPS couldnt figure out where i was like i experienced on my iphone.
OK. Yes it is 2:21 in the morning and I am hitting the sack. Take a look. Feedback appreciated. I changed crosstown to Major Highway vs Freeway after reading the road naming conventions in the Wiki. Thats why the road is now red.
Second, the GPS points as arrows. IF you zoom in, you get a pretty good model for the flow.
Caution: The new roads will NOT match the aerial views. Those are outdated.
Lastly, I have LOCKED all the new segments and have labelled them with a suffix of CONST ZN. Since no one else seemed to have addressed that kind of naming, I added it to the general naming wiki entry.
===Basic Rules===
Start by following the naming rules for your major roads. Interstate as “I- 10”.
US highways as “US Hwy 90”. To show that the segments are part of a construction zone, just add the suffix “CONST ZN”. “I- 10” becomes “I- 10 CONST ZN”.
“US Hwy 90” becomes “US Hwy 90 CONST ZN”.
When temporarily re-setting road geometry, closely monitor recent GPS points as the aerial maps will likely display an out-dated view. Also, be sure to closely monitor these sections of roadway and remove the CONST ZN suffix whenever the construction is done.
Area Manager - Edina Mn
Have a great day!
Hi there. It was alot better. I need to start fixing on/off ramps now.