UM Geospatial Digital Special Collections

Citation: Miami Dade County (2019). Miami-Dade Property Boundary [gis dataset]. Miami Dade County. https://gis-mdc.opendata.arcgis.com/datasets/MDC::property-boundary-view/about. last updated: 2024-10-28 (update frequency: As Needed). Abstract: A polygon feature class of all properties within Miami-Dade County. A polygon feature class of all properties within Miami-Dade County that includes property appraiser data. Updated: Weekly-Sat The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_Sphere Projection: Mercator_Auxiliary_Sphere Key words: Florida, Miami-Dade County, MDC, Geography, Property, Housing, Parcels, Population, Infrastructure Open Geospatial Consortium Standards: dynamic vector tiles | | WMS (coming soon) | WFS (coming soon) Analytical Functions: gdsc_get_attributes(tablename=mdc_property_boundary,lat=25.718,lng=-80.279,identifier=folio,attrs=[folio,ttrrss,x_coord,y_coord,true_site_addr,true_site_unit,true_site_city,true_site_zip_code,true_mailing_addr1,true_mailing_addr2,true_mailing_addr3,true_mailing_city,true_mailing_state,true_mailing_zip_code,true_mailing_country,true_owner1,true_owner2,true_owner3,condo_flag,parent_folio,dor_code_cur,dor_desc,subdivision,bedroom_count,bathroom_count,half_bathroom_count,floor_count,unit_count,building_actual_area,building_heated_area,lot_size,year_built,assessment_year_cur,assessed_val_cur,dos_1,price_1,legal],normal='') ETL documentation

ETL for mdc_property_boundary

######### # GDSC ETL is performed in two steps: shell script to ETL data into postgres # and then additional transformations with SQL in postGIS (if needed). #### ######### # Step 1 - bash script (pseudo code) #### # create directory structure and move into it mkdir -p /data/mdc_property_boundary/{download,etl} && cd /data/mdc_property_boundary # set update flag based on last update and update frequency do_update=0 if date() < last_update + update_frequency else do_update = 1 # download if update flag is set: if do_update == 1 then wget -O download/mdc_property_boundary.json 'https://opendata.arcgis.com/api/v3/datasets/ed0468f5e579464b84727a4ab614fd40_0/downloads/data?format=geojson&spatialRefId=4326&where=1%3D1' # replace column names Shape__Length and Shape__Area to avoid conflict when # providing as service on ArcServer. sed -i 's/Shape__Length/shape_length/gI; s/Shape__Area/shape_area/gI' download/mdc_property_boundary.json # load into postGIS with: ogr2ogr -lco GEOMETRY_NAME=geom -f PostgreSQL PG:"" download/mdc_property_boundary.json -nlt multipolygon -nln mdc_property_boundary ######### # Step 2 - SQL script (pseudo code): #### # remove duplicate points and make geometries valid: UPDATE mdc_property_boundary SET geom=ST_MakeValid(ST_RemoveRepeatedPoints(geom));" # add local geometry column and reproject existing geometries into local EPSG: SELECT AddGeometryColumn ( 'mdc_property_boundary', 'geom_local',2236,'multipolygon',2 ); UPDATE mdc_property_boundary SET geom_local=ST_MakeValid(ST_RemoveRepeatedPoints(ST_Transform(ST_Multi(geom),2236))); CREATE INDEX mdc_property_boundary_geom_local_idx ON mdc_property_boundary USING GIST (geom_local); NOTIFY pgrst, 'reload schema';"