Road Types (USA) – Airports and Surrounding Area
The US Road Types are being overhauled and driveable roads are being discussed in detail here.
I propose that those who wish to engage in a lively discussion on guidance relating to Runways, Taxiways, and other features around airports such as airport parking lots, rental car facilities, taxi staging areas, etc. Some of these topics are covered in other areas such as Parking Lots and Private Roads, but I think Waze would benefit from standardization around airports. The more consistent Waze is around major travel hubs, the better the user experience will be. The product of these discussions could be used to enhance or complement existing wiki pages.
A couple examples to start:
Runways - Naming
I would recommend using the FAA identifier rather than the ICAO identifier for runway markings. I think if you try to standardize on ICAO (KXXX) you will just end up confusing the masses -- most people recognize the FAA identifier. Further, some airfields don't have an ICAO identifier but all airfields have an FAA identifier.
Runways - Elevation
I would recommend setting the standard that all runways should be set to elevation = ground (0). In the rare instances where a road crosses under a runway's path, the road should deviate elevation to the negative. In the extremely rare case where a runway and a road intersect, no junction should be formed and the road should deviate elevation to the positive so it appears over the runway. This would make it easy to standardize on 0 for runway elevation, since the vast majority of runways never cross paths with a road.
Taxiways
I would recommend providing guidance that airport taxiways should not be mapped. In many larger airports the taxiways can be quite complex, would appear the same size/color as runways, and would reduce the distinctive appearance of the runways being identified as runways. Google Maps solves this by using a thinner, lighter line for taxiways. Waze should just omit them.
Restricted Access Roads
I would recommend that segments which require SIDA or other TSA, DHS, or airport authority credentials to access should not be mapped in Waze. Some may disagree - but until Waze offers some way to alert the user that their destination may be in a restricted area like google, navigon, garmin, and some others do - I don't think it is safe or prudent to even have the ability to possibly maybe route someone onto airport property.
I would concede that you could map the segments as long as they were never connected to the main driveable network (similar to railroads and walking paths), but we would need a way for WME Validator to flag that. Ideas?
Standardized Airport Feature Naming (Roads, Lots, Places, etc)
I propose that those who wish to engage in a lively discussion on guidance relating to Runways, Taxiways, and other features around airports such as airport parking lots, rental car facilities, taxi staging areas, etc. Some of these topics are covered in other areas such as Parking Lots and Private Roads, but I think Waze would benefit from standardization around airports. The more consistent Waze is around major travel hubs, the better the user experience will be. The product of these discussions could be used to enhance or complement existing wiki pages.
A couple examples to start:
Runways - Naming
I would recommend using the FAA identifier rather than the ICAO identifier for runway markings. I think if you try to standardize on ICAO (KXXX) you will just end up confusing the masses -- most people recognize the FAA identifier. Further, some airfields don't have an ICAO identifier but all airfields have an FAA identifier.
Change to: (e.g., "SMF Runway 16R-34L".)Name each runway using the FAA airport identifier, the word runway, and the runway designations with the lower number first (e.g., "KSMF Runway 16R-34L".)
Runways - Elevation
I would recommend setting the standard that all runways should be set to elevation = ground (0). In the rare instances where a road crosses under a runway's path, the road should deviate elevation to the negative. In the extremely rare case where a runway and a road intersect, no junction should be formed and the road should deviate elevation to the positive so it appears over the runway. This would make it easy to standardize on 0 for runway elevation, since the vast majority of runways never cross paths with a road.
Taxiways
I would recommend providing guidance that airport taxiways should not be mapped. In many larger airports the taxiways can be quite complex, would appear the same size/color as runways, and would reduce the distinctive appearance of the runways being identified as runways. Google Maps solves this by using a thinner, lighter line for taxiways. Waze should just omit them.
Restricted Access Roads
I would recommend that segments which require SIDA or other TSA, DHS, or airport authority credentials to access should not be mapped in Waze. Some may disagree - but until Waze offers some way to alert the user that their destination may be in a restricted area like google, navigon, garmin, and some others do - I don't think it is safe or prudent to even have the ability to possibly maybe route someone onto airport property.
I would concede that you could map the segments as long as they were never connected to the main driveable network (similar to railroads and walking paths), but we would need a way for WME Validator to flag that. Ideas?
Standardized Airport Feature Naming (Roads, Lots, Places, etc)
bgodette brought up a good point here - there could be value in standardizing the naming of some common features at major airports such as cell phone waiting lots, arrivals/departures access, rental car location, etc.bgodette wrote:That discussion will likely lead to standardized naming of important navigational points that aren't normal Places, eg "SFO - Rental Return" "SFO - Cell Waiting" "DIA - Arrivals East" etc.
Re: runways