Back to Browsing catalogs
City of Courtenay Open Data
Open Data Catalogue City of Courtenay Welcome! Terms of Use This is the community's public platform for exploring and downloading open data, discovering and building apps, and engaging to solve important local issues. You can analyze and combine Open Datasets using maps, as well as develop new web and mobile applications. Let's make our great community even better, together! We will continue to add data to this page as it becomes available. For more information, please review the City of Courtenay's • The City of Courtenay makes no representation or warranty; either expressed or implied, in fact or in law, with respect to the accuracy, completeness or appropriateness of the data, materials or documents contained or referenced herein or provided. • In addition, the City of Courtenay shall not be responsible for any action, cost, loss or liability whatsoever arising from the reliance on or use of this information provided by the City. • These files are for reference purposes only and the City of Courtenay is not liable for any consequences or damages any individual may incur as a result of misrepresented, misquoted, or mistaken information. • The information provided is not meant to be an authoritative guide. Search Data and Apps Find Data Explore Data Categories OR All Data Zoning and Property Transportation Environment Electrical Storm Sewer Water Featured Apps See More
IndexedGeneral
Property | Value |
---|---|
Link | https://data-courtenay.opendata.arcgis.com/ |
Status | scheduled |
Catalog type | Geoportal |
Owner name | City of Courtenay |
Owner type | Unknown |
Owner link | None |
Owner location | Canada |
Software | arcgishub (ArcGIS Hub) |
Tags | |
Access modes | open |
Content types | dataset, map_layer |
API Status | active |
Coverage
code | name |
---|---|
CA | Canada |
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.