Data on the Open Data Network

Publishers

Refine by:Found 8,584 results

transportation Close

transportation - The Transportation category contains data, from across the Open Data Network™ of publishers, related to transportation, taxis, uberlyft, bikes, parking, buses, road congestion, road repair, ferries, bridges, rideshare and tolls.

API
On-street Car Park Bay Restrictions
data.melbourne.vic.gov.au | Last Updated 2022-03-01T22:22:14.000Z
Upcoming Changes: Please note that our parking system is being improved and this dataset may be disrupted. <a href='https://www.melbourne.vic.gov.au/building-and-development/shaping-the-city/city-projects/Pages/parking-sensor-upgrade.aspx'>See more information here</a>. Each row contains information about the restrictions that apply to one parking bay. Each restriction consists of a set of columns: How the data joins: There are three datasets that make up the live parking sensor release. They are the on-street parking bay sensors, on-street parking bays and the on-street car park bay restrictions. The way the datasets join is as follows. The on-street parking bay sensors join to the on-street parking bays by the marker_id attribute. The on-street parking bay sensors join to the on-street car park bay restrictions by the bay_id attribute. The on-street parking bays and the on-street car park bay restrictions don’t currently join. Field information: - FromDay: The first day in the range on which this restriction applies (0=Sunday, 6=Saturday) - ToDay: The final day in the range, inclusive. (1-5=Monday to Friday) - StartTime: The time each day when the restriction applies. - EndTime: The time each day when the restriction ends. - TypeDesc: The type of restriction. Eg: "2P Meter" (two hour parking, paid for using a meter), "Disabled Only" (only vehicles with disabiled permits can park). - Description: A compact, human-readable description of the overall restrictions. TKT A stands for Ticket Area covers multiple bays within that area. DIS ONLY and DIS are both disabled parking spaces - Duration: The time that a vehicle can park in the spot (assuming they can legally park there). - DisabilityExt: For bays that aren't limited to disabled permits, how much time a vehicle with disabled permit can spend in the spot. Usually twice the regular amount of time. - EffectiveOnPH: Does this restriction apply on public holidays. - Exemption: Which vehicles are exempt. There can be multiple restrictions, occurring at non-overlapping times. Each restriction is a set of columns with a number: FromDay1, ToDay1, StartTime1, EndTime1, etc. Disclaimer: While all due care has been taken to ensure the data of this website is accurate, current and available please note: · there may be errors or omission in it · there may be occasions where the data is not available and/or the website will be unavailable. The City of Melbourne and its employees accept no responsibility for any loss, damage, claim, expense, cost or liability whatsoever (including in contract, tort including negligence, pursuant to statue and otherwise) arising in respect of or in connection with accessing, using or reliance upon the data in this website, or the unavailability of the data or the website.
API
RICAPS On-road Transportation Emissions roll-up 2
datahub.smcgov.org | Last Updated 2019-05-22T23:00:49.000Z
Data 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
Nimbus-7 SMMR Derived Monthly Global Snow Cover and Snow Depth
nasa-test-0.demo.socrata.com | Last Updated 2015-07-19T09:14:15.000Z
The data set consists of monthly global snow cover and snow depth derived from Nimbus-7 SMMR data for 1978 through 1987. The SMMR data are interpolated for spatial and temporal gaps, and averaged for display in polar stereographic projection. Maps are based on six-day average brightness temperature data from the middle week of each month. Data are placed into 1/2 degree latitude by 1/2 degree longitude grid cells uniformly subdividing a polar stereographic map according to the geographic coordinates of the center of the radiometers' fields of view. Overlapping data from separate orbits in the same six-day period are averaged to give a single brightness temperature assumed to be at the cell's center. Oceans and bays are masked so that only microwave data for land areas are displayed. Comparisons of SMMR snow cover maps with previous maps produced by NOAA/NESDIS and US Air Force Global Weather Center indicate that the total snow covered area derived from SMMR is usually about ten percent less than that measured by the earlier products, because passive microwave sensors often can't detect shallow dry snow less than about 5 cm deep. Snow depths are comparable, showing SMMR results to be especially good for uniform snow covered areas such as the Canadian high plains and Russian steppes. Heavily forested and mountainous areas tend to mask the microwave snow signatures, and SMMR snow depth derivations are less reliable in those areas. Formerly distributed by NASA/GSFC/NSSDC and NASA Pilot Land Data System (PLDS), these data are now available via ftp from NSIDC.
API
An Effective And Efficient Transportation Network Indicator Summary
stat.montgomerycountymd.gov | Last Updated 2018-07-02T19:09:26.000Z
An 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
LA County Traffic Signal Incidents
data.lacounty.gov | Last Updated 2017-07-19T15:15:58.000Z
The Traffic Signal depict known/reported operational issues with County of Los Angeles Department of Public Works operated traffic signals only. These are generally those traffic signals located in unincorporated County areas or within those cities that contract to the County for traffic signal maintenance services. Traffic signal conditions can change frequently. Please check this site periodically before finalizing any travel plans. For those signals maintained by Public Works, please report any traffic signal concerns to our 24-7 Dispatch Center at (626)458-4357 (HELP).
API
Transport Route and Transport Route Separation Area
data.sunshinecoast.qld.gov.au | Last Updated 2022-07-13T22:48:20.000Z
"The Transport Route and Transport Route Seperation Area layer forms part of the Extractive Resources Overlay Maps for the Sunshine Coast Planning Scheme 2014. This layer is for the purpose of the Sunshine Coast Planning Scheme 2014 only. Please contact Council on 5475 7526 or email mail@sunshinecoast.qld.gov.au for more information on the Sunshine Coast Planning Scheme 2014. Notes on Extractive Resources Overlay Maps ─ * Overlays provide a trigger for consideration of an overlay issue to be verified by further on-site investigations. * In certain circumstances pre-existing development approvals may override the operation of an overlay."
API
Northern Hemisphere EASE-Grid 2.0 Weekly Snow Cover and Sea Ice Extent
nasa-test-0.demo.socrata.com | Last Updated 2015-07-19T09:14:22.000Z
The Northern Hemisphere EASE-Grid 2.0 Weekly Snow Cover and Sea Ice Extent Version 4 product combine snow cover and sea ice extent at weekly intervals from 23 October 1978 through 29 June 2014, and snow cover alone from 03 October 1966 through 29 June 2014. Snow cover extent for this data set is based on the NOAA/NCDC Climate Data Record (CDR) of Northern Hemisphere (NH) Snow Cover Extent (SCE) by D. Robinson (2012) and regridded to the EASE-Grid. The NOAA/NCDC CDR of Northern Hemisphere Snow Cover Extent data were derived from the manual interpretation of AVHRR, GOES, and other visible-band satellite data (Helfrich et al. 2007). Sea ice extent is regridded to EASE-Grid from Sea Ice Concentrations from Nimbus-7 SMMR and DMSP SSM/I-SSMIS Passive Microwave Data. Designed to facilitate study of Northern Hemisphere seasonal fluctuations of snow cover and sea ice extent, the data set also includes monthly climatologies describing average extent, probability of occurrence, and variance. Data are provided in flat, unsigned binary files and are available via FTP.
API
Off-street car parking 2021
data.melbourne.vic.gov.au | Last Updated 2022-12-09T00:11:31.000Z
Data collected as part of the City of Melbourne's Census of Land Use and Employment (CLUE). The data covers the period 2021. The number of off-street car parking spaces per property is recorded in CLUE. Car parking can be classified as: • Commercial: Car parking in a publicly accessible, paid parking facility • Residential: Car parking in a residential building or property • Private: Car parking in a non-residential building that is provided for use by staff, customers or visitors. For more information see http://www.melbourne.vic.gov.au/clue
API
Bicycle routes, including informal, on-road and off-road routes.
data.melbourne.vic.gov.au | Last Updated 2021-09-30T16:00:07.000Z
This dataset represents the bicycle routes within the municipal boundary of the City of Melbourne.
API
VIIRS/NPP BRDF/Albedo Snow Status Daily L3 Global 30ArcSec CMG V001
data.nasa.gov | Last Updated 2022-01-17T06:02:28.000Z
The Suomi National Polar-Orbiting Partnership (Suomi NPP) NASA Visible Infrared Imaging Radiometer Suite (VIIRS) Bidirectional Reflectance Distribution Function (BRDF) and Albedo Snow Status product (VNP43D52) is produced daily using 16 days of data at 30 arc second (1,000 meter) resolution. Data are temporally weighted to the ninth day, which is reflected in the file name. The VNP43D product suite is provided in a Climate Modeling Grid (CMG), which covers the entire globe for use in climate simulation models. Due to the large file size, each VNP43D product contains just one data layer for each of the parameters included in the VNP43MA2 (https://doi.org/10.5067/VIIRS/VNP43MA2.001) product. VNP43D40 through VNP43D53 are the 30 arc second BRDF/Albedo Quality values, the Local Solar Noon values, the Valid Observations of the moderate resolution bands (M1 through M5, M7, M8, M10, and M11) plus the Day/Night Band (DNB), the Snow Status, and the Uncertainty. Details regarding methodology are available on the VNP43MA2 product page and in the Algorithm Theoretical Basis Document (ATBD). VNP43D52 contains the snow status quality layer, which identifies each pixel as either “Snow-free Albedo Retrieved” or “Snow Albedo Retrieved” for the acquisition period.