Parent Layer:
Soil Classification
Name: Soil Survey Number
Display Field: AREASYMBOL
Type: Feature Layer
Geometry Type: esriGeometryPolygon
Description: The Order of a soil survey indicates the level of detail and relative intensity of field observation under which the map unit was developed. The order of a survey is commonly reflected in the scale of mapping, but not determined by it. Rather, the order of a survey is determined by the field procedures used to identify soil components and place map unit boundaries, the minimum permissible size of map unit delineation, and the kind of map unit to which soil components are aggregated.
Order 1 - Very intensive. The soils in each delineation are identified by transecting or traversing or even grid mapping. Soil boundaries are observed throughout their length. Remotely sensed data are used as an aid in boundary delineation. Order 1 surveys are made if very detailed information about soils, generally in small areas, is needed for very intensive land uses.
Order 2 - Intensive. The soils in each delineation are identified by field observations and by remotely sensed data. Boundaries are verified at closely spaced intervals. Order 2 surveys are made if detailed information about soil resources is needed to make predictions of soil suitability and treatment needs for intensive land uses. The information can be used in planning for general agriculture, construction, urban development, and similar uses that require precise knowledge of the soils and their variability.
Order 3 - Extensive. Soil boundaries are plotted by observation and interpretation of remotely sensed data. They are verified by traversing representative areas and by some transects. Order 3 surveys are made where land uses do not require precise knowledge of small areas or detailed soil information. The survey areas are commonly dominated by a single land use and have few subordinate uses. The soil information can be used in planning for range, forest, and recreational areas and in community planning.
Order 4 - Extensive. Soil boundaries are plotted by interpretation of remotely sensed data. They are verified by traversing representative areas and by some transects. Order 4 surveys are made if general soil information is needed about the potential and general management of land for extensive uses. The information can be used in locating, comparing, and selecting suitable areas for major kinds of land use, in regional land use planning, and in selecting areas for more intensive study and investigation.
Order 5 - Very extensive. The soil patterns and composition of map units are determined by mapping representative ideas and like areas by interpretation of remotely sensed data. Soils are verified by some onsite investigation or by traversing. Order 5 surveys are made to collect soil information in very large areas at a level of detail suitable for planning regional land use and interpreting information at a high level of generalization. The primary use of this information is selection of areas for more intensive study.
Some soil survey areas have two or more orders of mapping because they have distinct parts with different needs. For example, one part may be mapped to make predictions related to irrigation and the other may be mapped to make predictions related to range management. For the irrigated part, areas are mapped at the intensity required for an order 2 soil survey. For the rangeland part, areas are mapped as an order 3 survey. Reference:
Soil Science Division Staff. 2017. Soil survey manual. Chapter 4. C. Ditzler, K. Scheffe, and H.C. Monger (eds.). USDA Handbook 18. Government Printing Office, Washington, D.C.
Aggregation Method: No Aggregation Necessary; Tiebreak rule: Higher
Component Percent Cutoff: 0%
GeoDatabase: C:\Users\nina.mauney\Desktop\AACD\BigSandy_NRCD\Data\soils_GSSURGO_az_3816689_01\soils\gssurgo_g_az\gSSURGO_AZ.gdb
Featurelayer: MUPOLYGON
Rating Table: SDV_OrderSsa
Layer File: C:\Users\nina.mauney\Desktop\AACD\BigSandy_NRCD\Data\soils_GSSURGO_az_3816689_01\soils\gssurgo_g_az\Order_of_Soil_Survey.lyr
Copyright Text: Created by Nina Mauney on 2020-08-24 using script gSSURGO_CreateSoilMaps.py
Default Visibility: false
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 0
Max Scale: 0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: true
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
XMin: -1.28005437125E7
YMin: 3675985.7742
XMax: -1.20527425889E7
YMax: 4650198.256200001
Spatial Reference: 102100
(3857)
Drawing Info:
Renderer:
Simple Renderer:
Symbol: Style: esriSFSSolid
Color: [255, 235, 175, 0]
Outline:
Style: esriSLSSolid
Color: [255, 167, 127, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: [smunit]
Use Coded Values: true
Symbol:
Color: [255, 255, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: center
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 14
Font Family: Arial
Font Style: normal
Font Weight: bold
Font Decoration: none
Min. Scale: 100000.0
Max. Scale: 0.0
Advanced Query Capabilities:
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
HasZ: false
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
-
OBJECTID
(
type: esriFieldTypeOID, alias: OBJECTID
)
-
Shape
(
type: esriFieldTypeGeometry, alias: Shape
)
-
AREASYMBOL
(
type: esriFieldTypeString, alias: AREASYMBOL, length: 20
)
-
SPATIALVER
(
type: esriFieldTypeDouble, alias: SPATIALVER
)
-
MUSYM
(
type: esriFieldTypeString, alias: MUSYM, length: 6
)
-
MUKEY
(
type: esriFieldTypeString, alias: MUKEY, length: 30
)
-
musym_1
(
type: esriFieldTypeString, alias: Mapunit Symbol, length: 6
)
-
Shape_Length
(
type: esriFieldTypeDouble, alias: Shape_Length
)
-
Shape_Area
(
type: esriFieldTypeDouble, alias: Shape_Area
)
-
ECOSITEID_DCP
(
type: esriFieldTypeString, alias: ECOSITEID_DCP, length: 50
)
-
muname
(
type: esriFieldTypeString, alias: Mapunit Name, length: 240
)
-
smunit
(
type: esriFieldTypeString, alias: smunit, length: 30
)
-
smunitname
(
type: esriFieldTypeString, alias: smunitname, length: 270
)
Supported Operations:
Query
Generate Renderer
Return Updates
Iteminfo
Thumbnail
Metadata