A polygon feature class of the Miami-Dade County outer boundaries.Updated: Not Planned The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

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

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 Sewer Line. Export to CAD, GIS, PDF, CSV and access via API.

A line feature class of the Empowerment Zone boundaries within Miami-Dade County, derived from pre-selected U.S. Census Tracts.Updated: Not Planned The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A line feature class of the lots lines conforming the boundaries of the lot polygons in Miami-Dade County.Updated: Weekly-Sat The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A line feature class that represents all drainage features for the Unincorporated Miami-Dade County Service Area (UMSA), which can be represented by lines in a map, are represented in this layer, such as outfalls, culverts, infiltration trenches, ditches in the drainage network. The data was collected through permit files, surveys and тАЬas-builtsтАЭ, representing the best available information for each location at the time the layer was published.Updated: Monthly The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area. This census data layer has been imported into the Miami-Dade County ArcSDE infrastructure and re-projected to: Projected Coordinate System: NAD_1983_StatePlane_Florida_East_FIPS_0901_Feet Projection: Transverse_Mercator False_Easting: 656166.66666667 False_Northing: 0.00000000 Central_Meridian: -81.00000000 Scale_Factor: 0.99994118 Latitude_Of_Origin: 24.33333333 Linear Unit: Foot_US The boundaries have been aligned to Miami-Dade County base data where they have been found to NOT be within +/- 10 ft Population figures have been appended to the end of the feature classes attribute table: Pop2010, HU2010, HISPAN, WHITENH, BLACKNH, AMERINDIANNH, ASIANNH, HAWIANNH, OTHERNH, and MULTIRACE. Definitions can be found in the census documentation.

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, stairways, and winter trails.

A line feature class of the Urban Infill Area lines conforming the boundaries of the Urban Infill Area polygons within Miami-Dade County. Created by the Planning and Zoning Department (1998).Updated: Not Planned The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A line feature class of the Coastal Construction Control line along the shoreline that runs from Golden Beach (Broward County Line) to Key Biscayne.Updated: Not Planned The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A polygon feature class of the Community Development District (CDD) boundaries maintained by the Miami-Dade County Special Taxing District office. CDD's are special taxing districts or local units of special-purpose government. A CDD may charge separate non-ad valorem special assessments for satisfying the debt obligations of the district relating to financing, constructing, maintaining and servicing the district's improvements and/or services.Updated: Weekly-Fri The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A line feature class of Miami-Dade County's Urban Development Boundary(UDB) boundaries. The boundary was adopted by the Board of County Commissioners (BCC) as per recommendation. This boundary identifies the area where urban development may occur through the year 2030. Development orders permitting urban development will generally be approved within the UDB at some time through the year 2030 provided that level-of-service standards for necessary public facilities will be met. Adequate countywide capacity will be maintained within the UDB by increasing development densities or intensities inside the UDB or by expanding the UDB when the need for such change is determined to be necessary through the amendment process.Revisions: Date: November 2021 By: Juan C. Pelaez Reason: The Urban Development Boundary (UDB) is updated as a result of Comprehensive Development Master Plan (CDMP) amendment approvals, and is subject to Interpretation by the Director of the Regulatory and Economic Resources (RER) Department where there are questions pertaining to its alignment.Last updated November 2021. Updated: Annually The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A line feature class of the county flood criteria boundaries within Miami-Dade County. The purpose of the Miami-Dade County Flood Criteria Map is to determine the minimum ground surface elevation of developed properties, crown/grade of roads, and secondary canal banks based on a 10-year, 24-hour storm event, 2060 scenario with SLR, and the minimum top elevation of seawalls, unless higher elevations are required by other regulatory applicable standards. Available for review and comment October 22, 2021 through December 22, 2021.Updated: Every 10 yrs The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

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 filewith no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent dataset, or they can be combined to cover the entire nation. The Area Hydrography Shapefile contains the geometry and attributes of both perennial and intermittent area hydrography features, including ponds, lakes, oceans, swamps (up to the U.S. nautical three-mile limit), glaciers, and the area covered by large rivers, streams, and/or canals that are represented as double-line drainage. Single-line drainage water features can be found in the Linear Hydrography Shapefile (LINEARWATER.shp). Linear water features includes single-line drainage water features and artificial path features, where they exist, that run through double-line drainage features such as rivers, streams, and/or canals, and serve as a linear representation of these features.

A line feature class of the parcel lines conforming the boundaries of the parcel polygons feature class.Updated: Weekly-Sat The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

A polygon feature class of Public Safety Answering Point (PSAP) boundaries within Miami-Dade County, FL.Updated: As Needed The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

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) System (MTS). The MTS 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. Edges refer to the linear topological primitives that make up the MTS. The All Lines shapefile contains linear features such as roads, railroads, and hydrography. Additional attribute data associated with the linear features found in the All Lines shapefile are available in relationship (.dbf) files that users must download separately. The All Lines shapefile contains the geometry and attributes of each topological primitive edge. Each edge has a unique TIGER/Line identifier (TLID) value.

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) System (MTS). The MTS 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 Census Bureau includes landmarks in the MTS for locating special features and to help enumerators during field operations. Some of the more common landmark types include airports, cemeteries, parks, schools, and churches and other religious institutions. The Census Bureau adds landmark features to MTS on an as-needed basis and does not ensure that all instances of a particular feature are included. The presence or absence of a landmark such as a hospital or prison does not mean that the living quarters associated with that landmark were geocoded to that census tabulation block or excluded from the census enumeration. The Area Landmark shapefile does not include military installations or water bodies because they appear in their own separate shapefiles, mil.shp and areawater.shp respectively.