Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A polygon feature class of municipal boundaries within Miami-Dade County, data includes the municipal codes and names.Updated: As Needed The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A polygon feature class of the City of Miami Commissioner District boundaries. The purpose of the district layer is to divide voters by City of Miami Commissioner Districts. It is used in general analysis, as well as for mapping purposes.Updated: Every 10 yrs The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
The following data set contains service request activity for Miami-Dade County. The data sets include services completed proactively by Miami-Dade County departments and requests submitted by citizens via phone (311), online (miamidade.gov), and other self service channels such as the 311Direct mobile application. With a few exceptions, the dataset does not generally include requests from other cities (City of Miami, Coral Gables, etc.) unless the work is owned by Miami-Dade County staff. THIS DATA SET IS STILL IN BETA. Please keep that in mind as you review it.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A point feature class of Miami-Dade County Municipal City Halls created for the Miami-Dade County Office of Emergency Management (OEM). Municipal City Halls are considered OEM Critical Locations.Updated: Bi-Annually The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This polygon feature class of City of Miami's projects is prepared to support our iMDC Utility Coordination application, and it is periodically updated by the iMDC Utility Coordination Data Processor job(s) after validating City of Miami's provided data for this solution. Any invalid data not meeting the required schema or criteria for collaboration is not reflected in this feature class. Updated: Daily The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterThe High Accuracy Elevation Data Project collected elevation data (meters) on a 400 meter topographic grid with a vertical accuracy of +/- 15 centimeters to define the topography in South Florida. The data are referenced to the horizontal datum North American Datum 1983 (NAD 83) and the vertical datum North American Vertical Datum 1988 (NAVD 88). In some areas, the surveying was accomplished using airboats. Because access was a logistical problem with airboats, the USGS developed a helicopter-based instrument known as the Airborne Height Finder (AHF). All subsequent data collection used the AHF. Data were collected from the Loxahatchee National Wildlife Refuge, south through the Water Conservation Areas (1A, 2A, 2B, 3A, and 3B), Big Cypress National Park, the Everglades National Park, to the Florida Bay. The data are available for the areas shown on the USGS High Accuracy Elevation Data graphic at http://sofia.usgs.gov/exchange/desmond/desmondelev.html . The work was performed for Everglades ecosystem restoration purposes.
The data are from regional topographic surveys to collect and provide elevation data to parameterize hydrologic and ecological numerical simulation models that are being developed for ecosystem restoration activities. Surveying services were also rendered to provide vertical reference points for numerous water level gauges. Modeling of sheet flow and water surface levels in the wetlands of South Florida is very sensitive to changes in elevation due to the expansive and extremely low relief terrain. Hydrologists determined minimum vertical accuracy requirements for the elevation data for use as input to hydrologic models. As a result, elevation data with a vertical accuracy specification of +/-15 centimeters (cm) relative to the North American Vertical Datum of 1988 (NAVD88) were collected in critical areas using state-of-the-art differential global positioning system (GPS) technology and data processing techniques.
Facebook
TwitterThe U.S. Geological Survey (USGS) is coordinating the aquisition of high accuracy elevation data. Three formats of the data are available for each data set: .cor files which contain complete lists of Global Positioning System point files, .asc files which are the same as the .cor files but have been reformatted to process into ARC/INFO coverages, and .e00 files which are the ARC/INFO coverages. The files are available in the same 7.5- by 7.5-minute coverages as USGS quadrangles. The elevation data is collected on a 400 by 400 meter grid. The elevations are referenced to the horizontal North American Datum of 1983 (NAD83) and vertical North American Vertical Datum of 1988 (NAVD88).
This project is performing regional topographic surveys to collect and provide elevation data to parameterize hydrologic and ecological numerical simulation models that are being developed for ecosystem restoration activities. Surveying services are also being rendered to provide vertical reference points for numerous water level gauges.
Modeling of sheet flow and water surface levels in the wetlands of South Florida is very sensitive to changes in elevation due to the expansive and extremely low relief terrain. Hydrologists have determined minimum vertical accuracy requirements for the elevation data for use as input to hydrologic models. As a result, elevation data with a vertical accuracy specification of +/-15 centimeters (cm) relative to the North American Vertical Datum of 1988 (NAVD88) are being collected in critical areas using state-of-the-art differential global positioning system (GPS) technology and data processing techniques.
Facebook
Twitterhttps://www.florida-demographics.com/terms_and_conditionshttps://www.florida-demographics.com/terms_and_conditions
A dataset listing Florida counties by population for 2024.
Facebook
TwitterThis dataset is a combination of the Broward County Parks, Broward County City Parks, and Broward County State Parks datasets.
Broward County Parks: The locations of all sixty-two county-owned and operated parks, last updated March 2013 when the Lafayette Park boundary changed. This layer was reviewed by the Parks and Recreation Division of Broward County on 5/15/2015 with no updates required. This layer will be updates as park boundaries change or new parks are added to Broward County.
Broward County City Parks: The GIS Section reviews the BCGIS.ParkCity layer annually in support of the EOC and the Comprehensive Plan. The data is checked for inclusion and geometric placement accuracy. The GIS Section is no longer updating City Parks 100%. We will be reviewing a select handful of parks each year. Generally we will begin our update schedule with the largest cities first, but a good city parks source may alter that schedule. The years listed below indicate which cities have been updated.
2009: All parks corrected to parcels. Corrected/updated Weston with T. Gates data.
2010: The cities' parks updated included Hollywood, Pompano Beach, and Hollywood.
The review technique was a review and/or incorporation of geodata from Ft. Lauderdale and website information incorporation from Pompano and Hollywood.
2011: Davie Parks updated and corrected based on Irene Degroot's shapefile and aerials. Wilton Manors update complete, city managers office said pocket parks are to be expected soon. West Park parks reflect parcels - note Mary Saunders Park is a very irregular shape, made up of many rights-of-way and will be an exception to our parcel based rule.
2013: Toni Peyton said there were no changes to county parks since Miramar Pinelands. She requested a map of POD parks. Pembroke Pines - reviewed park inventory, park map locator, and spoke with Lori of Chuck Vones' (Dir. Parks and Rec) office. Reviewed Miramar Park Inventory.
2014: Reviewed and updated Coral Springs, Lauderdale By the Sea, Pembroke Park, Pembroke Pines, Lighthouse Point, Fort Lauderdale, Coconut Creek, and West Park.
2015: Reviewed 05/15/15
Broward County State Parks: Two State Parks in Broward County, Fl. Data reviewed 05/15/2015.
Source: Parks and Recreation Division of Broward County
Effective Date: 03/2013
Last Update: 05/15/2015
Update Cycle: As needed
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A line feature class derived from our main Miami-Dade County's Streets Feature Class. Maintenance Code -- Definition =============================AP - Airport/Port MaintainedCC - County/City MaintainedCI - City MaintainedCM - County Maintained Within CityCO - County MaintainedPC - Private CityPR - Private ROW CountySR - State MaintainedU - UnknownUR - Undeveloped ROWUpdated: Weekly-Sat The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A polygon feature class of the City of North Miami Council District boundaries. The purpose of the district layer is to divide voters by City of North Miami Council Districts. It is used in general analysis, as well as for mapping purposes.Updated: Every 10 yrs The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Facebook
TwitterTracking response rates of Coral Gables residents across the city and by their census tract.Statistic show the ongoing, cumulative response rates (CRR) for place (cities) in Miami Dade County; and, for census tracts in and around Coral Gables.The information is collected through the 2020 Census online resources and made into 2 map layers. One layer shows CRR for cities in Miami Dade. The other layer shows CRR for census tracts in and around Coral Gables. Click on a city or tract will show a popup that shows the name and response rate for the object.Direct any question to the Information Technology GIS section itsd@coralgables.com; or by calling the IT Help Desk at 305 569 2448 (HELP).
Facebook
TwitterCities in the U.S. are getting hotter, and that is causing significant health risks, especially to minorities, the elderly, and impoverished. There is significant spatial variation in temperature across a city due to changes in the landscape (elevation, tree cover, development, etc). NOAA has been engaged in a nationwide effort with CAPA Strategies to use a combination of Sentinel-2 satellite data along with temperature readings recorded from car- and bike-mounted sensors to generate detailed maps of the urban areas most impacted by heat. These measurements have been combined into single raster layers for morning, afternoon, and evening temperatures. As of 2020, 27 cities (26 in the U.S) have been mapped; a total of 50 cities will be mapped by the end of 2021. This layer shows the census tract (neighborhood) averages for those temperatures, along with additional information calculated for each neighborhood including:Temperature anomaly (neighborhood temperature compared to the citywide average based on the CAPA data)Impervious surfaceTree coverDemographicsTotal populationPopulation <5Population >65MinorityMedian incomePovertyCombining these different types of information can help planners identify areas at risk and help to develop mitigation and resilience plans to improve urban living conditions. More information about the campaign can be found in this Story Map by NOAA.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A polygon feature class of the 2010 Census Block Pop Demographic boundaries within Miami-Dade County. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces. The boundaries have been aligned to Miami-Dade County base data where they have been found to NOT be within +/- 10 ft. Population and demographic figures have been appended to the end of the feature classes attribute table.Updated: Every 10 yrs The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
A polygon feature class of municipal boundaries within Miami-Dade County, data includes the municipal codes and names.Updated: As Needed The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere