- API
An Effective And Efficient Transportation Network Indicator Summary
stat.montgomerycountymd.gov | Last Updated 2018-07-02T19:09:26.000ZAn Effective And Efficient Transportation Network Indicator Summary. To see details for each benchmark county, go to https://reports.data.montgomerycountymd.gov/dataset/An-Effective-And-Efficient-Transportation-Network-/qxyx-qs79
- API
RICAPS On-road Transportation Emissions roll-up 2
datahub.smcgov.org | Last Updated 2019-05-22T23:00:49.000ZData by city showing transportation contribution to greenhouse gas emissions in the County. This data is part of the Regionally Integrated Climate Action Planning Suite (RICAPS) program. The majority of cities used the “in-boundary” methodology that relies on data from the Highway Performance Monitoring System. The inventories for South San Francisco and Unincorporated County use the “origin-destination” methodology from that relies on data from Metropolitan Transportation Commission (MTC). So, directly comparing vehicle miles traveled (VMT) across all cities is not statistically possible. Each city in San Mateo County has the opportunity to develop its own Climate Action Plan (CAP) using tools developed by C/CAG in conjunction with DNV KEMA https://www.dnvgl.com/ and Hara. http://www.verisae.com/default.aspx. This project was funded by grants from the Bay Area Air Quality Management District (BAAQMD) and Pacific Gas and Electric Company (PG&E). Climate Action Plans developed from these tools will meet BAAQMD's California Environmental Quality Act (CEQA) guidelines for a Qualified Greenhouse Gas Reduction Strategy. For more information, please see the RICAPS site: http://www.smcenergywatch.com/progress_report.html
- API
Vital Signs: Transit Cost-Effectiveness – by operator
data.bayareametro.gov | Last Updated 2018-07-06T18:04:51.000ZVITAL SIGNS INDICATOR Transit Cost-Effectiveness (T13) FULL MEASURE NAME Net cost per transit boarding (cost per boarding minus fare per boarding) LAST UPDATED May 2017 DESCRIPTION Transit cost-effectiveness refers to both the total and net costs per transit boarding, both of which are adjusted to reflect inflation over time. Net costs reflect total operating costs minus farebox revenue (i.e. operating costs that are not directly funded by system users). The dataset includes metropolitan area, regional, mode, and system tables for net cost per boarding, total cost per boarding, and farebox recovery ratio. DATA SOURCE Federal Transit Administration: National Transit Database http://www.ntdprogram.gov/ntdprogram/data.htm Bureau of Labor Statistics: Consumer Price Index http://www.bls.gov/data/ CONTACT INFORMATION vitalsigns.info@mtc.ca.gov METHODOLOGY NOTES (across all datasets for this indicator) Simple modes were aggregated to combine the various bus modes (e.g. rapid bus, express bus, local bus) into a single mode to avoid incorrect conclusions resulting from mode recoding over the lifespan of NTD. For other metro areas, operators were identified by developing a list of all urbanized areas within a current MSA boundary and then using that UZA list to flag relevant operators; this means that all operators (both large and small) were included in the metro comparison data. Financial data was inflation-adjusted to match 2015 dollar values using metro-specific Consumer Price Indices.
- API
Vital Signs: Commute Mode Choice (by Place of Residence) – Bay Area
data.bayareametro.gov | Last Updated 2020-05-20T21:50:47.000ZVITAL SIGNS INDICATOR Commute Mode Choice (T1) FULL MEASURE NAME Commute mode share by residential location LAST UPDATED April 2020 DESCRIPTION Commute mode choice, also known as commute mode share, refers to the mode of transportation that a commuter uses to travel to work, such as driving alone, biking, carpooling or taking transit. The dataset includes metropolitan area, regional, county, city and census tract tables by place of residence. DATA SOURCE U.S. Census Bureau: Decennial Census (1960-2000) - via MTC/ABAG Bay Area Census http://www.bayareacensus.ca.gov/transportation/Means19802000.htm U.S. Census Bureau: American Community Survey Form B08301 (2006-2018; place of residence) www.api.census.gov CONTACT INFORMATION vitalsigns.info@bayareametro.gov METHODOLOGY NOTES (across all datasets for this indicator) For the decennial Census datasets, the breakdown of auto commuters between drive alone and carpool is not available before 1980. "Other" includes bicycle, motorcycle, taxi, and other modes of transportation. For the American Community Survey datasets, 1-year rolling average data was used for metros, region, and county geographic levels, while 5-year rolling average data was used for cities and tracts. This is due to the fact that more localized data is not included in the 1-year dataset across all Bay Area cities. Regional mode shares are population-weighted averages of the nine counties’ modal shares. "Auto" includes drive alone and carpool for the simple data tables and is broken out in the detailed data tables accordingly, as it was not available before 1980. “Transit” includes public operators (Muni, BART, etc.) and employer-provided shuttles (e.g., Google shuttle buses). "Other" includes motorcycle, taxi, and other modes of transportation; bicycle mode share was broken out separately for the first time in the 2006 data and is shown in the detailed data tables. Census tract data is not available for tracts with insufficient numbers of residents or workers. The metropolitan area comparison was performed for the nine-county San Francisco Bay Area in addition to the primary MSAs for the nine other major metropolitan areas.
- API
The Omnibus Surveys - Omnibus Monthly Survey 2002 Dec SAS Data
datahub.transportation.gov | Last Updated 2018-12-19T00:13:38.000ZThe Omnibus Surveys are a convenient way to get very quick input on transportation issues; to see who uses what, how they use it, and how users view it, and what they think about it; and to gauge public satisfaction with the transportation system and government programs.The series of surveys include: A monthly household survey of 1,000 households each month, which collects data on core questions about general travel experiences, satisfaction with the system, and some demographic data. Targeted surveys to address special transportation issues, as the U.S. Department of Transportation (DOT) operating administrations need them
- API
The Omnibus Surveys - Omnibus Monthly Survey 2002 May EXCEL Data
datahub.transportation.gov | Last Updated 2018-12-19T00:13:36.000ZThe Omnibus Surveys are a convenient way to get very quick input on transportation issues; to see who uses what, how they use it, and how users view it, and what they think about it; and to gauge public satisfaction with the transportation system and government programs.The series of surveys include: A monthly household survey of 1,000 households each month, which collects data on core questions about general travel experiences, satisfaction with the system, and some demographic data. Targeted surveys to address special transportation issues, as the U.S. Department of Transportation (DOT) operating administrations need them
- API
Election Results, Special Election Runoff, December 5, 2017
data.fultoncountyga.gov | Last Updated 2024-01-30T22:52:27.000ZThis data set consists of all Fulton County Election results from the Special Election Runoff, December 5, 2017 to present. Included with each record is the race, candidate, precinct, number of election day votes, number of absentee by mail votes, number of advance in person votes, number of provisional votes, total number of votes, name of election, and date of election. This data set is updated after each election.
- API
Election Results, Special Election Runoff, February 3, 2015
data.fultoncountyga.gov | Last Updated 2024-01-30T22:52:06.000ZThis data set consists of all Fulton County Election results from the Special Election Runoff, February 3, 2015, to present. Included with each record is the race, candidate, precinct, number of election day votes, number of absentee by mail votes, number of advance in person votes, number of provisional votes, total number of votes, name of election, and date of election. This data set is updated after each election.
- API
Vital Signs: Time in Congestion - Corridor (Updated October 2018)
data.bayareametro.gov | Last Updated 2018-10-24T00:31:33.000ZVITAL SIGNS INDICATOR Time Spent in Congestion (T7) FULL MEASURE NAME Time Spent in Congestion LAST UPDATED October 2018 DATA SOURCE MTC/Iteris Congestion Analysis No link available CA Department of Finance Forms E-8 and E-5 http://www.dof.ca.gov/Forecasting/Demographics/Estimates/E-8/ http://www.dof.ca.gov/Forecasting/Demographics/Estimates/E-5/ CA Employment Division Department: Labor Market Information http://www.labormarketinfo.edd.ca.gov/ CONTACT INFORMATION vitalsigns.info@bayareametro.gov METHODOLOGY NOTES (across all datasets for this indicator) Time spent in congestion measures the hours drivers are in congestion on freeway facilities based on traffic data. In recent years, data for the Bay Area comes from INRIX, a company that collects real-time traffic information from a variety of sources including mobile phone data and other GPS locator devices. The data provides traffic speed on the region’s highways. Using historical INRIX data (and similar internal datasets for some of the earlier years), MTC calculates an annual time series for vehicle hours spent in congestion in the Bay Area. Time spent in congestion is defined as the average daily hours spent in congestion on Tuesdays, Wednesdays and Thursdays during peak traffic months on freeway facilities. This indicator focuses on weekdays given that traffic congestion is generally greater on these days; this indicator does not capture traffic congestion on local streets due to data unavailability. This congestion indicator emphasizes recurring delay (as opposed to also including non-recurring delay), capturing the extent of delay caused by routine traffic volumes (rather than congestion caused by unusual circumstances). Recurring delay is identified by setting a threshold of consistent delay greater than 15 minutes on a specific freeway segment from vehicle speeds less than 35 mph. This definition is consistent with longstanding practices by MTC, Caltrans and the U.S. Department of Transportation as speeds less than 35 mph result in significantly less efficient traffic operations. 35 mph is the threshold at which vehicle throughput is greatest; speeds that are either greater than or less than 35 mph result in reduced vehicle throughput. This methodology focuses on the extra travel time experienced based on a differential between the congested speed and 35 mph, rather than the posted speed limit. To provide a mathematical example of how the indicator is calculated on a segment basis, when it comes to time spent in congestion, 1,000 vehicles traveling on a congested segment for a 1/4 hour (15 minutes) each, [1,000 vehicles x ¼ hour congestion per vehicle= 250 hours congestion], is equivalent to 100 vehicles traveling on a congested segment for 2.5 hours each, [100 vehicles x 2.5 hour congestion per vehicle = 250 hours congestion]. In this way, the measure captures the impacts of both slow speeds and heavy traffic volumes. MTC calculates two measures of delay – congested delay, or delay that occurs when speeds are below 35 miles per hour, and total delay, or delay that occurs when speeds are below the posted speed limit. To illustrate, if 1,000 vehicles are traveling at 30 miles per hour on a one mile long segment, this would represent 4.76 vehicle hours of congested delay [(1,000 vehicles x 1 mile / 30 miles per hour) - (1,000 vehicles x 1 mile / 35 miles per hour) = 33.33 vehicle hours – 28.57 vehicle hours = 4.76 vehicle hours]. Considering that the posted speed limit on the segment is 60 miles per hour, total delay would be calculated as 16.67 vehicle hours [(1,000 vehicles x 1 mile / 30 miles per hour) - (1,000 vehicles x 1 mile / 60 miles per hour) = 33.33 vehicle hours – 16.67 vehicle hours = 16.67 vehicle hours]. Data sources listed above were used to calculate per-capita and per-worker statistics. Top congested corridors are ranked by total vehicle hours of delay, meaning that the highlighted corridors reflect a combination of slow speeds and heavy t
- API
Northern Hemisphere Snow Cover Monthly Statistics at 1 Degree Resolution V001 (NHSNOWM) at GES DISC
data.nasa.gov | Last Updated 2022-01-17T05:45:22.000ZThis product is Snow Cover Statistics. The dataset was prepared by Dr. Peter Romanov at Cooperative Institute for Climate Studies(CICS) of the University of Maryland for Northern Eurasia Earth Science Partnership Initiative (NEESPI) program. The product includes the monthly snow statistics (frequency of occurrence) for Northern Hemisphere at 1x1 degree spatial resolution. The dataset covers the time period from January 2000 to November 2014. Monthly data were derived from daily snow cover charts produced at NOAA/NESDIS within Interactive Multisensor Ice Mapping System (IMS).