Table A.10. GCIS Data from ITS Sources
| No. | Data Element | Description | Links to ITS Data Sources |
|---|
| 1 | crossing | Highway-rail Crossing Identification Number. Serves as the master identifier for the crossing. The DOT Crossing Identification Number is unique to this highway-rail crossing. | TMDD: "Node Type" allows grade crossing as a valid value, but no unique ID for a grade crossing is provided. Also allows an "event" (incident to occur on grade crossing ("relation to junction") but a specific grade crossing is not identified.
NA: "crossing_id" refers tot his data element. |
| 2 | effdate | Beginning date for the crossing. The date 700101 is used in the original record if the crossing was in service at the time this file was organized. For crossings opened, closed or changed since then, the 'effective date' appears in the update record. (YYMMDD) | |
| 3 | edate | '999999' appears in the most current record for each crossing. For a change to a crossing or a crossing closure, the day before the 'Effective Date' is placed as the EDATE of the record which is current before the update record is added. (YYMMDD) | |
| 4 | reason | A code pertaining to the status of the pertinent highway-rail crossing record. | |
| 5 | state | Code for the state where the highway-rail crossing is located. Uses assigned FIPS codes for states. | |
| 6 | cntycd | Code for the county where the highway-rail crossing is located. Preceded by constant "C" in the first character. Uses FIPS codes assigned by county. (See the FRA Auxiliary Tables) | |
| 7 | state2 | Code for the state where the highway-rail crossing is located. Uses assigned FIPS codes for states. (See the FRA Auxiliary Tables) | |
| 8 | citycd | Code for the city where the highway-rail crossing is located. Uses assigned FIPS codes for cities. (See the FRA Auxiliary Tables) | |
| 9 | nearest | Code to indicate that the city nearest the highway-rail crossing is used in a record for a crossing not located in a city or town. This flag indicates whether the crossing is within or without the limits of a named locality. | |
| 10 | railroad | Code for the railroad company responsible for maintenance of the highway-rail crossing. (See the FRA Auxiliary Tables) | |
| 11 | rrdiv | Name of the operating division of the railroad responsible for maintenance of the highway-rail crossing. Not all railroads are divided into divisions. | |
| 12 | rrsubdiv | Name of the operating subdivision of railroad responsible for maintenance of the highway-rail crossing. Not all railroads are divided into sub-divisions. | |
| 13 | highway | Identification of highway at the highway-rail crossing by type and highway number. | |
| 14 | street | Name of the street or road, spelled out. | |
| 15 | Rrid | Crossing Identification number other than the DOT-AAR number. Railroad or Public Utilities Commission assigned number, posted at or assigned to the highway-rail crossing. | |
| 16 | ttstn | Standard Point Location Code (SPLC) for the nearest timetable station of the company maintaining the crossing. SPLC's are assigned to transportation points by the Transportation Data Coordinating Committee, a joint operation of the National Motor Freight Traffic Association and the Association of American Railroads. | |
| 17 | branch | Line or branch name used by the railroad to describe this segment of track. | |
| 18 | milepost | Railroad milepost number at which the highway-rail crossing is located. Distance along the railroad line from a standard reference point, which is, however, not specified in the file. | |
| 19 | mapref | County map identification or reference number used to locate the highway-rail crossing. County map identification code, provided by the highway agency to locate the highway-rail crossing within the county. | |
| 20 | typexing | Numeric code specifying the type category of the highway-rail crossing. | NA: crossing_equipment_data_for_highways set aside for this information |
| 21 | Posxing | Numeric code specifying the position category of the highway-rail crossing. | |
| 22 | prvcat | Numeric code indicating the usage category of a private vehicle highway-rail crossing. | |
| 23 | prvind | Indicator of whether or not any warning devices are present at a private vehicle crossing. Valid values for field are coded. | |
| 24 | prvsign | Description of any warning device present at a private vehicle crossing. | |
| 25 | init | Code to designate what agency has initiated the update. Generated during entry of the record into the file. For original inventory, the value is "4". | |
| 26 | batch | Code field, which gives the year, Julian day, and a batch number during original inventory. Identification number of batches of updates during update phase. Determined by the batch identification system used. | |
| 27 | usercd | This field is not currently used. | |
| 28 | update | Coded date of update. Code for month and year of update. | |
| 29 | link | This will contain the link identification code (LIC) from the rail network model for the line on which the crossing lies. LIC id is a five-digit code incorporating the alphabetical abbreviation of the owning railroad and a sequence number (e.g., "BN017" would be the 17th segment of the Burlington Northern Railroad). | |
| 30 | daythru | Normal, or average, number of daily through train movements over this grade crossing between 6AM and 6PM. | |
| 31 | dayswt | Normal, or average, number of daily local, industrial, or switch engine train movements over this grade crossing between 6AM and 6PM. | |
| 32 | nghtthru | Normal, or average, number of daily through train movements over this grade crossing between 6PM and 6AM. | |
| 33 | nghtswt | Normal, or average, number of daily local, industrial, or switch engine train movements using this grade crossing between 6PM and 6AM. | |
| 34 | Lt1mov | Code to distinguish crossings with very low train traffic. | |
| 35 | maxttspd | Maximum timetable speed at the highway-rail crossing, in miles per hour. | |
| 36 | minspd | Minimum typical speed of trains at the highway-rail crossing. | |
| 37 | maxspd | Maximum typical speed of trains at the highway-rail crossing. | |
| 38 | maintrk | Number of main tracks at the highway-rail crossing. A track is considered to be a main track if through trains operate on the track. This field reflects the number of main tracks of all railroads at the crossing. | |
| 39 | othrtrk | Number of tracks other than main tracks at the highway-rail crossing. This field reflects the number of tracks of all railroads at the crossing, which do not carry through trains. | |
| 40 | othrdes | Description of tracks considered to be other than main tracks at the highway-rail crossing. Track is considered to be "other" track if no through trains operate on it. The description is necessarily only a brief label. | |
| 41 | sepind | Indicates whether another railroad operates a separate track over this highway-rail crossing. | |
| 42 | seprr | Codes for the railroads operating separate tracks over this highway-rail crossing. Codes should appear in 4-character sub-fields. No code should repeat within the field. For valid RR codes see the FRA Auxiliary Tables. | |
| 43 | sameind | Indicates whether another railroad operates on the operating railroad's track at the crossing. | |
| 44 | samerr | Codes for other railroads operating on the operating railroad's tracks at this highway-rail crossing. Codes should appear in 4-character sub-fields. No code should repeat within the field. For valid RR codes see the FRA Auxiliary Tables. | |
| 45 | wdcode | Code for the highest level of warning device at the crossing. Lower level devices may also be present. | |
| 46 | xbuckrf | Number of masts with reflectorized cross-bucks at the highway-rail crossing. Two or more cross-bucks mounted on a single mast are counted as one. If the crossing has a train-activated device, the cross-bucks mounted on that device are not counted. | |
| 47 | xbucknrf | Number of masts with non-reflectorized cross-bucks at the highway-rail crossing. Two or more cross-bucks mounted on a single mast are counted as one. If the crossing has a train-activated device, the cross-bucks mounted on that device are not counted. | |
| 48 | stopstd | Number of standard highway stop signs at the highway-rail crossing. Standard highway stop signs are red with white letters and have eight sides. | |
| 49 | stopoth | Number of stop signs not classified as standard stop signs at the highway-rail crossing. A standard highway stop sign is red with white letters and has eight sides. All other stop signs are classified as "other stop signs". | |
| 50 | othsgn1 | Number of signs of the first type other than cross-bucks-or stop signs at the highway-rail crossing. This field gives the number of passive signs of any one type not otherwise provided for on the inventory form. | |
| 51 | othdes1 | Description of the first type of sign other than cross-bucks or stop signs at the highway-rail crossing. Indicates presence of a sign other than cross-bucks at the crossing. | |
| 52 | othsgn2 | Number of signs of the second type other than cross-bucks or stop signs at the highway-rail crossing. This field gives the number of passive signs of any type not otherwise provided for on the inventory form and not covered in field OTHSGN1. | |
| 53 | othdes2 | Description of the second type of signs other than cross-bucks or stop signs at the highway-rail crossing. Indicates presence of a sign other than cross-bucks at the crossing. | |
| 54 | gaterw | Number of gates with red and white reflectorized arms at the highway-rail crossing. | |
| 55 | gateoth | Number of all gates other than red and white reflectorized arms at the highway-rail crossing. | |
| 56 | flashov | Number of cantilevered flashing lights over traffic lanes of the roadway approaching the highway-rail crossing. | |
| 57 | flashnov | Number of cantilevered flashing lights not over traffic lanes of the roadway approaching the highway-rail crossing. Cantilevered flashers either not reaching the roadway or over only parking lanes, turnout lanes, or shoulders are classified as not over traffic lane. | |
| 58 | flashmas | Number of mast mounted flashing lights at the highway-rail crossing. All flashers on a single mast are counted as one flasher. | |
| 59 | flashoth | Number of flashing lights at the highway-rail crossing not conforming to the Manual on Uniform Traffic Control Devices published by FHWA. Indicates the presence of flashing lights at a crossing. | |
| 60 | flashdes | Description of flashing lights at the highway-rail crossing not in accordance with the Manual on Uniform Traffic Control Devices published by FHWA. | |
| 61 | hwysgnl | Number of highway traffic signals at the highway-rail crossing. Applies only to train activated red-amber-green signals that control street traffic over the highway-rail crossing. | |
| 62 | wigwags | Number of wigwags at the highway-rail crossing. All wigwags present at highway-rail crossing are counted separately. | |
| 63 | bells | Number of bells at the highway-rail crossing. All bells present at the crossing are counted whether alone or in conjunction with other warning devices. | |
| 64 | specpro | Description of non-train activated special warning device at the highway-rail crossing. Examples are manually operated signals on gates, train crew flagging the crossing, watchmen, and floodlights. The number of hours in effect daily should be recorded for watchmen and manually operated gates. For floodlights, the number of masts with lights should be recorded. Only floodlighting, which is of a type distinctive in volume, distribution, or color from ordinary street or other lighting, should be recorded. | |
| 65 | nosigns | A flag to indicate whether any signs or signals are present at the highway-rail crossing. | |
| 66 | compower | Is commercial electric power available within 500 feet of the crossing? | |
| 67 | sgnleqp | Is track equipped with signals to control train operation? | |
| 68 | spsel | A flag to indicate whether the crossing signal is equipped with a device to provide a uniform warning. | |
| 69 | develtyp | Indicates the predominant type of development in the vicinity of the crossing. Five broad categories are provided. The instructions for filling out the inventory form state that more than one category may be indicated. | |
| 70 | hwypved | A flag to indicate whether or not the highway at the highway-rail crossing is paved. | |
| 71 | downst | A flag to indicate whether the highway-rail crossing involves track running parallel to and within a street or highway. | |
| 72 | pavemrk | Indicates the presence of highway pavement markings at the highway-rail crossing. Pavement markings are recorded if they are as prescribed or generally similar to those contained in the highway traffic manual. If both stop lines and railroad crossing symbols are present, both are recorded. | |
| 73 | hwynear | A flag to indicate whether the street or highway at the highway-rail crossing is intersected by another street or highway, and if so, the distance from the crossing where the intersection exists. | |
| 74 | advwarn | A flag to indicate whether advance-warning signs are present on any of the highway approaches to the highway-rail crossing. | |
| 75 | xangle | Classification according to the smallest angle between the highway and the track at the highway-rail crossing. | |
| 76 | xsurface | Code for the type of surface covering the highway-rail crossing. Ten categories are provided. | |
| 77 | traficln | Number of traffic lanes crossing the tracks. Only through traffic lanes crossing the track are counted. Shoulders and lanes used for parking are excluded. Value must be non-zero. | TMDD: "Number of Through Lanes" on a link can be used.
|
| 78 | truckln | A flag to indicate whether truck pullout lanes are present at the highway-rail crossing. Only special added lanes are recorded which are provided to accommodate vehicles that are required to stop at highway-rail crossing. | |
| 79 | sthwy1 | A flag to indicate whether the highway-rail crossing is on the state highway system. | TMDD: Link and node "owners" are coded as free text.
|
| 80 | hwysys | Code for highway system type. The codes indicate the type of highway system as such, whether toll is imposed, and whether trucks are allowed. | |
| 81 | hwyclass | Code for functional classification of the highway crossing the tracks. The codes indicate the functional class as such and distinguish among rural and several population classes of urban. | TMDD: "Link Type" has inconsistent coding; allows: Freeway, Arterial, Collector, and Local only
|
| 82 | aadt | Estimated average daily highway traffic over the highway-rail crossing. Total traffic in both directions is recorded, based on most recent available information or estimates. Must be greater than zero. | TMDD: Only link volume is provided, with no formal specification of time period. AADT may be derived from link volumes only if they are archived with appropriate time and location stamps.
|
| 83 | pcttruk | Percentage of trucks in the traffic stream over the highway-rail crossing. | |
| 84 | latitude | Grade crossing latitudinal coordinate, from the center of the crossing. Used to identify a unique crossing using a standardized location point. Used in conjunction with Longitude to identify unique crossing position. | TMDD: Node latitude and longitude can be used.
|
| 85 | longitud | Grade crossing longitudinal coordinate, from the center of the crossing. Used to identify a unique crossing using a standardized location point. Used in conjunction with Latitude to identify unique crossing position. | |
| 86 | llsource | Source of the latitude/longitude data. Was it determined (interpolated) by the computer, confirmed on-site by GPS, or other. If the latitude/longitude data are submitted on the inventory form, then they are considered to be 'actual'; otherwise, they are considered to be "estimated". | |
| 87 | intrprmp | Status of grade crossing interconnection/preemption type. Specific active public/private at grade crossings with an automatic warning device. | |
| 88 | humpsign | A flag indicating whether or not signs are present at a high profile hump surface. | |
| 89 | hscorrid | High-speed rail corridor identifying code. Used to identify the "Section 1010" high-speed corridor on which the crossing is located, if it is located on such a corridor. | |
| 90 | dotacpd | DOT Accident Prediction Value - annual input. Provided by FRA Office of Safety from programs run by that office. | |
| 91 | acpddate | The effective date for the DOT Accident Prediction Value. | |
| 92 | acccnt1 | Accident History. For any crossing with an accident history within the most recent five years, would contain the count of the number of accidents occurring at the crossing during the five-year period. | NA: "hri_incident_data" reserved for this information |
| 93 | acccnt2 | Accident History. | |
| 94 | acccnt3 | Accident History. | |
| 95 | acccnt4 | Accident History. | |
| 96 | acccnt5 | Accident History. | |
| 97 | histdate | This field will indicate when the fields ACCCNT1 through ACCCNT5 were generated. Generated by the system. | |
| 98 | schlbus | Daily average number of scheduled school buses passing over the crossing on a school day. Back and forth counts as 2. | |
| 99 | whistban | A flag indicating whether or not a whistle ban is in effect for the crossing. | |
| 100 | passcd | Types of passenger trains using this crossing. | |
| 101 | passcnt | Number of passenger trains using this crossing, per day | |
| 102 | rrmain | This field will contain the code for the parent railroad of the Railroad Operating Company. Must be a valid railroad code. See FRA Auxiliary Tables. | |
| 103 | xingownr | This field will contain the code for the owner of the crossing. Must be a valid railroad code. See FRA Auxiliary Tables. | |
| 104 | source | This field will indicate the source of the last update. | |
| 105 | updatdat | This field will contain the date that the last update to the record was posted. Must be valid date. | |
| 106 | longbdat | This field will contain the same date as the field EFFDATE, in this record, except that the year will be four characters in this data element. Must be a valid date. | |
| 107 | longedat | This field will contain the same date as the field EDATE, in this record, except that the year will be four characters in this data element. Must be a valid date. | |
| 108 | fourquad | This field will indicate whether or not four-quadrant gates are present at the crossing. | |
| 109 | twoquad | This field will indicate whether or not two-quadrant gates with median barriers are present at the crossing. | |
| 110 | openpub | This field will indicate whether or not this private crossing is open to public access. | |
| 111 | rrnarr1 | This field will contain whatever the railroad desires to enter. | |
| 112 | rrnarr2 | This field will contain whatever the railroad desires to enter. | |
| 113 | rrnarr3 | This field will contain whatever the railroad desires to enter. | |
| 114 | rrnarr4 | This field will contain whatever the railroad desires to enter. | |
| 115 | stnarr1 | This field will contain whatever the State desires to enter. | |
| 116 | stnarr2 | This field will contain whatever the State desires to enter. | |
| 117 | stnarr3 | This field will contain whatever the State desires to enter. | |
| 118 | stnarr4 | This field will contain whatever the State desires to enter. | |
| 119 | aadtyear | This field will contain the year of the last AADT update. Generated by the system during the update process. | |
| 120 | aadtcalc | This field will identify how the last AADT update was calculated. | |
| 121 | traindat | This field will contain the year of the last trains update. | |
| 122 | traincal | This field will identify how the last train's update was calculated. | |
| 123 | reserve1 | Reserved for the future use. | |
| 124 | reserve2 | Reserved for the future use. | |
| 125 | reserve3 | Reserved for the future use. | |
| 126 | reserve4 | Reserved for the future use. | |
| 127 | reserve5 | Reserved for the future use. | |
| 128 | dotcaspd | DOT Predicted Casualty Rate - annual input. Provided by FRA Office of Safety from programs run by that office. | |
| 129 | dotfatpd | DOT Predicted Fatality Rate - annual input. Provided by FRA Office of Safety from programs run by that office. | |
| 130 | funccat | This field will contain the Functional Category (to be determined). | |
| 131 | rrcont | This field will contain the telephone number of the railroad contact associated with the crossing. | |
| 132 | hwycont | This field will contain the telephone number of the State highway contact associated with the crossing. | |
| 133 | polcont | This field will contain the telephone number of the Police contact associated with the crossing. | |
| 134 | narr | Free form comments. | |
