Layers:
-
Class Maximum Value: 10
Label: 0 - 10.00
Description: N/A
Symbol:
-
Class Maximum Value: 20
Label: 10.01 - 20.00
Description: N/A
Symbol:
-
Class Maximum Value: 50
Label: 20.01 - 50.00
Description: N/A
Symbol:
-
Class Maximum Value: 100
Label: 50.01 - 100.00
Description: N/A
Symbol:
-
Class Maximum Value: 500
Label: 100.01 - 500.00
Description: N/A
Symbol:
- OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
- WELLID ( type: esriFieldTypeString, alias: WELLID, length: 20 )
- RECSOURCE ( type: esriFieldTypeString, alias: RECSOURCE, length: 7 )
- DEPTH ( type: esriFieldTypeDouble, alias: DEPTH )
- SAND_THICK ( type: esriFieldTypeSingle, alias: SAND_THICK )
- SHAPE ( type: esriFieldTypeGeometry, alias: Shape )
Layer: Surficial_Sand_Thickness_Points (106)
Name: Surficial_Sand_Thickness_PointsDisplay Field: WELLID
Type: Feature Layer
Geometry Type: esriGeometryPoint
Description: <DIV STYLE="text-align:Left;"><DIV><P><SPAN>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>
Service Item Id: 9853be4c70ab4dbfb2119cadc725371e
Copyright Text:
Default Visibility: true
MaxRecordCount: 2000
MaxSelectionCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 0.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
-
XMin: -9802392.349
YMin: 4550442.3364999965
XMax: -9438602.2889
YMax: 5125081.3298999965
Spatial Reference: 102100 (3857) LatestVCSWkid(0)
Drawing Info:
-
Renderer:
- Class Breaks Renderer:
Field: SAND_THICK
Min. Value: 0.0
ClassBreakInfos:
Labeling Info:
-
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true
HasZ: false
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeNone
Type ID Field: null
Fields: