{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "Dataset Origin: Originally a copy of GISLIB.BND_500K_WMDS.\nModifications: NWF, SR, and SJR records were replaced with reprojected 24K extents (GISLIB.BND_024K_NWFWMD_EXT, GISLIB.BND_024K_SRWMD_EXT, GISLIB.BND_024K_SJRWMD_EXT) with buffered gulf or ocean extents.\nPurpose: For use in EReg/EPermitting applications, The procedures in the SJR.GIS package are using Rest services which are listed in the table SJR.GIS_SRVC_URL on a given database. This dataset will be used as in put to that package.\nTopology: Built to evaluate and correct gaps/overlaps using best judgement. References included Spring 2025 statewide parcels, detailed county boundaries, Esri basemap imagery, and embedded county boundaries. Gaps/overlaps between SWF and SF were not addressed.\n\nFrom GISLIB.BND_500K_WMDS\nThis feature class has an st_geometry SRID value of 3. It was specifically setup with this SRID to work with st_geometry queries in existing SJRWMD applications. A bug in ArcSDE 10.1 requires the exact SRID value of the feature in the SQL query to be used in these queries, otherwise Esri states that unknown results can occur. Esri will be working on a fix such that any SRID value of the same coordinate system will work. edean 09/11/2013", "description": "

Topologically modified dataset specifically requested by OIT-AppDev to address EReg\\EPermitting app issues where point features fell outside of the district extent, along the gulf or ocean. The buffered versions of these wmd boundaries individually worked correctly. However, a consolidated statewide dataset is needed as a REST service input. jstokes, 2025.03.10<\/SPAN><\/P><\/DIV><\/DIV><\/DIV>", "summary": "Dataset Origin: Originally a copy of GISLIB.BND_500K_WMDS.\nModifications: NWF, SR, and SJR records were replaced with reprojected 24K extents (GISLIB.BND_024K_NWFWMD_EXT, GISLIB.BND_024K_SRWMD_EXT, GISLIB.BND_024K_SJRWMD_EXT) with buffered gulf or ocean extents.\nPurpose: For use in EReg/EPermitting applications, The procedures in the SJR.GIS package are using Rest services which are listed in the table SJR.GIS_SRVC_URL on a given database. This dataset will be used as in put to that package.\nTopology: Built to evaluate and correct gaps/overlaps using best judgement. References included Spring 2025 statewide parcels, detailed county boundaries, Esri basemap imagery, and embedded county boundaries. Gaps/overlaps between SWF and SF were not addressed.\n\nFrom GISLIB.BND_500K_WMDS\nThis feature class has an st_geometry SRID value of 3. It was specifically setup with this SRID to work with st_geometry queries in existing SJRWMD applications. A bug in ArcSDE 10.1 requires the exact SRID value of the feature in the SQL query to be used in these queries, otherwise Esri states that unknown results can occur. Esri will be working on a fix such that any SRID value of the same coordinate system will work. edean 09/11/2013", "title": "GISLIB.BND_500K_WMDS_EXT", "tags": [ "EReg", "EPermitting" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 150000000, "maxScale": 5000, "spatialReference": "", "accessInformation": "The St Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided as is. Further documentation of this data can be obtained by contacting: GIS_Support@sjrwmd.com or St Johns River Water Management District, c/o GIS, PO Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500. Complete liability disclaimer information available at https://www.sjrwmd.com/disclaimer.html.", "licenseInfo": "" }