nl2sqlproj/spider2-nl2sql huggingface dataset:
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmcrash_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"),
  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_2017` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_contributing_circumstances, non_motorist_contributing_circumstances_name) VALUES (1, 'Alabama', 10065, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10079, 0, 1, 0, 'None Noted'), (1, 'Alabama', 10079, 0, 2, 0, 'None Noted'), (1, 'Alabama', 10079, 0, 3, 0, 'None Noted'), (1, 'Alabama', 10118, 0, 1, 0, 'None Noted');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.nmimpair_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"),
  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_2018` (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 (18, 'Indiana', 180490, 0, 9, 0, 'None/Apparently Normal'), (25, 'Massachusetts', 250343, 0, 5, 0, 'None/Apparently Normal'), (36, 'New York', 360078, 0, 5, 0, 'None/Apparently Normal'), (36, 'New York', 360712, 0, 5, 0, 'None/Apparently Normal'), (36, 'New York', 360744, 0, 5, 0, 'None/Apparently Normal');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.maneuver_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_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.")
)
OPTIONS(
  description="This data file contains information about actions taken by\nthe driver to avoid something or someone in the road. There is at least one record per\nin-transport motor vehicle. Each maneuver is a separate record."
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.maneuver_2015` (state_number, state_name, consecutive_number, vehicle_number, driver_maneuvered_to_avoid, driver_maneuvered_to_avoid_name) VALUES (1, 'Alabama', 10034, 5, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10034, 6, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10095, 5, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10095, 6, 0, 'Driver Did Not Maneuver to Avoid'), (1, 'Alabama', 10095, 7, 0, 'Driver Did Not Maneuver to Avoid');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.distract_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_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_2018` (state_number, state_name, consecutive_number, vehicle_number, driver_distracted_by, driver_distracted_by_name) VALUES (1, 'Alabama', 10141, 5, 96, 'Not Reported'), (1, 'Alabama', 10141, 6, 96, 'Not Reported'), (1, 'Alabama', 10333, 5, 96, 'Not Reported'), (6, 'California', 61372, 5, 96, 'Not Reported'), (6, 'California', 61824, 5, 96, 'Not Reported');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.safetyeq_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_safety_equipment_use STRING OPTIONS(description="This data element indicates the safety equipment that was used by this nonmotorist involved in the crash. 1 None Used 2 Helmet -- Reflective Equipment/Clothing (Jacket, Backpack, etc.) 3 Reflective Clothing (Jacket, Backpack, etc.) 4 Protective Pads (Elbows, Knees, Shins, etc.) 5 Lighting 7 Other Safety Equipment 8 Not Reported 9 Unknown if Used"),
  non_motorist_safety_equipment_use_name STRING OPTIONS(description="This data element indicates the safety equipment that was used by this nonmotorist involved in the crash. 1 None Used 2 Helmet -- Reflective Equipment/Clothing (Jacket, Backpack, etc.) 3 Reflective Clothing (Jacket, Backpack, etc.) 4 Protective Pads (Elbows, Knees, Shins, etc.) 5 Lighting 7 Other Safety Equipment 8 Not Reported 9 Unknown if Used")
);

INSERT INTO `bigquery-public-data.nhtsa_traffic_fatalities.safetyeq_2016` (state_number, state_name, consecutive_number, vehicle_number, person_number, non_motorist_safety_equipment_use, non_motorist_safety_equipment_use_name) VALUES (1, 'Alabama', 10381, 0, 4, '1', 'None Used'), (1, 'Alabama', 10381, 0, 5, '1', 'None Used'), (1, 'Alabama', 10381, 0, 6, '1', 'None Used'), (1, 'Alabama', 10381, 0, 7, '1', 'None Used'), (6, 'California', 62896, 0, 4, '1', 'None Used');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.nhtsa_traffic_fatalities.maneuver_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_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_2019` (state_number, state_name, consecutive_number, vehicle_number, driver_maneuvered_to_avoid, driver_maneuvered_to_avoid_name) VALUES (1, 'Alabama', 10532, 5, 0, 'Driver Did Not Maneuver to Avoid'), (4, 'Arizona', 40257, 5, 0, 'Driver Did Not Maneuver to Avoid'), (4, 'Arizona', 40257, 6, 0, 'Driver Did Not Maneuver to Avoid'), (4, 'Arizona', 40257, 7, 0, 'Driver Did Not Maneuver to Avoid'), (4, 'Arizona', 40259, 5, 0, 'Driver Did Not Maneuver to Avoid');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.new_york.tlc_fhv_trips_2015`
(
  location_id INT64 OPTIONS(description="The TLC taxi zone of the trip pick-up."),
  pickup_datetime TIMESTAMP OPTIONS(description="The date and time of the trip pick-up."),
  dispatching_base_num STRING OPTIONS(description="The TLC Base License Number of the base that dispatched the trip."),
  borough STRING OPTIONS(description=""),
  zone STRING OPTIONS(description=""),
  service_zone STRING OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.new_york.tlc_fhv_trips_2015` (location_id, pickup_datetime, dispatching_base_num, borough, zone, service_zone) VALUES (NULL, '2015-12-16 14:00:00+00:00', 'B00001', '', '', ''), (NULL, '2015-06-03 07:00:00+00:00', 'B00001', '', '', ''), (NULL, '2015-10-15 11:00:00+00:00', 'B00001', '', '', ''), (NULL, '2015-05-18 07:40:00+00:00', 'B00001', '', '', ''), (NULL, '2015-06-12 18:00:00+00:00', 'B00001', '', '', '');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.new_york.citibike_trips`
(
  tripduration INT64 OPTIONS(description="Trip Duration (in seconds)"),
  starttime TIMESTAMP OPTIONS(description="Start Time"),
  stoptime TIMESTAMP OPTIONS(description="Stop Time"),
  start_station_id INT64 OPTIONS(description="Start Station ID"),
  start_station_name STRING OPTIONS(description="Start Station Name"),
  start_station_latitude FLOAT64 OPTIONS(description="Start Station Latitude"),
  start_station_longitude FLOAT64 OPTIONS(description="Start Station Longitude"),
  end_station_id INT64 OPTIONS(description="End Station ID"),
  end_station_name STRING OPTIONS(description="End Station Name"),
  end_station_latitude FLOAT64 OPTIONS(description="End Station Latitude"),
  end_station_longitude FLOAT64 OPTIONS(description="End Station Longitude"),
  bikeid INT64 OPTIONS(description="Bike ID"),
  usertype STRING OPTIONS(description="User Type (Customer = 24-hour pass or 7-day pass user, Subscriber = Annual Member)"),
  birth_year INT64 OPTIONS(description="Year of Birth"),
  gender STRING OPTIONS(description="Gender (unknown, male, female)")
);

INSERT INTO `bigquery-public-data.new_york.citibike_trips` (tripduration, starttime, stoptime, start_station_id, start_station_name, start_station_latitude, start_station_longitude, end_station_id, end_station_name, end_station_latitude, end_station_longitude, bikeid, usertype, birth_year, gender) VALUES (1367, '2016-08-07 14:42:39+00:00', '2016-08-07 15:05:26+00:00', 520, 'W 52 St & 5 Ave', 40.75992262, -73.97648516, 3265, 'E 2 St & 2 Ave', 40.7245634290432, -73.9894437789917, 17847, 'Customer', NULL, 'unknown'), (1405, '2016-09-27 17:51:51+00:00', '2016-09-27 18:15:17+00:00', 520, 'W 52 St & 5 Ave', 40.75992262, -73.97648516, 263, 'Elizabeth St & Hester St', 40.717590818059804, -73.99622440338135, 25536, 'Subscriber', 1991, 'male'), (335, '2015-11-16 16:22:47+00:00', '2015-11-16 16:28:22+00:00', 520, 'W 52 St & 5 Ave', 40.75992262, -73.97648516, 3234, 'E 40 St & Madison Ave', 40.751593684511114, -73.98043155670166, 14914, 'Subscriber', 1959, 'male'), (605, '2016-05-09 16:59:20+00:00', '2016-05-09 17:09:25+00:00', 520, 'W 52 St & 5 Ave', 40.75992262, -73.97648516, 3236, 'W 42 St & Dyer Ave', 40.75898481399634, -73.99379968643188, 18863, 'Subscriber', 1960, 'male'), (579, '2016-05-31 17:08:55+00:00', '2016-05-31 17:18:34+00:00', 520, 'W 52 St & 5 Ave', 40.75992262, -73.97648516, 3236, 'W 42 St & Dyer Ave', 40.75898481399634, -73.99379968643188, 14917, 'Subscriber', 1985, 'male');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.new_york.tree_census_1995`
(
  recordid INT64,
  address STRING,
  house_number STRING,
  street STRING,
  zip_original INT64,
  cb_original INT64,
  site STRING,
  species STRING,
  diameter INT64,
  status STRING,
  wires STRING,
  sidewalk_condition STRING,
  support_structure STRING,
  borough STRING,
  x FLOAT64,
  y FLOAT64,
  longitude FLOAT64,
  latitude FLOAT64,
  cb_new INT64,
  zip_new INT64,
  censustract_2010 STRING,
  censusblock_2010 STRING,
  nta_2010 STRING,
  segmentid INT64,
  spc_common STRING,
  spc_latin STRING,
  location STRING
);

INSERT INTO `bigquery-public-data.new_york.tree_census_1995` (recordid, address, house_number, street, zip_original, cb_original, site, species, diameter, status, wires, sidewalk_condition, support_structure, borough, x, y, longitude, latitude, cb_new, zip_new, censustract_2010, censusblock_2010, nta_2010, segmentid, spc_common, spc_latin, location) VALUES (21111, '700 W 123 ST', '700.0', 'W 123 ST', 0, 0, 'Across', 'QUPA', 15, 'Poor', 'None', 'Good', 'None', 'Manhattan', 1.0, 1.0, 1.0, 1.0, 0, 0, NULL, NULL, 'Unknown', 0, 'OAK, PIN', 'QUERCUS PALUSTRIS', '(1.0, 1.0)'), (21116, '700 W 123 ST', '700.0', 'W 123 ST', 0, 0, 'Across', 'QUPA', 13, 'Good', 'None', 'Good', 'None', 'Manhattan', 1.0, 1.0, 1.0, 1.0, 0, 0, NULL, NULL, 'Unknown', 0, 'OAK, PIN', 'QUERCUS PALUSTRIS', '(1.0, 1.0)'), (3219, '53-054 WASHINGTON SQ W', NULL, 'WASHINGTON SQ W', 0, 0, 'Across', 'QUPA', 7, 'Good', 'None', 'Good', 'None', 'Manhattan', 1.0, 1.0, 1.0, 1.0, 0, 0, NULL, NULL, 'Unknown', 0, 'OAK, PIN', 'QUERCUS PALUSTRIS', '(1.0, 1.0)'), (32660, '870/860 1 AV', NULL, '1 AV', 0, 0, 'Across', 'QUPH', 11, 'Good', 'None', 'Good', 'None', 'Manhattan', 1.0, 1.0, 1.0, 1.0, 0, 0, NULL, NULL, 'Unknown', 0, 'OAK, WILLOW', 'QUERCUS PHELLOS', '(1.0, 1.0)'), (32661, '870/860 1 AV', NULL, '1 AV', 0, 0, 'Across', 'QUPH', 11, 'Good', 'None', 'Good', 'None', 'Manhattan', 1.0, 1.0, 1.0, 1.0, 0, 0, NULL, NULL, 'Unknown', 0, 'OAK, WILLOW', 'QUERCUS PHELLOS', '(1.0, 1.0)');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.new_york.citibike_stations`
(
  station_id STRING NOT NULL OPTIONS(description="Unique identifier of a station."),
  name STRING OPTIONS(description="Public name of the station."),
  short_name STRING OPTIONS(description="Short name or other type of identifier, as used by the data publisher."),
  latitude FLOAT64 OPTIONS(description="The latitude of station. The field value must be a valid WGS 84 latitude in decimal degrees format."),
  longitude FLOAT64 OPTIONS(description="The longitude of station. The field value must be a valid WGS 84 latitude in decimal degrees format."),
  region_id INT64 OPTIONS(description="ID of the region where station is located."),
  rental_methods STRING OPTIONS(description="Array of enumerables containing the payment methods accepted at this station."),
  capacity INT64 OPTIONS(description="ANumber of total docking points installed at this station, both available and unavailable."),
  eightd_has_key_dispenser BOOL OPTIONS(description=""),
  num_bikes_available INT64 OPTIONS(description="Number of bikes available for rental."),
  num_bikes_disabled INT64 OPTIONS(description="Number of disabled bikes at the station."),
  num_docks_available INT64 OPTIONS(description="Number of docks accepting bike returns."),
  num_docks_disabled INT64 OPTIONS(description="Number of empty but disabled dock points at the station."),
  is_installed BOOL OPTIONS(description="Is the station currently on the street?"),
  is_renting BOOL OPTIONS(description="Is the station currently renting bikes?"),
  is_returning BOOL OPTIONS(description="Is the station accepting bike returns?"),
  eightd_has_available_keys BOOL OPTIONS(description=""),
  last_reported TIMESTAMP OPTIONS(description="Timestamp indicating the last time this station reported its status to the backend, in NYC local time.")
);

INSERT INTO `bigquery-public-data.new_york.citibike_stations` (station_id, name, short_name, latitude, longitude, region_id, rental_methods, capacity, eightd_has_key_dispenser, num_bikes_available, num_bikes_disabled, num_docks_available, num_docks_disabled, is_installed, is_renting, is_returning, eightd_has_available_keys, last_reported) VALUES ('495', 'W 47 St & 10 Ave', '6824.07', 40.76269882, -73.99301222, 71, 'KEY, CREDITCARD', 0, False, 0, 0, 0, 0, True, True, True, False, '1970-01-02 00:00:00+00:00'), ('3171', 'Amsterdam Ave & W 82 St', '7360.10', 40.78524672, -73.97667321, 71, 'KEY, CREDITCARD', 0, False, 0, 0, 0, 0, False, False, False, False, '1970-01-02 00:00:00+00:00'), ('3603', '31 Ave & 30 St', '6857.09', 40.7647, -73.9240312, 71, 'KEY, CREDITCARD', 0, False, 0, 0, 0, 0, False, False, False, False, '1970-01-02 00:00:00+00:00'), ('3733', 'Avenue C & E 18 St', '5769.04', 40.730563, -73.973984, 71, 'KEY, CREDITCARD', 0, False, 0, 0, 0, 0, False, False, False, False, '1970-01-02 00:00:00+00:00'), ('3792', 'Columbus Dr at Exchange Pl', 'JC106', 40.71687, -74.03281, 70, 'KEY, CREDITCARD', 0, False, 0, 0, 0, 0, False, False, False, False, '1970-01-02 00:00:00+00:00');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.new_york.tree_species`
(
  species_scientific_name STRING OPTIONS(description=""),
  species_common_name STRING OPTIONS(description=""),
  form STRING OPTIONS(description=""),
  growth_rate STRING OPTIONS(description=""),
  fall_color STRING OPTIONS(description=""),
  environmental_tolerances STRING OPTIONS(description=""),
  location_tolerances STRING OPTIONS(description=""),
  notes_suggested_cultivars STRING OPTIONS(description=""),
  tree_size STRING OPTIONS(description=""),
  comments STRING OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.new_york.tree_species` (species_scientific_name, species_common_name, form, growth_rate, fall_color, environmental_tolerances, location_tolerances, notes_suggested_cultivars, tree_size, comments) VALUES ('Quercus phellos', 'Willow Oak', 'Rounded', 'Slow', 'Yellow/Orange', 'Drought and Pollution Tolerant', 'Median Tree', 'Plant Spring Only', 'Large (Mature Height > 50 ft)', ''), ('Cotinus sp.', 'Smoke Tree', 'Rounded', 'Slow', 'Red/Bronze', 'none', 'Small Tree Pit (<3 ft)', '''Royal Purple'' or ''Grace''', 'Small (Mature Height < 25 ft)', ''), ('Prunus serrulata ''Kwanzan''', 'Japanese Flowering Cherry', 'Rounded', 'Slow', 'Red/Orange', 'none', 'Small Tree Pit (<3 ft)', 'Double–flowering', 'Small (Mature Height < 25 ft)', ''), ('Amelanchier sp.', 'Serviceberry', 'Rounded', 'Slow', 'Red/ Yellow', 'Wet Site and Shade Tolerant', 'Small Tree Pit (<3 ft)', '''Autumn Sunset,'' ''Cumulus,'' and ''White Pillar''', 'Small (Mature Height < 25 ft)', ''), ('Prunus padus', 'European Birdcherry', 'Rounded', 'Slow', 'Yellow/Bronze', 'none', 'Small Tree Pit (<3 ft)', 'One of the First Trees to Leaf Out in the Spring', 'Small (Mature Height < 25 ft)', '');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.new_york.tlc_fhv_trips_2016`
(
  location_id INT64 OPTIONS(description="The TLC taxi zone of the trip pick-up"),
  pickup_datetime TIMESTAMP OPTIONS(description="The date and time of the trip pick-up."),
  dispatching_base_num STRING OPTIONS(description="The TLC Base License Number of the base that dispatched the trip."),
  borough STRING OPTIONS(description=""),
  zone STRING OPTIONS(description=""),
  service_zone STRING OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.new_york.tlc_fhv_trips_2016` (location_id, pickup_datetime, dispatching_base_num, borough, zone, service_zone) VALUES (NULL, '2016-04-03 10:40:00+00:00', 'B00001', '', '', ''), (NULL, '2016-04-20 18:33:00+00:00', 'B00001', '', '', ''), (NULL, '2016-05-04 12:19:00+00:00', 'B00001', '', '', ''), (NULL, '2016-02-05 11:08:00+00:00', 'B00001', '', '', ''), (NULL, '2016-10-09 12:00:00+00:00', 'B00001', '', '', '');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_incidents.incidents_2009`
(
  unique_key INT64 OPTIONS(description="The unique incident number for this accident."),
  descript STRING OPTIONS(description=""),
  date DATE OPTIONS(description=""),
  time TIME OPTIONS(description=""),
  address STRING OPTIONS(description=""),
  longitude FLOAT64 OPTIONS(description=""),
  latitude FLOAT64 OPTIONS(description=""),
  location STRING OPTIONS(description="Latitude/Longitude"),
  timestamp TIMESTAMP OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.austin_incidents.incidents_2009` (unique_key, descript, date, time, address, longitude, latitude, location, timestamp) VALUES (2009920242, 'DWI', '2009-04-02', '03:29:00', '300 BLOCK W 5TH ST', nan, nan, NULL, '2009-04-02 09:29:00+00:00'), (2009920163, 'DWI', '2009-04-02', '02:14:00', '500 BLOCK BOWIE ST', nan, nan, NULL, '2009-04-02 08:14:00+00:00'), (2009920147, 'DWI', '2009-04-02', '02:50:00', '800 BLOCK W 6TH ST', nan, nan, NULL, '2009-04-02 08:50:00+00:00'), (2009920181, 'DWI', '2009-04-02', '02:30:00', '1200 BLOCK W HOWARD LN', nan, nan, NULL, '2009-04-02 08:30:00+00:00'), (2009920231, 'DWI', '2009-04-02', '03:35:00', '200 BLOCK E RIVERSIDE DR', nan, nan, NULL, '2009-04-02 09:35:00+00:00');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_incidents.incidents_2008`
(
  unique_key INT64 OPTIONS(description="The unique incident number for this accident."),
  descript STRING OPTIONS(description=""),
  date DATE OPTIONS(description=""),
  time TIME OPTIONS(description=""),
  address STRING OPTIONS(description=""),
  longitude FLOAT64 OPTIONS(description=""),
  latitude FLOAT64 OPTIONS(description=""),
  location STRING OPTIONS(description="Latitude/Longitude"),
  timestamp TIMESTAMP OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.austin_incidents.incidents_2008` (unique_key, descript, date, time, address, longitude, latitude, location, timestamp) VALUES (20082020068, 'DWI', '2008-07-20', '00:28:00', '5100 BLOCK S 1ST ST', nan, nan, NULL, '2008-07-20 06:28:00+00:00'), (20082020342, 'DWI', '2008-07-20', '02:28:00', '1500 BLOCK BURTON DR', nan, nan, NULL, '2008-07-20 08:28:00+00:00'), (20082020396, 'DWI', '2008-07-20', '02:58:00', '12100 BLOCK N IH 35 NB', nan, nan, NULL, '2008-07-20 08:58:00+00:00'), (20082020511, 'DWI', '2008-07-20', '04:19:00', '6100 BLOCK N LAMAR BLVD', nan, nan, NULL, '2008-07-20 10:19:00+00:00'), (20082020474, 'DWI', '2008-07-20', '03:47:00', '5800 BLOCK WELLINGTON DR', nan, nan, NULL, '2008-07-20 09:47:00+00:00');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_incidents.incidents_2016`
(
  unique_key INT64 OPTIONS(description="The unique incident number for this accident."),
  descript STRING OPTIONS(description=""),
  date DATE OPTIONS(description=""),
  time TIME OPTIONS(description=""),
  address STRING OPTIONS(description=""),
  longitude FLOAT64 OPTIONS(description=""),
  latitude FLOAT64 OPTIONS(description=""),
  location STRING OPTIONS(description="Latitude/Longitude"),
  timestamp TIMESTAMP OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.austin_incidents.incidents_2016` (unique_key, descript, date, time, address, longitude, latitude, location, timestamp) VALUES (2016961910, 'DWI', '2016-04-05', '23:02:00', '100 BLOCK S 1ST ST', nan, nan, NULL, '2016-04-06 05:02:00+00:00'), (2016960096, 'DWI', '2016-04-05', '01:50:00', '1100 BLOCK W 6TH ST', nan, nan, NULL, '2016-04-05 07:50:00+00:00'), (2016960107, 'THEFT', '2016-04-05', '02:04:00', '400 BLOCK E 6TH ST', nan, nan, NULL, '2016-04-05 08:04:00+00:00'), (20168001593, 'THEFT', '2016-04-05', '15:43:00', '1000 BLOCK W 5TH ST', nan, nan, NULL, '2016-04-05 21:43:00+00:00'), (2016961144, 'THEFT', '2016-04-05', '15:47:00', '2600 BLOCK E 7TH ST', nan, nan, NULL, '2016-04-05 21:47:00+00:00');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_incidents.incidents_2011`
(
  unique_key INT64 OPTIONS(description="The unique incident number for this accident."),
  descript STRING OPTIONS(description=""),
  date DATE OPTIONS(description=""),
  time TIME OPTIONS(description=""),
  address STRING OPTIONS(description=""),
  longitude FLOAT64 OPTIONS(description=""),
  latitude FLOAT64 OPTIONS(description=""),
  location STRING OPTIONS(description="Latitude/Longitude"),
  timestamp TIMESTAMP OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.austin_incidents.incidents_2011` (unique_key, descript, date, time, address, longitude, latitude, location, timestamp) VALUES (20111302003, 'DWI', '2011-05-10', '21:41:00', '500 BLOCK WOODWARD ST', nan, nan, NULL, '2011-05-11 03:41:00+00:00'), (20111312329, 'DWI', '2011-05-10', '23:33:00', '5200 BLOCK E STASSNEY LN', nan, nan, NULL, '2011-05-11 05:33:00+00:00'), (20111302219, 'DWI', '2011-05-10', '11:54:00', '9700 BLOCK NORTH LAKE CREEK PKWY', nan, nan, NULL, '2011-05-10 17:54:00+00:00'), (20111301818, 'RAPE', '2011-05-10', '20:06:00', '5700 BLOCK LAS ALAS TRL', nan, nan, NULL, '2011-05-11 02:06:00+00:00'), (20111301226, 'RAPE', '2011-05-10', '15:13:00', '10700 BLOCK LAKE CREEK PKWY', nan, nan, NULL, '2011-05-10 21:13:00+00:00');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_incidents.incidents_2010`
(
  unique_key INT64 OPTIONS(description="The unique incident number for this accident."),
  descript STRING OPTIONS(description=""),
  date DATE OPTIONS(description=""),
  time TIME OPTIONS(description=""),
  address STRING OPTIONS(description=""),
  longitude FLOAT64 OPTIONS(description=""),
  latitude FLOAT64 OPTIONS(description=""),
  location STRING OPTIONS(description="Latitude/Longitude"),
  timestamp TIMESTAMP OPTIONS(description="")
);

INSERT INTO `bigquery-public-data.austin_incidents.incidents_2010` (unique_key, descript, date, time, address, longitude, latitude, location, timestamp) VALUES (20105002170, 'FOUND PROPERTY', '2009-12-14', '11:52:00', '4000 BLOCK MC KINNEY FALLS PKWY', nan, nan, NULL, '2009-12-14 17:52:00+00:00'), (20105003000, 'DEBIT CARD ABUSE', '2009-12-14', '15:57:00', '800 BLOCK SHERATON AVE', nan, nan, NULL, '2009-12-14 21:57:00+00:00'), (20105000978, 'VIOL OF PROTECTIVE ORDER', '2009-12-14', '05:00:00', '3200 BLOCK PECAN SPRINGS RD', nan, nan, NULL, '2009-12-14 11:00:00+00:00'), (20102392318, 'DWI', '2010-08-27', '22:27:00', '3800 BLOCK TODD LN', nan, nan, NULL, '2010-08-28 04:27:00+00:00'), (20102392717, 'DWI', '2010-08-27', '23:24:00', '800 BLOCK W 6TH ST', nan, nan, NULL, '2010-08-28 05:24:00+00:00');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_crime.crime`
(
  unique_key INT64 OPTIONS(description="Unique identifier for the record."),
  address STRING OPTIONS(description="Full address where the incident occurred."),
  census_tract FLOAT64 OPTIONS(description=""),
  clearance_date TIMESTAMP OPTIONS(description=""),
  clearance_status STRING OPTIONS(description=""),
  council_district_code INT64 OPTIONS(description="Indicates the council district code where the incident occurred."),
  description STRING OPTIONS(description="The subcategory of the primary description."),
  district STRING OPTIONS(description="Indicates the police district where the incident occurred."),
  latitude FLOAT64 OPTIONS(description=""),
  longitude FLOAT64 OPTIONS(description=""),
  location STRING OPTIONS(description=""),
  location_description STRING OPTIONS(description="Description of the location where the incident occurred."),
  primary_type STRING OPTIONS(description="The primary description of the NIBRS/UCR code."),
  timestamp TIMESTAMP OPTIONS(description="Time when the incident occurred. This is sometimes a best estimate."),
  x_coordinate INT64 OPTIONS(description="The x coordinate of the location where the incident occurred"),
  y_coordinate INT64 OPTIONS(description="The y coordinate of the location where the incident occurred"),
  year INT64 OPTIONS(description="Indicates the year in which the incident occurred."),
  zipcode STRING OPTIONS(description="Indicates the zipcode where the incident occurred.")
)
OPTIONS(
  description="Austin Crime table"
);

INSERT INTO `bigquery-public-data.austin_crime.crime` (unique_key, address, census_tract, clearance_date, clearance_status, council_district_code, description, district, latitude, longitude, location, location_description, primary_type, timestamp, x_coordinate, y_coordinate, year, zipcode) VALUES (2016680909, '710 E BEN WHITE SVRD WB Austin, TX', nan, '2016-03-10 12:00:00+00:00', 'Not cleared', NULL, 'THEFT BY SHOPLIFTING          ', 'D', nan, nan, NULL, '710 E BEN WHITE SVRD WB', 'Theft', '2016-03-08 12:00:00+00:00', NULL, NULL, 2016, NULL), (20165010210, '2901 S CAP OF TEXAS HWY Austin, TX', nan, 'NaT', NULL, NULL, 'THEFT                         ', 'UK', nan, nan, NULL, '2901 S CAP OF TEXAS HWY', 'Theft', '2016-03-09 12:00:00+00:00', NULL, NULL, 2016, NULL), (20165000995, '7501 E BEN WHITE BLVD SVRD EB Austin, TX', nan, 'NaT', NULL, NULL, 'BURGLARY OF VEHICLE           ', 'UK', nan, nan, NULL, '7501 E BEN WHITE BLVD SVRD EB', 'Theft', '2016-01-08 12:00:00+00:00', NULL, NULL, 2016, NULL), (2016110707, '12319 CEDAR SPUR RD Austin, TX', nan, '2016-01-12 12:00:00+00:00', 'Cleared by Arrest', NULL, 'AUTO THEFT                    ', 'UK', nan, nan, NULL, '12319 CEDAR SPUR RD', 'Auto Theft', '2016-01-11 12:00:00+00:00', NULL, NULL, 2016, NULL), (20165001420, '14200 LAURINGBURG DR Austin, TX', nan, '2016-07-14 12:00:00+00:00', 'Not cleared', NULL, 'THEFT                         ', 'A', nan, nan, NULL, '14200 LAURINGBURG DR', 'Theft', '2016-01-11 12:00:00+00:00', NULL, NULL, 2016, NULL);
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_waste.waste_and_diversion`
(
  load_id INT64,
  report_date DATE,
  load_type STRING,
  load_time TIMESTAMP,
  load_weight FLOAT64,
  dropoff_site STRING,
  route_type STRING,
  route_number STRING
)
OPTIONS(
  description="Austin waste and diversion"
);

INSERT INTO `bigquery-public-data.austin_waste.waste_and_diversion` (load_id, report_date, load_type, load_time, load_weight, dropoff_site, route_type, route_number) VALUES (827369, '2019-05-21', 'RECYCLED METAL', '2019-05-21 02:30:00+00:00', 760.0, 'AUSTIN IRON AND METAL', 'BULK', 'BU05'), (827104, '2019-05-20', 'RECYCLED METAL', '2019-05-20 12:00:00+00:00', 610.0, 'AUSTIN IRON AND METAL', 'BULK', 'BU05'), (827456, '2019-05-22', 'RECYCLED METAL', '2019-05-22 02:32:00+00:00', 610.0, 'AUSTIN IRON AND METAL', 'BULK', 'BU05'), (834192, '2019-07-16', 'RECYCLED METAL', '2019-07-16 03:33:00+00:00', 1250.0, 'AUSTIN IRON AND METAL', 'BULK', 'BU06'), (834048, '2019-07-15', 'RECYCLED METAL', '2019-07-15 01:15:00+00:00', 1070.0, 'AUSTIN IRON AND METAL', 'BULK', 'BU06');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_bikeshare.bikeshare_stations`
(
  station_id INT64,
  name STRING,
  status STRING,
  address STRING,
  alternate_name STRING,
  city_asset_number INT64,
  property_type STRING,
  number_of_docks INT64,
  power_type STRING,
  footprint_length INT64,
  footprint_width FLOAT64,
  notes STRING,
  council_district INT64,
  modified_date TIMESTAMP
)
OPTIONS(
  description="Austin Bikeshare Stations table"
);

INSERT INTO `bigquery-public-data.austin_bikeshare.bikeshare_stations` (station_id, name, status, address, alternate_name, city_asset_number, property_type, number_of_docks, power_type, footprint_length, footprint_width, notes, council_district, modified_date) VALUES (3464, 'Pease Park', 'closed', '1155 Kingsbury St', NULL, NULL, NULL, NULL, NULL, NULL, nan, NULL, 9, '2021-01-04 12:00:00+00:00'), (1002, '6th & Navasota St.', 'closed', '1308 W. 6th St.', NULL, NULL, NULL, NULL, NULL, NULL, nan, NULL, 3, '2021-01-04 12:00:00+00:00'), (1007, 'Lavaca & 6th', 'closed', '601 Lavaca St.', NULL, NULL, NULL, NULL, NULL, NULL, nan, NULL, 9, '2021-01-04 12:00:00+00:00'), (1004, 'Red River & LBJ Library', 'closed', '2322 Red River Street', NULL, NULL, NULL, NULL, NULL, NULL, nan, NULL, 1, '2021-01-04 12:00:00+00:00'), (1003, '8th & Guadalupe', 'closed', '800 Guadalupe St.', NULL, NULL, NULL, NULL, NULL, NULL, nan, NULL, 9, '2021-01-04 12:00:00+00:00');
-- DBMS: bigquery
CREATE TABLE `bigquery-public-data.austin_bikeshare.bikeshare_trips`
(
  trip_id STRING OPTIONS(description="Numeric ID of bike trip"),
  subscriber_type STRING OPTIONS(description="Type of the Subscriber"),
  bike_id STRING OPTIONS(description="ID of bike used"),
  bike_type STRING OPTIONS(description="Type of bike used"),
  start_time TIMESTAMP OPTIONS(description="Start timestamp of trip"),
  start_station_id INT64 OPTIONS(description="Numeric reference for start station"),
  start_station_name STRING OPTIONS(description="Station name for start station"),
  end_station_id STRING OPTIONS(description="Numeric reference for end station"),
  end_station_name STRING OPTIONS(description="Station name for end station"),
  duration_minutes INT64 OPTIONS(description="Time of trip in minutes")
);

INSERT INTO `bigquery-public-data.austin_bikeshare.bikeshare_trips` (trip_id, subscriber_type, bike_id, bike_type, start_time, start_station_id, start_station_name, end_station_id, end_station_name, duration_minutes) VALUES ('4098781', '24 Hour Walk Up Pass', '14', 'classic', '2015-03-12 22:24:45+00:00', 2546, 'ACC - West & 12th Street', '2546', 'ACC - West & 12th Street', 44), ('4098776', '24 Hour Walk Up Pass', '24', 'classic', '2015-03-12 22:22:59+00:00', 2546, 'ACC - West & 12th Street', '2546', 'ACC - West & 12th Street', 46), ('4098773', '24 Hour Walk Up Pass', '789', 'classic', '2015-03-12 22:21:57+00:00', 2546, 'ACC - West & 12th Street', '2546', 'ACC - West & 12th Street', 80), ('4098766', '24 Hour Walk Up Pass', '306', 'classic', '2015-03-12 22:20:09+00:00', 2546, 'ACC - West & 12th Street', '2546', 'ACC - West & 12th Street', 47), ('4098761', '24 Hour Walk Up Pass', '362', 'classic', '2015-03-12 22:19:11+00:00', 2546, 'ACC - West & 12th Street', '2546', 'ACC - West & 12th Street', 47);
-- DBMS: bigquery
CREATE TABLE `isb-cgc-bq.HTAN_versioned.lipidomics_metadata_r2_v2`
(
  Component STRING OPTIONS(description="Category of metadata (e.g. Diagnosis, Biospecimen, scRNA-seq Level 1, etc.); provide the same one for all items/rows."),
  Filename STRING OPTIONS(description="Name of a file"),
  File_Format STRING OPTIONS(description="Format of a file (e.g. txt, csv, fastq, bam, etc.)"),
  HTAN_Parent_Biospecimen_ID STRING OPTIONS(description="HTAN Biospecimen Identifier (eg HTANx_yyy_zzz) indicating the biospecimen(s) from which these files were derived; multiple parent biospecimen should be comma-separated"),
  HTAN_Data_File_ID STRING OPTIONS(description="Self-identifier for this data file - HTAN ID of this file HTAN ID SOP (eg HTANx_yyy_zzz)"),
  Assay_Type STRING OPTIONS(description="The type and level of assay this metadata applies to (e.g. RPPA, Nanostring DSP, etc.)"),
  entityId STRING OPTIONS(description="Synapse ID of entity"),
  HTAN_Center STRING OPTIONS(description="Name of HTAN Center e.g. HTAN HTAPP"),
  Data_Release STRING OPTIONS(description="Inclusion in HTAN Data Release e.g. Release 1.0"),
  File_Size INT64 OPTIONS(description="Size of file (bucket object) in bytes"),
  Base_Filename STRING OPTIONS(description="Base name of file"),
  md5 STRING OPTIONS(description="md5 hash of file")
)
OPTIONS(
  friendly_name="HTAN LIPIDOMICS METADATA R2 VERSIONED",
  description="Data was extracted from HTAN Synapse projects in April 2022.",
  labels=[("access", "open"), ("data_type", "file_metadata"), ("program", "htan"), ("source", "htan"), ("status", "current"), ("category", "metadata")]
);

INSERT INTO `isb-cgc-bq.HTAN_versioned.lipidomics_metadata_r2_v2` (Component, Filename, File_Format, HTAN_Parent_Biospecimen_ID, HTAN_Data_File_ID, Assay_Type, entityId, HTAN_Center, Data_Release, File_Size, Base_Filename, md5) VALUES ('OtherAssay', 'lipidomics/batch-1/mode-1/A001-C-005.mzML', 'mzML', 'HTA10_01_005', 'HTA10_01_00504001', 'Shotgun MS (lipidomics)', 'syn23764007', 'HTAN Stanford', 'Release 1.0', 16184839, 'A001-C-005.mzML', 'e3986baa00b95a8e17eccabc6c4ce929'), ('OtherAssay', 'lipidomics/batch-1/mode-2/A001-C-005.mzML', 'mzML', 'HTA10_01_005', 'HTA10_01_00504002', 'Shotgun MS (lipidomics)', 'syn23764047', 'HTAN Stanford', 'Release 1.0', 23506973, 'A001-C-005.mzML', '9c6513109046a739f14d93b498b92afa'), ('OtherAssay', 'lipidomics/batch-1/mode-1/A001-C-007.mzML', 'mzML', 'HTA10_01_007', 'HTA10_01_00704001', 'Shotgun MS (lipidomics)', 'syn23763993', 'HTAN Stanford', 'Release 1.0', 16174895, 'A001-C-007.mzML', 'd9f844f3d9f7daa463ac1bc17d412a59'), ('OtherAssay', 'lipidomics/batch-1/mode-2/A001-C-007.mzML', 'mzML', 'HTA10_01_007', 'HTA10_01_00704002', 'Shotgun MS (lipidomics)', 'syn23764023', 'HTAN Stanford', 'Release 1.0', 23606573, 'A001-C-007.mzML', '167361f0262342cb5f3e2be69053cb08'), ('OtherAssay', 'lipidomics/batch-1/mode-1/A001-C-021.mzML', 'mzML', 'HTA10_01_021', 'HTA10_01_02104001', 'Shotgun MS (lipidomics)', 'syn23763976', 'HTAN Stanford', 'Release 1.0', 16164951, 'A001-C-021.mzML', '9cb5b95188c391d9d168d27ca27b0cfe');
-- DBMS: bigquery
CREATE TABLE `isb-cgc-bq.HTAN_versioned.tissueOrOrganOfOrigin_to_wholeOrgan_mapping_r4`
(
  Whole_Organ STRING OPTIONS(description="Name of whole organ"),
  Tissue_or_Organ_of_Origin STRING OPTIONS(description="Value of HTAN attribute 'Tissue or Organ of Origin'")
)
OPTIONS(
  friendly_name="TISSUE OR ORGAN OF ORIGIN TO WHOLE ORGAN MAPPING TABLE R4 VERSIONED",
  description="Mapping of HTAN \"Tissue or Organ of Origin\" value, which an be organ part, to a whole organ. This table was derived from the json mapping file https://github.com/ncihtan/htan-portal/blob/master/data/human-organ-mappings.json",
  labels=[("access", "open"), ("data_type", "data_dictionary"), ("program", "htan"), ("source", "htan"), ("category", "metadata"), ("status", "current")]
);

INSERT INTO `isb-cgc-bq.HTAN_versioned.tissueOrOrganOfOrigin_to_wholeOrgan_mapping_r4` (Whole_Organ, Tissue_or_Organ_of_Origin) VALUES ('Adrenal Gland', 'Adrenal gland NOS'), ('Adrenal Gland', 'Cortex of adrenal gland'), ('Adrenal Gland', 'Medulla of adrenal gland'), ('Bile Duct', 'Ampulla of Vater'), ('Bile Duct', 'Biliary tract NOS');
-- DBMS: bigquery
CREATE TABLE `isb-cgc-bq.HTAN_versioned.cds_drs_map_r5`
(
  name STRING OPTIONS(description="Name of a file"),
  entityId STRING OPTIONS(description="Synapse ID of entity"),
  HTAN_Data_File_ID STRING OPTIONS(description="Self-identifier for this data file - HTAN ID of this file HTAN ID SOP (eg HTANx_yyy_zzz)"),
  drs_uri STRING OPTIONS(description="CDS-assigned DRS URI of file")
)
OPTIONS(
  friendly_name="HTAN FILE SYNAPSE ID TO CDS DRS URI MAP R5 VERSIONED",
  description="This table contains DRS URIs for HTAN Data Files available in NCI's Cancer Data Service (CDS) repository and was generated April 2024. CSVs generated from this table are compatible with the \"Import from a manifest file\" data access method: https://docs.cancergenomicscloud.org/docs/import-from-a-drs-server#import-from-a-manifest-file. Data corresponds to dbGaP study phs002371.v5.p1: https://www.ncbi.nlm.nih.gov/projects/gap/cgi-bin/study.cgi?study_id=phs002371.v5.p1",
  labels=[("access", "open"), ("data_type", "file_metadata"), ("program", "htan"), ("source", "htan"), ("category", "metadata"), ("status", "current")]
);

INSERT INTO `isb-cgc-bq.HTAN_versioned.cds_drs_map_r5` (name, entityId, HTAN_Data_File_ID, drs_uri) VALUES ('S1.bam', 'syn26546212', 'HTA7_1_1453', 'drs://nci-crdc.datacommons.io/dg.4DFC/adde2232-a6d9-489b-86e2-22c4c08b0987'), ('S2.bam', 'syn26546217', 'HTA7_1_1564', 'drs://nci-crdc.datacommons.io/dg.4DFC/e836d169-01aa-40b9-ac27-bc4c6d417c8a'), ('S3.bam', 'syn26546241', 'HTA7_1_1598', 'drs://nci-crdc.datacommons.io/dg.4DFC/b7a010f7-2ce3-43e3-b75d-5a95f7b7f0f8'), ('S4.bam', 'syn26546518', 'HTA7_1_1609', 'drs://nci-crdc.datacommons.io/dg.4DFC/897a0598-bbaa-4860-83b5-b567e9f5538f'), ('S5.bam', 'syn26546529', 'HTA7_1_1620', 'drs://nci-crdc.datacommons.io/dg.4DFC/3a036835-1058-43e0-bda5-7ba7e4c7abd5');