ArcGIS REST Services Directory Login
JSON

Layer: Streets (HOCO AACO) (ID: 31)

View In:   ArcGIS Online Map Viewer

Parent Layer: Zoom4 - 1: 18056

Name: Streets (HOCO AACO)

Display Field: FEAT_CODE

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: Road edges can include roads, driveways, parking areas, and runways / taxiway features and are represented by polylines. Detailed descriptions of the individual features are below.Road edges, including alleyways that are greater than 10 feet in width are captured. Road edges are defined as the edge of the improved or unimproved surface (including the shoulder if improved) and attributed with the appropriate surface type. Road edges are compiled through bridge polygons and can overlap bridge polygons. Roads have precedence over parking areas and are used for sides of parking areas. Road polylines are created based on surface type and connect the road intersections to form an X within the intersection with the midpoint of the X being the center of the intersection. This X is snapped to the road centerline at the midpoint of the X as well. For roads that do not fully intersect, a line is drawn straight across where the two roads meet or a Y intersection is used. These lines are assigned a feature code of intersection line. The road network is compiled to have all open intersections unless the surface type changes. For areas where surface type has changed, a pavement change line is drawn connecting the edge of the road at the change to the centerline at the change and then to the other side of the road edge at the change. Roads are attributed by surface type of paved, unpaved, or under construction. Roads are attributed by status type in the form of closed for road sections that have curb / gutter and open for open road sections. All roads in the County centerline are captured if they exist as of the 2011 imagery.Driveways are captured and attributed as paved or unpaved. Other feature classes may have coincident geometry to one or more sides of a driveway. Parking areas are captured to the outer extents of the parking area including the driving lanes and access roads connecting to the main road. Other feature classes may have coincident geometry with the sides of a parking area. Parking areas are attributed as paved or unpaved. Parking areas are attributed by status type in the form of closed for sections that have curb / gutter and open for open sections.All airport runways and taxiways are captured and attributed with surface type and open / closed status.Domain values for this feature include ROAD, DRIVEWAY, PARKING AREA, RUNWAY / TAXIWAY, and INTERSECTION LINE with statuses of OPEN, CLOSED or NA and surfaces of PAVED, UNPAVED, UNDER CONSTRUCTION, or NA.

Service Item Id: 4ce40956d8284b72b99ebf2db4c83aeb

Copyright Text:

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Effective Min Scale: 18056

Effective Max Scale: 9030

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:

Fields: Templates:
Capabilities: Query

Sync Can Return Changes: false

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: false

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Analytic   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata