Place points. 12345 Main St can be the point’s GIS address, but the point itself will route to the actual spot IF it is close enough to the parent road to actually drop the pin. There is a limitation as to how far you can place a point from the named street, and sometimes you can place one and then move it, other times not.
Basically, the place points are Waze’s version of what the routing engine used to do with poorly placed Google points… route to the nearest road rather than to the named street, so we still have to be careful and ensure that there is a PLR or PVT road leading to the point.
This works for apartments, business complexes, etc…
So for an apartment/Condo complex, and I would tag the place as “other” rather than Private residential, using “12345 Main St Bldg 23” will allow a direct search based on those parameters.
Assuming that the access control into the private development is configured properly, guests should be routed to one of the entrances with a guard shack, call box, or some other way for the public to enter.
It is important to remember that the ENTIRE address needs to be spelled out in the name. Just using “Building 9” like in my example is going to result in the search engine not returning a result for “12345 Main Bldg 9” but by setting it to “12345 Main St Building 9” the auto-fill is going to present a list of options after typing “12345 Main”
The thing that Fredo and I have been discussing is a way to cause the building to actually render on the app. So far, mine has not for two sizes. I’m up to 27m x 27m now and we’ll see if it renders tomorrow. I have local gas stations that are around 31m square and they render (barely). If it’s going to take much more than 27m x 27m, it’s going to be impractical for many complexes, as my 27m x 27m encompasses the largest back yards in my complex (most are 5m x 5m, these are 5m x 7m) as well as the courtyard in front of the building. I might be able to push to 31m x 31m, but it’s going to mean the buildings will have some overlap.
Still not rendering at 27x27. I’m up to 30x33 now, and that includes about a 50% overlap of the next building, so it doesn’t look like getting decent rendering is going to be possible for smaller apartment/condo buildings with only 3 or 4 units.
Longer apartment houses that are a couple hundred feet long shouldn’t be a problem.
What you are suggesting is that with all the buildings having a searchable number xx/street name/building number which may cause a complex with a single address and with 30 or more buildings to give 30 or more possible address possibilites.
Thus back to my original context of having a way to route to the complex main street address, then have a layer that shows the unit number so as you are driving through the complex you can see in on the app as you’re driving. If you don’t cross the address point, but keep going to find Waze tries to circle back around to the address point. I’m generating this WME Feature Request to allow for a way to identify buildings in an office complex or unit numbers in an apartment complex that share the same main address. If I have a general idea of where in the complex a number is, I can manually route myself there. The biggest issue is that it’s not always easy to see apartment / office building numbers from the parking lot. But if there was a layer visible on the client, and parking lot roads visible on the client map, then I can more easily find my way to the building number.
Ya, it’s definitely not an ideal situation the way it is.
At 30x30 the building is rendering, however, now the quandary…
If I label it “Building 9” it comes up in the search results… along with 5 or 6 additional “Building 9” in other cities. It renders on the app as “Building 9” and doesn’t look too bad. It routes properly along the PLR to the building. Included in the auto-fill list is the general address for the development.
If I change the name to 12635 Franklin Ct Building 9, it then no longer appears the same in the search results. I am only given one search option, it DOES display Building 9 in the result, but it uses the development address stop point on the parent street and does not use the PLR.
Also, with the area so small, and the name that long, the display is incredibly crowded and it would not be practical even for filling in this 11-building development:
Confirmd today on the Jan 10th tile update.
I renamed the area back to “Building 9” (and added a Building 10) and it is searchable by that name and routes to the building.
If I name it using the complete adress including building 9, is only routes to the stop point on the street.
Next step, convert to Point and see if the routing is consistent… especially given that at 30x30, areas are simply not practical and too cluttered.
I don’t want to undo their work, but also I don’t see any usefulness currently, unless you are visiting someone in those apartments, and when you leave you can’t find your way out, which is unlikely. So I deleted a few obviously unhelpful segments, and straightened some out, but left the bulk of them there, in case someone tries some building number magic later.
I’m thinking we may want a Wiki page at least expressing that mapping apartment complex roads (as parking lot or private roads) is currently not helpful. Something along the lines of
I think the full address with building xx is simply too large. I think the area places are too large and get in the way of editing on WME. The general idea is for apartments or condos with a single address for the whole complex to have a layer or something like that with a simple buildng number viewable enough to see and drive up to that building. It is perhaps more important when a covered parking is parallel to the plr when you really can’t see the numbers on the building. Imagine a huge complex with at least 30 buildings. It’s very difficult to find the building numbers even if you took a picture of the complex map. Simpler is better, so just a number is better than a long address plus building number. I just want a number. Don’t even need the word “building”. The other issue is searching in navigation the long address plus the word “building” #xx would likely get truncated in the client search windows anyhow. Right?
As I indicated, there are a couple of issues.
When I put the complete address in the “Name” field, I could not get routing to the building. It would ONLY go to the stop point on the road.
Now, “Franklyn Webster Square #9” would likely work, though possibly truncated, but most people navigating to apartment/condo are doing so by address.
The alternative is to use the building number… but that is not specific enough, and while possibly useful in the short term, more than a few developments will quickly flood the map and make the search impossible… especially given Waze’s penchant for ignoring distance (I plugged in Carl’s Jr and it gave me a result in Mexico, but no local results)… and I don’t “get” the ignoring of distance, I routinely have Waze return results that are 2000 miles away, yet the app cannot route more than 1000 miles.
So areas need to be too large to render
Points do not render, and if the address is in the searchable name, Waze routes to the stop point.
We really have no “good” solution other than to use points and make sure that the HN is removed so the address is “detached” from the street.
Places are still workarounds, and not effective at all in complexes with smaller buildings. What we need is a new layer probably that would allow things such as zip codes, state lines, county lines, subdivisions if appropriate, and my personal pet peeve the apartment and condo complexes with one address and multiple buildings. Still, I maintain, I don’t need full address and building number, I just need the number once I get into the complex. Maybe a popup button that allows me to turn on building numbers that are clear and large enough to be read. Doesn’t “have” to be navigable, just visual really. This would be particularly important in larger complexes with MANY buildings which would be hard to find.
And, of course, the same issue with Mobile Home communities, etc. One address for the whole community and each mobile home has a lot# or space#, private driveway, etc. Wish there was at least a unit,suite,lot, etc field in the place address form…
The mobile home community can be dealt with using a bit of a hack…
Unless it actually has a name, name the private road to match the mobile home park name.
At that point, the space number becomes the house number, and would be navigable by Waze.
Not possible if the mobile home park name matches the parent street, but that’s somewhat rare.
The issue with mobile home communities is the size of the area size. Currently area sizes 30m x 30m are rendering. I wouldn’t personally want each individual mobile home number being rendered, like I wouldn’t want to see every apartment number rendered. Mostly the issue I started with is a larger building like an apartment complex with difficult to decifer sequence of building numbers having a number hover over the building entrance from the plr. Someone mentioned TX doesn’t do plrs in apartment complexes, however that’s not really the national standard. Basic plr roads are fine without doing every nook and cranny. If we had a way to render smaller numbers as a layer then maybe mobile homes. Ultimately I wouldn’t want to drive past a mobile home or apartment complex and be forced to see all their numbers. Ideally a new layer for the app that could be turned on if desired to see apartment building numbers , or villages within a city, or zip codes etc. But easy to turn off from the app.
As with my “Building 9” experiment in my condo complex, it would only take a few editors adding these to end up with a search result in the app that looked like:
Space 37
Space 37
Space 37
Space 37
Space 37
Space 37
Space 37
Space 37
Space 37
Space 37
Space 37
Space 37
Thus rendering it useless.
I was referring to using actual HOUSE NUMBERS attached to the PVT road segment… only possible if the segment is named (and the name and address are not duplicated elsewhere in the city).
This would be completely routable, without the need to input the name of the park… just the space number and street/city
I’ve read this thread with great interest as Hawaii has a development philosophy of using neighborhood areas zoned as single dwelling apartment “buildings”. They all have the same street address but individual unit numbers to identify, much like trailer parks. I’ve jumped in here because one very large area of O’ahu has developed quite quickly and I can only surmise that I will be getting more UR’s about not being able to navigate to individual residences.
Anyhoo…
Did anybody find a solution?
Download the Beans app from the play store. It is what we use as a food delivery driver. It shows you the building each apt is in with live gps so you know where to exactly go because no in apts realize it’s impossible to find a Bldg number or address in the dark because no complex lights them up.
So I deleted a few obviously unhelpful segments, and straightened some out, but left the bulk of them there, in case someone tries some building number magic later.