Welcome to Boulder's Open Data Catalog. The purpose of Boulder Open Data Catalog is to increase public access to high value, machine readable datasets generated by the City of Boulder. We invite you to actively participate in shaping the future of Boulder's Open Data Catalog by contacting us to suggest additional datasets or building and submitting applications with the available data.
25 datasets found. Showing results 1-10 of 25 with the tag gis
The planning area I, II, III map defines the city's service area which sets the city's urban growth boundary and ensures a logical extension of urban services.
City Benchmark information includes the Benchmark ID, Location, Description, Elevations in COB datum from level circuits, and NGVD 29,NGVD88 datum’s. Elevation accuracy is within 0.10 ft. and should be verified between multiple Benchmarks. Source – level circuits ran by city crews and city contractors.
Source Public Works - Utility Engineering
City of Boulder - city limits . Source – created from city parcel data layer
Designated city historic districts and landmarks. Source – City Planning Department
Lakes, ponds, creeks, irrigation ditches, and irrigation laterals. Source – digitized from aerial photography
Main highways and arterials, Source – digitized from aerial photography
Centralized portal to GIS and map information for the city. Provides access to zoning, land use, flood, annexation, wetlands, ownership parcel and other information. Displays comprehensive parcel information from Boulder County and the city's Property Information Report. Learn how to use the eMap Link by reviewing the eMaps Tutorial.
Property (Fee and Conservation Easements) owned by Open Space and Mountain Parks (OSMP). There is no public access on conservation easements.
Open Space and Mountain Parks (OSMP) maps the perimeter of all active prairie dog colonies each fall. This dataset contains OSMP and BCPOS data since 1996 CLIPPED to OSMP lands only. This includes Jointly owned properties and colonies mapped on easements. To query out a specific year please use a definition query similar to “Year” = 2013.