{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "HPMS, Safety Analyst, ISHDM, MIRE 2.0, KDOT Transportation Planning\n\nThe source of the data is Videolog. from oracle database in Shared Schema.\nSHARED.REFPOST \n\n\nNote: LIDAR collected Sign data is not brought into KHub database yet.", "description": "
The reference direction codes come from the standard FHWA rosette: 1=N, 2=NE (not used here), 3=E, 5=S, 7=W<\/SPAN><\/SPAN><\/P> <\/P> ReferencePost (Mile Marker) is the number on the green sign. There is a RefPost_Tenths field available in the source data (oracle database, shared schema) for the enhanced centerline posts found on the interstates, but it is not currently available in the khub data.<\/SPAN><\/P> <\/P> Attributes in KHub are: [ReferencePost],<\/SPAN>[ReferenceDirection], <\/SPAN>,<\/SPAN><\/SPAN>[MeasuredLatitude], <\/SPAN>,<\/SPAN><\/SPAN>[MeasuredLongitude], <\/SPAN>,<\/SPAN><\/SPAN>[MeasuredAltitude]<\/SPAN><\/SPAN><\/P> The measured Lat,Long attributes would be helpful to create point locations based on the spatial coordinates (Lat, Long) rather than county LRS logmile<\/SPAN><\/P> The attribute ReferenceDirection uses the domain dReferenceDirection<\/SPAN><\/P> name<\/SPAN><\/SPAN><\/P><\/TD> Code<\/SPAN><\/SPAN><\/P><\/TD> Value<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 0<\/SPAN><\/SPAN><\/P><\/TD> East-West<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 1<\/SPAN><\/SPAN><\/P><\/TD> North<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 2<\/SPAN><\/SPAN><\/P><\/TD> Northeast<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 3<\/SPAN><\/SPAN><\/P><\/TD> East<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 4<\/SPAN><\/SPAN><\/P><\/TD> Southeast<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 5<\/SPAN><\/SPAN><\/P><\/TD> South<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 6<\/SPAN><\/SPAN><\/P><\/TD> Southwest<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 7<\/SPAN><\/SPAN><\/P><\/TD> West<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 8<\/SPAN><\/SPAN><\/P><\/TD> Northwest<\/SPAN><\/SPAN><\/P><\/TD><\/TR> dReferenceDirection<\/SPAN><\/SPAN><\/P><\/TD> 9<\/SPAN><\/SPAN><\/P><\/TD> North-South<\/SPAN><\/SPAN><\/P><\/TD><\/TR><\/TBODY><\/TABLE> <\/P> HISTORY<\/SPAN><\/P> From CANSYS Metadata Master Report:<\/SPAN><\/P> STRP - (State Reference Post) <\/SPAN><\/P> State reference posts are the green mile marker signs along the roadway. Note that the number reflected on the mile marker will not always match the route milepost of the location of the sign. When a roadway is changed the sign doesnt always gets moved in the field.<\/SPAN><\/P> (STRP) - Altitude -- IIT_NUM_ATTRIB19 <\/SPAN><\/P> Comes from Videolog <\/SPAN><\/P> (STRP) - Cycle -- IIT_NUM_ATTRIB21 <\/SPAN><\/P> Come from Videolog - TFO use only <\/SPAN><\/P> (STRP) - Disk -- IIT_CHR_ATTRIB30 <\/SPAN><\/P> Come from Videolog TFO use only <\/SPAN><\/P> (STRP) - Frame -- IIT_NUM_ATTRIB20 <\/SPAN><\/P> Come from Videolog TFO use only <\/SPAN><\/P> (STRP) - Latitude -- IIT_NUM_ATTRIB17 <\/SPAN><\/P> Latitude of sign <\/SPAN><\/P> (STRP) - Longitude -- IIT_NUM_ATTRIB18 <\/SPAN><\/P> Longitude of sign <\/SPAN><\/P> (STRP) - Ref Post Route -- IIT_CHR_ATTRIB26 <\/SPAN><\/P> Route that the reference post exists on <\/SPAN><\/P> (STRP) - Reference Post -- IIT_NUM_ATTRIB16 <\/SPAN><\/P> Number on sign <\/SPAN><\/P> (STRP) - Route in city -- IIT_CHR_ATTRIB29 <\/SPAN><\/P> Identifies if route in city limits - <\/SPAN><\/P> Code Y - Yes<\/SPAN><\/P><\/LI> Code N - No<\/SPAN><\/P><\/LI><\/UL> (STRP) - Virtual -- IIT_CHR_ATTRIB28 <\/SPAN><\/P> Identifies if a point was created to emulate a sign. <\/SPAN><\/P> Code Y - Yes <\/SPAN><\/P><\/LI> Code N - No <\/SPAN><\/P><\/LI><\/UL> (STRP) - Visible -- IIT_CHR_ATTRIB27 <\/SPAN><\/P> Identifies if the sign is visible or not. <\/SPAN><\/P> Code Y - Yes<\/SPAN><\/P><\/LI> Code N - No <\/SPAN><\/P><\/LI><\/UL><\/DIV><\/DIV><\/DIV>",
"summary": "HPMS, Safety Analyst, ISHDM, MIRE 2.0, KDOT Transportation Planning\n\nThe source of the data is Videolog. from oracle database in Shared Schema.\nSHARED.REFPOST \n\n\nNote: LIDAR collected Sign data is not brought into KHub database yet.",
"title": "Reference Post",
"tags": [
"KDOT",
"KHUB",
"Reference",
"Post",
"Mile Marker"
],
"type": "",
"typeKeywords": [],
"thumbnail": "",
"url": "",
"minScale": 150000000,
"maxScale": 5000,
"spatialReference": "",
"accessInformation": "KDOT",
"licenseInfo": " 23 USC 409<\/SPAN><\/P><\/DIV><\/DIV><\/DIV>"
}