EVCI Roads, Highways, and Freeway Exits (Dataset)
About this dataset
Columns (3)
Sample rows
| name | OBJECTID | orientation |
|---|---|---|
| McClintock Dr. | 1 | vertical |
| 202 - 101 Intersection | 2 | |
| Rio Saltado Pkwy. | 3 | right |
| W University Dr. | 4 | right |
| Apache Blvd. | 5 | right |
| Broadway Rd. | 6 | right |
| Southern Ave. | 7 | southave |
| Baseline Rd. | 8 | right |
A sample of the data. The full table and an interactive map open with a free account.
Related datasets
✦ Suggested by OrionAIThis feature layer provides counts of registered medium & heavy duty (class 2b to 8) electric vehicles in Tempe by zip code. Each record represents a zip code and includes details about counts of registered vehicles each zip code. This data is sourced from national vehicle registration data. This information is a component of ongoing efforts to provide resources for EV charging infrastructure development in the City of Tempe. Data Scope Vehicle registration data was summarized for Q4 2025. Data Use For use in the Tempe EVCI Development Strategy Map Data Limitations Polygons depict interpretations of USPS zip code boundaries and were accessed from the City of Tempe's Data Catalog. Data does not depict class 1, light duty vehicle registration information. Data Dictionary Additional Information Contact Name: Sustainability Division Contact Email: sustainability@tempe.gov Data Source: IHS Markit, City of Tempe Data Source Type: GIS Feature Layer Preparation Method: Zip Code boundary data for Tempe was joined with vehicle registration by zip code. Publish Method: Manual Publish Frequency: One-time, static dataset
This feature layer provides counts of forecasted chargers needed and current gap in charging for census tracts in Tempe. Each record represents a census tract in Tempe and includes details on forecasted charger count, existing charger, and gap in chargers at level 2 and DC Fast charging power levels. This modeled dataset was created by Catalyst Mobility (formerly Calstart). This information is a component of ongoing efforts for EV charging infrastructure development for Tempe. Data Scope Charger forecasts are to 2050 for level 2 and DC fast charging power levels. Data Use Intended to be used in the Tempe EVCI Development Strategy Map. Data Limitations Charger count data is forecasted and may not reflect actual future conditions. Data Dictionary Additional Information Contact Name: Sustainability Division Contact Email: sustainability@tempe.gov Data Source: Catalyst Mobility (formerly Calstart) Data Source Type: GIS Feature Layer Preparation Method: See Task 2 of Electric Vehicle Charging Infrastructure (EVCI) Siting Plan Assessment Publish Method: Manual Publish Frequency: One-time static
This feature layer view provides the locations of business districts in Tempe. It includes the area location and district name. This data supports the story map Tempe Through the Eyes of Innovation. Tempe’s business districts offer a range of environments designed to support companies at every stage, from emerging startups to global industry leaders. Each district reflects a different strength of the city’s economy, whether it is advanced manufacturing, technology and research, urban office space, or mixed-use development. Together, they create a connected network of opportunity anchored by strong infrastructure, access to talent, and proximity to major transportation corridors. Data Scope Business district areas representing different concentrations of economic activity within the city. Data Use Provides geographic context for understanding the location and distribution of key economic activity areas. Data Limitations District boundaries are generalized areas and do not represent official or precise boundaries. Additional Information Contact Name: Lisa Hausz Contact Email: lisa_hausz@tempe.gov Data Source: Economic Development Department Data Source Type: ArcGIS Pro project. Preparation Method: District boundaries were developed in ArcGIS Pro and published to ArcGIS Online. Publish Method: Manual. Publish Frequency: Intermittent as updates occur.
This page provides data for the Carbon Neutrality performance measure. The City of Tempe is committed to protecting the environment. Carbon emissions are a significant contributor to the pollution of our atmosphere. Sources of carbon emissions include the energy used in city buildings and facilities, and in the fuel used in transit, city vehicles, and employee commuting. This performance measure puts the City on a path to being a carbon-neutral city. The municipal carbon footprint includes buildings, streetlights, water treatment, electricity, and fuel usage for fleet, transit, solid waste, and employee commute. The performance measure dashboard is available at 4.19 Carbon Neutrality Data Dictionary Additional Information Source: City pisions (is this word correct?): fleet, WUD, solid waste. APS, SRP, MAG, SHROG, and Valley Metro Contact: Grace Kelly Contact E-Mail: Grace_Kelly@tempe.gov Data Source Type: CSV Preparation Method: It is part of a larger data set and uses proprietary software. Publish Frequency: Every 5 years Publish Method: Manual
This page provides data for the Tree and Shade Canopy performance measure. Sustainable growth for the City of Tempe is influenced by many factors, including the development and maintenance of our tree canopy. An adequate canopy provides shade, cooling, reduces water evaporation, and is an indication of a healthy and well-maintained environment. As per the Urban Forestry Master Plan, this data represents tree canopy in parks, street right-of-ways, and municipally owned and managed facilities. The performance measure dashboard is available at 4.11 Tree Coverage Data Dictionary Additional Information Source: Contact: Craig Hayton Contact E-Mail: Craig_Hayton@tempe.gov Data Source Type: CSV Preparation Method: Tracked by staff quarterly Publish Frequency: Annual Publish Method: Manual
Primary roads, secondary roads, local roads, and railroads; January 1, 2020
Indexed by OrionGIS from ArcGIS Online public items (authoritative). Data is loaded from the publisher's own server when you use it. Permanent link