WMS:GSSHA Join SSURGO Data: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
Line 14: Line 14:
Some SSURGO data may contain hybrid HYDGRP classes, such as "A/B."  Because WMS does not support hybrid HYDGRP fields, the entry will be changed to first group listed.  For example, if the entry is "B/D," WMS will change the entry to "B."
Some SSURGO data may contain hybrid HYDGRP classes, such as "A/B."  Because WMS does not support hybrid HYDGRP fields, the entry will be changed to first group listed.  For example, if the entry is "B/D," WMS will change the entry to "B."


Often there are missing fields in the data.  WMS provides the option to set a default value to be assigned to missing fields to avoid blanks.  You can set these values in the dialog shown below.  
Often there are missing fields in the data.  WMS provides the option to set a default value to be assigned to missing fields to avoid blanks.  A user can set these values in the dialog shown below.  


[[Image:ssurgo.jpg|thumb|none|left|300 px|''Join SSURGO Data'' dialog]]
[[Image:ssurgo.jpg|thumb|none|left|300 px|''Join SSURGO Data'' dialog]]
Line 23: Line 23:
After cleaning and filling the data, the attributes are then matched up with their corresponding MUKEY and joined to the GIS layer.  If more than one entry exists for an MUKEY, the corresponding parameters that occur most frequently are joined to the layer.   
After cleaning and filling the data, the attributes are then matched up with their corresponding MUKEY and joined to the GIS layer.  If more than one entry exists for an MUKEY, the corresponding parameters that occur most frequently are joined to the layer.   


It should be noted that the shapefile's *.dbf file is not changed in this process.  If the shapefile is opened in another WMS project, you will need to select the '''Join SSURGO Data''' command again in order to join the data.
It should be noted that the shapefile's *.dbf file is not changed in this process.  If the shapefile is opened in another WMS project, a user will need to select the '''Join SSURGO Data''' command again in order to join the data.


== Related Topics ==
== Related Topics ==

Revision as of 15:28, 2 September 2014

The *.dbf file associated with SSURGO shapefiles contains the following attributes: AREASYMBOL, SPATIALVER, MUSYM, and MUKEY. In order to join more attributes, which can then be mapped to the soil coverage, you should use the Join SSURGO Data command.

The Join SSURGO Data command opens three *.txt files located in the tabular folder the downloaded SSURGO data: comp.txt, chtextur.txt, and chorizon.txt.


The following data is extracted from the *.txt files:

  • comp.txt: HYDGRP
  • chtextur.txt: TEXTURE
  • chorizon.txt: KSAT, MOISTURE, FIELDCAP, and WILTINGPT.


Clean and Fill Values

Some SSURGO data may contain hybrid HYDGRP classes, such as "A/B." Because WMS does not support hybrid HYDGRP fields, the entry will be changed to first group listed. For example, if the entry is "B/D," WMS will change the entry to "B."

Often there are missing fields in the data. WMS provides the option to set a default value to be assigned to missing fields to avoid blanks. A user can set these values in the dialog shown below.

File:Ssurgo.jpg
Join SSURGO Data dialog


The combo boxes list the soil groups and textures that exist in the SSURGO data and are defaulted to the group and texture that occur most often.

After cleaning and filling the data, the attributes are then matched up with their corresponding MUKEY and joined to the GIS layer. If more than one entry exists for an MUKEY, the corresponding parameters that occur most frequently are joined to the layer.

It should be noted that the shapefile's *.dbf file is not changed in this process. If the shapefile is opened in another WMS project, a user will need to select the Join SSURGO Data command again in order to join the data.

Related Topics