User:Thortok2000 View history

(Created page with "According to Google, there is a business called 'Total Wine & More' with the address of 6671 S Virginia St located in this building: https://www.waze.com/editor/?zoom=9&lat=3...")
 
 
(41 intermediate revisions by 2 users not shown)
Line 1: Line 1:
According to Google, there is a business called 'Total Wine & More' with the address of 6671 S Virginia St located in this building:
===== Intro/Summary =====


https://www.waze.com/editor/?zoom=9&lat=39.46533&lon=-119.78567&env=usa&layers=TBFTFFTTTTTTTFTFTTTTTTTTT
This guide is to help you with destination issues!


I zoomed way in to specify the building, but if you'll zoom out you'll notice it's much closer to the ramp than it is to S Virginia St.
It is currently a work in progress and should not be followed as a standard until it has been approved and added to the main wiki.  This is Thortok2000's personal sandbox and should be treated as such. =P


[b]So step 1[/b], click S Virginia St and add a house number for this building for 6671 (you'll have to put it in the middle of the parking lot sort of near the 6675 number since the maxium distance doesn't reach) and put the stop point at the entrance to the parking lot (near Sierra Center Parkway.)
== Destination Correcting ==


[b]Step 2[/b], add some parking lot roads (just the border and 'main lanes' of the parking lot should be sufficient, it's currently not standard to map every lane of a parking lot), making sure to include the drivable surfaces that are nearest any businesses and anywhere the parking lot connects to the surrounding streets.
It is a common complaint of most Wazers that their destination was not set at the correct location.  Knowing how to handle this kind of UR and fixing it for our Wazers will go a long way towards satisfaction in the product and continued usage, and possibly even recommending it to others!


[b]What the user will see after the fix[/b]:  Waze will route him onto S Virginia St and then into the parking lot, directly taking him to the front door of the business.  Note that it will only route the user on the parking lot roads you map, so if you only map the border, it will suggest that they not drive through the parking lot but instead travel around the border of it(However, this is generally 'close enough' that the user can figure out where to go from there.)  On the flip side, every parking lot road you add on the map will be permanently displayed for all users, for a slight additional amount of clutter (including users who are just driving past and not navigating within this parking lot) so until Waze changes how parking lot roads are displayed the current standard is to not map unnecessary lanes.
The irony of the situation is that often this problem is not actually caused by WazeWaze is currently growing a large list of mapped places, but where a place is not mapped, or not mapped correctly, other search providers like Google are still used as a fallback.


[b]Reason this happens[/b]:  Google has coordinates for 'just the address' and it has coordinates for the address by POI or business name (and possibly multiple POI's for multiple business names all sharing the same address).  It's silly that it does this, but it can result in a different location for the POI than for the address with no business name specified, even though it's the same address.  In this case, the POI for the business is closer to the ramp than it is to any other drivable surface currently mapped by Waze, including S Virginia St.
This page will attempt to explain in more detail why a user might get routed to the wrong spot and how you can work around it and/or fix it!


[b]Possible complication[/b]:  If the POI in google is slightly off from the building and/or even a correctly mapped parking lot road in the front of the building is still not 'close enough' to the location provided by Google that Waze is still mapping to the drivable surface behind the address, usually/sometimes adding the house number in Waze will fix that too but your best bet is to go into Google.com/mapmaker and submit a request to move the POI closer to the front of the building.  At that time you may also want to move the 'pin' for the 'address without a business name' to the correct location as well.
Take note that even after it's fixed, the app will not automatically update position data for already-obtained destinations! Even after an address has been adjusted or a place added or updated, the app will retain the stale search result's position data indefinitely and navigation will continue to fail. To correct this, remind the reporter to remove any existing instances of the destination in the recents and favorites lists and then search for the destination again from scratch.


I checked this specific location and the pin with the business name is sort of in the middle of the building but should be close enough if you add a parking lot road in front of it, that should be closer than the ramp behind it without an edit necessary in Google.  The pin for the address without a name is smack in the middle of the street a little north of the actual parking lot the businesses are in, exactly where it shows when searching that address in Waze. I'd go ahead and make the edits in Google for you but they're currently in maintenance.
=== Step 1: Get the Address in Question ===


[b]Variation[/b]:  Sometimes the POI information comes from a Landmark in Waze (normally not for simple businesses like this since they shouldn't be mapped, but for parks and airports and stuff.) If this POI provided by Waze is again closer to the 'wrong' drivable surface than the correct one, the same kind of thing can happen.  The POI for the landmark can be easily seen as the 'dot' in the middle that you use to move the entire landmark without changing the shape of it (after selecting it of course.)  The workaround for this is to leave the 'main' landmark with the correct shape, but no name, and create a tiny landmark near the entrance of the location that has the name.  This POI dot is also where the name shows up in the Waze client as well (if/when the user is at the correct zoom/angle to see the name come up at all.)
You can't fix anything if you don't know what address the user needs fixedSo, the first thing you'll need to do is ask them what the address they want fixed is.  This is not included in the report by default for privacy reasons; if the user wishes to give this information to you it is of course their prerogative.  But we can't fix it if we don't know what to fix!


[b]In the future[/b]: Make sure you also ask the user what, if any, business name they used to search with, as that will let you know which location Google is giving them.  You can also attempt to find this 'business name' yourself, like I did, based on the address alone, but getting that data from the user is more accurate as there could be multiple business listings in Google sharing the same address but for whatever reason not all located in the same place.  (In which case I recommend 'report duplicate' in Google's mapmaker or at the very least repositioning the offending data.)
=== Step 2:  Check for Business Name (If Applicable) ===
 
As will be the case with a good portion of UR's for destination issues, the location can easily be in a commercial area.  If so, chances are it's referring to a business.  It's often good to ask your Wazer what the business name is when asking for the address, but if they only give you the address you can attempt to google a business name yourself (or if they only give you the business name you'll need to look up the address for it, too.)  To ensure the problem doesn't happen again and to be a good editor, you'll need both business name and address when correcting businesses.
 
=== Step 3:  How to Fix ===
 
==== Nudging House Number in Waze ====
 
Setting a House Number in Waze is easy.  You can follow the instructions [[House_Numbers_in_WME|here]].  Also remember to set the stop point.  You should pretty much always do this every single time you go to correct an address, even if you wind up also doing one or more of the other methods.
 
If the house number already exists, give it a 'nudge', moving it by at least one pixel, and save your work.  This will ensure that the house number for that street and city (and any street/city combination in the alt names) of the segment that house number's stop point is on, will be searchable destinations in Waze and override matching data from other providers.
 
This only helps when searching by address, though.  Note that the stop point must be on a segment with the street's name that the address includes. You are currently unable to set a stop point anywhere else, using the House Number system.
 
For situations where you would rather route to the 'closest drivable surface', use place points.  When a residential place point is added, it will override the house number system.  For businesses however, it's always good to nudge the house number to be used as a fallback, even if a place point also exists, in case a user searches for the business by address instead of by name.  And it's still a good habit to be in for residential areas, even if a point exists!
 
==== Put a Drivable Surface Closer ====
 
Most destination search results, including all searches done by business name instead of by address, are going to be either from a 3rd party provider such as Google, or routing to a place mapped in Waze.  When this is done, coordinates are given to Waze and Waze sets the checkered flag at that exact spot, and then says you have reached your destination when you get to the closest mapped drivable surface to that spot.  Usually this is all that's needed for proper routing, but it can sometimes cause errors, which is why we get UR's about it!
 
While Waze's area places have a stop point you can set that fixes the issue quite easily, point-type places do not.  In some cases it would be against the standard to move the point place any closer to the road, or the use of a non-Waze search result is common enough that we may have to map roads closer to the coordinates provided by the search result anyway.
 
If the closest drivable surface is incorrect, typically the road 'behind' the location, then this issue is easily fixed by mapping a drivable surface closer.  This most commonly means the [[Best_map_editing_practice#Parking_Lots|parking lot]] in front of the address for business locations.  For residential, it might mean mapping the [[Driveways|driveway]].  Either way, make sure to follow standards!
 
This is not an acceptable reason to map a drivable surface that doesn't exist.  If you have nowhere to map a drivable surface closer, you will have to use the final method.
 
==== Mapping a Place in Waze ====
 
This is well covered in the [[Places|places wiki]].  Make sure to map them to the standard.  The reason this is pertinent to destination issues however is that by adding (or updating) a place in Waze, it provides a better search result than erroneous data in other providers, such as Google.  The more accurately you map a place, the better the data in Waze will be for all future Wazers trying to find this destination!
 
For routing issues, you may want to slightly nudge the point (or stop point of an area) closer to the drivable surface you want the destination to be.  Make sure to follow standards as you do so, though.
 
=== Educating the User:  How to do this in the app ===
 
Most users don't have access to the WME to make changes themselvesEven if they do, all place changes by rank 1 editors are automatically PURs to be approved by higher level editors, until they become 'trusted.'
 
You can't mess with house numbers or mapping drivable surfaces closer in the app.  But when it comes to places, those ''can'' be done in the app.  Either by you, or by any other user that wishes to help improve the map, even if they've never signed in to WME.  Whenever anyone makes an edit to a place, whether it's in WME or the app, and they are 'trusted', the edit goes through automatically.  If they are not trusted, or they are suggesting an edit to a place that's locked higher than their editor rank (and anyone who's never been in WME is treated as rank 1), then it comes through as a PUR (even if the edit is made in WME instead of the app).
 
Unfortunately, there's not an easy way to communicate with people who submit PUR's, like there is with UR's.  You can only either approve or deny.
 
To that end, if you encounter a UR with a destination issue, it's recommended to do everything you can to fix it yourself.  Only after doing so should you recommend the possibility of submitting PUR's instead of UR's.  Below is a breakdown of the three methods of submitting PUR's (or making edits, if trusted) via the app.  Here is some suggested verbiage for closing a destination issue UR:
 
:''I've gone ahead and updated Waze's information for this destination.  In the future, the best way to report this would be to provide information directly via the app!  After searching for the destination, but before hitting 'Go', you can scroll down and suggest an edit or report a problem.  If you are physically at the correct location, you can also report a 'place update' instead of a 'map problem' to create a new place.  And a final option is to hit the camera icon after arriving at a destination.  Any of these methods adds or updates the data in Waze so that it can be used instead of using bad search result data from Google or other providers.  You even score points when you do this!  Thanks for helping to make the Waze map better for everyone!''
 
:''Want to take even more direct action in improving the map?  Become a volunteer map editor like us!  Then you can edit anywhere you've driven from the comfort of your web browser!  To begin, just go to https://www.waze.com/editor  We sure could use your help!''
 
==== Suggest an Edit / Report a Problem ====
'''Best method''':  After searching for the destination, but before hitting 'Go', you can scroll down and suggest an edit or report a problem.
 
''Pros'':
* Don't have to be physically at the location, can do from anywhere.
* Don't have to take a picture.
 
''Cons'':
* Has to already be mapped in Waze or those options don't appear.  Doesn't work when choosing a search result from another provider.
 
==== Submit a Place Update ====
Report a 'place update' instead of a 'map problem' to create a new place.
 
''Pros'':
* Based on your location, suggests road names and possible duplicates while creating place.
* After creating the place, it is now in Waze and can be edited using the first method (the confirmation screen for creating a new place gives an option to edit additional details).
 
''Cons'':
* Requires that you take a picture.
* Requires that you are at or near the intended location.
 
==== Submit a Photo Reminder ====
The app, by default, prompts to submit a photo when you reach your destination.  This is essentially the same as submitting a place update (and includes the same pros and cons), although it copies the name from your search resultIf your search result was already a Waze place, it updates that instead of making a duplicate.
 
''Pros'':
* Helps prevent duplicates of Waze places if the Waze search result is used.
* Confirms that you're already near the right spot or you wouldn't get the reminder.
* Copies name from search result if it came from another provider.
* Setting is enabled by default to remind people to help submit place updates.
 
''Cons'':
* Requires that you take a picture, even if place already exists in Waze.
* Requires that you set your destination in Waze.
* Can be turned off and cannot be used if it was not turned on before you got there.

Latest revision as of 19:42, 20 August 2015

Intro/Summary

This guide is to help you with destination issues!

It is currently a work in progress and should not be followed as a standard until it has been approved and added to the main wiki. This is Thortok2000's personal sandbox and should be treated as such. =P

Destination Correcting

It is a common complaint of most Wazers that their destination was not set at the correct location. Knowing how to handle this kind of UR and fixing it for our Wazers will go a long way towards satisfaction in the product and continued usage, and possibly even recommending it to others!

The irony of the situation is that often this problem is not actually caused by Waze. Waze is currently growing a large list of mapped places, but where a place is not mapped, or not mapped correctly, other search providers like Google are still used as a fallback.

This page will attempt to explain in more detail why a user might get routed to the wrong spot and how you can work around it and/or fix it!

Take note that even after it's fixed, the app will not automatically update position data for already-obtained destinations! Even after an address has been adjusted or a place added or updated, the app will retain the stale search result's position data indefinitely and navigation will continue to fail. To correct this, remind the reporter to remove any existing instances of the destination in the recents and favorites lists and then search for the destination again from scratch.

Step 1: Get the Address in Question

You can't fix anything if you don't know what address the user needs fixed. So, the first thing you'll need to do is ask them what the address they want fixed is. This is not included in the report by default for privacy reasons; if the user wishes to give this information to you it is of course their prerogative. But we can't fix it if we don't know what to fix!

Step 2: Check for Business Name (If Applicable)

As will be the case with a good portion of UR's for destination issues, the location can easily be in a commercial area. If so, chances are it's referring to a business. It's often good to ask your Wazer what the business name is when asking for the address, but if they only give you the address you can attempt to google a business name yourself (or if they only give you the business name you'll need to look up the address for it, too.) To ensure the problem doesn't happen again and to be a good editor, you'll need both business name and address when correcting businesses.

Step 3: How to Fix

Nudging House Number in Waze

Setting a House Number in Waze is easy. You can follow the instructions here. Also remember to set the stop point. You should pretty much always do this every single time you go to correct an address, even if you wind up also doing one or more of the other methods.

If the house number already exists, give it a 'nudge', moving it by at least one pixel, and save your work. This will ensure that the house number for that street and city (and any street/city combination in the alt names) of the segment that house number's stop point is on, will be searchable destinations in Waze and override matching data from other providers.

This only helps when searching by address, though. Note that the stop point must be on a segment with the street's name that the address includes. You are currently unable to set a stop point anywhere else, using the House Number system.

For situations where you would rather route to the 'closest drivable surface', use place points. When a residential place point is added, it will override the house number system. For businesses however, it's always good to nudge the house number to be used as a fallback, even if a place point also exists, in case a user searches for the business by address instead of by name. And it's still a good habit to be in for residential areas, even if a point exists!

Put a Drivable Surface Closer

Most destination search results, including all searches done by business name instead of by address, are going to be either from a 3rd party provider such as Google, or routing to a place mapped in Waze. When this is done, coordinates are given to Waze and Waze sets the checkered flag at that exact spot, and then says you have reached your destination when you get to the closest mapped drivable surface to that spot. Usually this is all that's needed for proper routing, but it can sometimes cause errors, which is why we get UR's about it!

While Waze's area places have a stop point you can set that fixes the issue quite easily, point-type places do not. In some cases it would be against the standard to move the point place any closer to the road, or the use of a non-Waze search result is common enough that we may have to map roads closer to the coordinates provided by the search result anyway.

If the closest drivable surface is incorrect, typically the road 'behind' the location, then this issue is easily fixed by mapping a drivable surface closer. This most commonly means the parking lot in front of the address for business locations. For residential, it might mean mapping the driveway. Either way, make sure to follow standards!

This is not an acceptable reason to map a drivable surface that doesn't exist. If you have nowhere to map a drivable surface closer, you will have to use the final method.

Mapping a Place in Waze

This is well covered in the places wiki. Make sure to map them to the standard. The reason this is pertinent to destination issues however is that by adding (or updating) a place in Waze, it provides a better search result than erroneous data in other providers, such as Google. The more accurately you map a place, the better the data in Waze will be for all future Wazers trying to find this destination!

For routing issues, you may want to slightly nudge the point (or stop point of an area) closer to the drivable surface you want the destination to be. Make sure to follow standards as you do so, though.

Educating the User: How to do this in the app

Most users don't have access to the WME to make changes themselves. Even if they do, all place changes by rank 1 editors are automatically PURs to be approved by higher level editors, until they become 'trusted.'

You can't mess with house numbers or mapping drivable surfaces closer in the app. But when it comes to places, those can be done in the app. Either by you, or by any other user that wishes to help improve the map, even if they've never signed in to WME. Whenever anyone makes an edit to a place, whether it's in WME or the app, and they are 'trusted', the edit goes through automatically. If they are not trusted, or they are suggesting an edit to a place that's locked higher than their editor rank (and anyone who's never been in WME is treated as rank 1), then it comes through as a PUR (even if the edit is made in WME instead of the app).

Unfortunately, there's not an easy way to communicate with people who submit PUR's, like there is with UR's. You can only either approve or deny.

To that end, if you encounter a UR with a destination issue, it's recommended to do everything you can to fix it yourself. Only after doing so should you recommend the possibility of submitting PUR's instead of UR's. Below is a breakdown of the three methods of submitting PUR's (or making edits, if trusted) via the app. Here is some suggested verbiage for closing a destination issue UR:

I've gone ahead and updated Waze's information for this destination. In the future, the best way to report this would be to provide information directly via the app! After searching for the destination, but before hitting 'Go', you can scroll down and suggest an edit or report a problem. If you are physically at the correct location, you can also report a 'place update' instead of a 'map problem' to create a new place. And a final option is to hit the camera icon after arriving at a destination. Any of these methods adds or updates the data in Waze so that it can be used instead of using bad search result data from Google or other providers. You even score points when you do this! Thanks for helping to make the Waze map better for everyone!
Want to take even more direct action in improving the map? Become a volunteer map editor like us! Then you can edit anywhere you've driven from the comfort of your web browser! To begin, just go to https://www.waze.com/editor We sure could use your help!

Suggest an Edit / Report a Problem

Best method: After searching for the destination, but before hitting 'Go', you can scroll down and suggest an edit or report a problem.

Pros:

  • Don't have to be physically at the location, can do from anywhere.
  • Don't have to take a picture.

Cons:

  • Has to already be mapped in Waze or those options don't appear. Doesn't work when choosing a search result from another provider.

Submit a Place Update

Report a 'place update' instead of a 'map problem' to create a new place.

Pros:

  • Based on your location, suggests road names and possible duplicates while creating place.
  • After creating the place, it is now in Waze and can be edited using the first method (the confirmation screen for creating a new place gives an option to edit additional details).

Cons:

  • Requires that you take a picture.
  • Requires that you are at or near the intended location.

Submit a Photo Reminder

The app, by default, prompts to submit a photo when you reach your destination. This is essentially the same as submitting a place update (and includes the same pros and cons), although it copies the name from your search result. If your search result was already a Waze place, it updates that instead of making a duplicate.

Pros:

  • Helps prevent duplicates of Waze places if the Waze search result is used.
  • Confirms that you're already near the right spot or you wouldn't get the reminder.
  • Copies name from search result if it came from another provider.
  • Setting is enabled by default to remind people to help submit place updates.

Cons:

  • Requires that you take a picture, even if place already exists in Waze.
  • Requires that you set your destination in Waze.
  • Can be turned off and cannot be used if it was not turned on before you got there.