I have a delivery driver who used the paved road feature in the app to pave some service roads through the airport. He then submitted two URs asking that they be put in. I'm impressed about this effort and I wish there were more drivers like him. I applaud that he understand what to do when something's not right in Waze, but that's beside the point.

I informed him, as a general rule we don't label or mark the roads inside the property lines of the airport that aren't conducive to traffic. The roads to the terminals for passengers are the primary roads we'll put into Waze, but I also told him I'd check on a few things. ATL, IAH, MDW, MIA, FLL, MSY, SAT, AUS, SEA, LAS, DFW, ORD, BOS, NWK, LGA, don't have any of the service roads marked. LAX, DIA, PDX, and JFK do. Those were just some of the airports I had checke. I wasn't going to check all of the airports around the country.

My question is, are those roads really conducive to the typical Waze user? Do we really need to mark them all with private roads, or service roads? Is there a possibility that Waze would direct someone to a terminal using those roads? I'm not convinced on putting them in, as it's only going to benefit maybe 150 people out of the 3000+ that use Waze in S Florida. I haven't had any issues with it in while I was in San Antonio, or editing in Texas.

Another thing I noticed is the airports are set up entirely differently across the country. Some are landmarked, some have layers of landmarks, some have their airport codes in them, and others don't. I know this is asking a lot, but could we come to a general consensus about setting these all the same, throughout the country?