ArcGIS REST Services Directory Login
JSON

ItemInfo

Item Information

snippet: Legacy RouteID from CANSYS or legacy system reference for RouteId cross walk. This data is used for Conflating Pavement Management data for 0.1 mile Pavement distress data (ev_HPMSPavementCondition) because Pavement management data collection still refers to State Highway System by Legacy RouteId. This cross walk event also enable us to use ESRI' LRMtoLRM Translation tool to convert data from CANSYS LRS to KHUB LRS. When KHub is in production and all interfaces are using KHub RouteId then this data item may no longer be necessary
summary: Legacy RouteID from CANSYS or legacy system reference for RouteId cross walk. This data is used for Conflating Pavement Management data for 0.1 mile Pavement distress data (ev_HPMSPavementCondition) because Pavement management data collection still refers to State Highway System by Legacy RouteId. This cross walk event also enable us to use ESRI' LRMtoLRM Translation tool to convert data from CANSYS LRS to KHUB LRS. When KHub is in production and all interfaces are using KHub RouteId then this data item may no longer be necessary
accessInformation: KDOT
thumbnail:
maxScale: 5000
typeKeywords: []
description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Legacy Route ID from CANSYS or legacy system reference. This data is used for Conflating Pavement Management data for 0.1 mile Pavement distress data (ev_HPMSPavementCondition) because Pavement management data collection still refers to State Highway System by Legacy RouteId.</SPAN></P><P><SPAN /></P><P><SPAN>Example: KHubRouteId: 02310007000 was LegacyCRND 023I0007000-EB in CANSYS.</SPAN></P><P><SPAN>Also, KHub routeId is determined based on how vehicle traverse the roadway along ramps at intercahnge loactions(whereas in Cansys, the routes could terminate at the middle of a bridge). KHub Routes follow divided highway geometry where applicable. This has caused some differences in mileage and alignment changes when compared to systems that still use the concept of how routes were identified in CANSYS</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
licenseInfo:
catalogPath:
title: GEO.ev_LegacyRoute
type:
url:
tags: ["Conflate","Legacy Route","CANSYS RouteId"]
culture: en-US
portalUrl:
name:
guid:
minScale: 150000000
spatialReference: