As the subject says: Does the Waze App allow speed limit editing in Toronto, Ontario?
This is assuming that my editing level is sufficient (as per the WME) on the Web Site
or
That the segments have been previously unlocked to my level.
The reason that I am asking is that I am trying to find the most efficient method to update speed limits (all steps involved) considering that I do not have a navigator to take notes 
I am very open too all suggestions.
Thank you in advance.
Yes. In the client app, you can report a speed limit (Report > Map Issue > Speed Limit). Your selected speed limit then appears on the WME and you can finalize it there. An easy way to mass-produce speed limits would probably be to drive around with the Waze app and report missing speed limits where/when you see them.
Shorty after I joined I stopped at every pole (on my street) that had a speed limit that was different than the map and put the information into the app.
I do not think that I really knew/understood the WME.
Weeks later the Waze APP map was still not updated.
At that time, I had no idea that there were editing levels, etc.
Knowing what I know now …
I am editing level-1.
When using the app, I do not know what editing level is necessary when clicking on Map error and updating the speed limit.
So, assuming that I try to update a level-2 segment (in the Waze app) … what will happen when I ‘edit the map’ in WME?
I am not being lazy, but I was very frustrated when I first joined and kept stopping (in each direction) and kept tapping in the speed limits over and over for multiple segments and nothing seemed to come out of the effort.
I really enjoy the ‘work’ and would like to make a contribution of my time as long as the community gets something out of it.
Am I missing something?
Any UR (including speed limits) submitted by anybody takes time to show up in the WME. When it does, you have to manually confirm that the speed limit matches the road segments, just like any other UR.
If you want a less tedious way, you could always try the ITO Map. If you find the correct road you’re looking for and click on it, it shows a blob of text. The speed limit of that road is somewhere there.
P.S.: I am also Rank 1, I feel your pain!!
It is not possible, in any way, to edit speed limits from the Waze app. The only way to change speed limits is by editing the Waze map in WME (Waze Map Editor).
Reporting an incorrect speed limit via the app generates a UR (User Request) on the Waze Map Editor. However, there are major problems with this. When Waze introduced this feature, the map was rapidly flooded with SLURs (Speed Limit URs). You couldn’t tell which way they user was travelling or whether they were reporting the before/after limit. Bugs in the app mean that sometime the required speed to report isn’t available. Some users just report for the points, regardless of accuracy. Some report advisory limits (eg 30mph for a sharp bend).
After the overwhelming number of reports, Waze removed all the reports from the map. They didn’t remove the ability for people to make reports in the app! So for quite a long time, the reports just went into a black hole.
Now Waze are trying to “cluster” the reports to get something a bit more meaningful. But these reports are only visible to Beta map editors and, frankly, the clustering isn’t working well.
So the reports you are making are only visible to Beta editors and they may well not be much use.
There are a couple of suggestions that might help you in sorting out speed limits. Personally, I carry a Digital Voice Recorder in the car - when I see a problem I make a quick voice note and sort it out when I get home. If you have a Dashcam, this could also be very useful to go back over a recent journey.
There are also a couple of user-created phone apps that work with Waze to report speed limits. These apps effectively allow you to create a precise and distinct User Report with the speed limit information. You can then go to WME and implement the changes. Note that, as mentioned above, URs do not always show up immediately - they can sometimes take a few days, particularly if there are server delays or they were reported as part of a long drive.
You can find a couple of them here: WURM: Waze Update Request Marker and Waze Speed Limit Button. I can’t tell you much about them because they’re Android only (I have an iPhone). They may even be versions of the same thing, based on reading the first post of one.
Also bear in mind that, as a level 1 editor, you may need to request segments to be unlocked if they are locked above your level.
:mrgreen:
Thank you for the evolution lesson to where we are now.
Extremely useful information.
I also use an IPhone (5) and no Android.
I am trying to deal with 2 scenarios.
The first is that I would like to fill in the blanks in terms of speed limits for many segments within perhaps 5-10 minutes from my house.
The shape of the area is similar to a rectangle.
As some editors have suggested, a laptop in the car tethered to a SmartPhone and opened on the WME would be great (I think).
But, I am worried about my 2 Gb/month dataplan.
So, a printed map and a pen will probably be the method to use while I drive.
Since I do not have a navigator I will pull off the road on a periodic basis to make notes on the paper map.
Oh, by the way, here in Ontario, Canada we have laws against ‘distracted driving’ and I will definitely follow the rules of the road.
Scenario 2 is driving to clients, etc.
I actually already own a voice recorder however I am worried about pressing its buttons to record anomalies (see above).
I could start recording when leaving and stop recording when arriving but I would then have to replay a lot of audio.
Which leads me to ‘Hey Siri’!
I have used this great app to send myself and others text messages and Emails.
It is also does voice recordings (of course).
IOW - no touching of buttons = (hopefully) no distracted driving tickets.
I had no idea!! Sorry for the false information, allanc275.
NP at all.
I am very analytical by nature (and profession) so the complete historical explanation was very interesting to read.
Somehow, I get the feeling that there is soooo much more about Wave that I do not know nor do I know what to ask or where to look.
Often with any topic (not specifically Waze), you need to know the question before you can find out information.
However, sometimes one does not know the question so you can not find the information.
Or, the information is disjointed and does not follow a natural flow.
BTW - I hate writing documentation as do most other technicians and would rather do the technical work anytime :oops:
Have you seen the Wazeopedia? It’s filled with… well… everything related to Waze!
Yes, I have read various wikis.
However, I missed the part about the Wave App, SL changes and the black-hole.
On the other hand perhaps it has not been updated with certain aspects.
We both did because it wasn’t on the Wiki. It was on the forums!
We both did because it wasn’t on the Wiki. It was on the forums!
[/quote]
Cool. Good find!
Well, I think that the two sources really serve different purposes.
In their simplest form:
Any Wiki, not saying just Waze, should have current instructions and is also a ‘how-to’.
You click on a topic in a menu, it is explained, etc.
So, you go to the URL with the index, scroll down to speed limits (or similar), click on the link and Voila - you get the instructions/tutorial that are current.
The history of how we got to where we are now, as kindly provided earlier in this topic, can be in the same Wiki or another.
I am not a Wiki specialist so I do not really how a Wiki should be completely organized.
So, to me, the Wiki should be read for instructions before one undertakes a task.
However, it is available for reference on an on-going basis.
Forums are different in purpose (IMHO).
As per your example, someone had a problem and wanted to resolve it.
So, they asked the community at the time of the issue which is great.
However, any given thread or post may or may not be obsolete by the time that we read it.
Problems get resolved, a feature might be removed, etc.
Hence the need for the Wiki which should be current and is the ‘instruction manual’.
Thoughts?
I agree completely.
I talked to my superiors and they ruled out his going in the wiki because this is not a very common topic and that this is info about the client app (Wazeopedia is WME, not Waze app). Not many clients visit Wazeopedia. Also, the cluttering as discussed before by iainhouse is only for Beta Testers, and Wazeopedia doesn’t really cover Beta Testing in general.
I’m still new at this, too.
True.
I should where you’re going with this, and like this idea. Let’s still not forget about the Forum Rules where they ask that you search in the Forum, FAQ and Support first. The way I see it, you’re replacing these…? I can, however, see a Glossary being put into Wazeopedia and updated constantly.
So, where is all of this material for the Waze App?
I definitely understand what some are saying about this documentation but the WME editor and Waze APP are intertwined to some extent.
Maybe more in the past and less today and in the future - but they are still ‘related’.
If there is currently a unique location for the Waze APP forums, supports, FAQs, etc. then perhaps the two entities should link to each other?
If input to the Waze APP drops notes, requests, etc. onto the WME maps then they are linked, no?
Waze App Forums, Waze App Support. These are designed for the less experienced Wazer (non-Editor). Right now, I (personally) don’t see and need to join them together. Maybe there’s something I’m not seeing?
Yes, URs from the client app show up in the WME. Apart from conversations (Reporter to Editor on URs) and changing the client map, there’s really no other link between the two. The Waze App is completely different from the WME, too.
However, if you’d like to request something big like this(which is where I see this comvo heading), I recommend doing it in the Feature Request Forum (there’s a Forum for that!)
Thank you for the links as I do not recall seeing the Waze App links before!
When I said ‘inking them together’ (or whatever the words were) I meant at a very high level not necessarily within a thread unless necessary.
They are related mostly in one direction WME > App and a little in the other.
I do not know if either (perhaps a small one or two liner) mentions the other near the top (or bottom) of the top page?
Something like, ‘if you need further information about the Waze App please click here’.
In my industry (IT) I see links to ‘related products’ all of the time.
They are related, though. When you first enter the forums, you can choose between Waze App or WME (et al). At any given time, each subforum will eventually related to another. You were right when saying that this is a one-way relationship, though!
Let’s not forget, Waze.com is designed for clients and editors. Wazeopedia is designed for Editors. The forums are designed for both (depending on the forum). Each website has different needs.
If this is what you’re suggesting, I would still recommend head over to the Feature Request forum. The people there know what they’re doing and your idea will go farther there. If you’d like, you can link it up to this topic (link). Good luck with your ideas there!
I do not think that it is necessary.
After quickly browsing through all of the links that you have provided - I can say that we are on the same page.
I did not know that the top level page for the editor and app forums existed in one place. :oops:
It is a common problem, not specifically with Waze, that when you search for something in a browser you will not necessarily pop into the page that would have been so handy that you linked to.
So when I was one or more levels down in the hierarchy, I do not think that I clicked on whatever link would have taken me back to your top-level ‘forums’ page.
Make sense or am I babbling?
Makes perfect sense. Are we done here?
Yes.
Until the next time something crops up. 