This data set consists of a digital map of the extent of fields and a summary of the irrigated acreage for the period between January 2019 and February 2021 compiled for Broward and Miami-Dade Counties, Florida. Attributes for each field include a general or specific crop type, irrigation system, and primary water source for irrigation.

Bare-earth 5-foot DEM as 32-bit floating point raster format in ArcGIS GRID Raster format in compliance with USGS LIDAR Base Specifications: georeferencing information, delivered without overlap and with no edge artifacts or mismatched, “NODATA” value for void areas, bridges removed from the surface, etc. Download 5ft DEM / Download DEM Metadata

The Commission Districts dataset is a spatial data representation of the five districts of City of Miami, originally created by the City Clerk's Office, City of Miami. Each district is administered by a commissioner, which is elected every four years. The data layer is maintained and managed by the GIS Team of the City of Miami.

A polygon feature class of Right Of Way (ROW) boundaries within Miami-Dade County. This data was derived from the Lot layer and is maintain in the Esri Parcel Fabric (PF) data model.Updated: Not Planned The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

Geospatial data about Miami-Dade County, Florida WaterLine. Export to CAD, GIS, PDF, CSV and access via API.

Geospatial data about Miami-Dade County, Florida Property Boundaries. Export to CAD, GIS, PDF, CSV and access via API.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

Geospatial data about Miami-Dade County, Florida County Park Boundary. Export to CAD, GIS, PDF, CSV and access via API.

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

Geospatial data about Miami-Dade County, Florida Subdivisions. Export to CAD, GIS, PDF, CSV and access via API.

The City Boundary layer, originally created by the Office of City Clerk, bounds the City of Miami to its current limits. The layer is edited and maintained by GIS Team of the City. This layer is a representation of the official City of Miami Boundary Legal Description based on the legal survey of the city, but it is not to be construed as an official survey of the city boundary. It may be used for general reference purposes but not in place of an official survey or other legal instrument.

Geospatial data about Miami-Dade County, Florida Environmentally Endangered Lands (EEL). Export to CAD, GIS, PDF, CSV and access via API.

The ATLSS Data Visualization System was designed to make it simple to view and analyze Spatially-Explicit Species Index (SESI) models.

Miami Dade WASD Water Map Book (Atlas pages) Index layer

Geospatial data about Miami-Dade County, Florida Storm Drains. Export to CAD, GIS, PDF, CSV and access via API.

These data were automated to provide an accurate high-resolution historical shoreline of Miami, Florida suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://www.fisheries.noaa.gov/inport/item/39808

Geospatial data about Miami-Dade County, Florida Natural Forest Communities (NFC). Export to CAD, GIS, PDF, CSV and access via API.

Statistical analyses and maps representing mean, high, and low water-level conditions in the surface water and groundwater of Miami-Dade County were made by the U.S. Geological Survey, in cooperation with the Miami-Dade County Department of Regulatory and Economic Resources, to help inform decisions necessary for urban planning and development. Sixteen maps were created that show contours of (1) the mean of daily water levels at each site during October and May for the 2000-2009 water years; (2) the 25th, 50th, and 75th percentiles of the daily water levels at each site during October and May and for all months during 2000-2009; and (3) the differences between mean October and May water levels, as well as the differences in the percentiles of water levels for all months, between 1990-1999 and 2000-2009. The 80th, 90th, and 96th percentiles of the annual maximums of daily groundwater levels during 1974-2009 (a 35-year period) were computed to provide an indication of unusually high groundwater-level conditions. These maps and statistics provide a generalized understanding of the variations of water levels in the aquifer, rather than a survey of concurrent water levels. Water-level measurements from 473 sites in Miami-Dade County and surrounding counties were analyzed to generate statistical analyses. The monitored water levels included surface-water levels in canals and wetland areas and groundwater levels in the Biscayne aquifer. Maps were created by importing site coordinates, summary water-level statistics, and completeness of record statistics into a geographic information system, and by interpolating between water levels at monitoring sites in the canals and water levels along the coastline. Raster surfaces were created from these data by using the triangular irregular network interpolation method. The raster surfaces were contoured by using geographic information system software. These contours were imprecise in some areas because the software could not fully evaluate the hydrology given available information; therefore, contours were manually modified where necessary. The ability to evaluate differences in water levels between 1990-1999 and 2000-2009 is limited in some areas because most of the monitoring sites did not have 80 percent complete records for one or both of these periods. The quality of the analyses was limited by (1) deficiencies in spatial coverage; (2) the combination of pre- and post-construction water levels in areas where canals, levees, retention basins, detention basins, or water-control structures were installed or removed; (3) an inability to address the potential effects of the vertical hydraulic head gradient on water levels in wells of different depths; and (4) an inability to correct for the differences between daily water-level statistics. Contours are dashed in areas where the locations of contours have been approximated because of the uncertainty caused by these limitations. Although the ability of the maps to depict differences in water levels between 1990-1999 and 2000-2009 was limited by missing data, results indicate that near the coast water levels were generally higher in May during 2000-2009 than during 1990-1999; and that inland water levels were generally lower during 2000-2009 than during 1990-1999. Generally, the 25th, 50th, and 75th percentiles of water levels from all months were also higher near the coast and lower inland during 2000–2009 than during 1990-1999. Mean October water levels during 2000-2009 were generally higher than during 1990-1999 in much of western Miami-Dade County, but were lower in a large part of eastern Miami-Dade County.

A polygon feature class of properties and other areas that may contain wetlands within Miami-Dade County.Updated: As Needed The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere