Our travel datasets provide extensive, structured data covering various aspects of the global travel and hospitality industry. These datasets are ideal for businesses, analysts, and developers looking to gain insights into hotel pricing, short-term rentals, restaurant listings, and travel trends. Whether you're optimizing pricing strategies, analyzing market trends, or enhancing travel-related applications, our datasets offer the depth and accuracy you need.

Key Travel Datasets Available:

  Hotel & Rental Listings: Access detailed data on hotel properties, short-term rentals, and vacation stays from platforms like 
    Airbnb, Booking.com, and other OTAs. This includes property details, pricing, availability, guest reviews, and amenities.

  Real-Time & Historical Pricing Data: Track hotel room pricing, rental occupancy rates, and pricing trends 
    to optimize revenue management and competitive analysis.

  Restaurant Listings & Reviews: Explore restaurant data from Tripadvisor, OpenTable, Zomato, Deliveroo, and Talabat, 
    including restaurant details, customer ratings, menus, and delivery availability.

  Market & Trend Analysis: Use structured datasets to analyze travel demand, seasonal trends, and consumer preferences 
    across different regions.

  Geo-Targeted Data: Get location-specific insights with city, state, and country-level segmentation, 
    allowing for precise market research and localized business strategies.



Use Cases for Travel Datasets:

  Dynamic Pricing & Revenue Optimization: Adjust pricing strategies based on real-time market trends and competitor analysis.
  Market Research & Competitive Intelligence: Identify emerging travel trends, monitor competitor performance, and assess market demand.
  Travel & Hospitality App Development: Enhance travel platforms with accurate, up-to-date data on hotels, restaurants, and rental properties.
  Investment & Financial Analysis: Evaluate travel industry performance for investment decisions and economic forecasting.



  Our travel datasets are available in multiple formats (JSON, CSV, Excel) and can be delivered via 
  API, cloud storage (AWS, Google Cloud, Azure), or direct download. 
  Stay ahead in the travel industry with high-quality, structured data that powers smarter decisions.

The purpose of the data set is to provide multi-modal data and contextual information (weather and incidents) that can be used to research and develop applications for the USDOT Dynamic Mobility Applications (DMA) program. This legacy dataset was created before data.transportation.gov and is only currently available via the attached file(s). Please contact the dataset owner if there is a need for users to work with this data using the data.transportation.gov analysis features (online viewing, API, graphing, etc.) and the USDOT will consider modifying the dataset to fully integrate in data.transportation.gov. Additional related data can be found here: https://data.transportation.gov/Automobiles/Seattle-20-Second-Freeway/ixg2-6cni

Introduction

This Czech Call Center Speech Dataset for the Travel industry is purpose-built to power the next generation of voice AI applications for travel booking, customer support, and itinerary assistance. With over 30 hours of unscripted, real-world conversations, the dataset enables the development of highly accurate speech recognition and natural language understanding models tailored for Czech -speaking travelers.

Created by FutureBeeAI, this dataset supports researchers, data scientists, and conversational AI teams in building voice technologies for airlines, travel portals, and hospitality platforms.

Speech Data

The dataset includes 30 hours of dual-channel audio recordings between native Czech speakers engaged in real travel-related customer service conversations. These audio files reflect a wide variety of topics, accents, and scenarios found across the travel and tourism industry.

Topic Diversity

Inbound and outbound conversations span a wide range of real-world travel support situations with varied outcomes (positive, neutral, negative).

These scenarios help models understand and respond to diverse traveler needs in real-time.

Transcription

Each call is accompanied by manually curated, high-accuracy transcriptions in JSON format.

Metadata

Extensive metadata enriches each call and speaker for better filtering and AI training:

Usage and Applications

This dataset is ideal for a variety of AI use cases in the travel and tourism space:

STS dataset was collected by a context-aware recommender system mobile app named as "South Tyrol Suggests". The app provides context-aware recommendations for attractions, events, public services, restaurants, and much more based on the rating preferences and personality factors of users.

Contextual variables includes

• distance: far away, near by
• time available: half day, one day, more than one day
• temperature: burning, hot, warm, cool, cold, freezing
• crowdedness: crowded, not crowded, empty
• knowledge of surroundings: new to area, returning visitor, citizen of the area
• season: spring, summer, autumn, winter
• budget: budget traveler, price for quality, high spender
• daytime: morning, noon, afternoon, evening, night
• weather: clear sky, sunny, cloudy, rainy, thunderstorm, snowing
• companion: alone, with friends/colleagues, with family, with girlfriend/boyfriend, with children
• mood: happy, sad, active, lazy weekday: weekday, weekend
• travel goal: visiting friends, business, religion, health care, social event, education, scenic/landscape, hedonistic/fun, activity/sport
• means of transport: no transportation means, a bicycle, a car, public transport

More details can be found here:

Braunhofer, Matthias, Mehdi Elahi, and Francesco Ricci. "Techniques for cold-starting context-aware mobile recommender systems for tourism." Intelligenza Artificiale 8, no. 2 (2014): 129-143.

Introduction

This Russian Call Center Speech Dataset for the Travel industry is purpose-built to power the next generation of voice AI applications for travel booking, customer support, and itinerary assistance. With over 30 hours of unscripted, real-world conversations, the dataset enables the development of highly accurate speech recognition and natural language understanding models tailored for Russian -speaking travelers.

Created by FutureBeeAI, this dataset supports researchers, data scientists, and conversational AI teams in building voice technologies for airlines, travel portals, and hospitality platforms.

Speech Data

The dataset includes 30 hours of dual-channel audio recordings between native Russian speakers engaged in real travel-related customer service conversations. These audio files reflect a wide variety of topics, accents, and scenarios found across the travel and tourism industry.

Topic Diversity

Inbound and outbound conversations span a wide range of real-world travel support situations with varied outcomes (positive, neutral, negative).

These scenarios help models understand and respond to diverse traveler needs in real-time.

Transcription

Each call is accompanied by manually curated, high-accuracy transcriptions in JSON format.

Metadata

Extensive metadata enriches each call and speaker for better filtering and AI training:

Usage and Applications

This dataset is ideal for a variety of AI use cases in the travel and tourism space:

Images of various facilities used as a tool to eliminate travel time and for immediate access to concerned areas. App thumbnails images 4 per row and allows the user to enlarge each photo individually. Includes Kansas EG, Mason City, OMA, Omaha Long Range Radar, St. Louis SJW ALSF E/G Replacement %3F%3F%3F

Introduction

This Indian English Call Center Speech Dataset for the Travel industry is purpose-built to power the next generation of voice AI applications for travel booking, customer support, and itinerary assistance. With over 30 hours of unscripted, real-world conversations, the dataset enables the development of highly accurate speech recognition and natural language understanding models tailored for English -speaking travelers.

Created by FutureBeeAI, this dataset supports researchers, data scientists, and conversational AI teams in building voice technologies for airlines, travel portals, and hospitality platforms.

Speech Data

The dataset includes 30 hours of dual-channel audio recordings between native Indian English speakers engaged in real travel-related customer service conversations. These audio files reflect a wide variety of topics, accents, and scenarios found across the travel and tourism industry.

Topic Diversity

Inbound and outbound conversations span a wide range of real-world travel support situations with varied outcomes (positive, neutral, negative).

These scenarios help models understand and respond to diverse traveler needs in real-time.

Transcription

Each call is accompanied by manually curated, high-accuracy transcriptions in JSON format.

Metadata

Extensive metadata enriches each call and speaker for better filtering and AI training:

Usage and Applications

This dataset is ideal for a variety of AI use cases in the travel and tourism space:

This dataset supports commuter guidebook by providing estimated travel times between selected TAZs. Data is modeled or calculated and reflects average conditions, not real-world travel. Intended for visualization and informational use.Travel times are estimates only and not based on observed trips. Values are calculated or modeled using assumptions and average speeds. Not suitable for routing, operational planning, or emergency response.Metadata

Table from the American Community Survey (ACS) B08303 travel time to work. These are multiple, nonoverlapping vintages of the 5-year ACS estimates of population and housing attributes starting in 2010 shown by the corresponding census tract vintage. Also includes the most recent release annually.King County, Washington census tracts with nonoverlapping vintages of the 5-year American Community Survey (ACS) estimates starting in 2010. Vintage identified in the "ACS Vintage" field.The census tract boundaries match the vintage of the ACS data (currently 2010 and 2020) so please note the geographic changes between the decades. Tracts have been coded as being within the City of Seattle as well as assigned to neighborhood groups called "Community Reporting Areas". These areas were created after the 2000 census to provide geographically consistent neighborhoods through time for reporting U.S. Census Bureau data. This is not an attempt to identify neighborhood boundaries as defined by neighborhoods themselves.Vintages: 2010, 2015, 2020, 2021, 2022, 2023ACS Table(s): B08303Data downloaded from: Census Bureau's Explore Census Data The United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

Advanced mobile functions and empowered smartphones have provided tourists with various location-based service apps that reshaped the business model of the tourism sector. Despite their importance to tourists, l-apps still have limitations, such as ignorance of tourist preferences and the mismatch between app introduction and tourist experience, therefore affecting tourist loyalty to destinations. Understanding tourist-oriented factors thus becomes critical for l-app designers and service providers. This study integrates the technology-acceptance model (TAM) into a unique context to examine the roles of digital literacy, perceived ease of use, perceived autonomy, virtual-content congruence, and tourist engagement on tourist loyalty. Our empirical test of a structural equation model based on a randomly recruited 319 customers found that tourists’ digital literacy influences their engagement and perceived ease of use, which mediates the relationship between digital literacy and engagement; tourists’ perceived autonomy influences their engagement. Moreover, we found the moderating role of information-experience congruency between digital literacy, perceived ease of use, and perceived autonomy and tourist engagement, thus contributing to the boundary conditions of the TAM model. Finally, tourist engagement contributes to tourist loyalty. The study contributes to the integration of the technology acceptance model with a tourist orientation. The findings also offer meaningful, practical implications and recommendations on l-app design to stakeholders of tourist destinations.

Introduction

This Vietnamese Call Center Speech Dataset for the Travel industry is purpose-built to power the next generation of voice AI applications for travel booking, customer support, and itinerary assistance. With over 30 hours of unscripted, real-world conversations, the dataset enables the development of highly accurate speech recognition and natural language understanding models tailored for Vietnamese -speaking travelers.

Created by FutureBeeAI, this dataset supports researchers, data scientists, and conversational AI teams in building voice technologies for airlines, travel portals, and hospitality platforms.

Speech Data

The dataset includes 30 hours of dual-channel audio recordings between native Vietnamese speakers engaged in real travel-related customer service conversations. These audio files reflect a wide variety of topics, accents, and scenarios found across the travel and tourism industry.

Topic Diversity

Inbound and outbound conversations span a wide range of real-world travel support situations with varied outcomes (positive, neutral, negative).

These scenarios help models understand and respond to diverse traveler needs in real-time.

Transcription

Each call is accompanied by manually curated, high-accuracy transcriptions in JSON format.

Metadata

Extensive metadata enriches each call and speaker for better filtering and AI training:

Usage and Applications

This dataset is ideal for a variety of AI use cases in the travel and tourism space:

Capstone Project from Google's Data Analysis professional certificate.

Using the data from Divvy's public database to conduct Data Analysis in order to find statistics of users, both members and casual, and using that data to come up with ways to promote the app so that more casual users become members.

Travel easy with the Perth Airport appGet live flight information and status updates, plan your trip to and from the airport, easily book parking and more, right in the palm of your hand with the official Perth Airport app. Show full description

Introduction

This Turkish Call Center Speech Dataset for the Travel industry is purpose-built to power the next generation of voice AI applications for travel booking, customer support, and itinerary assistance. With over 30 hours of unscripted, real-world conversations, the dataset enables the development of highly accurate speech recognition and natural language understanding models tailored for Turkish -speaking travelers.

Created by FutureBeeAI, this dataset supports researchers, data scientists, and conversational AI teams in building voice technologies for airlines, travel portals, and hospitality platforms.

Speech Data

The dataset includes 30 hours of dual-channel audio recordings between native Turkish speakers engaged in real travel-related customer service conversations. These audio files reflect a wide variety of topics, accents, and scenarios found across the travel and tourism industry.

Topic Diversity

Inbound and outbound conversations span a wide range of real-world travel support situations with varied outcomes (positive, neutral, negative).

These scenarios help models understand and respond to diverse traveler needs in real-time.

Transcription

Each call is accompanied by manually curated, high-accuracy transcriptions in JSON format.

Metadata

Extensive metadata enriches each call and speaker for better filtering and AI training:

Usage and Applications

This dataset is ideal for a variety of AI use cases in the travel and tourism space:

Supporting datasets for Allen et al. (2018) - Global Estimates of River Flow Wave Travel Times and Implications for Low-Latency Satellite Data, Geophysical Research Letters, https://doi.org/10.1002/2018GL077914

The code used to produce these data is available as a Github repository, permanently hosted on Zenodo: https://doi.org/10.5281/zenodo.1219784

Abstract

Earth-orbiting satellites provide valuable observations of upstream river conditions worldwide. These observations can be used in real-time applications like early flood warning systems and reservoir operations, provided they are made available to users with sufficient lead time. Yet, the temporal requirements for access to satellite-based river data remain uncharacterized for time-sensitive applications. Here we present a global approximation of flow wave travel time to assess the utility of existing and future low-latency/near-real-time satellite products, with an emphasis on the forthcoming SWOT satellite. We apply a kinematic wave model to a global hydrography dataset and find that global flow waves traveling at their maximum speed take a median travel time of 6, 4 and 3 days to reach their basin terminus, the next downstream city and the next downstream dam respectively. Our findings suggest that a recently-proposed ≤2-day latency for a low-latency SWOT product is potentially useful for real-time river applications.

Description of repository datasets:

1. riverPolylines.zip contains ESRI shapefile polylines of river networks with outputs from main analysis. These continental-scale shapefiles contain the following attributes for each river segment:

"ARCID" : unique identifier for each river segment line, defined as the river reach between river junctions/heads/mouths. The first 10 attributes are taken from Andreadis et al. (2013): https://doi.org/10.5281/zenodo.61758

"UP_CELLS" : number of upstream cells (pixels)

"AREA" : upstream drainage area (km2)

"DISCHARGE" : discharge (m3/s)

"WIDTH" : mean bankfull river width (m)

"WIDTH5" : 5th percentile confidence interval bankfull river width (m)

"WIDTH95" : 95th percentile confidence interval bankfull river width (m)

"DEPTH" : mean bankfull river depth (m)

"DEPTH5" : 5th percentile bankfull river depth (m)

"DEPTH95" : 95th percentile confidence bankfull river depth (m)

"LENGTH_KM" : segment length (km)

"ORIG_FID" : original ID of segment

"ELEV_M" : lowest elevation of segment (m). Derived from HydroSHEDS 15 sec hydrologically conditioned DEM: https://hydrosheds.cr.usgs.gov/datadownload.php?reqdata=15demg

"POINT_X" : longitude of lowest point of segment (WGS84, decimal degrees)

"POINT_Y" : latitude of lowest point of segment (WGS84, decimal degrees)

"SLOPE" : average slope of segment (m/m)

"CITY_JOINS" : an index associated with how likely a city/population center is located on the segment. Population center data from: http://web.ornl.gov/sci/landscan/ and http://www.naturalearthdata.com/downloads/10m-cultural-vectors/10m-populated-places/

"CITY_POP_M" : population of joined city (max N inhabitants)

"DAM_JOINSC" : an index associated with how likely a dam is located on the segment. Dam data from Global Reservoir and Dam (GRanD) Database: http://www.gwsp.org/products/grand-database.html

"DAM_AREA_S" : surface area of joined dam (m2)

"DAM_CAP_MC" : volumetric capacity of joined dam (m3)

"CELER_MPS" : modeled river flow wave celerity (m/s)

"PROPTIME_D" : travel time of flow wave along segment (days)

"hBASIN" : main basin UID for the hydroBASINS dataset: http://www.hydrosheds.org/page/hydrobasins

"GLCC" : Global Land Cover Characterization at segment centroid: https://lta.cr.usgs.gov/glcc/globdoc2_0

"FLOODHAZAR" : flood hazard composite index from the DFO (via NASA Sedac): http://sedac.ciesin.columbia.edu/data/set/ndh-flood-hazard-frequency-distribution

"SWOT_TRAC_" : SWOT track density (N overpasses per orbit cycle @ segment centroid). Created using SWOTtrack SWOTtracks_sciOrbit_sept15 polygon shapefile, uploaded here.

"UPSTR_DIST" : upstream distance to the basin outlet (km)

"UPSTR_TIME" : upstream flow wave travel time to the basin outlet (days)

"CITY_UPSTR" : upstream flow wave travel time to the next downstream city (days)

"DAM_UPSTR_" : upstream flow wave travel time to the next downstream dam (days)

"MC_WIDTH" : mean of Monte Carlo simulated bankfull widths (m)

"MC_DEPTH" : mean of Monte Carlo simulated bankfull depths (m)

"MC_LENCOR" : mean of Monte Carlo simulated river length correction (km)

"MC_LENGTH" : mean of Monte Carlo simulated river length (m)

"MC_SLOPE" : mean of Monte Carlo simulated river slope (-)

"MC_ZSLOPE" : mean of Monte Carlo simulated minimum slope threshold (m)

"MC_N" : mean of Monte Carlo simulated Manning’s n (s/m^(1/3))

"CONTINENT" : integer indicating the HydroSHEDS region of shapefile

1. hydrosheds_connectivity.zip contains network connectivity CSVs for river polyline shapefiles. The tables do not contain headers:

Col1: segment unique identifier (UID) corresponding to the ARCID column of the riverPolylines shapefiles

Col2: Downstream UID

Col3: Number of upstream UIDs

Col4 – Col12: Upstream UIDs

1. SWOTtracks_sciOrbit_sept15_density.zip contains a polygon shapefile derived from SWOTtracks_sciOrbit_sept15_completeOrbit containing the sampling frequency of SWOT (number of observations per complete orbit cycle). Polygon attributes correspond to each unique shape formed from overlapping swaths:

FID : unique identifier of each polygon

CENTROID_X : polygon centroid longitude (WGS84 - decimal degrees)

CENTROID_Y : polygon centroid latitude (WGS84 - decimal degrees)

COUNT_count: SWOT sampling frequency (N observations per complete orbit cycle)

1. USGS_gauge_site_information.csv : table containing the list of USGS sites analyzed in the validation and obtained from http://nwis.waterdata.usgs.gov/nwis/dv Header descriptions contained within table.

2. validation_gaugeBasedCelerity.zip contains polyline ESRI shapefiles covering North and Central America, where USGS gauges provided gauge-based celerity estimates. These files have FIDs and attributes corresponding to riverPolylines shapefiles described above and also contrain the folllowing fields:

GAUGE_JOIN : an index associated with how likely a gauge is located on the segment. Gauge location information is contained in USGS_gauge_site_information.csv

GAUGE_SITE: USGS gauge site number of joined gauge

GAUGE_HUC8: which hydrological unit code the gauge is located in

OBS_CEL_R: gauge-based correlation score (R). Upstream and downstream gauges were compared via lagged cross correlation analysis. The calculated celerity between the paired gauges were assigned to each segment between the two gauges. If there were multiple pairs of upstream and downstream gauges, the the mean celerity value was assigned, weighted by the quality of the correlation, R. Same weighted mean was applied in assigning R.

OBS_CEL_MPS: gauge-based celerity estimate (m/s).

1. tab1_latencies.csv contains data shown in Table 1 of the manuscript.

2. figS3S4_monteCarloSim_global_runMeans.csv contains the mean of the Monte Carlo simulation inputs and outputs shown in Figure S3 and Figure S4. Column headers descriptions are given in riverPolylines (dataset #1 above). Some columns have rows with all the same value because these variables did not vary between ensemble runs.

3. figS5_travelTimeEnsembleHistograms.zip contains data shown in Figure S5. Each csv corresponds to a figure component:

tabdTT_b.csv : basin outlet travel times for all rivers

tabdTT_b_swot.csv : basin outlet travel times for SWOT

tabdTT_c.csv : next downstream city travel times for all rivers

tabdTT_c_swot.csv : next downstream city travel times for SWOT

tabdTT_d.csv : next downstream dam travel times for all rivers

tabdTT_d_swot.csv : next downstream dam travel times for SWOT

The datasets in this zip file are in support of FHWA-JPO-16-379, Analysis, Modeling, and Simulation (AMS) Testbed Development and Evaluation to Support Dynamic Mobility Applications (DMA) and Active Transportation and Demand Management (ATDM) Programs - calibration Report for Phoenix Testbed : Final Report. The compressed zip file totals 1.1 GB in size. The zip file have been uploaded as-is; no further documentation was supplied by NTL, excepted as noted: All located .docx files were converted to .pdf document files which are an archival format. These .pdfs were then added to the zip file alongside the original .docx files. The initial zip file presented to NTL contained uncompressed datasets and duplicative zip files of the files. In order to make the overall size of the this zip file more manageable, duplicative files were deleted. The zip file can be unzipped using any zip compression/decompression software. This zip file contains files in the following formats: .pdf document files which can be read using any pdf reader; .cvs text files which can be read using any text editor; .docx document files which can be read in Microsoft Word and some other word processing programs; .txt text files which can be opened with any text editor; .xlsx spreadsheet files which can be read in Microsoft Excel and some other spreadsheet programs; .cfg computer configuration files; .db database files, which can be opened with many database programs; .rif raster image files, these files may have been created by the Corel Painter image editing application, a proprietary software program, although other image programs may open the files [software requirements]. These files were last accessed in 2017.

This zip file contains POSTDATA.ATT (.ATT); Print to File (.PRN); Portable Document Format (.PDF); and document (.DOCX) files of data to support FHWA-JPO-16-385, Analysis, modeling, and simulation (AMS) testbed development and evaluation to support dynamic mobility applications (DMA) and active transportation and demand management (ATDM) programs — evaluation report for ATDM program. Zip size is 168 MB. Files were accessed in 2017. Data will be preserved as is.

This layer shows workers' place of residence by commute length. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the percentage of commuters whose commute is 90 minutes or more. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B08303Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

The datasets in this zip file are in support of Intelligent Transportation Systems Joint Program Office (ITS JPO) report FHWA-JPO-16-385, "Analysis, Modeling, and Simulation (AMS) Testbed Development and Evaluation to Support Dynamic Mobility Applications (DMA) and Active Transportation and Demand Management (ATDM) Programs — Evaluation Report for ATDM Program," and FHWA-JPO-16-389, "Analysis, Modeling, and Simulation (AMS) Testbed Development and Evaluation to Support Dynamic Mobility Applications (DMA) and Active Transportation and Demand Management (ATDM) Programs : Evaluation Report for the San Diego Testbed : Draft Report". The files in this zip file are specifically related to the San Diego Testbed. The compressed zip files total 3.17 GB in size. The files have been uploaded as-is; no further documentation was supplied by NTL. Direct download of data zip file: https://doi.org/10.21949/1500873 All located .docx files were converted to .pdf document files which are an open, archival format. These pdfs were then added to the zip file alongside the original .docx files. These files can be unzipped using any zip compression/decompression software. This zip file contains files in the following formats: .pdf document files which can be read using any pdf reader; .cvs text files which can be read using any text editor; .txt text files which can be read using any text editor; .docx document files which can be read in Microsoft Word and some other word processing programs; . xlsx spreadsheet files which can be read in Microsoft Excel and some other spreadsheet programs; .dat data files which may be text or multimedia; as well as GIS or mapping files in the following formats: .mxd, .dbf, .prj, .sbn, .shp., .shp.xml; which may be opened in ArcGIS or other GIS software. [software requirements] These files were last accessed in 2017.