sketch wrote:I agree on runways except that there's no reason to include any airport identifier, so "Runway 4R/22L".
I'm ambivalent on this one. I went with what's on the Revised Road Types (USA) to start, and tweaked it to be FAA instead of ICAO. I do think having the airport code in there could clutter up the map. I can also see very very slight value in having it there if it displays in the app. I do lean towards agreeing with you though - leave the identifier off and just call it "Runway 16-34" or "Runway 16/34" whatever the standard is
sketch wrote:I agree on leaving restricted-access roads off the map, and this was a significant part of that former discussion. The community agrees on this, I believe.
Excellent. Once we have a chance to codify it in the wiki, I will start reaching out to AMs and suggesting they clean up some of the on-airport roads
sketch wrote:I think some of this is in the Wiki already, I'm just not sure where. Agreed some of it should be in the Road types article.
Agreed. When the dust settles from the public roadway changes, we can pick this one up.
I think something that AMs should be doing ASAP is checking their airport Places to make sure the stop point is in the right place now that they're supported. I've run into a couple issues lately where Waze routed me around the back side of a very large airport - of course when I'm late for a flight