View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
Service Description:
All Layers and Tables Has Versioned Data: false
MaxRecordCount: 2000
Supported Query Formats: JSON
Supports Query Data Elements:
Layers:
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The business rules for Pavement Sections are maintained by Central Office Asset Management, specifically Todd Shields as of Fall 2020. Generally speaking, a PK needs to reside on current routes and the increasing side of a dual carriage way on County Log if applicable. PKs should not reside on ramps. PKs should be primarily either HMA (flexible) or PCCP (rigid) pavements. As noted in the summary, multiple PKs can be included in planned work, but generally planned work (maintenance or contract) should not be planned for only a part of a PK. They should typically function as an indivisible/atomic unit of pavement locations. If they do need to be divided, the existing PK should be reitred and replaced. There can be multiple records for a single PK if they either ride along a route that has a gap (such as a roundabout intersection) or they ride for a brief period on another route (again like at an intersection).</SPAN></P><P><SPAN>Regarding fields:</SPAN></P><UL><LI><P><SPAN>PAVEMENT_KEY is the identifier (first digit is indicative of district, but the other values don't hold an specific meaning beyond their distinctiveness),</SPAN></P></LI><LI><P><SPAN>LOCATION_DESC describes the beginning and end of the route with the route itself typically not referrenced since it is inherent to the route ID,</SPAN></P></LI><LI><P><SPAN>ROAD_CATEGORY is generally how much traffic a road has and whether it is interstate or not (see separate Road Category business rules for more information),</SPAN></P></LI><LI><P><SPAN>PW_AREA_SYS is pavement area (including shoulders) in sq yds and is expected to be populated systemiatically based on information from dTIMS,</SPAN></P></LI><LI><P><SPAN>PS_AREA_SYS are similar to PW_AREA_SYS but are expected to be generated when a project is developed, when a new PK is created, or whenever such value is calculated and will function as manual overrides to the systemically derived values from PW_AREA_SYS</SPAN></P></LI><LI><P><SPAN>The remainder of the fields are standard for event layers on RAH</SPAN></P></LI></UL><P><SPAN>Please note that LRSE_Pavement_Section is the old version of this data from prior to the conversion from State Log to the current version of County Log/One Log.</SPAN></P></DIV></DIV></DIV>
Service Item Id: a7916d12639548e4bc6bf14dc7c05a2a
Copyright Text: Primarily administered by Kevin Munro with some assistance by Adam Tyra, Data is maintained collaboratively by Central Office Assement Management, Central Office Pavement Asset, and the district Pavement Asset Engineers and their assistants.
Spatial Reference:
26916
(26916)
LatestVCSWkid(0)
Initial Extent:
XMin: 358865.57145492575
YMin: 4152876.138094364
XMax: 555570.9793447583
YMax: 4321099.314977524
Spatial Reference: 26916
(26916)
LatestVCSWkid(0)
Full Extent:
XMin: 408954.4249999998
YMin: 4181697.5001
XMax: 691585.25
YMax: 4625038.555
Spatial Reference: 26916
(26916)
LatestVCSWkid(0)
Units: esriMeters
Document Info:
Enable Z Defaults: true
Sync Capabilities:
Supports Registering Existing Data: true
Supports Sync Direction Control: true
Supports PerLayer Sync: true
Supports PerReplica Sync: false
Supports RollbackOnFailure : false
Supports Async: true
Supports ApplyEdits With Global Ids: true
Supports Dynamic Layers: false
Child Resources:
Info
Replicas
Relationships
Supported Operations:
Query
Apply Edits
Append
Create Replica
Synchronize Replica
Unregister Replica