20230610
09482900
1.0
FALSE
LRSE_Pavement_Sections
002
408954.425000
691585.250000
4181697.500100
4625038.555000
1
Projected
GCS_North_American_1983
Linear Unit: Meter (1.000000)
NAD_1983_UTM_Zone_16N
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.5'><WKT>PROJCS["NAD_1983_UTM_Zone_16N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-87.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",26916]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>10000</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>16093472.186944401</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>6.2136994949494902e-007</MTolerance><HighPrecision>true</HighPrecision><WKID>26916</WKID><LatestWKID>26916</LatestWKID></ProjectedCoordinateSystem>
20200918
10433300
20200918
11024700
150000000
5000
ItemDescription
Version 6.2 (Build 9200) ; Esri ArcGIS 10.5.1.7333
LRSE_Pavement_Sections
0.000000
0.000000
1
-88.095440
-84.695584
41.777192
37.762550
This feature class is the authoritative source of information for where Pavement Sections (aka Pavement Keys) are located. The sections are intended to be correlated with programmed and maintenance activites. Multiple pavement sections can be included in a single activity, but an activity should not take place on a partial PK with any frequency without the PKs being retired (a date added to "To_Date") and 2 or more PKs taking its place. The limits of the PKs are primarily determined by the Pavement Asset Engineers in each district in collaboration with the Central Office Pavement and Asset Management teams.
<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>
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.
Pavement
Sections
PK
PKs
Key
Keys
Asset
Management
Road
Feature Class
dataset
EPSG
6.13(3.0.1)
29468
Simple
FALSE
29468
TRUE
TRUE
LRSE_Pavement_Sections
Feature Class
29468
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
ROUTE_ID
ROUTE_ID
String
17
0
0
FROM_MEASURE
FROM_MEASURE
Double
8
38
8
TO_MEASURE
TO_MEASURE
Double
8
38
8
FROM_DATE
From Date
Date
8
0
0
TO_DATE
To Date
Date
8
0
0
EVENT_ID
EventID
String
50
0
0
LOCATION_DESC
Location_Desc
String
150
0
0
PAVEMENT_KEY
PK
Integer
4
10
0
ROAD_CATEGORY
ROAD_CATEGORY
String
2
0
0
PW_AREA_SYS
PW Area sys
Double
8
38
8
PS_AREA_SYS
PS Area sys
Double
8
38
8
CREATED_BY
Created By
String
25
0
0
DATE_CREATED
Date Created
Date
8
0
0
EDITED_BY
Edited By
String
25
0
0
DATE_EDITED
Date edited
Date
8
0
0
DATE_ATTR_EFFECTIVE
Date Attr Effective
Date
8
0
0
LOCERROR
LocError
String
100
0
0
SHAPE
SHAPE
Geometry
4
0
0
Feature geometry.
Esri
Coordinates defining the features.
GLOBALID
GLOBALID
GlobalID
38
0
0
SHAPE.LEN
SHAPE.LEN
Double
0
0
0
20200918