Changes

From Wazeopedia

Road types/USA

1,599 bytes added, 3 years ago
Exceptions: made caption visible to match Wazeopedia edit
The {{Freeway}} and {{Ramp}} road types each have their own special rules. The {{Major Highway}}, {{Minor Highway}}, and {{Primary Street}} types are designated using a set of minimum criteria, as explained [[#Highways|below]].
====Exceptions==== Occasionally, if deemed necessary for proper routing, a particular road's type may be set higher than as prescribed in these rules. If a road has a '''higher''' type than set forth in these rules, there may be a reason for it.  [[File:Connector.png|thumb|right|300px|Connector.png|Because the freeway exit is signed to the state route at the bottom of the image, and exiting traffic must use the road on the left to reach it, this road has been given the Major Highway type.]] One common reason for a road to be set to a higher type is if that road is a '''connecting road''' between two roads with higher types. Promotion of a connecting road is only warranted if the road is signed from one road ''to'' the other. For example, a freeway exit may be signed as to a particular highway, but the only way to get to that highway from the exit ramps is over a lesser road. Where such connections are supported by signage, the road type of the connecting road should match the lower of the two roads that it connects, up to major highway (In the USA a road may only ever be set to freeway if it meets the criteria of the [[Road types/USA#Freeway|Freeway]] section). Promotion of connecting roads preserves routing continuity and prevents Waze from pruning out valid routes. In rare cases, a particular road may require a '''lower''' type than as prescribed in these rules. Contact your regional coordinator before lowering the type of any road past the bounds of the rules.
Special rules are used to determine the road types of [[Creating and Editing a roundabout#Road type|roundabouts]] and [[At-grade connectors#How to label the connector type|at-grade connectors]].
*various County (or Parish) Highway systems, in some states
Waze's definition of "highways" includes all theseInterstate, US and state highways, but it also includes all other roads that are classified as arterial roads under the FHWA functional classification lists maintained by state governments, even though they may not necessarily a be part of any numbered highway system. In other words Functional classification of roads is determined more by how the roads are used than by how they are constructed, think of and the dictionary definition criteria are slightly different between urban and rural areas. Because of "this, some urban roads may be classified as arterials and have highway" ("a main roadtypes in Waze, espeven though they appear very similar to other non-highway roads. one connecting major towns or cities") rather than In using functional classification and numbered highway systems, the decision on which roads should be classified as highways rests ultimately with the legal definition of governments that build and maintain the termroads.
Waze distinguishes three classes of highway: {{Freeway}}, {{Major Highway}}, and {{Minor Highway}}.
=== Runway/Taxiway[[File:Service road.png|200px|Service road.png]] {{Anchor|Runway|Taxiway}} {{@||Runway/Taxiway}}===
[[File:Runways.png|right|300px]]Airport runways and private airstrips may be mapped using the Runway/Taxiway road type. The Runway/Taxiway type is for display only and must never connect to drivable road segments. If a drivable road and a runway cross, set the [[elevation]] of the road below that of the runway and ensure there is no connection. Draw each runway as a single segment and lock it to prevent lower-ranking editors from attaching a road. Do not form junctions where runways cross each other.
Name each runway using the word ''Runway'' and the runway designations with the lower number first and a hyphen between runway numbers (e.g., "Runway 16R-34L".) <!-- The preferred airport identifier is the [http://en.wikipedia.org/wiki/International_Air_Transport_Association_airport_code IATA] [http://en.wikipedia.org/wiki/List_of_airports 3-letter code], for example "SFO", "LAX", "JFK", etc. If the airport in question is not included in that list, use the [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code ICAO] [http://en.wikipedia.org/wiki/International_Civil_Aviation_Organization_airport_code#Prefixes 4-letter code] instead. If the airport is not included in that list use the [http://www.faa.gov/air_traffic/publications/atpubs/lid/lidhme.htm FAA identifier]. --> For the "City" field of runway segments, check "None" to avoid any chance of [[City smudge|city smudging]]. {{clear}}
[[File:Fly-inCommunity.png|right|250px]]
Despite its title, the Runway/Taxiway road type should never be used for an aircraft taxiway because it would render the same as a runway and confuse the display. Taxiways not intended for frequent access by street vehicles should not be mapped at all with any road type. Taxiways that do commonly serve street vehicles as well as aircraft, for example at [http://www.waze.com/editor/?zoom=5&lat=38.68054&lon=-120.98836&env=usa&layers=389 fly-in communities], may be mapped as Streets provided they remain disconnected from any runway.
{{clear}}
=== {{@|Driveways}} ===
Most Many residents of urban communities have very short driveways between the named road that they live on and the garage or carport on their property. In general these very short segments should not be mapped , because they have no name, would clutter the map in the client app, take a lot of time to draw, and would greatly increase the overall size of the Waze mapping database with very little return.
In the case of very long driveways, it may helpful to a driver to see the driveway mapped on the client app or even necessary for Waze to determine how to reach the destination. In those cases it may be prudent to add a road. See the article on [[Driveways]] for more information.
193
edits