NASIS Mapunit History Text Notes Legend Mapunit Mapunit History

Map Unit Text Notes Legend Map Unit Mapunit History Jamie Kienzle, Grant County Area, Oregon (GCAO)

The palest ink is better than the best memory. Chinese Proverb

“Documentation is like chocolate or cold beer: when it is good, it is very, very good; and when it is bad, it is better than nothing.” Dick Brandon quotes

Where’s the old SS Records? Thrown out in moves, burned up??

Stored in the work truck? Or hidden like a mushroom?

Where’s the old SS Records? Stored in old file cabinets, Where?? Thrown out by other disciplines, the Soils data is now on the internet, so the old map unit documents must no longer be needed! They’re taking up too much space!???

Save the documentation in NASIS for Future users! Mapunit History Mapunit Text Profiles in Pedon

Legend Master Mapunit History can only be entered or edited by the legend master. Thus, the project leader (or others with legend permissions) have to enter the data! It will be important for project members to review the Mapunit History report for map units that they have mapped.

Mapunit History is a way to: Document all review decisions Document when field map unit symbols were first used—the mapping season year Document when field symbols are combined Document join map units—joining with other correlated soil surveys

Mapunit History is a way to: Document---map unit changes and why. Examples: –Map unit slope change, from additional mapping and/or transects –One component correlated to another series –Component order changed, from additional transects –Changes resulting from various correlation events –Combined symbols, minimum acreage –Document map unit changes in an update survey

Sources of Information Previous Progress Field Review Reports Field mapping notes Surveyor’s memory (But some information could now be gone with a retirement!!) Correlation documents Reference lab sample profiles MO official series file folders Documentation for Progress Field Reviews

Grant County Area, Oregon-- Example, Legend changes for the Progress Review with the reasons for all changes.

After Data entry, two Mapunit History Reports displays the information.

CORR- NASIS Mapunit History Report Local, MLRA01_Office

CORR - Mapunit History Text Report by date Local, MLRA01_Office

NASIS Report by date Local, MLRA01_Office

Entering Data

Choices--Correlation Kind

Choice list – Correlation Kind Join Statement Name Change Status change – added Status change – disapproved Status change – dropped/combined Status change – reinstated Symbol change

Correlation Event Choices

Choice – Correlation Event Correlation amendment Correlation team meeting Final correlation Final field review Initial field review Progress field review Technical assist

Correlation Example—click text field then Zoom to open; Or double click on text.

Correlation Example; the Text field shown; Correlation Event: Final Correlation; Kind: Name change—slight map unit name change at the interim correlation.

Example of a join statement, Joining with another soil survey; in this case, along the Grant/Harney match.

This is an example of map unit History from a survey update. The original map unit has been modified and the land use has changed.

Example of a combined symbol; officially approved at the Progress Field Review.

This keeps a record of all previously used symbols. Thus, hopefully, there will be no surprise (unknown) symbols on the digital maps!!

Map Unit History Adding past information---Tips –One of the NASIS Reports loads by date. –When adding a field (for data entry), the current date is automatically entered. Thus, change the date first to an earlier date or the date of the event, like a Progress Field Review date, etc. –Otherwise, the report cannot use the date to separate out and print the specific event.

Mapunit History was opened (insert or F8) 01/03/2007 and that date was automatically entered in Date.

Use Copy and Paste For example, use a generic statement for joins or final correlation events. Then copy the information into the affected map units. That saves typing the same statement repeatedly, but it captures the effect of the event and the date for each map unit.

Example of a join statement-- Joining with a correlated SS. This same statement was copied and pasted into all the same join map units.

Report Example-- Report-- Mapunit History Text Notes by date range.

Report Example—All Events and Kinds Selected, You can select from one, up to all the Correlation Events and Correlation Kinds

Report Result: Date range selected to capture all additions and changes for A report like this is useful for a Progress Review.

Those who live in glass houses shouldn’t throw stones!

In other words, is your Soil Survey map unit information saved for the future?