Waze US Webinars

We periodically hold “webinars” for various topics. These are intended to be informative and instructional on topics of editing the map for beginners to advanced Wazers.

Look here in the future for updated information about the timing and details of these webinars. Information will change on this first post as webinars are announced, but may be repeated in subsequent message to refresh date of posting and alert others.

FUTURE WEBINARS:
None listed at this time.

PAST WEBINARS:

Topic: 102 - Roles & Ranks for Community & Editing
Archive Video URL: Google+ YouTube
Date: Thursday April 17th (Completed)
Start Time: 9 pm Eastern, 6 pm Pacific
Duration: About 25 minutes. No Q&A occurred.
Presenters: Vectorspace
Target Audience / Who should attend: Those interested in learning more about the Ranks and Roles in the Waze Editing Community to be more effective at editing.
Purpose: New editors, and even those who have some experience, are often confused about roles and ranks in the Waze Community and how they work. Some clarity should help you learn faster and have better interactions while editing.
Outline:

  • Community Roles, Editing Roles, Editing Ranks
  • Why have roles and ranks? What are cones & badges?
  • Identifying who’s who in the Waze Community
  • Editing Rank
  • Client Application Rank
  • Editing Role examples
  • Community Role examples

If you haven’t yet voted on the best time for you to attend webinars, please do so at the following link. You can pick any number of days and times that work for you.

https://www.waze.com/forum/viewtopic.php?f=129&t=86586

Because of the dynamic nature of this information, this forum will be purged of older messages so that we can focus on the more near-term activities.

Excellent presentation. Hope to see more of these more often! Thank you!

Thanks… I need to figure out how to get On Air videos like this to have interactive Q&A via video and chat. Didn’t work for this one, but it was our first attempt!

I can help you test it out. Remind me on G+ later. I caught part of it, was very nice.

Sent using Tapatalk for Android 4.4.2

Great presentation, I subscribed to the spanihs forum thread . Tahnks :slight_smile:

Thanks. I am going to give that one again with an updated slide set and also, hopefully, some online interaction.

I too enjoyed the presentation a lot, thanks!

One thing that could help is more info about approaching higher-ranking editors for help.

Twice now I’ve seen broken road edits that were apparently “abandoned” by their editors after they realized they could not fix it due to the presence of a locked segment (of course it’s possible they didn’t even realize that it was broken at all). Abandoning the edits at that stage is the worst possible outcome.

Twice also I’ve seen editors handle a UR involving locked segments by starting the conversation with something like “needs Rank 5 to fix this” and then abandoning the UR. Yikes.

So it seems like clarifying the paths for approaching higher-ranking editors could be useful…?

Great job, cheers!

Great points. Thank you. I’ll put these in our mentoring docs .

I already just added it to the skills list. Great idea.

Sent using Tapatalk for Android 4.4.2

Glad to help! It made me think of another couple of suggestions. These are not related to editor levels/ranks/badges but I don’t know where else to put them.

When I first started, the nomenclature of Map Problems and Update Requests really confused me. I did understand that there were two separate sources of alert pins, one automated the other user-generated, but if you stop to think, you realize the words “Map Problem” and “Update Request” do nothing to distinguish those sources. You just have to know. When Alan set me straight, I joked, so, if a user reports a map problem it isn’t a Map Problem, and if the system requests an update it isn’t an Update Request. To this day I say “User Report” instead of “Update Request” because the language more closely represents the meaning.

Even more confusing was that the meaning of the “Not identified” and “Solved” buttons is totally different depending on whether you are working a UR or an MP. If you are working a UR, “not identified” means you didn’t nail it and “solved” means you did. But if you are working an MP, “not identified” means “escalate to a paid out-of-town editor of unknown skill with unpredictable results” and “solved” means either “I think I fixed it” or “consider this a bogus report and ignore it”.

Once you’ve been doing this a month or so you forget that it was ever unclear. But boy was I confused at first!

Hope this helps!

I was led to believe that the proper method for responding to Map Problems according to the wiki was to mark as Not Identified if there is no problem at that point, and to mark as Solved only if you actually made a change on the map to fix the problem. If you were unable to determine what the problem was or if it should be corrected, leave it marked as Open to let other editors see it.

Sent using Tapatalk for Android 4.4.2

Interesting! The MP wiki is different now than it was when I was learning late last year. Back then it said

but now it says

This is a significant change in the meaning of the “not identified” button. Good to know.

Just want to post thanks to all for organizing these webinars. I generally won’t be able to take part live because of the time difference (for most of the year we’re three hours behind Pacific), but it’s great to at least have this resource archived!

Appreciate the feedback! I wanted to mention that we intended to hold more of these, but the last couple months have been hectic and May, with end of school and graduations, is particularly bad. We’ll start them up “soon.” :slight_smile:

Is there a collection of ideas for future topics?

One edition might be a briefing explaining the best process for improving point-of-interest routing (corrections to search engines, the effect of adding Place points or areas and of tweaking house numbers, etc.). This is the source of most URs, in my experience.

This is a great suggestion. We should do this one soon :slight_smile: