nl2sqlproj/spider2-nl2sql huggingface dataset:
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmprior_2015`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  person_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files. 001-999 Assigned Person Number"),
  non_motorist_action_circumstances INT64 OPTIONS(description="This data element describes the action(s) of the non-motorist immediately prior to their involvement in the crash. For more info on the codes, please look at <NM11 Non-Motorist Action/Circumstances> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  non_motorist_action_circumstances_name STRING OPTIONS(description="This data element describes the action(s) of the non-motorist immediately prior to their involvement in the crash.")
)
OPTIONS(
  description="This data file contains information about the actions of people\nwho are not occupants of motor vehicles (e.g., pedestrians and bicyclists) at the time of\ntheir involvement in the crash. There is one record per action and there is at least one\nrecord for each person who is not an occupant of a motor vehicle."
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.nmprior_2015` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_action_circumstances, non_motorist_action_circumstances_name) VALUES (13, 'Georgia', 130830, 0, 1, 1, 'Going To or From School (K-12)'), (20, 'Kansas', 200273, 0, 1, 1, 'Going To or From School (K-12)'), (21, 'Kentucky', 210469, 0, 1, 1, 'Going To or From School (K-12)'), (49, 'Utah', 490258, 0, 1, 1, 'Going To or From School (K-12)'), (56, 'Wyoming', 560042, 0, 1, 1, 'Going To or From School (K-12)');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_2020`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  condition_impairment_at_time_of_crash_driver INT64 OPTIONS(description="This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement. For more info on the codes, please look at <D23 Condition (Impairment) at Time of Crash- Driver> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  condition_impairment_at_time_of_crash_driver_name STRING OPTIONS(description="This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_2020` (state_number, state_name, consecutive_number, vehicle_number, condition_impairment_at_time_of_crash_driver, condition_impairment_at_time_of_crash_driver_name) VALUES (1, 'Alabama', 10049, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10106, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10367, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10571, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10572, 5, 0, 'None/Apparently Normal');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.violatn_2017`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  violations_charged STRING OPTIONS(description="This data element identifies all violations charged to this driver. For more info on the codes, please look at <D21 Violations Charged> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  violations_charged_name STRING OPTIONS(description="This data element identifies all violations charged to this driver. For more info on the codes, please look at <D21 Violations Charged> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.violatn_2017` (state_number, state_name, consecutive_number, vehicle_number, violations_charged, violations_charged_name) VALUES (1, 'Alabama', 10477, 5, '0', 'None'), (4, 'Arizona', 40164, 5, '0', 'None'), (4, 'Arizona', 40164, 6, '0', 'None'), (4, 'Arizona', 40164, 7, '0', 'None'), (4, 'Arizona', 40453, 5, '0', 'None');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.vision_2020`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  drivers_vision_obscured_by INT64 OPTIONS(description="This data element records impediments to this driver’s visual field that were noted in the case materials. For more info on the codes, please look at <PC14 Driver’s Vision Obscured by> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  drivers_vision_obscured_by_name STRING OPTIONS(description="This data element records impediments to this driver’s visual field that were noted in the case materials. For more info on the codes, please look at <PC14 Driver’s Vision Obscured by> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.vision_2020` (state_number, state_name, consecutive_number, vehicle_number, drivers_vision_obscured_by, drivers_vision_obscured_by_name) VALUES (1, 'Alabama', 10049, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10106, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10367, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10571, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10572, 5, 0, 'No Obstruction Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.factor_2019`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  contributing_circumstances_motor_vehicle INT64 OPTIONS(description="This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash. For more info on the codes, please look at <PC4 Contributing Circumstances, Motor Vehicle> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  contributing_circumstances_motor_vehicle_name STRING OPTIONS(description="This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.factor_2019` (state_number, state_name, consecutive_number, vehicle_number, contributing_circumstances_motor_vehicle, contributing_circumstances_motor_vehicle_name) VALUES (1, 'Alabama', 10390, 5, 0, 'None'), (1, 'Alabama', 10532, 5, 0, 'None'), (4, 'Arizona', 40037, 5, 0, 'None'), (4, 'Arizona', 40257, 5, 0, 'None'), (4, 'Arizona', 40257, 6, 0, 'None');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.damage_2019`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  damaged_areas INT64 OPTIONS(description="This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case materials. 1-12 Clock points 13 Top 14 Undercarriage 15 No Damage 99 Unknown"),
  damaged_areas_name STRING OPTIONS(description="This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case materials.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.damage_2019` (state_number, state_name, consecutive_number, vehicle_number, damaged_areas, damaged_areas_name) VALUES (1, 'Alabama', 10390, 5, 1, '1 Clock Value'), (4, 'Arizona', 40257, 7, 1, '1 Clock Value'), (5, 'Arkansas', 50123, 5, 1, '1 Clock Value'), (5, 'Arkansas', 50163, 5, 1, '1 Clock Value'), (5, 'Arkansas', 50411, 5, 1, '1 Clock Value');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmprior_2018`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  person_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files. 001-999 Assigned Person Number"),
  non_motorist_action_circumstances INT64 OPTIONS(description="This data element describes the action(s) of the non-motorist immediately prior to their involvement in the crash. For more info on the codes, please look at <NM11 Non-Motorist Action/Circumstances> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  non_motorist_action_circumstances_name STRING OPTIONS(description="This data element describes the action(s) of the non-motorist immediately prior to their involvement in the crash.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.nmprior_2018` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_action_circumstances, non_motorist_action_circumstances_name) VALUES (4, 'Arizona', 40643, 0, 1, 1, 'Going To or From School (K-12)'), (8, 'Colorado', 80018, 0, 1, 1, 'Going To or From School (K-12)'), (8, 'Colorado', 80133, 0, 1, 1, 'Going To or From School (K-12)'), (8, 'Colorado', 80170, 0, 1, 1, 'Going To or From School (K-12)'), (13, 'Georgia', 131144, 0, 1, 1, 'Going To or From School (K-12)');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.factor_2015`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  contributing_circumstances_motor_vehicle INT64 OPTIONS(description="This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash. For more info on the codes, please look at <PC4 Contributing Circumstances, Motor Vehicle> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  contributing_circumstances_motor_vehicle_name STRING OPTIONS(description="This data element describes this vehicle’s possible pre-existing defects or maintenance conditions that may have contributed to the crash.")
)
OPTIONS(
  description="This data file contains information about vehicle circumstances\nwhich may have contributed to the crash. There is at least one record per in-transport\nmotor vehicle. Each factor is a separate record."
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.factor_2015` (state_number, state_name, consecutive_number, vehicle_number, contributing_circumstances_motor_vehicle, contributing_circumstances_motor_vehicle_name) VALUES (1, 'Alabama', 10034, 5, 0, 'None'), (1, 'Alabama', 10034, 6, 0, 'None'), (1, 'Alabama', 10095, 5, 0, 'None'), (1, 'Alabama', 10095, 6, 0, 'None'), (1, 'Alabama', 10095, 7, 0, 'None');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_2017`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  condition_impairment_at_time_of_crash_driver INT64 OPTIONS(description="This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement. For more info on the codes, please look at <D23 Condition (Impairment) at Time of Crash- Driver> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  condition_impairment_at_time_of_crash_driver_name STRING OPTIONS(description="This data element identifies physical impairments to this driver that may have contributed to the crash as identified by law enforcement.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_2017` (state_number, state_name, consecutive_number, vehicle_number, condition_impairment_at_time_of_crash_driver, condition_impairment_at_time_of_crash_driver_name) VALUES (1, 'Alabama', 10477, 5, 0, 'None/Apparently Normal'), (4, 'Arizona', 40164, 5, 0, 'None/Apparently Normal'), (4, 'Arizona', 40164, 6, 0, 'None/Apparently Normal'), (4, 'Arizona', 40164, 7, 0, 'None/Apparently Normal'), (4, 'Arizona', 40453, 5, 0, 'None/Apparently Normal');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.vision_2016`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  drivers_vision_obscured_by INT64 OPTIONS(description="This data element records impediments to this driver’s visual field that were noted in the case materials. For more info on the codes, please look at <PC14 Driver’s Vision Obscured by> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  drivers_vision_obscured_by_name STRING OPTIONS(description="This data element records impediments to this driver’s visual field that were noted in the case materials. For more info on the codes, please look at <PC14 Driver’s Vision Obscured by> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.vision_2016` (state_number, state_name, consecutive_number, vehicle_number, drivers_vision_obscured_by, drivers_vision_obscured_by_name) VALUES (1, 'Alabama', 10264, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10762, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10762, 6, 0, 'No Obstruction Noted'), (1, 'Alabama', 10845, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10878, 5, 0, 'No Obstruction Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.damage_2015`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  damaged_areas INT64 OPTIONS(description="This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case materials. 1-12 Clock points 13 Top 14 Undercarriage 15 No Damage 99 Unknown"),
  damaged_areas_name STRING OPTIONS(description="This data element identifies all the areas on this vehicle that were damaged in the crash as reflected in the case materials.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.damage_2015` (state_number, state_name, consecutive_number, vehicle_number, damaged_areas, damaged_areas_name) VALUES (1, 'Alabama', 10141, 5, 1, '1 Clock Value'), (1, 'Alabama', 10141, 6, 1, '1 Clock Value'), (1, 'Alabama', 10286, 5, 1, '1 Clock Value'), (1, 'Alabama', 10343, 5, 1, '1 Clock Value'), (4, 'Arizona', 40532, 7, 1, '1 Clock Value');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.distract_2015`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  driver_distracted_by INT64 OPTIONS(description="This data element identifies the attribute(s) which best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. For more info on the codes, please look at <PC16 Driver Distracted By> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  driver_distracted_by_name STRING OPTIONS(description="This data element identifies the attribute(s) which best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur.")
)
OPTIONS(
  description="This data file contains information about driver distractions.\nThere is at least one record per in-transport motor vehicle. Each distraction is a separate\nrecord."
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.distract_2015` (state_number, state_name, consecutive_number, vehicle_number, driver_distracted_by, driver_distracted_by_name) VALUES (1, 'Alabama', 10034, 5, 0, 'Not Distracted'), (1, 'Alabama', 10034, 6, 0, 'Not Distracted'), (1, 'Alabama', 10095, 10, 0, 'Not Distracted'), (1, 'Alabama', 10141, 5, 0, 'Not Distracted'), (1, 'Alabama', 10141, 6, 0, 'Not Distracted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmcrash_2020`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  person_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files. 001-999 Assigned Person Number"),
  non_motorist_contributing_circumstances INT64 OPTIONS(description="This data element describes the action(s) and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash. For more info on the codes, please look at <NM12 Non-Motorist Contributing Circumstances> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  non_motorist_contributing_circumstances_name STRING OPTIONS(description="This data element describes the action(s) and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.nmcrash_2020` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_contributing_circumstances, non_motorist_contributing_circumstances_name) VALUES (1, 'Alabama', 10044, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10156, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10169, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10186, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10209, 0, 1, 0, 'None Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.maneuver_2018`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  driver_maneuvered_to_avoid INT64 OPTIONS(description="This data element identifies the thing(s) this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle. For more info on the codes, please look at <PC15 Driver Maneuvered to Avoid> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  driver_maneuvered_to_avoid_name STRING OPTIONS(description="This data element identifies the thing(s) this driver attempted to avoid while the vehicle was on the road portion of the trafficway, just prior to the first harmful event for this vehicle.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.maneuver_2018` (state_number, state_name, consecutive_number, vehicle_number, driver_maneuvered_to_avoid, driver_maneuvered_to_avoid_name) VALUES (1, 'Alabama', 10141, 5, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10141, 6, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10386, 5, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10519, 5, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10531, 5, 0, 'Driver Did Not Maneuver to Avoid');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmimpair_2015`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  person_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files. 001-999 Assigned Person Number"),
  condition_impairment_at_time_of_crash_non_motorist INT64 OPTIONS(description="This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement. For more info on the codes, please look at <NM14 Condition (Impairment) at Time of Crash- Non-Motorist> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  condition_impairment_at_time_of_crash_non_motorist_name STRING OPTIONS(description="This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.")
)
OPTIONS(
  description="This data file contains information about physical\nimpairments of people who are not occupants of motor vehicles. There is one record per\nimpairment and there is at least one record for each person who is not an occupant of a\nmotor vehicle."
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.nmimpair_2015` (state_number, state_name, consecutive_number, vehicle_number, person_number, condition_impairment_at_time_of_crash_non_motorist, condition_impairment_at_time_of_crash_non_motorist_name) VALUES (1, 'Alabama', 10777, 0, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10777, 0, 6, 0, 'None/Apparently Normal'), (1, 'Alabama', 10777, 0, 7, 0, 'None/Apparently Normal'), (1, 'Alabama', 10777, 0, 8, 0, 'None/Apparently Normal'), (1, 'Alabama', 10777, 0, 9, 0, 'None/Apparently Normal');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.distract_2019`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  driver_distracted_by INT64 OPTIONS(description="This data element identifies the attribute(s) which best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur. For more info on the codes, please look at <PC16 Driver Distracted By> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  driver_distracted_by_name STRING OPTIONS(description="This data element identifies the attribute(s) which best describe this driver’s attention to driving prior to the driver’s realization of an impending critical event or just prior to impact if realization of an impending critical event does not occur.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.distract_2019` (state_number, state_name, consecutive_number, vehicle_number, driver_distracted_by, driver_distracted_by_name) VALUES (1, 'Alabama', 10390, 5, 96, 'Not Reported'), (6, 'California', 60320, 5, 96, 'Not Reported'), (6, 'California', 60320, 6, 96, 'Not Reported'), (6, 'California', 60419, 5, 96, 'Not Reported'), (6, 'California', 61386, 5, 96, 'Not Reported');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmimpair_2019`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  person_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files. 001-999 Assigned Person Number"),
  condition_impairment_at_time_of_crash_non_motorist INT64 OPTIONS(description="This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement. For more info on the codes, please look at <NM14 Condition (Impairment) at Time of Crash- Non-Motorist> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  condition_impairment_at_time_of_crash_non_motorist_name STRING OPTIONS(description="This data element identifies physical impairments to this non-motorist that may have contributed to the crash as identified by law enforcement.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.nmimpair_2019` (state_number, state_name, consecutive_number, vehicle_number, person_number, condition_impairment_at_time_of_crash_non_motorist, condition_impairment_at_time_of_crash_non_motorist_name) VALUES (1, 'Alabama', 10368, 0, 4, 0, 'None/Apparently Normal'), (6, 'California', 61258, 0, 4, 0, 'None/Apparently Normal'), (6, 'California', 62124, 0, 4, 0, 'None/Apparently Normal'), (6, 'California', 62124, 0, 5, 0, 'None/Apparently Normal'), (6, 'California', 62124, 0, 6, 0, 'None/Apparently Normal');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmcrash_2016`
(
  state_number INT64 OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC). For more info on the codes, please look at <C1/V1/D1/PC1/P1/NM1 State Number> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  state_name STRING OPTIONS(description="This data element identifies the state in which the crash occurred. The codes are from the General Services Administration’s (GSA) publication of worldwide Geographic Location Codes (GLC)."),
  consecutive_number INT64 OPTIONS(description="This data element is the unique case number assigned to each crash. It appears on each data file and is used to merge information from the data files together. xxxxxx Two Characters for State Code followed by Four Characters for Case Number"),
  vehicle_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each vehicle in the case. This data element appears on each vehicle level data file and is used in conjunction with the ST_CASE data element to merge information from vehicle level data files. 000-999 Assigned Number of Motor Vehicle"),
  person_number INT64 OPTIONS(description="This data element is the consecutive number assigned to each person in the case (i.e., each occupant, pedestrian, or non-motorists involved in the crash). This data element appears on each person level data file and is used in conjunction with the ST_CASE data element (and sometimes the VEH_NO data element) to merge information from person level data files. 001-999 Assigned Person Number"),
  non_motorist_contributing_circumstances INT64 OPTIONS(description="This data element describes the action(s) and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash. For more info on the codes, please look at <NM12 Non-Motorist Contributing Circumstances> section in the pdf: https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812315"),
  non_motorist_contributing_circumstances_name STRING OPTIONS(description="This data element describes the action(s) and/or circumstances of this non-motorist that law enforcement indicated may have contributed to the crash.")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.nmcrash_2016` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_contributing_circumstances, non_motorist_contributing_circumstances_name) VALUES (1, 'Alabama', 10013, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10013, 0, 2, 0, 'None Noted'), (1, 'Alabama', 10024, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10039, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10085, 0, 1, 0, 'None Noted');