LCS Field Short Description
x = field used in these file formats | |||||||||
Field Number | Field Name | Description | Type | Nominal Value | Example Value | CSV | JSON | TXT | XML |
---|---|---|---|---|---|---|---|---|---|
1 | data | wrapper for cctv data set | x | x | |||||
1.1 | lcs | wrapper for lcs record | x | x | |||||
1.1.1 | index | index number for lcs record | string | 0 to 35 characters | M5AA-0004-2013-03-07-07:01:00 | x | x | x | x |
1.1.2 | recordTimestamp | wrapper for this record's timestamp | x | x | |||||
1.1.2.1 | recordDate | this record's creation date | date | yyyy-mm-dd | 2013-03-04 | x | x | x | x |
1.1.2.2 | recordTime | this record's creation 24-hour time in PST or PDT | time | hh:mm:ss | 11:21:02 | x | x | x | x |
1.1.2.3 | recordEpoch | this record's creation time using Unix's signed 64 bit integer time format. | long | 0 to 9223372036854775807 | 1362424862 | x | x | x | x |
1.1.3 | location | wrapper for lcs location information | x | x | |||||
1.1.3.1 | travelFlowDirection | traffic flow direction on the highway that this lane closure affects | string | North / South, East / West, North, East, South, West, N/A, null | South | x | x | x | x |
1.1.3.2 | begin | wrapper for lcs location information begin point | x | x | |||||
1.1.3.2.1 | beginDistrict | caltrans district id at the begin point | int | 1 to 12 | 2 | x | x | x | x |
1.1.3.2.2 | beginLocationName | lcs location description at the begin point | string | 0 to 100 characters | 0.3 mi north of Sweetbriar Ave | x | x | x | x |
1.1.3.2.3 | beginFreeFormDescription | lcs alternative location description at the begin point | string | 0 to 100 characters | x | x | x | x | |
1.1.3.2.4 | beginNearbyPlace | nearby populated place based on zip code of lcs at the begin point | string | 0 to 100 characters / Not Reported | Castella | x | x | x | x |
1.1.3.2.5 | beginLongitude | wgs84 longitude at the begin point | float | -180 to 180 / Not Reported | -122.323898 | x | x | x | x |
1.1.3.2.6 | beginLatitude | wgs84 latitude at the begin point | float | -90 to 90 / Not Reported | 41.126355 | x | x | x | x |
1.1.3.2.7 | beginElevation | elevation in feet at the begin point | int | -282 to 14494 / Not Reported | 2040 | x | x | x | x |
1.1.3.2.8 | beginDirection | identifies which direction of travel the on-ramp, off-ramp or connector structure is affected by the lane closure at the begin point. this field is also sometimes used for other facilities, such as Surface Street and Rest Area, when it makes sense to distinguish which traffic flow direction on the facility is affected by the lane closure. |
string | North / South, East / West, North, East, South, West, N/A, null | x | x | x | x | |
1.1.3.2.9 | beginCounty | county name at the begin point | string | See County Chart | Shasta | x | x | x | x |
1.1.3.2.10 | beginRoute | route name at the begin point | string | See Route Chart | I-5 | x | x | x | x |
1.1.3.2.11 | beginRouteSuffix | route suffix identifier at the begin point | string | See Suffix Chart | x | x | x | x | |
1.1.3.2.12 | beginPostmilePrefix | postmile prefix identifier at the begin point | string | See Prefix Chart | R | x | x | x | x |
1.1.3.2.13 | beginPostmile | postmile number at the begin point | float | 0 to 999.999 | 62.001 | x | x | x | x |
1.1.3.2.14 | beginAlignment | alignment identifier at the begin point | string | See Alignment Chart | L | x | x | x | x |
1.1.3.2.15 | beginMilepost | absolute postmile number at the begin point | float | 0 to 999.999 | 722.642 | x | x | x | x |
1.1.3.3 | end | wrapper for lcs location information end point | x | x | |||||
1.1.3.3.1 | endDistrict | caltrans district id at the end point | int | 1 to 12 | 2 | x | x | x | x |
1.1.3.3.2 | endLocationName | lcs location description at the end point | string | 0 to 100 characters | 0.6 mi south of Conant Rd | x | x | x | x |
1.1.3.3.3 | endFreeFormDescription | lcs alternative location description at the end point | string | 0 to 100 characters | x | x | x | x | |
1.1.3.3.4 | endNearbyPlace | nearby populated place based on zip code of lcs at the end point | string | 0 to 100 characters / Not Reported | Castella | x | x | x | x |
1.1.3.3.5 | endLongitude | wgs84 longitude at the end point | float | -180 to 180 / Not Reported | -122.338481 | x | x | x | x |
1.1.3.3.6 | endLatitude | wgs84 latitude at the end point | float | -90 to 90 / Not Reported | 41.103179 | x | x | x | x |
1.1.3.3.7 | endElevation | elevation in feet at the end point | int | -282 to 14494 / Not Reported | 1893 | x | x | x | x |
1.1.3.3.8 | endDirection | identifies which direction of travel the on-ramp, off-ramp or connector structure is affected by the lane closure at the end point. this field is also sometimes used for other facilities, such as Surface Street and Rest Area, when it makes sense to distinguish which traffic flow direction on the facility is affected by the lane closure. |
string | North / South, East / West, North, East, South, West, N/A, null | x | x | x | x | |
1.1.3.3.9 | endCounty | county name at the end point | string | See County Chart | Shasta | x | x | x | x |
1.1.3.3.10 | endRoute | route name at the end point | string | See Route Chart | I-5 | x | x | x | x |
1.1.3.3.11 | endRouteSuffix | route suffix identifier at the end point | string | See Suffix Chart | x | x | x | x | |
1.1.3.3.12 | endPostmilePrefix | postmile prefix identifier at the end point | string | See Prefix Chart | x | x | x | x | |
1.1.3.3.13 | endPostmile | postmile number at the end point | float | 0 to 999.999 | 60.001 | x | x | x | x |
1.1.3.3.14 | endAlignment | alignment identifier at the end point | string | See Alignment Chart | x | x | x | x | |
1.1.3.3.15 | endMilepost | absolute postmile number at the end point | float | 0 to 999.999 | 720.642 | x | x | x | x |
1.1.4 | closure | wrapper for lcs closure information | string | x | x | ||||
1.1.4.1 | closureID | lcs closure ID | string | 0 to 6 characters | M5AA | x | x | x | x |
1.1.4.2 | logNumber | lcs log number | string | 0 to 1000 | 4 | x | x | x | x |
1.1.4.3 | closureTimestamp | wrapper for this closure's timestamps | x | x | |||||
1.1.4.3.1 | closureRequestDate | closure request date | date | yyyy-mm-dd | 2013-02-28 | x | x | x | x |
1.1.4.3.2 | closureRequestTime | closure request time 24-hour time in PST or PDT | time | hh:mm:ss | 14:46:00 | x | x | x | x |
1.1.4.3.3 | closureRequestEpoch | closure request time using Unix's signed 64 bit integer time format. | long | 0 to 9223372036854775807 | 1362090360 | x | x | x | x |
1.1.4.3.4 | closureStartDate | closure start date | date | yyyy-mm-dd | 2013-03-07 | x | x | x | x |
1.1.4.3.5 | closureStartTime | closure start time 24-hour time in PST or PDT | time | hh:mm:ss | 07:01:00 | x | x | x | x |
1.1.4.3.6 | closureStartEpoch | closure start time using Unix's signed 64 bit integer time format. | long | 0 to 9223372036854775807 | 1362668460 | x | x | x | x |
1.1.4.3.7 | closureEndDate | closure end date. if indefinite, closureEndDate will be 2999-12-31, closureEndTime will be 23:59:00. | date | yyyy-mm-dd | 2013-03-07 | x | x | x | x |
1.1.4.3.8 | closureEndTime | closure end time 24-hour time in PST or PDT. if indefinite, closureEndDate will be 2999-12-31, closureEndTime will be 23:59:00. | time | hh:mm:ss | 15:01:00 | x | x | x | x |
1.1.4.3.9 | closureEndEpoch | closure end time using Unix's signed 64 bit integer time format. if indefinite, closureEndEpoch will be 32503708740. | long | 0 to 9223372036854775807 | 1362697260 | x | x | x | x |
1.1.4.3.10 | isClosureEndIndefinite | are closureEndDate and closureEndTime both indefinite. | boolean | true / false | false | x | x | x | x |
1.1.4.4 | facility | type of roadway facility | string | See Facility Chart | Mainline | x | x | x | x |
1.1.4.5 | typeOfClosure | type of closure being performed | string | Lane / Full / One-way / Alternating | Lane | x | x | x | x |
1.1.4.6 | typeOfWork | type of work being performed | string | See Type of Work Chart | Shoulder Work | x | x | x | x |
1.1.4.7 | durationOfClosure | estimation of the duration of closure | string | See Duration Chart | Standard | x | x | x | x |
1.1.4.8 | estimatedDelay | estimated delay due to the closure | integer | 0 to 999 / Not Reported | 0 | x | x | x | x |
1.1.4.9 | lanesClosed | lanes of the roadway to be closed | integer | 0 to 10 / See Lane Type Chart | 2, RShoulder | x | x | x | x |
1.1.4.10 | totalExistingLanes | total number of travel lanes for traffic | integer | 0 to 10 / Not Reported | 2 | x | x | x | x |
1.1.4.11 | isCHINReportable | does the closure meet the criteria for reporting to the Caltrans Highway Information Network (CHIN)? | boolean | true / false | false | x | x | x | x |
1.1.4.12 | code1097 | wrapper for this record's status start of closure | x | x | |||||
1.1.4.12.1 | isCode1097 | has the closure started? | boolean | true / false | false | x | x | x | x |
1.1.4.12.2 | code1097Timestamp | wrapper for closure start timestamp | x | x | |||||
1.1.4.12.2.1 | code1097Date | date the closure started | date | yyyy-mm-dd | x | x | x | x | |
1.1.4.12.2.2 | code1097Time | time the closure started 24-hour time in PST or PDT | time | hh:mm:ss | x | x | x | x | |
1.1.4.12.2.3 | code1097Epoch | time the closure started using Unix's signed 64 bit integer time format. | long | 0 to 9223372036854775807 | x | x | x | x | |
1.1.4.13 | code1098 | wrapper for closure end time | x | x | |||||
1.1.4.13.1 | isCode1098 | has the closure ended? | boolean | true / false | false | x | x | x | x |
1.1.4.13.2 | code1098Timestamp | wrapper for closure end timestamp | x | x | |||||
1.1.4.13.2.1 | code1098Date | date the closure ended | date | yyyy-mm-dd | x | x | x | x | |
1.1.4.13.2.2 | code1098Time | time the closure ended 24-hour time in PST or PDT | time | hh:mm:ss | x | x | x | x | |
1.1.4.13.2.3 | code1098Epoch | time the closure ended using Unix's signed 64 bit integer time format. | long | 0 to 9223372036854775807 | x | x | x | x | |
1.1.4.14 | code1022 | wrapper for closure cancellation | x | x | |||||
1.1.4.14.1 | isCode1022 | has the closure been cancelled? | boolean | true / false | false | x | x | x | x |
1.1.4.14.2 | code1022Timestamp | wrapper for closure cancellation timestamp | x | x | |||||
1.1.4.14.2.1 | code1022Date | date the closure was cancelled | date | yyyy-mm-dd | x | x | x | x | |
1.1.4.14.2.2 | code1022Time | time the closure was cancelled 24-hour time in PST or PDT | time | hh:mm:ss | x | x | x | x | |
1.1.4.14.2.3 | code1022Epoch | time the closure was cancelled using Unix's signed 64 bit integer time format. | long | 0 to 9223372036854775807 | x | x | x | x |
LCS Field Long Description
Field Name : data
- Field Number : 1
- Description : used as the wrapper for the LCS data set
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1
- Description : Wrapper for LCS record
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.1
- Description : Describes the index number for LCS record.
- Type : xs:string
- Nominal Value : 1 to 35 characters. Each index number is unique to the data set.
- Example Value : M5AA-0004-2013-03-07-07:01:00
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.2
- Description : Wrapper for this record's timestamp
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.2.1
- Description : Describes the date when this record was last modified
- Type : xs:date
- Nominal Value : yyyy-mm-dd; where yyyy is the four-digit year value, mm is the two-digit month value and dd is the two-digit day value
- Example Value : 2013-03-04
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.2.2
- Description : Describes the 24-hour time when this record was last modified. Value is in either Pacific Daylight Time (PDT) or Pacific Standard Time (PST)
- Type : xs:time
- Nominal Value : hh:mm:ss; where hh is the two-digit hour value, mm is the two-digit minute value and ss is the two-digit second value
- Example Value : 11:21:02
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.2.3
- Description : Describes the Unix's signed 64 bit integer time format.
- Type : xs:long
- Nominal Value : 0 to 9223372036854775807
- Example Value : 1362424862
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3
- Description : Wrapper for LCS location information
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.3.1
- Description : Traffic flow direction on the highway that this lane closure affects
- Type : xs:string
- Nominal Value : North / South, East / West, North, East, South, West, N/A, null
- Example Value : South
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2
- Description : Wrapper for LCS location information begin point
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.3.2.1
- Description : Describes which Caltrans District the equipment is located in at the begin point. See District map for more information
- Type : xs:int
- Nominal Value : 1 to 12
- Example Value : 2
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.2
- Description : The operational description of where the LCS is located at the begin point
- Type : xs:string
- Nominal Value : 0 to 100 characters
- Example Value : 0.3 mi north of Sweetbriar Ave
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.3
- Description : The alternative description of where the LCS is located at the begin point
- Type : xs:string
- Nominal Value : 0 to 100 characters
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.4
- Description : The nearby populated place based on the zip code where the LCS is located in at the begin point
- Type : xs:string
- Nominal Value : 0 to 100 characters. Some locations may not have a value for this field
- Example Value : Castella
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.5
- Description : The WGS84 longitude where the LCS is located at the begin point
- Type : xs:float
- Nominal Value : -180 to 180. Value is in decimal degrees
- Example Value : -122.323898
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.6
- Description : The WGS84 latitude where the LCS is located at the begin point
- Type : xs:float
- Nominal Value : -90 to 90. Value is in decimal degrees
- Example Value : 41.126355
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.7
- Description : The elevation where the LCS is located at the begin point. Based on the 90 meter digital elevation model
- Type : xs:int
- Nominal Value : -282 to 14494. Value is in feet
- Example Value : 2040
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.8
- Description : Identifies which direction of travel the on-ramp, off-ramp or connector structure is affected by the lane closure at the begin point.
This field is also sometimes used for other facilities, such as Surface Street and Rest Area, when it makes sense to distinguish which traffic flow direction on the facility is affected by the lane closure. - Type : xs:string
- Nominal Value : North / South, East / West, North, East, South, West, N/A, null
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.9
- Description : The county name where the LCS is located at the begin point
- Type : xs:string
- Nominal Value : See County Chart for more information
- Example Value : Shasta
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.10
- Description : The route name where the LCS is located at the begin point
- Type : xs:string
- Nominal Value : See Route Chart for more information
- Example Value : I-5
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.11
- Description : The route suffix identifier used internally within Caltrans at the begin point
- Type : xs:string
- Nominal Value : See Route Suffix Chart for more information. Some locations may not have a value for this field
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.12
- Description : The postmile prefix identifier used internally within Caltrans at the begin point
- Type : xs:string
- Nominal Value : See Postmile Prefix Chart for more information. Some locations may not have a value for this field
- Example Value : R
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.13
- Description : The postmile where the LCS is located at the begin point. The postmile value starts at 0 at the southern / eastern border of a county and increases as the route moves north / west
- Type : xs:float
- Nominal Value : 0 to 999.999
- Example Value : 62.001
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.14
- Description : The alignment identifier used internally within Caltrans at the begin point
- Type : xs:string
- Nominal Value : See Alignment Chart for more information. Some locations may not have a value for this field
- Example Value : L
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.2.15
- Description : The milepost where the LCS is located at the begin point. The milepost value starts at 0 at the southern / eastern border tip of the route and increases as the route moves north / west. Milepost is analogous to the odometer reading of the route
- Type : xs:float
- Nominal Value : 0 to 999.999
- Example Value : 722.642
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3
- Description : Wrapper for LCS location information end point
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.3.3.1
- Description : Describes which Caltrans District the equipment is located in at the end point. See District map for more information
- Type : xs:int
- Nominal Value : 1 to 12
- Example Value : 2
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.2
- Description : The operational description of where the LCS is located at the end point
- Type : xs:string
- Nominal Value : 0 to 100 characters
- Example Value : 0.6 mi south of Conant Rd
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.3
- Description : The alternative description of where the LCS is located at the end point
- Type : xs:string
- Nominal Value : 0 to 100 characters
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.4
- Description : The nearby populated place based on the zip code where the LCS is located in at the end point
- Type : xs:string
- Nominal Value : 0 to 100 characters. Some locations may not have a value for this field
- Example Value : Castella
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.5
- Description : The WGS84 longitude where the LCS is located at the end point
- Type : xs:float
- Nominal Value : -180 to 180. Value is in decimal degrees
- Example Value : -122.338481
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.6
- Description : The WGS84 latitude where the LCS is located at the end point
- Type : xs:float
- Nominal Value : -90 to 90. Value is in decimal degrees
- Example Value : 41.103179
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.7
- Description : The elevation where the LCS is located at the end point. Based on the 90 meter digital elevation model
- Type : xs:int
- Nominal Value : -282 to 14494. Value is in feet
- Example Value : 1893
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.8
- Description : Identifies which direction of travel the on-ramp, off-ramp or connector structure is affected by the lane closure at the end point.
This field is also sometimes used for other facilities, such as Surface Street and Rest Area, when it makes sense to distinguish which traffic flow direction on the facility is affected by the lane closure. - Type : xs:string
- Nominal Value : North / South, East / West, North, East, South, West, N/A, null
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.9
- Description : The county name where the LCS is located at the end point
- Type : xs:string
- Nominal Value : See County Chart for more information
- Example Value : Shasta
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.10
- Description : The route name where the LCS is located at the end point
- Type : xs:string
- Nominal Value : See Route Chart for more information
- Example Value : I-5
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.11
- Description : The route suffix identifier used internally within Caltrans at the end point
- Type : xs:string
- Nominal Value : See Route Suffix Chart for more information. Some locations may not have a value for this field
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.12
- Description : The postmile prefix identifier used internally within Caltrans at the end point
- Type : xs:string
- Nominal Value : See Postmile Prefix Chart for more information. Some locations may not have a value for this field
- Example Value : R
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.13
- Description : The postmile where the LCS is located at the end point. The postmile value starts at 0 at the southern / eastern border of a county and increases as the route moves north / west
- Type : xs:float
- Nominal Value : 0 to 999.999
- Example Value : 60.001
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.14
- Description : The alignment identifier used internally within Caltrans at the end point
- Type : xs:string
- Nominal Value : See Alignment Chart for more information. Some locations may not have a value for this field
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.3.3.15
- Description : The milepost where the LCS is located at the end point. The milepost value starts at 0 at the southern / eastern border tip of the route and increases as the route moves north / west. Milepost is analogous to the odometer reading of the route
- Type : xs:float
- Nominal Value : 0 to 999.999
- Example Value : 720.642
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4
- Description : Wrapper for LCS closure information
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.1
- Description : LCS closure ID
- Type : xs:string
- Nominal Value : 0 to 10 characters.
- Example Value : M5AA
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.2
- Description : LCS log number
- Type : xs:int
- Nominal Value : 0 to 1000
- Example Value : 4
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3
- Description : Wrapper for this closure's timestamps
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.3.1
- Description : Closure request date
- Type : xs:date
- Nominal Value : yyyy-mm-dd; where yyyy is the four-digit year value, mm is the two-digit month value and dd is the two-digit day value
- Example Value : 2013-02-28
- Used in file formats : JSON, XML
- Field Number : 1.1.4.3.2
- Description : Closure request date
- Type : xs:time
- Nominal Value : hh:mm:ss; where hh is the two-digit hour value, mm is the two-digit minute value and ss is the two-digit second value
- Example Value : 14:46:00
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.3
- Description : Describes the Unix's signed 64 bit integer time format.
- Type : xs:long
- Nominal Value : 0 to 9223372036854775807
- Example Value : 1362090360
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.4
- Description : Closure start date
- Type : xs:date
- Nominal Value : yyyy-mm-dd; where yyyy is the four-digit year value, mm is the two-digit month value and dd is the two-digit day value
- Example Value : 2013-03-07
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.5
- Description : Closure start time in PST or PDT
- Type : xs:time
- Nominal Value : hh:mm:ss; where hh is the two-digit hour value, mm is the two-digit minute value and ss is the two-digit second value
- Example Value : 07:01:00
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.6
- Description : Describes the Unix's signed 64 bit integer time format.
- Type : xs:long
- Nominal Value : 0 to 9223372036854775807
- Example Value : 1362668460
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.7
- Description : Closure end date
- Type : xs:date
- Nominal Value : yyyy-mm-dd; where yyyy is the four-digit year value, mm is the two-digit month value and dd is the two-digit day value. if indefinite, closureEndDate will be 2999-12-31, closureEndTime will be 23:59:00.
- Example Value : 2013-03-07
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.8
- Description : Closure end time in PST or PDT
- Type : xs:time
- Nominal Value : hh:mm:ss; where hh is the two-digit hour value, mm is the two-digit minute value and ss is the two-digit second value. if indefinite, closureEndDate will be 2999-12-31, closureEndTime will be 23:59:00.
- Example Value : 15:01:00
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.9
- Description : Describes the Unix's signed 64 bit integer time format. if indefinite, closureEndEpoch will be 32503708740.
- Type : xs:long
- Nominal Value : 0 to 9223372036854775807
- Example Value : 1362697260
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.3.10
- Description : Describes if closureEndDate and closureEndTime are both indefinite.
- Type : xs:boolean
- Nominal Value : true / false
- Example Value : false
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.4
- Description : Type of roadway facility
- Type : xs:string
- Nominal Value : See Facility Chart for more information
- Example Value : Mainline
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.5
- Description : Type of closure being performed
- Type : xs:string
- Nominal Value : Lane / Full / One-way / Alternating
- Example Value : Lane
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.6
- Description : Type of work being performed
- Type : xs:string
- Nominal Value : See Type of Work Chart for more information
- Example Value : Shoulder Work
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.7
- Description : Estimation of the duration of closure
- Type : xs:string
- Nominal Value : See Duration Chart for more information
- Example Value : Standard
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.8
- Description : Estimated delay due to the closure
- Type : xs:int
- Nominal Value : 0 to 999 / Not Reported
- Example Value : 0
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.9
- Description : Lanes of the roadway to be closed
- Type : xs:int
- Nominal Value : 0 to 10 / See Lane Type Chart
- Example Value : 2, RShoulder
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.10
- Description : Total number of travel lanes for traffic
- Type : xs:int
- Nominal Value : 0 to 10 / Not Reported
- Example Value : 2
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.11
- Description : Does the closure meet the criteria for reporting to the Caltrans Highway Information Network (CHIN)?
- Type : xs:boolean
- Nominal Value : true / false
- Example Value : false
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.12
- Description : Wrapper for this record's status start of closure
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.12.1
- Description : Has the closure started?
- Type : xs:boolean
- Nominal Value : true / false
- Example Value : false
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.12.2
- Description : Wrapper for closure start timestamp
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.12.2.1
- Description : Date the closure started
- Type : xs:date
- Nominal Value : yyyy-mm-dd; where yyyy is the four-digit year value, mm is the two-digit month value and dd is the two-digit day value
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.12.2.2
- Description : Time the closure started in PST or PDT
- Type : xs:time
- Nominal Value : hh:mm:ss; where hh is the two-digit hour value, mm is the two-digit minute value and ss is the two-digit second value
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.12.2.3
- Description : Describes the Unix's signed 64 bit integer time format.
- Type : xs:long
- Nominal Value : 0 to 9223372036854775807
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.13
- Description : Wrapper for closure end time
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.13.1
- Description : Has the closure ended?
- Type : xs:boolean
- Nominal Value : true / false
- Example Value : false
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.13.2
- Description : Wrapper for closure end timestamp
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.13.2.1
- Description : Date the closure ended
- Type : xs:date
- Nominal Value : yyyy-mm-dd; where yyyy is the four-digit year value, mm is the two-digit month value and dd is the two-digit day value
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.13.2.2
- Description : Time the closure ended in PST or PDT
- Type : xs:time
- Nominal Value : hh:mm:ss; where hh is the two-digit hour value, mm is the two-digit minute value and ss is the two-digit second value
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.13.2.3
- Description : Describes the Unix's signed 64 bit integer time format.
- Type : xs:long
- Nominal Value : 0 to 9223372036854775807
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.14
- Description : Wrapper for closure cancellation
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.14.1
- Description : Has the closure been cancelled?
- Type : xs:boolean
- Nominal Value : true / false
- Example Value : false
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.14.2
- Description : Wrapper for closure cancellation timestamp
- Type : not applicable
- Nominal Value : not applicable
- Example Value : not applicable
- Used in file formats : JSON, XML
- Field Number : 1.1.4.14.2.1
- Description : Date the closure was cancelled
- Type : xs:date
- Nominal Value : yyyy-mm-dd; where yyyy is the four-digit year value, mm is the two-digit month value and dd is the two-digit day value
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.14.2.2
- Description : Time the closure was cancelled in PST or PDT
- Type : xs:time
- Nominal Value : hh:mm:ss; where hh is the two-digit hour value, mm is the two-digit minute value and ss is the two-digit second value
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML
- Field Number : 1.1.4.14.2.3
- Description : Describes the Unix's signed 64 bit integer time format.
- Type : xs:long
- Nominal Value : 0 to 9223372036854775807
- Example Value :
- Used in file formats : CSV, JSON, TXT, XML