nl2sqlproj/spider2-nl2sql huggingface dataset:
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.factor_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"),
  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_2020` (state_number, state_name, consecutive_number, vehicle_number, contributing_circumstances_motor_vehicle, contributing_circumstances_motor_vehicle_name) VALUES (1, 'Alabama', 10049, 5, 0, 'None Noted'), (1, 'Alabama', 10106, 5, 0, 'None Noted'), (1, 'Alabama', 10367, 5, 0, 'None Noted'), (1, 'Alabama', 10571, 5, 0, 'None Noted'), (1, 'Alabama', 10572, 5, 0, 'None Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.damage_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"),
  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_2020` (state_number, state_name, consecutive_number, vehicle_number, damaged_areas, damaged_areas_name) VALUES (1, 'Alabama', 10572, 6, 13, 'Top'), (5, 'Arkansas', 50373, 5, 13, 'Top'), (5, 'Arkansas', 50460, 5, 13, 'Top'), (6, 'California', 60298, 5, 13, 'Top'), (6, 'California', 60400, 5, 13, 'Top');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_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"),
  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_2018` (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', 10059, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10141, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10141, 6, 0, 'None/Apparently Normal'), (1, 'Alabama', 10333, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10386, 5, 0, 'None/Apparently Normal');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.vision_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"),
  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_2019` (state_number, state_name, consecutive_number, vehicle_number, drivers_vision_obscured_by, drivers_vision_obscured_by_name) VALUES (1, 'Alabama', 10390, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10532, 5, 0, 'No Obstruction Noted'), (4, 'Arizona', 40257, 5, 0, 'No Obstruction Noted'), (4, 'Arizona', 40257, 6, 0, 'No Obstruction Noted'), (4, 'Arizona', 40257, 7, 0, 'No Obstruction Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.vision_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"),
  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_2018` (state_number, state_name, consecutive_number, vehicle_number, drivers_vision_obscured_by, drivers_vision_obscured_by_name) VALUES (1, 'Alabama', 10059, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10141, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10141, 6, 0, 'No Obstruction Noted'), (1, 'Alabama', 10333, 5, 0, 'No Obstruction Noted'), (1, 'Alabama', 10386, 5, 0, 'No Obstruction Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_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"),
  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_2019` (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', 10390, 5, 0, 'None/Apparently Normal'), (1, 'Alabama', 10532, 5, 0, 'None/Apparently Normal'), (4, 'Arizona', 40037, 5, 0, 'None/Apparently Normal'), (4, 'Arizona', 40257, 5, 0, 'None/Apparently Normal'), (4, 'Arizona', 40257, 6, 0, 'None/Apparently Normal');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.violatn_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"),
  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_2015` (state_number, state_name, consecutive_number, vehicle_number, violations_charged, violations_charged_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.nmprior_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_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_2016` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_action_circumstances, non_motorist_action_circumstances_name) VALUES (6, 'California', 60433, 0, 1, 1, 'Going To or From School (K-12)'), (8, 'Colorado', 80017, 0, 1, 1, 'Going To or From School (K-12)'), (15, 'Hawaii', 150091, 0, 1, 1, 'Going To or From School (K-12)'), (28, 'Mississippi', 280634, 0, 1, 1, 'Going To or From School (K-12)'), (29, 'Missouri', 290188, 0, 1, 1, 'Going To or From School (K-12)');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.damage_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"),
  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_2017` (state_number, state_name, consecutive_number, vehicle_number, damaged_areas, damaged_areas_name) VALUES (4, 'Arizona', 40715, 6, 15, 'No Damage'), (4, 'Arizona', 40715, 9, 15, 'No Damage'), (4, 'Arizona', 40715, 10, 15, 'No Damage'), (4, 'Arizona', 40715, 11, 15, 'No Damage'), (6, 'California', 60018, 5, 15, 'No Damage');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmprior_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_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_2020` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_action_circumstances, non_motorist_action_circumstances_name) VALUES (10, 'Delaware', 100081, 0, 1, 1, 'Going To or From School (K-12)'), (26, 'Michigan', 260597, 0, 1, 1, 'Going To or From School (K-12)'), (55, 'Wisconsin', 550050, 0, 2, 1, 'Going To or From School (K-12)'), (55, 'Wisconsin', 550398, 0, 1, 1, 'Going To or From School (K-12)'), (4, 'Arizona', 40038, 0, 1, 2, 'Waiting to Cross Roadway');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_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"),
  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.")
)
OPTIONS(
  description="This data file contains information about physical impairments\nof drivers of motor vehicles. There is one record per impairment and there is at least one\nrecord for each driver of an in-transport motor vehicle"
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_2015` (state_number, state_name, consecutive_number, vehicle_number, condition_impairment_at_time_of_crash_driver, condition_impairment_at_time_of_crash_driver_name) VALUES (2, 'Alaska', 20035, 5, 98, 'Not Reported'), (2, 'Alaska', 20035, 6, 98, 'Not Reported'), (17, 'Illinois', 170920, 7, 98, 'Not Reported'), (17, 'Illinois', 170920, 8, 98, 'Not Reported'), (20, 'Kansas', 200060, 5, 98, 'Not Reported');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.factor_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"),
  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_2017` (state_number, state_name, consecutive_number, vehicle_number, contributing_circumstances_motor_vehicle, contributing_circumstances_motor_vehicle_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.violatn_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"),
  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_2019` (state_number, state_name, consecutive_number, vehicle_number, violations_charged, violations_charged_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.violatn_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"),
  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_2020` (state_number, state_name, consecutive_number, vehicle_number, violations_charged, violations_charged_name) VALUES (1, 'Alabama', 10049, 5, '0', 'None'), (1, 'Alabama', 10106, 5, '0', 'None'), (1, 'Alabama', 10367, 5, '0', 'None'), (1, 'Alabama', 10571, 5, '0', 'None'), (1, 'Alabama', 10572, 5, '0', 'None');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.vision_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"),
  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_2017` (state_number, state_name, consecutive_number, vehicle_number, drivers_vision_obscured_by, drivers_vision_obscured_by_name) VALUES (1, 'Alabama', 10477, 5, 0, 'No Obstruction Noted'), (4, 'Arizona', 40164, 5, 0, 'No Obstruction Noted'), (4, 'Arizona', 40164, 6, 0, 'No Obstruction Noted'), (4, 'Arizona', 40164, 7, 0, 'No Obstruction Noted'), (4, 'Arizona', 40453, 5, 0, 'No Obstruction Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.drimpair_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"),
  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_2016` (state_number, state_name, consecutive_number, vehicle_number, condition_impairment_at_time_of_crash_driver, condition_impairment_at_time_of_crash_driver_name) VALUES (19, 'Iowa', 190336, 5, 98, 'Not Reported'), (29, 'Missouri', 290236, 5, 98, 'Not Reported'), (29, 'Missouri', 290236, 6, 98, 'Not Reported'), (29, 'Missouri', 290238, 5, 98, 'Not Reported'), (29, 'Missouri', 290554, 5, 98, 'Not Reported');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmprior_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"),
  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_2019` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_action_circumstances, non_motorist_action_circumstances_name) VALUES (4, 'Arizona', 40827, 0, 1, 1, 'Going To or From School (K-12)'), (8, 'Colorado', 80036, 0, 1, 1, 'Going To or From School (K-12)'), (8, 'Colorado', 80473, 0, 1, 1, 'Going To or From School (K-12)'), (11, 'District of Columbia', 110017, 0, 1, 1, 'Going To or From School (K-12)'), (12, 'Florida', 120768, 0, 1, 1, 'Going To or From School (K-12)');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.damage_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"),
  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_2018` (state_number, state_name, consecutive_number, vehicle_number, damaged_areas, damaged_areas_name) VALUES (1, 'Alabama', 10141, 5, 15, 'No Damage'), (1, 'Alabama', 10141, 6, 15, 'No Damage'), (5, 'Arkansas', 50188, 5, 15, 'No Damage'), (6, 'California', 60274, 5, 15, 'No Damage'), (6, 'California', 60600, 5, 15, 'No Damage');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.factor_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"),
  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_2018` (state_number, state_name, consecutive_number, vehicle_number, contributing_circumstances_motor_vehicle, contributing_circumstances_motor_vehicle_name) VALUES (1, 'Alabama', 10059, 5, 0, 'None'), (1, 'Alabama', 10141, 5, 0, 'None'), (1, 'Alabama', 10141, 6, 0, 'None'), (1, 'Alabama', 10333, 5, 0, 'None'), (1, 'Alabama', 10386, 5, 0, 'None');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.violatn_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"),
  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_2016` (state_number, state_name, consecutive_number, vehicle_number, violations_charged, violations_charged_name) VALUES (1, 'Alabama', 10264, 5, '0', 'None'), (1, 'Alabama', 10762, 5, '0', 'None'), (1, 'Alabama', 10762, 6, '0', 'None'), (1, 'Alabama', 10845, 5, '0', 'None'), (1, 'Alabama', 10878, 5, '0', 'None');