ZIP Code business counts data for Maptitude mapping software are from Caliper Corporation and contain aggregated ZIP Code Business Patterns (ZBP) data and Rural-Urban Commuting Area (RUCA) data.

Business location data for Maptitude mapping software are from Caliper Corporation and contain point locations for businesses.

All regional statistics at Eurostat refer to NUTS. However, some data collections use postcodes to reference the geographic location. Therefore, Eurostat has established a link between postcodes and NUTS level 3 codes in order to exploit information which originally is coded only by postcodes.

Various projects in Eurostat and other services of the Commission as well as the European Investment Bank have expressed their need for a link between postcodes and NUTS codes. The most important application at Eurostat is in transport statistics where the information is used to identify the flows of goods transport on roads. Another application is to geo-code address registers with the regional NUTS codes because postcodes are generally available as part of the address.

The TERCET NUTS-postal codes matching tables contain a lookup-list of European postal codes and their corresponding NUTS codes for the NUTS versions 2010, 2013, 2016 and 2021. There are matching tables for most of the EU, Candidate, EFTA and the United Kingdom. Eurostat has applied a number of quality assurance measures to ensure the best possible quality of the data including formatting checks, checks for completeness of postal codes and checks for spatial accuracy of the geocoding.

Additional tables containing distance matrixes for different modes of transport are provided.

Nevertheless, due to the very diverse and complex situation in Europe for postal codes data we cannot guarantee that all postal codes are included and have been correctly matched. Should you detect any errors, we would be grateful if you could notify them to us at ESTAT-USER-SUPPORT@ec.europa.eu. The matching tables have been created with data and tools that allow for their free and public distribution for statistical and other non-commercial purposes.

More information on quality assurance and data sources can be found in the methodological notes.

KNOWN ISSUES FOR NUTS (as of 15/07/2020) * Malta has only higher level Postal districts * Data for CY has gaps for NUTS 2021, GISCO is working on improving the coverage. * Data for Albania and Montenegro are missing, GISCO is looking into improving the coverage.

Summary

Geojson files used to visualize geospatial layers relevant to identifying and assessing trucking fleet decarbonization opportunities with the MIT Climate & Sustainability Consortium's Geospatial Trucking Industry Decarbonization Explorer (Geo-TIDE) tool.

Relevant Links

Link to the online version of the tool (requires creation of a free user account).

Link to GitHub repo with source code to produce this dataset and deploy the Geo-TIDE tool locally.

Funding

This dataset was produced with support from the MIT Climate & Sustainability Consortium.

Original Data Sources

These geojson files draw from and synthesize a number of different datasets and tools. The original data sources and tools are described below:

Filename(s) Description of Original Data Source(s) Link(s) to Download Original Data License and Attribution for Original Data Source(s)

faf5_freight_flows/*.geojson

trucking_energy_demand.geojson

highway_assignment_links_*.geojson

infrastructure_pooling_thought_experiment/*.geojson

Regional and highway-level freight flow data obtained from the Freight Analysis Framework Version 5. Shapefiles for FAF5 region boundaries and highway links are obtained from the National Transportation Atlas Database. Emissions attributes are evaluated by incorporating data from the 2002 Vehicle Inventory and Use Survey and the GREET lifecycle emissions tool maintained by Argonne National Lab.

Shapefile for FAF5 Regions

Shapefile for FAF5 Highway Network Links

FAF5 2022 Origin-Destination Freight Flow database

FAF5 2022 Highway Assignment Results

Attribution for Shapefiles: United States Department of Transportation Bureau of Transportation Statistics National Transportation Atlas Database (NTAD). Available at: https://geodata.bts.gov/search?collection=Dataset.

License for Shapefiles: This NTAD dataset is a work of the United States government as defined in 17 U.S.C. § 101 and as such are not protected by any U.S. copyrights. This work is available for unrestricted public use.

Attribution for Origin-Destination Freight Flow database: National Transportation Research Center in the Oak Ridge National Laboratory with funding from the Bureau of Transportation Statistics and the Federal Highway Administration. Freight Analysis Framework Version 5: Origin-Destination Data. Available from: https://faf.ornl.gov/faf5/Default.aspx. Obtained on Aug 5, 2024. In the public domain.

Attribution for the 2022 Vehicle Inventory and Use Survey Data: United States Department of Transportation Bureau of Transportation Statistics. Vehicle Inventory and Use Survey (VIUS) 2002 [supporting datasets]. 2024. https://doi.org/10.21949/1506070

Attribution for the GREET tool (original publication): Argonne National Laboratory Energy Systems Division Center for Transportation Research. GREET Life-cycle Model. 2014. Available from this link.

Attribution for the GREET tool (2022 updates): Wang, Michael, et al. Summary of Expansions and Updates in GREET® 2022. United States. https://doi.org/10.2172/1891644

grid_emission_intensity/*.geojson

Emission intensity data is obtained from the eGRID database maintained by the United States Environmental Protection Agency.

eGRID subregion boundaries are obtained as a shapefile from the eGRID Mapping Files database.

eGRID database

Shapefile with eGRID subregion boundaries

Attribution for eGRID data: United States Environmental Protection Agency: eGRID with 2022 data. Available from https://www.epa.gov/egrid/download-data. In the public domain.

Attribution for shapefile: United States Environmental Protection Agency: eGRID Mapping Files. Available from https://www.epa.gov/egrid/egrid-mapping-files. In the public domain.

US_elec.geojson

US_hy.geojson

US_lng.geojson

US_cng.geojson

US_lpg.geojson

Locations of direct current fast chargers and refueling stations for alternative fuels along U.S. highways. Obtained directly from the Station Data for Alternative Fuel Corridors in the Alternative Fuels Data Center maintained by the United States Department of Energy Office of Energy Efficiency and Renewable Energy.

US_elec.geojson

US_hy.geojson

US_lng.geojson

US_cng.geojson

US_lpg.geojson

Attribution: U.S. Department of Energy, Energy Efficiency and Renewable Energy. Alternative Fueling Station Corridors. 2024. Available from: https://afdc.energy.gov/corridors. In the public domain.

These data and software code ("Data") are provided by the National Renewable Energy Laboratory ("NREL"), which is operated by the Alliance for Sustainable Energy, LLC ("Alliance"), for the U.S. Department of Energy ("DOE"), and may be used for any purpose whatsoever.

daily_grid_emission_profiles/*.geojson

Hourly emission intensity data obtained from ElectricityMaps.

Original data can be downloaded as csv files from the ElectricityMaps United States of America database

Shapefile with region boundaries used by ElectricityMaps

License: Open Database License (ODbL). Details here: https://www.electricitymaps.com/data-portal

Attribution for csv files: Electricity Maps (2024). United States of America 2022-23 Hourly Carbon Intensity Data (Version January 17, 2024). Electricity Maps Data Portal. https://www.electricitymaps.com/data-portal.

Attribution for shapefile with region boundaries: ElectricityMaps contributors (2024). electricitymaps-contrib (Version v1.155.0) [Computer software]. https://github.com/electricitymaps/electricitymaps-contrib.

gen_cap_2022_state_merged.geojson

trucking_energy_demand.geojson

Grid electricity generation and net summer power capacity data is obtained from the state-level electricity database maintained by the United States Energy Information Administration.

U.S. state boundaries obtained from this United States Department of the Interior U.S. Geological Survey ScienceBase-Catalog.

Annual electricity generation by state

Net summer capacity by state

Shapefile with U.S. state boundaries

Attribution for electricity generation and capacity data: U.S. Energy Information Administration (Aug 2024). Available from: https://www.eia.gov/electricity/data/state/. In the public domain.

electricity_rates_by_state_merged.geojson

Commercial electricity prices are obtained from the Electricity database maintained by the United States Energy Information Administration.

Electricity rate by state

Attribution: U.S. Energy Information Administration (Aug 2024). Available from: https://www.eia.gov/electricity/data.php. In the public domain.

demand_charges_merged.geojson

demand_charges_by_state.geojson

Maximum historical demand charges for each state and zip code are derived from a dataset compiled by the National Renewable Energy Laboratory in this this Data Catalog.

Historical demand charge dataset

The original dataset is compiled by the National Renewable Energy Laboratory (NREL), the U.S. Department of Energy (DOE), and the Alliance for Sustainable Energy, LLC ('Alliance').

Attribution: McLaren, Joyce, Pieter Gagnon, Daniel Zimny-Schmitt, Michael DeMinco, and Eric Wilson. 2017. 'Maximum demand charge rates for commercial and industrial electricity tariffs in the United States.' NREL Data Catalog. Golden, CO: National Renewable Energy Laboratory. Last updated: July 24, 2024. DOI: 10.7799/1392982.

eastcoast.geojson

midwest.geojson

la_i710.geojson

h2la.geojson

bayarea.geojson

saltlake.geojson

northeast.geojson

Highway corridors and regions targeted for heavy duty vehicle infrastructure projects are derived from a public announcement on February 15, 2023 by the United States Department of Energy.

The shapefile with Bay area boundaries is obtained from this Berkeley Library dataset.

The shapefile with Utah county boundaries is obtained from this dataset from the Utah Geospatial Resource Center.

Shapefile for Bay Area country boundaries

Shapefile for counties in Utah

Attribution for public announcement: United States Department of Energy. Biden-Harris Administration Announces Funding for Zero-Emission Medium- and Heavy-Duty Vehicle Corridors, Expansion of EV Charging in Underserved Communities (2023). Available from https://www.energy.gov/articles/biden-harris-administration-announces-funding-zero-emission-medium-and-heavy-duty-vehicle.

Attribution for Bay area boundaries: San Francisco (Calif.). Department Of Telecommunications and Information Services. Bay Area Counties. 2006. In the public domain.

Attribution for Utah boundaries: Utah Geospatial Resource Center & Lieutenant Governor's Office. Utah County Boundaries (2023). Available from https://gis.utah.gov/products/sgid/boundaries/county/.

License for Utah boundaries: Creative Commons 4.0 International License.

incentives_and_regulations/*.geojson

State-level incentives and regulations targeting heavy duty vehicles are collected from the State Laws and Incentives database maintained by the United States Department of Energy's Alternative Fuels Data Center.

Data was collected manually from the State Laws and Incentives database.

Attribution: U.S. Department of Energy, Energy Efficiency and Renewable Energy, Alternative Fuels Data Center. State Laws and Incentives. Accessed on Aug 5, 2024 from: https://afdc.energy.gov/laws/state. In the public domain.

These data and software code ("Data") are provided by the National Renewable Energy Laboratory ("NREL"), which is operated by the Alliance for Sustainable Energy, LLC ("Alliance"), for the U.S. Department of Energy ("DOE"), and may be used for any purpose whatsoever.

costs_and_emissions/*.geojson

diesel_price_by_state.geojson

trucking_energy_demand.geojson

Lifecycle costs and emissions of electric and diesel trucking are evaluated by adapting the model developed by Moreno Sader et al., and calibrated to the Run on Less dataset for the Tesla Semi collected from the 2023 PepsiCo Semi pilot by the North American Council for Freight Efficiency.

In

(Link to Metadata) EmergencyE911_RDS was originally derived from RDSnn (now called TransRoad_RDS). "Zero-length ranges" in the ROADS layer pertain to grand-fathered towns that have not yet provided the Enhanced 9-1-1 Board road segment range information. RDSnn was originally developed using a combination of paper and RC Kodak RF 5000 orthophotos (visual image interpretation and manual digitizing of centerlines). Road attributes (RTNO and CLASS) were taken from the official VT Agency of Transportation (VTrans) highway maps. New roads not appearing on the photos were digitized with locations approximated from the VTrans highway maps. State Forest maps were used to determine both location and attributes of state forest roads. Some data updates have used RF 2500 or RF 1250 orthophotos and GPS, or other means for adding new roads and improving road locations. The Enhanced E911 program added new roads from GPS and orthos between 1996-1998. Also added road name and address geocoding. VCGI PROCESSING (Tiling and Added items); E911 provides the EmergencyE911_RDS data to VCGI in a statewide format. It lacks FIPS6 coding, making it difficult to extract data on the basis of town/county boundaries. As a result, VCGI has added FIPS6 to the attribute table. This field was originally populated by extracting MCODE value from RDNAME and relating to TBPOLY.PAT to bring over matching MCODE values. FIPS6 problems along the interstates and "Gores & Grants" in the Northeast Kingdom, were corrected. All features with an MCODE equal to 200 or 579 were assigned a FIPS6 equal to 0. The center point of these arcs were then intersected with BoundaryTown_TBHASH to assign a FIPS6 value. This information was then transfered back into the RDS.AAT file via a relate. A relate was established between the ROADNAMES.DBF file (road name lookup table) and the RDS.AAT file. The RDFLNAME attribute was populated by transfering the NAME value in the ROADNAMES.DBF table. The RDFLNAME item was then parsed into SUF.DIR, STREET.NAME, STREET.TYPE, and PRE.DIR, making addressing matching functions a little easier. See the "VT Road Centerline Data FAQ" for more information about TransRoad_RDS and EmergencyE911_RDS. https://vcgi.vermont.gov/techres/?page=./white_papers/default_content.cfmField Descriptions:OBJECTID: Internal feature number, automatically generated by Esri software.SEGMENTID: Unique segment ID.ARCID: Arc identifier, unique statewide. The ARCID is a unique identifier for every ARC in the EmergencyE911_RDS data layer.PD: Prefix Direction, previously name PRE.DIR.PT: Prefix Type.SN: Street Name. Previously named STREET.ST: Street Type.SD: Suffix Direction, i.e., W for West, E for East, etc.GEONAMEID: Unique ID for each road name.PRIMARYNAME: Primary name.ALIAS1: Alternate road name 1.ALIAS2: Alternate road name 2.ALIAS3: Alternate road name 3.ALIAS4: Alternate road name 4.ALIAS5: Alternate road name 5.COMMENTS: Free text field for miscellaneous comments.ONEWAY: One-way street. Uses the Oneway domain*.NO_MSAG:MCODE: Municipal code.LESN: Left side of road Emergency Service Number.RESN: Right side of road Emergency Service Number.LTWN: Left side of road town.RTWN: Right side of road town.LLO_A: Low address for left side of road.RLO_A: Low address for right side of road.LHI_A: High address for left side of road.RHI_A: High address for right side of road.LZIP: Left side of road zip code.RZIP: Right side of road zip code.LLO_TRLO_TLHI_TRHI_TRTNAME: Route name.RTNUMBER: Route number.HWYSIGN: Highway sign.RPCCLASSAOTCLASS: Agency of Transportation class. Uses AOTClass domain**.ARCMILES: ESRI ArcGIS miles.AOTMILES: Agency of Transportation miles.AOTMILES_CALC:UPDACT:SCENICHWY: Scenic highway.SCENICBYWAY: Scenic byway.FORMER_RTNAME: Former route name.PROVISIONALYEAR: Provisional year.ANCIENTROADYEAR: Ancient road year.TRUCKROUTE: Truck route.CERTYEAR:MAPYEAR:UPDATEDATE: Update date.GPSUPDATE: Uses GPSUpdate domain***.GlobalID: GlobalID.STATE: State.GAP: Gap.GAPMILES: Gap miles.GAPSTREETID: Gap street ID.FIPS8:FAID_S:RTNUMBER_N:LCOUNTY:RCOUNTY:PRIMARYNAME1:SOURCEOFDATA: Source of data.COUNTRY: Country.PARITYLEFT:PARITYRIGHT:LFIPS:RFIPS:LSTATE:RSTATE:LESZ:RESZ:SPEED_SOURCE: Speed source.SPEEDLIMIT: Speed limit.MILES: Miles.MINUTES: Minutes.Shape: Feature geometry.Shape_Length: Length of feature in internal units. Automatically computed by Esri software.*Oneway Domain:N: NoY: Yes - Direction of arcX: Yes - Opposite direction of arc**AOTClass Domain:1: Town Highway Class 1 - undivided2: Town Highway Class 2 - undivided3: Town Highway Class 3 - undivided4: Town Highway Class 4 - undivided5: State Forest Highway6: National Forest Highway7: Legal Trail. Legal Trail Mileage Approved by Selectboard after the enactment of Act 178 (July 1, 2006). Due to the introduction of Act 178, the Mapping Unit needed to differentiate between officially accepted and designated legal trail versus trails that had traditionally been shown on the maps. Towns have until 2015 to map all Class 1-4 and Legal Trails, based on new changes in VSA Title 19.8: Private Road - No Show. Private road, but not for display on local maps. Some municipalities may prefer not to show certain private roads on their maps, but the roads may need to be maintained in the data for emergency response or other purposes.9: Private road, for display on local maps10: Driveway (put in driveway)11: Town Highway Class 1 - North Bound12: Town Highway Class 1 - South Bound13: Town Highway Class 1 - East Bound14: Town Highway Class 1 - West Bound15: Town Highway Class 1 - On/Off Ramp16: Town Highway Class 1 - Emergency U-Turn20: County Highway21: Town Highway Class 2 - North Bound22: Town Highway Class 2 - South Bound23: Town Highway Class 2 - East Bound24: Town Highway Class 2 - West Bound25: Town Highway Class 2 - On/Off Ramp30: State Highway31: State Highway - North Bound32: State Highway - South Bound33: State Highway - East Bound34: State Highway - West Bound35: State Highway - On/Off Ramp40: US Highway41: US Highway - North Bound42: US Highway - South Bound43: US Highway - East Bound44: US Highway - West Bound45: US Highway - On/Off Ramp46: US Highway - Emergency U-Turn47: US Highway - Rest Area50: Interstate Highway51: Interstate Highway - North Bound52: Interstate Highway - South Bound53: Interstate Highway - East Bound54: Interstate Highway - West Bound55: Interstate Highway - On/Off Ramp56: Interstate Highway - Emergency U-Turn57: Interstate Highway - Rest Area59: Interstate Highway - Other65: Ferry70: Unconfirmed Legal Trail71: Unidentified Corridor80: Proposed Highway Unknown Class81: Proposed Town Highway Class 182: Proposed Town Highway Class 283: Proposed Town Highway Class 384: Proposed State Highway85: Proposed US Highway86: Proposed Interstate Highway87: Proposed Interstate Highway - Ramp88: Proposed Non-Interstate Highway - Ramp89: Proposed Private Road91: New - Class Unknown92: Military - no public access93: Public - Class Unknown95: Class Under Review96: Discontinued Road97: Discontinued Now Private98: Not a Road99: Unknown***GPSUpdate Domain:Y: Yes - Needs GPS UpdateN: No - Does not need GPS UpdateG: GPS Update CompleteV: GPS Update Complete - New RoadX: Unresolved Segment