ArcGIS REST Services Directory Login
Home > services > PW > Driveways (FeatureServer) > Driveways Help | API Reference
JSON

Layer: Driveways (ID: 0)

View In:   ArcGIS Online Map Viewer

Name: Driveways

Display Field: Name_Needed

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Generalized depiction of driveways in the County. (1) Driveway approaches are broken into three general classifications, residential driveway approach, commercial driveway approach and temporary construction approach. Commonly overlooked design issues include inadequate radii at the intersection with the roadway, excessive approach grades and grade changes within the driveway approach area, consideration of water runoff, inadequate width, and inadequate entering sight distance. Existing driveways may be reconstructed to meet current county standards. No person, party, firm, corporation, or entity shall construct, or alter any approach from any abutting property to any county road located in unincorporated Chelan County, permanently or on a temporary basis, without first obtaining or having an approach permit from the department of public works. A copy of each driveway approach permit shall be available for inspection at the site during the life of the permit.</SPAN></P><P><SPAN /></P><P><SPAN>(2) A residential driveway approach is used to serve two single-family residences (primary or accessory residences). Driveways serving as access to more than two single-family residences (primary or accessory) will be considered a shared residential driveway.</SPAN></P><P><SPAN /></P><P><SPAN>(3) A shared residential driveway will be the minimum standard road used to serve three or four residences. The shared residential driveway standard shall be used on the common shared portion of a driveway. No more than four residences are served unless the road is upgraded to an emergency vehicle access road (EVAR). All shared residential driveways shall meet the following criteria:</SPAN></P><P><SPAN /></P><P><SPAN>(A) The shared residential driveway will lie within a minimum twenty-foot easement. The full width of the easement will be clear of sight obstructions to a height of thirteen feet, six inches.</SPAN></P><P><SPAN /></P><P><SPAN>(B) The minimum width of the improved driving surface shall be twelve feet.</SPAN></P><P><SPAN /></P><P><SPAN>(C) The minimum surfacing shall be six inches of compacted crushed surfacing (either CSBC or CSTC) on a suitable subgrade.</SPAN></P><P><SPAN /></P><P><SPAN>(D) The maximum grade shall be twelve percent.</SPAN></P><P><SPAN /></P><P><SPAN>(E) Approved turnaround features will be constructed at the termination or within one hundred and fifty feet of the termination of any shared residential driveway. Where a shared residential driveway exceeds one thousand feet in length, pull out and turnaround features will be provided as follows:</SPAN></P><P><SPAN /></P><P><SPAN>(i) Pull out features will be constructed to a minimum of eighteen feet of total width (lane plus widening) and a minimum fifty feet in length, and will have no more than five hundred feet separation.</SPAN></P><P><SPAN /></P><P><SPAN>(ii) Turnaround features will be constructed with maximum of one thousand feet separation. Turnaround design will be based upon Standard Plan PW-23-A or PW-23-B except that the easement width shall be twenty feet minimum.</SPAN></P><P><SPAN /></P><P><SPAN>Address signs shall be installed at the intersection of any residential shared driveway and a county road. Additionally, address signs will be placed at any intersection that follows along the shared residential driveway. No parking shall be permitted on a shared residential driveway. The shared residential driveway shall be appropriately signed with “No Parking Fire Lane” signs placed along driveway and at locations of pull out or turnaround features.</SPAN></P><P><SPAN /></P><P><SPAN>All shared residential driveways shall have a maintenance agreement recorded with the final plat approval that specifies consistent maintenance in accordance with the approved plat/plans. Further, the “No Parking Fire Lane” shall be strictly enforced.</SPAN></P><P><SPAN /></P><P><SPAN>(4) Rural and urban residential, joint usage and shared residential driveway approaches shall be constructed at the maximum practical distance, but in no event (unless a closer distance is permitted in more intense land uses such as approved LAMIRDs or in UGAs) less than one hundred twenty-five feet from a state highway, county collector, or local access intersection; or less than seventy-five feet from a local access class 3 cul-de-sac intersection. Such driveway approaches shall not be spaced closer than seventy feet (unless a closer distance is permitted in more intense land uses such as approved LAMIRDs or in UGAs), measured centerline to centerline, from another driveway approach. See Standard Plan PW-25 for details.</SPAN></P><P><SPAN /></P><P><SPAN>(5) Accesses serving from five to twelve lots shall meet emergency vehicle access road standards.</SPAN></P><P><SPAN /></P><P><SPAN>(6) A commercial approach is used for multifamily and commercial uses with approach traffic volumes of more than forty or more vehicle trips per day. When multi-access points are desired to serve one site then each driveway approach shall conform to the applicable use criteria. See Standard Plan P-26 for details.</SPAN></P><P><SPAN /></P><P><SPAN>(7) A temporary construction approach is used for access to a county road from a construction site. Commercial approach design criteria shall be used with the addition of measures for preventing mud and construction debris from deposited on the county road. See Standard Plan P-27 for details. (Res. 2008-130 (part), 8/26/08)</SPAN></P></DIV></DIV></DIV>

Service Item Id: fdec55b921a34fa49ce04147607de3a2

Copyright Text: Chelan County Public Works

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 100000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: status

Fields: Types: Relationships:
Capabilities: Query,Create,Update,Delete,Uploads,Editing,Sync,Extract

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Attachments   Query Analytic   Query Related Records   Apply Edits   Add Features   Update Features   Delete Features   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata