Back to Browsing catalogs
City of Cupertino
GIS Open Data Portal Welcome to the City of Cupertino GIS Open Data Portal The City of Cupertino has created this open data portal to allow our Geographic Information Systems (GIS) data to be as transparent, discoverable, and usable as possible. To view spatial data, select a category below or search for a layer by name using the search bar. Explore Data Categories GIS Boundary Layers GIS Environmental Layers GIS Recreation Layers GIS Development Layers GIS Property Layers GIS Transportation Layers 2019 City of Cupertino The City of Cupertino does not guarantee the accuracy, adequacy, completeness or usefulness of any information. The City does not warrant the positional or thematic accuracy of the GIS data. The GIS data and cartographic digital files are not legal representations of the depicted data. Information shown on these layers is derived from public records that are constantly undergoing change. Under no circumstances shall GIS mapping be used for final design purposes. While every effort has been made to ensure the content, sequence, accuracy, timeliness or completeness of materials presented within these pages, the City of Cupertino assumes no responsibility for errors or omissions, and explicitly disclaims any representations and warranties, including, without limitation, the implied warranties of merchantability and fitness for a particular purpose
Not indexedGeneral
Property | Value |
---|---|
Link | https://gis-cupertino.opendata.arcgis.com/ |
Status | scheduled |
Catalog type | Geoportal |
Owner name | City of Cupertino |
Owner type | Unknown |
Owner link | None |
Owner location | United States |
Software | arcgishub (ArcGIS Hub) |
Tags | |
Access modes | open |
Content types | dataset, map_layer |
API Status | active |
Coverage
code | name |
---|---|
US | United States |
Languages
code | name |
---|---|
EN | English |
API Endpoints
Download
Feedback
If you notice any errors or missing data catalogs, please contact us at dateno@dateno.io or open an issue on GitHub. We will address it as soon as possible.