Citation: Miami-Dade County, Florida (2018). Miami-Dade Qualified Opportunity Zones [gis dataset]. Miami-Dade County. https://gis-mdc.opendata.arcgis.com/datasets/MDC::qualified-opportunity-zones/about. last updated: 2023-03-17 (update frequency: As Needed). Abstract: A polygon feature class with all population census tracts designated as Qualified Opportunity Zones (QOZs) as well as all population census tracts originally eligible for designation as a QOZ for purposes of 1400Z1 and 1400Z2 of the Internal Revenue Code (the Code). To identify areas designated as Qualified Opportunity Zones (QOZs). An Opportunity Zone is an economically-distressed community where new investments, under certain conditions, may be eligible for preferential tax treatment. Key words: Florida, Miami-Dade County, MDC, Property, Planning, Regulation, Qualified Opportunity Zone, Development, Population, Infrastructure Open Geospatial Consortium Standards: dynamic vector tiles | | WMS (coming soon) | WFS (coming soon) ESRI Standards: ArcGIS MapServer | ArcGIS FeatureServer | Open in ArcGIS Portal for GDSC Analytical Functions: gdsc_nearest_neighbor(table=mdc_qualified_opportunity_zones,lat=25.718,lng=-80.279,id=namelsad10) ETL documentation

ETL for mdc_qualified_opportunity_zones

######### # 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_qualified_opportunity_zones/{download,etl} && cd /data/mdc_qualified_opportunity_zones # 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_qualified_opportunity_zones.json 'https://services.arcgis.com/8Pc9XBTAsYuxx9Ny/arcgis/rest/services/QualifiedOpportunityZones_gdb/FeatureServer/0/query?outFields=*&where=1%3D1&outSR=4326&f=geojson' # 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_qualified_opportunity_zones.json # load into postGIS with: ogr2ogr -lco GEOMETRY_NAME=geom -f PostgreSQL PG:"" download/mdc_qualified_opportunity_zones.json -nlt multipolygon -nln mdc_qualified_opportunity_zones ######### # Step 2 - SQL script (pseudo code): #### # remove duplicate points and make geometries valid: UPDATE mdc_qualified_opportunity_zones SET geom=ST_MakeValid(ST_RemoveRepeatedPoints(geom)); # add local geometry column and reproject existing geometries into local EPSG: SELECT AddGeometryColumn ( 'mdc_qualified_opportunity_zones', 'geom_local', 2236, 'multipolygon', 2 ); UPDATE mdc_qualified_opportunity_zones SET geom_local=ST_MakeValid(ST_RemoveRepeatedPoints(ST_Transform(ST_Multi(geom), 2236))); CREATE INDEX mdc_qualified_opportunity_zones_geom_local_idx ON mdc_qualified_opportunity_zones USING GIST (geom_local); NOTIFY pgrst, 'reload schema'; # Move into corrrect directory and create derivative directory in data package on osgeo cd /data/mdc_qualified_opportunity_zones/ mkdir -p derived # Move into correct directory cd /data/mdc_qualified_opportunity_zones/ # Create pg_dump of table SQL in derivate directory on postgis. pg_dump -h postgis-2k0dg34uilke6ctl -t mdc_qualified_opportunity_zones > derived/mdc_qualified_opportunity_zones.sql # Create downloadable tarfile of SQL in derivative directory on postgis rm -f derived/mdc_qualified_opportunity_zones.sql.tar.gz tar -czf derived/mdc_qualified_opportunity_zones.sql.tar.gz meta_dcat_mdc_qualified_opportunity_zones.json -C derived mdc_qualified_opportunity_zones.sql