{ "currentVersion": 11.2, "cimVersion": "3.2.0", "serviceDescription": "

SAND_ILITH_PTS_IN is a point shapefile that shows total thickness of sand, as derived from logs of water wells in the state of Indiana. (It presents the source data in a shapefile format that was used to create a grid named \"SAND_ILITH_IN.\") The data were obtained from the iLITH Database of the Indiana Geological Survey. The following explanation of the iLITH Database appears in Open-File Study 00-8 of the Indiana Geological Survey: \"iLITH is a Microsoft Access database containing GIS capabilities that allows users to interact with a portion of the Indiana Department of Natural Resources (IDNR) Water-Well Record Database. iLITH differs from the IDNR database in that lithologic descriptions and drilling contractor names have been standardized, locational information for ~104,000 water-well logs has been verified, and the spatial information in the database has been standardized for use with USGS digital elevation data and US Census Bureau Tiger data. The iLITH graphical interface facilitates efficient interaction between the user and the database.\" Using Microsoft Access, queries were constructed that summed the total thickness of sand and gravel units for each well. Units with the following designations were included in the summation: \"sand,\" \"sand and clay,\" \"sand and gravel,\" \"sand with clay,\" \"sand with clay streaks,\" \"sand with gravel,\" \"silt and sand,\" \"gravel,\" \"gravel and clay,\" \"gravel and stone,\" \"gravel with boulders,\" \"gravel with clay,\" \"gravel with clay streaks,\" and \"gravel with sand.\" Some inconsistencies in the database were eliminated. The resulting table was then exported from Microsoft Access and imported into ESRI ArcView 3.2 to construct a point shapefile.<\/SPAN><\/P><\/DIV><\/DIV>", "hasVersionedData": false, "hasArchivedData": false, "hasBranchVersionedData": false, "supportsDisconnectedEditing": false, "supportsDatumTransformation": true, "supportsReturnServiceEditsOption": true, "returnServiceEditsHaveSR": true, "supportsQueryDataElements": true, "datesInUnknownTimezone": false, "supportsRelationshipsResource": true, "syncEnabled": false, "supportedExportFormats": "sqlite,filegdb,shapefile,csv,geojson", "extractChangesCapabilities": { "supportsReturnIdsOnly": false, "supportsReturnExtentOnly": false, "supportsReturnAttachments": false, "supportsLayerQueries": false, "supportsGeometry": false, "supportsFeatureReturn": false, "supportsReturnHasGeometryUpdates": false, "supportsFieldsToCompare": false, "supportsServerGens": false }, "supportedQueryFormats": "JSON", "maxRecordCount": 2000, "maxRecordCountFactor": 1, "capabilities": "Query,Extract", "description": "

SAND_ILITH_PTS_IN is a point shapefile that shows total thickness of sand, as derived from logs of water wells in the state of Indiana. (It presents the source data in a shapefile format that was used to create a grid named \"SAND_ILITH_IN.\") The data were obtained from the iLITH Database of the Indiana Geological Survey. The following explanation of the iLITH Database appears in Open-File Study 00-8 of the Indiana Geological Survey: \"iLITH is a Microsoft Access database containing GIS capabilities that allows users to interact with a portion of the Indiana Department of Natural Resources (IDNR) Water-Well Record Database. iLITH differs from the IDNR database in that lithologic descriptions and drilling contractor names have been standardized, locational information for ~104,000 water-well logs has been verified, and the spatial information in the database has been standardized for use with USGS digital elevation data and US Census Bureau Tiger data. The iLITH graphical interface facilitates efficient interaction between the user and the database.\" Using Microsoft Access, queries were constructed that summed the total thickness of sand and gravel units for each well. Units with the following designations were included in the summation: \"sand,\" \"sand and clay,\" \"sand and gravel,\" \"sand with clay,\" \"sand with clay streaks,\" \"sand with gravel,\" \"silt and sand,\" \"gravel,\" \"gravel and clay,\" \"gravel and stone,\" \"gravel with boulders,\" \"gravel with clay,\" \"gravel with clay streaks,\" and \"gravel with sand.\" Some inconsistencies in the database were eliminated. The resulting table was then exported from Microsoft Access and imported into ESRI ArcView 3.2 to construct a point shapefile.<\/SPAN><\/P><\/DIV><\/DIV>", "copyrightText": "", "advancedEditingCapabilities": { "supportsSplit": false, "supportsReturnServiceEditsInSourceSR": true, "supportsAsyncApplyEdits": true, "supportsApplyEditsbyUploadID": true, "supportedApplyEditsUploadIDFormats": "JSON", "supportsMultipatchOptionForServiceEdits": true, "supportedApplyEditsOptions": {"supportedEditingOptions": 0} }, "spatialReference": { "wkid": 102100, "latestWkid": 3857, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -20037700, "falseY": -30241100, "xyUnits": 10000, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 }, "initialExtent": { "xmin": -1.0077023649139253E7, "ymin": 4518733.35642322, "xmax": -9161630.012760745, "ymax": 5154142.53307678, "spatialReference": { "wkid": 102100, "latestWkid": 3857, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -20037700, "falseY": -30241100, "xyUnits": 10000, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "fullExtent": { "xmin": -9802392.349, "ymin": 4550442.3364999965, "xmax": -9438602.2889, "ymax": 5125081.3298999965, "spatialReference": { "wkid": 102100, "latestWkid": 3857, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -20037700, "falseY": -30241100, "xyUnits": 10000, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "allowGeometryUpdates": true, "allowTrueCurvesUpdates": true, "onlyAllowTrueCurveUpdatesByTrueCurveClients": true, "supportsApplyEditsWithGlobalIds": false, "supportsTrueCurve": true, "units": "esriMeters", "documentInfo": { "Title": "C:\\Users\\dbissey\\Desktop\\IndianaMapDataShare\\IndianaMapDataShare.aprx", "Author": "", "Comments": "", "Subject": "", "Category": "", "Keywords": "geoscientificInformation,Indiana Geological Survey,IGS,Indiana Department of Natural Resources,IDNR,Indiana Department of Transportation,INDOT,water well,sand,gravel,sand and gravel thickness,iLITH Database,surficial geology,hydrogeology,water supply,Indiana,Adams County,Allen County,Bartholomew County,Benton County,Blackford County,Boone County,Brown County,Carroll County,Cass County,Clark County,Clay County,Clinton County,Crawford County,Daviess County,Dearborn County,Decatur County,DeKalb County,Delaware County,Dubois County,Elkhart County,Fayette County,Floyd County,Fountain County,Franklin County,Fulton County,Gibson County,Grant County,Greene County,Hamilton County,Hancock County,Harrison County,Hendricks County,Henry County,Howard County,Huntington County,Jackson County,Jasper County,Jay County,Jefferson County,Jennings County,Johnson County,Knox County,Kosciusko County,Lagrange County,Lake County,LaPorte County,Lawrence County,Madison County,Marion County,Marshall County,Martin County,Miami County,Monroe County,Montgomery County,Morgan County,Newton County,Noble County,Ohio County,Orange County,Owen County,Parke County,Perry County,Pike County,Porter County,Posey County,Pulaski County,Putnam County,Randolph County,Ripley County,Rush County,Scott County,Shelby County,Spencer County,Starke County,Steuben County,St Joseph County,Sullivan County,Switzerland County,Tippecanoe County,Tipton County,Union County,Vanderburgh County,Vermillion County,Vigo County,Wabash County,Warren County,Warrick County,Washington County,Wayne County,Wells County,White County,Whitley County" }, "supportsQueryDomains": true, "supportsQueryContingentValues": true, "layers": [ { "id": 106, "name": "Surficial_Sand_Thickness_Points", "parentLayerId": -1, "defaultVisibility": true, "subLayerIds": null, "minScale": 0, "maxScale": 0, "type": "Feature Layer", "geometryType": "esriGeometryPoint" } ], "tables": [], "relationships": [], "enableZDefaults": false, "allowUpdateWithoutMValues": false, "supportsVCSProjection": true, "datumTransformations": [ { "geoTransforms": [ { "wkid": 108190, "latestWkid": 108190, "transformForward": false, "name": "WGS_1984_(ITRF00)_To_NAD_1983" } ] }, { "geoTransforms": [ { "wkid": 108190, "latestWkid": 108190, "transformForward": true, "name": "WGS_1984_(ITRF00)_To_NAD_1983" } ] }, { "geoTransforms": [ { "wkid": 108363, "latestWkid": 108363, "transformForward": false, "name": "WGS_1984_(ITRF08)_To_NAD_1983_2011" } ] }, { "geoTransforms": [ { "wkid": 108363, "latestWkid": 108363, "transformForward": true, "name": "WGS_1984_(ITRF08)_To_NAD_1983_2011" } ] } ], "referenceScale": 0, "serviceItemId": "ea45de1b42084563864553746e859eac" }