Name: LRSE_Pavement_Sections

Display Field: ROUTE_ID

Type: Feature Layer

Geometry Type: esriGeometryPolyline

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: 9f9ed1f9e52040c8bd56236f9fc49b33

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.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 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:

XMin: 408954.425
YMin: 4181697.5001
XMax: 691585.25
YMax: 4625038.555
Spatial Reference: 26916  (26916)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [142, 107, 57, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• ROUTE_ID ( type: esriFieldTypeString, alias: ROUTE_ID, length: 17 )
• FROM_MEASURE ( type: esriFieldTypeDouble, alias: FROM_MEASURE )
• TO_MEASURE ( type: esriFieldTypeDouble, alias: TO_MEASURE )
• FROM_DATE ( type: esriFieldTypeDate, alias: From Date, length: 8 )
• TO_DATE ( type: esriFieldTypeDate, alias: To Date, length: 8 )
• EVENT_ID ( type: esriFieldTypeString, alias: EventID, length: 50 )
• LOCATION_DESC ( type: esriFieldTypeString, alias: Location_Desc, length: 150 )
• PAVEMENT_KEY ( type: esriFieldTypeInteger, alias: PK , Range: [10000, 79999] )
• ROAD_CATEGORY ( type: esriFieldTypeString, alias: ROAD_CATEGORY, length: 2 , Coded Values: [A1: A1] , [A2: A2] , [B1: B1] , ...4 more... )
• PW_AREA_SYS ( type: esriFieldTypeDouble, alias: PW Area sys )
• PS_AREA_SYS ( type: esriFieldTypeDouble, alias: PS Area sys )
• CREATED_BY ( type: esriFieldTypeString, alias: Created By, length: 25 )
• DATE_CREATED ( type: esriFieldTypeDate, alias: Date Created, length: 8 )
• EDITED_BY ( type: esriFieldTypeString, alias: Edited By, length: 25 )
• DATE_EDITED ( type: esriFieldTypeDate, alias: Date edited, length: 8 )
• DATE_ATTR_EFFECTIVE ( type: esriFieldTypeDate, alias: Date Attr Effective, length: 8 )
• LOCERROR ( type: esriFieldTypeString, alias: LocError, length: 100 )
• GLOBALID ( type: esriFieldTypeGlobalID, alias: GLOBALID, length: 38 )
• CHIPABLE ( type: esriFieldTypeString, alias: CHIPABLE, length: 3 , Coded Values: [Yes: Yes] , [No: No] , [N/A: N/A] )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• SHAPE.LEN ( type: esriFieldTypeDouble, alias: SHAPE.LEN )

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

  Iteminfo   Thumbnail   Metadata