United States Department of Agriculture
Natural Resources Conservation Service		 Missouri Go to Accessibility Information
Skip to Page Content





Posting Data to the Staging Server and Soil Data Mart

The following document requires Adobe Acrobat.

Posting Data to the Staging Server and Soil Data Mart  (PDF, 118 KB)

Communication between the Missouri Digitizing Unit and the responsible state are essential to the success of the Mart, and subsequent progress toward our goals. We have categorized data by:

Version 1.0 SSURGO-tabular data in SSSD format
Version 2.0 SSURGO-tabular data in NASIS format
Version 2.1 SSURGO-tabular data in NASIS format for Warehouse

Below are three scenarios for the categories of data and the process to post data to the Soil Data Mart.

Initial Surveys-newly digitized, not previously SSURGO certified

Missouri DU will:

  1. Send acres by mapunit to the state after the survey has been digitized.
  2. Download a mapunit legend from NASIS to compare to the spatial mapunits, notify the state if discrepancies are found and make changes to the spatial data as needed.
  3. Request feature table, or at least a range of acres for each special feature (i.e. .25 to 5), from the state.
  4. Request metadata from the state.
  5. Upload spatial data and metadata to the staging server after the survey passes the 10% MLRA review, and meets SSURGO standards.
  6. Send an email to the state as a cue to upload the tabular data to the staging server, join the spatial and tabular data, and commit it to the Warehouse.

or

(If the tabular data already exists on the staging server for the survey)
Send an email to the state as a cue to join the spatial and tabular data, and commit the data to the Warehouse.

It is possible to have only spatial data or only tabular data sitting on the staging server for a survey. Only the state can commit the data to the Warehouse once both the spatial and tabular data are uploaded to the staging server.

The State will:

  1. (If the spatial data already exists on the staging server for the survey)
    Upload tabular data to the staging server, join it with the spatial data and commit it to the Warehouse.
  2. (If the spatial data does not exist on the staging server for the survey)
    Upload tabular data to the staging server and notify the DU by email as a cue to upload the spatial data
  3. Notify the DU if any errors occur in the spatial data during the commit process to the Warehouse.

 

"Rearchive" Surveys-SSURGO data already available on NCGC site

Version 1.0 SSURGO updated to Version 2.1 SSURGO

Missouri DU will:

  1. Download a mapunit legend from NASIS to compare to the spatial mapunits, notify the state if discrepancies are found and make changes to the spatial data as needed.
  2. Make spatial edits to the survey if needed: boundaries, mapunits, etc.
  3. Update edgematching to adjacent surveys if needed
  4. Update metadata
  5. Upload spatial data and metadata to the staging server after the survey meets SSURGO standards.
  6. Send an email to the state as a cue to upload the tabular data to the staging server, join the spatial and tabular data, and commit it to the Warehouse.

or

(If the tabular data already exists on the staging server for the survey)
Send an email to the state as a cue to join the spatial and tabular data, and commit the data to the Warehouse.

It is possible to have only spatial data or only tabular data sitting on the staging server for a survey. Only the state can commit the data to the Warehouse once both the spatial and tabular data are uploaded to the staging server.

The State will:

  1. Notify Missouri DU of any spatial edits needed (boundary changes, edgematching, mapunits)
  2. (If the spatial data already exists on the staging server for the survey)
    Upload tabular data to the staging server, join it with the spatial data and commit it to the Warehouse.
  3. (If the spatial data does not exist on the staging server for the survey)
    Upload tabular data to the staging server and notify the DU by email as a cue to upload the spatial data
  4. Notify the DU if any errors occur in the spatial data during the commit process to the Warehouse.

 

Version 2.0 updated to Version 2.1 Surveys-SSURGO already available on NCGC site, but need NASIS update to make available on the Soil Data Mart

Missouri DU will:

  1. Make any updates to spatial data if notified by the state

The State will:

  1. Notify Missouri DU of any spatial edits needed (boundary changes, edgematching, mapunits)
  2. Upload tabular data to the staging server, recall the spatial data, join it with the spatial data and commit it to the Warehouse-no need to notify DU unless spatial edits are needed


Useful Links:

Staging Server

Soil Data Mart

NCGC SSURGO Download Site

< Back to Missouri Regional Soils Digitizing Unit