Well, I’m really hoping we get some indication from waze that this is an acknowledged problem that will be fixed. But, if its not addressed at all, it seems to me that we will want to avoid using the category search triggers in place names.
I’m not seeing this, but maybe I’m looking in the wrong place.
Using precisely the trigger as the search name at least allows them to displayed in the instant results list while typing. It’s better than avoiding the name entirely and potentially not getting any results.
Sent using Tapatalk for Android 4.4.2
Again, I’m hoping that waze fixes the category searches so the proposed guidance will work the best.
But if they don’t, why won’t any standard name display all the results in the instant results while typing. In other words, if we use “Service Area” rather than “Rest Area” the results will still all be displayed in the instant results list while typing service area won’t they?
The problem with relying on the instant results is that if I don’t have a fast data connection, I may not get any instant results. If I then complete the search, if I’m using a category trigger, then potentially I don’t get any results. Again, if the category radius is fixed then this shouldn’t be a problem.
The standards are great. I am worried about this category search too, but nothing we do in the editor will change the fact that a search for “rest area” will perform a scenic overlook category search. It simply needs to be fixed – there’s no other solution.
Why is it called a Rest Area if there are no facilities? I thought the phrase Rest Area was derived directly from restroom, implying the availability of such facilities. Are there actually signs somewhere that specifically call a place with no facilities a rest area? Does MUTCD have anything to say about it?
The only times I’ve ever seen a no facilities sign is with like a parking area, picnic area, or scenic overlook sign to make clear that such places do not have such facilities. I don’t think it can officially be called a rest area without restrooms.
To have one search term which shows all areas nearby regardless of specific type where you can safely get off the highway.
Sent using Tapatalk for Android 4.4.2
Because rest areas are exactly that, an area to rest. When I moved to Miami, I stopped at rest areas to sleep, nothing else. They all had restrooms, but I didn’t need a restroom all the time. Also, look at it from a trucker’s perspective. They need places to pull over and sleep, too.
I brought up the same argument in the chat while we developed this. Many users do search “rest area” to find a restroom, but there are other reasons for rest areas – for example, many long-haul drivers (not just truck drivers!) will stop in a rest area for a quick nap. That’s why we’ll allow everyone to search “rest area”, but also hit them with the “no facilities” right after that, so they know to keep looking if they need to relieve themselves.
In Mississippi no-facilities rest areas are called “Parking Area”; in Tennessee there’s a “Truck Rest Haven”, but others mentioned “Rest Area” signed areas with no facilities elsewhere.
Teas has a mix of everything, but rest areas are rest areas. They built two new ones in between Austin and Dallas which are designated as “storm shelters”.
One small detail about naming the ramp from the freeway to the rest area – it should match the sign, and use the same format as unnumbered / numbered exits (as applicable). If the sign is just an arrow that says “Rest Area”, it should be named “to Rest Area”. If the sign says “Parking Area”, it should say “to Parking Area” even though the Place is called a “Rest Area”. If the sign says “REST AREA | LOUISIANA WELCOME CENTER”, then “to Rest Area / Louisiana Welcome Center”. If the sign says “REST AREA | TOURIST INFORMATION CENTER”, then “to Rest Area / Tourist Information Center”. If the sign is “Exit 34: Beckley Travel Plaza”, then “Exit 34: Beckley Travel Plaza”.
Makes sense, I’ll change it
Sent using Tapatalk for Android 4.4.2
One more thing: Where do we want to put the “official name” of rest areas that have their own official names?
For example, the Alabama Welcome Centers are named more than generically: http://www.dot.state.al.us/alabama_welcome_center.html
Alt name? In the description? Both?
I’m a fan of both, to support search and display.
Sent using Tapatalk for Android 4.4.2
Updated ramp names in my original suggestion post per sketch
[emoji1] and used a table in the forum.
Sent using Tapatalk for Android 4.4.2
The 2.5 mile limit is now item #247 on the bug list.
Sent using Tapatalk for Android 4.4.2
I updated the suggestion post with naming standards for specific vehicle only rest areas.
If there are no objections I’d lie to implement this in the wiki.
Ok. Agreed to all.
Once again we have a similar dilemma to city names. The map and navigation should reflect names and only names on posted signage but search results should reflect, or at least match, any colloquial name regardless of what may actually be posted there or en route.
Colloquial names and proper names not on signs should be added in the Alternate name field, and description. This way they work in search, are visible when the place is selected in the description, and are absent in navigation and the map.
Sent using Tapatalk for Android 4.4.2
I get that, but it still doesn’t get them to show in search results, thus creating the dilemma.
What do you mean? Alt names for places work fine in app search for me.