ArcGIS REST Services Directory Login
JSON

Layer: Jeffco Street Intersection (ID: 0)

Name: Jeffco Street Intersection

Display Field: INTNAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Data Type: Dynamic. Vintage: Current. ASP data is generally edited on a daily to weekly basis.</SPAN></P><P><SPAN>Street (road) intersections in Jefferson County, Colorado.</SPAN></P><P><SPAN>This intersection data is maintained in the AddressStreetPolitical (ASP) production database by IT Services via the ASP Tools. Source data is the Intersection feature class residing in the "ASP_Topology" topology, where coincidence is maintained relative ASP BaseLine, BasePoly and Intersection features. </SPAN></P><P><SPAN>Traditionally, intersection data was not available to the County enterprise, but the migration from AGE (Address Geocode Environment) to the AddressStreetPolitical (ASP) geodatabase-based data model, in 2012, provided an opportunity to create this data.</SPAN></P><P><SPAN>From ASP Phase 1 through Phase 4.3, intersection point features existed only where two or more BaseLine features met where column STRNAMEFULL (street name full) differed on the connecting linear segments. At ASP Tool Phase 4.4, intersection modeliing was enhanced to handle 1) intersection geometry where three or more BaseLine features connect at an endpoint, where all connecting segments carry the same street name, 2) elimination of intersection features where differing Z-levels (under- and over-passes) are in play as well as where only two street segments connect with only a change in street name.</SPAN></P><P><SPAN>Column INTUID (intersection unique identifier) is the unique Intersection feature key maintained by the ASP Tools, which is independant and not-to-be confused with Esri's OBJECTID. Column INTUID is used in the ASP "IntersectionAndStreet" and "IntersectionAndStreetName" bridge tables where many-to-many intersection-related correspondences (to street features, and to street names, respectively) are managed.</SPAN></P><P><SPAN>Column INTNAME (intersection name) contains a string of one or two differing STRNAMEFULL (street name full) values for connecting segments, concatenated with an "AND" where differing street names are present. Determining which two STRNAMEFULL values are employed, where three or more are available per connectivity at an intersection, was initially achieved through application logic in the ASP Tools whereby the first two distinct STRNAMEFULL values returned by database query were used. At Phase 4.4, the ASP Tool user has discretion in the street naming attached to an intersection.</SPAN></P><P><SPAN>Column INTTYPE (intersection type) is a domain-driven description of the geometric characteristic of the intersection, developed at ASP Phase 4.4. Examples: '3-WAY' (three-way street feature connectivity), '4-WAY', '5-WAY', 'RAB' (round-a-bout), etc. </SPAN></P><P><SPAN>This data is in State Plane Grid Coordinates, Colorado Central Zone, NAD83.</SPAN></P></DIV></DIV></DIV>

Service Item Id: 019809cdbe1846688c9fd4cd4f72a208

Copyright Text: Credit Jefferson County IT Services in any use of this data.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: 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: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata