MLRA REGION 10 NEWSLETTER--JULY 1, 1999 DOGGONE IT! A greeting from a farm dog can be an enjoyable part of field activity. Other times, it is a threat to personal safety. The significance of this treat is illustrated by an estimate from the Centers for Disease Control and Prevention that over 4.7 million people are bitten by dogs each year. Awareness of this danger and a knowledge of how dogs signal their intentions can reduce the number of these incidents. The following is based on an article in the fall 1998 issue of "Family Safety & Health" magazine, anecdote, and personal experience. Look for signs of pets before leaving a vehicle and approaching a rural residence. When a dog is present, be mindful that this is its territory and watch for any warning signs: * growling, snarling, or aggressive barking * shyness or fear, such as when the dog crouches, holds its head low or tail between its legs * fur raised up, ears erect, body stiff, or tail high * an unnaturally still or unresponsive dog * an injured or sick dog If approached by an aggressive dog: * Don't make eye contact or move suddenly. * Face the dog, but keep your head turned away and rely on peripheral vision. * If the dog lunges, don't try to overpower it. If you're holding something, put it in the dog's mouth. If necessary, put up your arm to protect your face. * If you're knocked down by the dog, curl up with face and knees toward the ground (turtle-like) and keep as quiet and motionless as possible until the dog leaves. Submitted with appreciation for all dogs friendly toward soil scientists and cyclists. Submitted by: Mike Walker ######################################################################### MORE ACHING BACKS In many cases back pain is due to problems with other parts of the body, specifically, the stomach and hamstring muscles. By strengthening your abdominal muscles you provide additional skeletal support in addition to your back. In addition, tight hamstring muscles have been shown to create lower back pain. Stretching these muscles helps to relieve lower back pain in these cases. Exercises that truly strengthen the abdominals, and stretch the hamstrings, may be all that is needed to relieve and prevent some types of back pain. I would encourage this approach prior to seeking chiropractic or osteopathic treatment and therapy. You may save yourself time and $$$. Contributed by: Marc Diers ######################################################################### POPULATION OF SURFACE ORGANIC LAYERS IN NASIS This is a letter received from Horace Smith, Director, Soil Survey Division, Washington, DC to State Conservationists and Regional Conservationists concerning Interpretations-National Soil Information System (NASIS). FROM: Horace Smith, Director, Soil Survey Division, Washington, DC Organic layers at the surface are important for some interpretations we make, while for other interpretations we exclude these O horizons. In addition, because of the current interest in carbon sequestration, O horizons have become all the more significant. In response to requests for improved quality of soil interpretations, the National Soil Survey Center is modifying national interpretations to recognize and accommodate organic horizons at the surface. To take advantage of this capability and ensure that we generate accurate interpretive results, O horizons will be entered as separate records in the NASIS horizon table and identified by enter an "O" in the Master horizon designation column. At a minimum, the master horizon designation and the top and bottom Representative Value depths must be populated for O horizons. Top and bottom depths will be measured from the soil surface as specified in the Soil Survey Manual. For those soils without organic layers at the surface, the soil surface is the top of the mineral surface. For those soils with organic surface layers, the soil surface is the top of the uppermost O horizon. The consistent entry of O horizons into NASIS will allow us to identify organic layers for the appropriate interpretations. ######################################################################### NSSC Pangaea RELEASE NOTES The following are changes to NASIS Objects owned by NSSC Pangaea. AREA TYPES contact: Russ Kelsea 402-437-5878 Added: survey area NC605 Changed: counties SD015 and SD017 (acres edited) survey area SD099 (acres edited) QUERIES No changes. REPORTS contact: Russ Kelsea 402-347-5878 or Jim Fortner 402-437-5755 Added: INTERP - Data Export (Component) SSS - NHQ Data Dump SSS - State Cumulative and Fiscal Year Progress UTIL - Area Documentation UTIL - Output from a Property (L-RV-H) UTIL - Output from a Property (RV only) UTIL - NASIS Users Changed: most reports (resequenced) most MANU reports (headers corrected) UTIL - NASIS Groups and Users (DSM indicator added) Data Mapunit: Where Used (new column added to identify legend status) GEOMORPHIC FEATURE TYPES No changes. EDIT SETUPS No changes. INTERPRETATIONS (Rules, Evaluations, Properties) contact: Bob Nielsen 402-437-4149 The following NASIS interpretation templates have been developed and tested by NSSC. They are ready for use and inclusion in soil survey reports and distribution to the public. It should be noted that these interpretations have had limited field testing and the interpretive results should be reviewed carefully before releasing the information to the public. BUILDING SITE DEVELOPMENT DWELLING WITH BASEMENTS DWELLINGS WITHOUT BASEMENTS LAWN, LANDSCAPING, AND GOLF FAIRWAYS LOCAL ROADS AND STREETS SHALLOW EXCAVATIONS SMALL COMMERCIAL BUILDINGS CONSTRUCTION MATERIAL GRAVEL SOURCE ROADFILL SAND SOURCE SOIL RECONSTRUCTION MATERIAL TOPSOIL SANITARY FACILITIES SANITARY LANDFILL (AREA) SEPTIC TANK ABSORPTION FIELDS SEWAGE LAGOONS ######################################################################### COPY & PASTE WITH MULTIPLE NASIS SESSIONS We have been receiving calls from users who want to know how to copy data from nasisclient and paste it into nasis when running nasis_ppp. These same instructions will work with multiple local sessions also. You just have to remember to run "nasis" instead of "nasisclient" The DXPC software changes your DISPLAY variable to hostname:8.0 where the 8 (in this example) is the number that is displayed when you start "nasis_ppp". This is an example of a screen when you start "nasis_ppp": NASIS dxpc script version 1.1b DISPLAY used by DXPC 8 dxpc proxy running in CLIENT mode Enter the following on your local computer to start the server nasis_server 162.79.121.200:8.0 Start your server, then hit to continue These are instructions for using the NASIS copy/paste buttons to copy data from "nasisclient" back to "nasis_ppp". 1. Run "nasis_ppp", make note of the number shown at the end of the "DISPLAY used by DXPC #". Example: DISPLAY used by DXPC 8 2. Before you run "nasisclient", set your display using the number you made note of in step 1. Note in the example below, that we used :8.0 instead of the usual :0.0. Example: setenv DISPLAY 162.79.121.200:8.0 or DISPLAY=162.79.121.200:8.0 export DISPLAY 3. With your display correctly set, run "nasisclient". 4. Now highlight the row of data in nasisclient and click on the copy button. Move your cursor to the table in nasis_ppp and click on the paste button. IMPORTANT!! If you terminate the nasis_ppp that you started first the dxpc process will be shutdown and the second nasis or nasisclient will die a quick death. You MUST EXIT the second nasisclient session first. Please call the Soils Hotline if you need further assistance. Tammy Cheever Soils Hotline 402-437-5379 ######################################################################### HELP ON HELP: NASIS HELP SYSTEM REBUILD Occasionally the find in the OnLine Help does not link to the correct help page. If you experience problems with the find in the OnLine Help your first course of action should be to rebuild the Find index. 1. Click on the Help on the main menu bar. 2. Click on contents. 3. Select the Find tab. 4. Along the right margin are four buttons Clear, Options, Find Now, and Rebuild 5. Click on the Rebuild button. This will rebuild the indexes for the OnLine Help. If you still experience problems after rebuilding the Find indexes please call the Soils Hotline or post the problem on the NASIS problem log. (http://nasis.nrcs.usda.gov/nasis/comment.shtml) Tammy Cheever Soils Hotline email: hotline@nssc.nrcs.usda.gov phone: 402-437-5378 or 5379 ######################################################################### MLRA-11 UPDATE--NEWSLETTER FROM INDIANAPOLIS (by Henry Ferguson, unless otherwise indicated) Summary of the contents: PART I Questions from MLRA 96+94A Steering Committee Meeting(MUG) PART II update on queries and reports. PART III New Edit setup for ownership and vintage of soil surveys PART IV Changes in Backups vs Archives PART V Suggestions for progress reporting in NASIS PART VI List of component choice list for those whose screens do not accommodate the entire list PART VII Reports from NASIS training A. Placement of 1990 Frozen Values in NASIS B. Protocol for making changes to Data Mapunits (DMU's) and Official Soil Series Descriptions (OSD's) common to Region-11 and Adjacent Regions C. Use of Regional, State, MLRA, or County Subset Legends. D. Populating Data Elements - Priority E. Identification Of Type Locations F. Naming of Data Mapunits G. MLRA Legends In Michigan PART VIII Copy and paste from Word to NASIS ********** Part I Questions from MLRA 96+94A Steering Committee Meeting(MUG) Overall question: Which MUG do we use and how many MUG's are there? At any given time there is only ONE mug to be used in MLRA-11. During the development of MUG we may bring in MUG's from other regions as examples. These should be renamed by us and we typically should make some indication that they should not be used. The real "MUG" should say yes in the ready to use column. It should also have the latest date and / or indicate that it is the true "MUG" in the description or name. Why is there only one mug for Region 11 and not one for each state? It was decided by the MUG committee to allow states flexibility in the properties section and to allow thumbnails if they were desired. However, the complexities of programming a MUG make it desirable to have only one program. In this way Bill, Rich, and Myself can pool our talents and time to create one very good product rather than three individual products. So you ask yourself, if there is only one MUG, where is the flexibility? The flexibility is written into the code and can be obtained in one of two ways. By answering yes or no to several upfront questions the MUG product is generated in very different ways. A mini profile description can be included by answering "y" or it can be omitted with a simple "n". Management statements can be included with a "y" or excluded with an "n". Properties of minor components can be included with a "y" or excluded with an "n". Interpretive groups for Michigan can be included with a "y" or excluded with an "n". It is important to check with your state staff to ensure that you populate NASIS properly and answer the questions properly to obtain a product which is satisfactory for your state. What about the flexibility in the properties paragraph which was decided upon by the MUG committee? At this time the "official" mug is not flexible as far as the properties paragraph goes. However this is extremely easy to overcome. We have a short term and a long term solution. In the short term, the solution is as simple as making a copy of the MUG report, putting a # sign in front of the print statement for each property that you wish to exclude, running the report, and then deleting the modified report so we are back to one MUG report. The long term solution would be to ask an upfront question such as, "For which state do you wish to run the mug?" Within the code we would then select the properties section to print based upon pre selected properties for each state. Which reports do we use to publish with and which are the ones to use to edit? There is no single answer to this question. It is important to match the reports that you wish to publish with the prewritten material that you choose to use in your manuscripts. For older surveys the easiest way to obtain a complete set of tables is to do a FOCS download and then generate a complete set of tables out of FOCS. Minor editing may need to be done to a couple of tables if this method is used. In particular the woodland table pulls from hidden tables which can not be edited in the database. To avoid this problem you can choose a local report for woodland which pulls from the forest productivity table. In this case the interps will still have to be edited in word, but the trees to plant and forest productivity columns will be OK. For the most part you do not want to edit any tables if possible. It is best to edit the database and then pull clean tables from the database for publication. How do we set the units of measure for the reports? You do not. Units of measure are built into the reports. Typically 2.54 is the conversion factor used to convert centimeters to inches. If you wish to use different units you need to use a different report. Is there a standard set of reports to use for editing? NO you should not edit reports (other than to prepare for updating the database). Tables for manuscripts should be generated just prior to publication and no editing should be necessary. (by the field) How do we keep inclusions from showing on reports? You can omit minor components by populating the major component flag and running a local query called something link MO-11 load the major components for a survey area. In the future it maybe desirable to have the minor components in your manuscript reports. MLRA-11 has created a complete set of manuscript tables with % of the component next to the component name. These reports have been created in preparation for the time that minor components are included in manuscript reports. Why do similar reports yield totally different information? (See Moisture) This question is unclear. Similarly named reports may yield totally different information because we are in a transition and individuals are trying out different ways of presenting data. This is the case for the soil moisture reports. The same report may yield very different looking results if the selected set is obtained using different options to a query or different queries. For example, the minor components may be included or excluded. The same report may yield very different looking results if the data base has been specifically populated for the report. An example is the mug report. If landscape position is populated it will show up in the report, but if it is not it will not. Effective Cation Exchange Capacity is reported on the Chemical properties report, do we record this and how? There are many blanks in NASIS. Whether or not you populate a given field depends upon the priorities set by your office and the availability of the data. Do not populate a field if you can not support the data or do not know how to populate the field. If you do not want this field in your finished manuscript, we can delete the entire column in word. If you wish to populate a field that you do not understand, contact your correlator for training and guidance. Where is woodland ordination found? It is hidden and will not be used in newer manuscripts. Is there a search capability for the individual fields? There is no way to populate interps or woodland ordination for woodland. Interpretations in the future will be generated from the data. This is one table that must be edited in Word for older documents. It is suggested that you finish up these older manuscripts as soon as possible. We will be deleting this column from future surveys. There is a possibility that interps for woodland may be deleted from future surveys as well. In your state wishes to keep these interps, they will be generated from the interps generator and published in a new report. When it comes time for your manuscript to be published, you should contact your correlator and state office for guidance. Can we have two different set of interps for units using the same pedon? (67B 210B) Ord of 8 for 67, 2 for 210. The answer is yes and no. Ordination symbols can not be edited in the database. Other interps can be edited in the component interpretation and component interpretation restriction tables. You must follow the guidelines for assigning interpretations. If there is a difference in flooding or slope there would obviously be a potential for differences in interps. At what point do we remove the old site index data and use what we are gathering? You do not remove any site index data from the hidden tables, this will be deleted for you. You may start populating the forest productivity table right now, but you must use a local report to print this data in report form. Where is water table data entered or is it a determined factor? Can these values be amended in the MUG printouts? Water table data is entered in the component soil moisture table. Do not modify data in a MUG report. It is important to edit the database. Are we going to use LCC, SMG and Woodland Ordination for all Forest Service Units? Mason did, Iosco didn't. This is a judgment call by the state and local office. If there is little or no cropland in a county, it is common for the LCC to be omitted. The Woodland Ordination is out and will only be used in older manuscripts if the state offices insist. Soil Management Groups are local groupings supported by the state. If the state mandates the local office shall comply. When I try to get MO11 map unit report (like old s5) to run I get an error message Column not in any table in Query. Thank you for bringing this up. As the national NASIS is updated there is a potential for changes in table makeup and field name changes. When this happens the national reports are updated, but local reports may not catch up. In this case there is a National report which takes the place of our local report and I should delete the local report. I am sorry that I can not remember the name of the National report at this time, but I believe that it is one of the last reports with the CORR prefix. PS. If any field people recognize these types of problems, please let me know. I will try to delete obsolete reports as soon as possible (or update them if it is more desirable to update them) Is there a way to make inclusions different looking in tables or in some way separate them - different font, size, italics, headings? YES and NO. I do not know of any way to make the minor components to look different in raw tables. It would be necessary in word to change the formatting of the component name manually, just as is done with many other words and phrases in the manuscript. I do not think that this is something that we want to do, although we certainly could. On the otherhand, we have created an entire set of manuscript tables with the % after the component name. If these tables are used either outside of a manuscript, or inside a manuscript, they do separate the minor components from the major components by giving the percent. Is there a query that allows you to select map units to get reports only by number or range of numbers. There are all kinds of queries and a query could certainly be written to select by mapunit number. There is no query at this time that does this, and I would need more clarification before we could write on at the MLRA-office. If anyone from the field needs a query such as this written, you must write a clear concise description of the query and give some examples of what you wish it to do. Send this to myself or Marie Roberts, and we will try to accommodate the request. There are queries that pull a selected set by map unit name and legend. These may do what you wish. Another alternative is to pull the legend and then load related a few map units. There are many queries out there, you may want to call other users to see if they have used the queries in the fashion that you wish to use. HOW do I know who to call? Just prior to your starting NASIS type the word who at a command prompt. This will tell you who is on the system at the same time you are. If you see someone's name consistently, they may a candidate for some of your questions. Once you get in NASIS you can view the NASIS site and view the user tables. These tables include phone numbers. This is a good way to keep in contact with other NASIS users. Help each other out. There are some misspellings in the MUG statements. How do we get them fixed? MUG is under development. Just send an elm to myself or your state office. Your comments will be forwarded to the MUG development team and the statements will get fixed. ********** PART II. Update on queries and reports. New developments in the MLRA-11 NASIS database by Henry Ferguson Marie Roberts and I have developed a set of queries to select text notes based upon area, status, kind, category, and subcategory. The queries are named as follows: Component text by area & kind & category Component text by area & kind & category & subcategory Data mapunit text by area & kind & category Data mapunit text by area & kind & category & subcategory Horizon text by area & kind & category Horizon text by area & kind & category & subcategory Legend text by area & kind & category Legend text by area & kind & category & subcategory Mapunit text by area & kind & category Mapunit text by area & kind & category & subcategory Please note that the reason that we had to develop two queries for each type of text was that a null in the subcategory field would cause a note to be missed when using the text by area & kind & category & subcategory query. For this reason a second query which omitted the subcategory level had to be written. Using these queries, it is possible to limit the number of notes which are printed out using some standard reports which we have created. Also please note, that any query that brings in an entire county will also bring in the text notes and can be used when you which to print out all notes regardless of kind, category, or subcategory. The corresponding reports to go along with these queries are as follows: Component text inventory(no notes only categories) Component text notes(Try me) Data mapunit text inventory(no notes only categories) Data mapunit text notes(Try me) Legend text inventory Legend text notes(Try me) Horizon text inventory Horizon text notes(Try me) Mapunit text inventory Mapunit text notes(Try me) There is a National report for Mapunit History notes so we did not make a local report for Mapunit History notes. Another set of queries of interest are called: Crop yield (Component) by area and crop Crop Yield (Data mapunit) by area and crop These two queries can be used to bring in all the oat yields and delete all oat yields for a county if you wish to eliminate that crop. These queries could also be used to bring in all the types of hay yields so you could globally assign them to one type of hay. You could also bring in all types of pasture yields to globally assign to one type of pasture. You could bring in all of one type of crop such as corn, if you wanted to edit those yields all at once and did not want the others in your way. We hope that these queries and reports will be of some use to you. Please provide us with comments and suggestions. Other reports that have been written have included: NAPRA A specific report used to download data for a water quality program. AASHTO used to compare AASHTO group index, % passing 200, LL and PI. This data could be loaded into an EXCEL spreadsheet and used to verify the AASHTO group index for low, RV, and high values. Additional comments on queries and reports: The first queries listed when you select local, are those that have been imported and we have not reviewed yet. The next queries are those that we have been working on most recently. At this time the queries that we have been working on deal with text notes. Please try these out by reading the description text and applying them to your counties. Note that suggested reports are listed in the query description. Mapunit, Datamapunit by mapunit name is a new query which is helpful for pulling up datamapunits by mapunit name in the region. Some of the most useful queries include: legend by name (all status) MO-11 Load the Major components for a survey are (major component flag must be populated) Component by component name and legend Component by component name and survey area Component month, component name, and legend Crop yields (component) by area, and crop Crop yields (data mapunit) by area, and crop On the report side. We have also been writing some reports and reorganizing them using the following convention: The reports that are least likely to work are found on top. These are the ones that have a no in the ready to use column. The first report that is sanctioned is the NAPRA report which is a download for a water quality module. Our version of the FOTG reports are grouped under the NAPRA report A text note called initials must be populated or the reports will be empty. See the report description for information regarding the population of this legend text note. Under the FOTG reports are the latest versions of the MUG reports being worked on in MI, OH, and IN. Under the Mug reports are text note reports for Area, Component, Data mapunit, Horizon, Legend, Mapunit , and Mapunit history. Under the text note reports are reports for general correlation. These include correlation errors, legend and dmu, legend and dmu description, legends in database by status, and correlation for SSURGO. Other reports include conversion legend, Map unit acres from legends and rep dmuid, Progress, and SSURGO conversion legend. Under these correlation type reports are check reports. These reports include Water table using top depths, AASHTO, AWC, Caco3, ecec, ksat, wfact, pH, Natl. Forest Acre check for SSURGO, and a sand fraction checklist using the engineering report format. Missouri's reports are under the check reports and all start with Mo- Michigan's reports are under Missouri's reports and most start with 10024. Under Michigan's reports are MANU(%) - Reports. These reports have been designed to include the % of each component in the table. If you load all components, even the minor components will be listed with the % after them. The last report is a Data Dump GIS. ********** PART III New Edit setup for ownership and vintage of soil surveys The newest edit setup that we have created is called the Ownership and vintage of soil surveys. This edit setup is particularly useful when comparing legends or when I change permissions on data for field offices. ********** PART IV. Changes in Backups vs Archives Please note that in the near future the legends which were called backups will be called archives. The term backup really is a misnomer for these legends. Since the MLRA-11 Regional Office will not be making regular backups of the legends they must be regarded as Archives. To retrieve these legends you must refer to them as BIL001 at this time or AIL001 once they are called archives. Each legend name starts with a z and ends with a z. If you wish to call them up, you must use the following format zadams*illinoisz for Adams County, Illinois. Or za*sz would give the same result if Adams is the only county in Illinois starting with a. Converting the legends from the backup area types to archive area types is not a high priority so do not look for that change too soon. ********** PART V. Suggestions for progress reporting in NASIS MO-10 is using a graphical approach to progress - MO-11 is suggesting the use of Legend Text Notes for population as well as using the existing fields for mapping progress, compilation and digitizing percents. The following note went out to a single project office for testing. The content may be of interest to others, but has not been mandated within MLRA-Region 11 at this time. We want to start reporting additional progress items in NASIS legend text note section. The MO-11 office will develop a survey area bar graph to reflect progress. This method will allow us to keep a complete current progress report of key correlation and soil business activities, within MO-11. Please note that existing fields for compilation %, digitization %, mapping complete, will come directly from NASIS as it exists. The additional information requested has to do with transects, and manuscript completion that is not well covered in the existing legend fields. Please refer to Pulaski Co. Legend Text Notes to see the "kind, category and subcategories to help with this process. Charles Love ********** PART VI List of component choice list for those whose screens do not accommodate the entire list One of our MLRA Project Leaders has had some problems editing in NASIS because choice lists are not completely viewable on his screen. If you have the same problem the following list may be of use to you. Note that if you use the arrow up key when the component field is selected you will end up bringing up the component pedon table. If you use the arrow up key twice you will get the component text field. Component Choice List (from Byron Nagel, MLRA Project Leader North Vernon, IN) Component Crop Yield Existing Plants Forest Productivity Forest Productivity - other Potential Ecosystem Potential Windbreak Trees to Managed Geomorphic Description Two Dimensional Surface Morphometry Three Dimensional Surface Morphometry Slope Shape Surface Morphometry Microrelief Surface Morphometry Erosion Accelerated Surface Fragments Parent Material Group Parent Material Month Soil Moisture Soil Temperature Restrictions Diagnostic Features Taxonomic Family Mineralogy Taxonomic Family Other Criteria Taxonomic Moisture Class Interpretation Interpretation Restriction Text Pedon ********** PART VII. Reports from NASIS training Thank you to all the participants for participating in the work groups. A major function of the work groups was to focus the training. It should be noted that the members of these workgroups may not have had the experience to come up with concrete conclusions during the course of the training. However, it is hoped that the individuals involved in the work groups would carry their experiences home, work in NASIS and keep the mission of the work group in mind. As more experience is gained, the participants may be able to formulate more concrete alternatives and help provide guidance to the region. ---------- A. Placement of 1990 Frozen Values in NASIS Task: To decide where to store the 1990 frozen soils data Group: Scot Haley Resource Soil Scientist Indianapolis, Indiana Ken McWilliams Resource Soil Scientist Jasper, Indiana George McElrath Resource Soil Scientist Corydon, Indiana Jerry Shively Resource Soil Scientist Greencastle, Indiana Bill Hosteter Soil Scientist Indianapolis, Indiana Mack Hodges Soil Scientist Champaign, Illionios Results: Consensus was reached that the three options should be as follows: 1) Store them in NASIS as a separate legend. 2) Scan the hard copies into word. 3) Store in Access. Consensus was not reached as to the best choice. Russ Kelsey hinted that NASIS was not the best place to store it right now. The group did not have a chance to get together after that discussion. I would assume that the group would suggest storing them in Access. Reporter: Scot Haley Suggestion for future discussion: Assemble electronic versions of the data into one tab delimited or pipe delimited file. Store in NASIS as a single legend text file that could easily be exported to Access, Excel or any other database or spreadsheet program by simply printing out a single legend text report from NASIS and saving it as a file for import. ---------- B. Protocol for making changes to Data Mapunits (DMU's) and Official Soil Series Descriptions (OSD's) common to Region-11 and Adjacent Regions MLRA Project Leader (MLRAPL) in whose area the OSD or DMU resides will maintain and coordinate changes to these objects. Resource Soil Scientists (RSS) will maintain and coordinate changes to the data for published Soil Surveys, but all changes need to be coordinated with the MLRAPL. Requests for changes to an OSD or DMU will be made to the MLRAPL with responsibility for these objects. When applicable, the requested change(s) to components of a DMU are to be based on actual lab or field test data. MLRAPL with responsibility for the OSD or DMU will coordinate with RSS in his area, and MLRAPL and RSS from surrounding MLRA's for their comments on the requested OSD or DMU change. The minimum area to canvass will be all Project Offices within the MLRA and other MLRA Project Offices that have correlated the map unit in the past. It is the responsibility of the other MLRAPL's to coordinate the request for changes with the RSS's who work in their MLRA area. After comments are received, the MLRAPL with responsibility for the OSD or DMU makes a preliminary decision on the requested change(s), and submit them to the Technical Committee for review. The Technical Committee will review the requested changes to the OSD or DMU for approval. If the Technical Committee does not agree to the proposed change or changes, the SDQS in the role as correlator will determine the need for a new OSD or DMU. MLRAPL will notify the SDQS Liaison when a request to change the DMU is approved by the Technical Committee. The SDQS responsible for routing changes to OSD's or DMU's among MO Regions, are to request to receive comments within 30 days. Technical Committees are established for reviewing and concurring on changes to Official Soil Series and Data Mapunits. Establish four Technical Committees based on the same MLRA areas of responsibility as with the SDQS's: 99/111 113/114/115/120/121/122 94A/96/97/98 95A/95B/108/110 Each Technical Committee will select a Chairperson and Recorder. It is suggested that each Technical Committee be comprised of the following: State Cooperators (DNR's, AG agencies, Consultants ) University Cooperators Resource Soil Scientist Technical Specialists (Foresters, Biologists, Agronomists/Resource Spec., Engineers) Action Items The State Soil Scientist or State Soil Liaison is to coordinate establishing and identifying those who will comprise the Technical Committees. MLRA Board of Directors submit this protocol as policy for Region-11. Subjects for future discussion: Are there data elements that can be populated with only the approval of the individuals using the data mapunit? ie. No routing to SDQS or to ARS using the series but not the same data mapunit. Can specific data elements be identified that should be routed for informational purposes only, and do not need approval authority? Can specific data elements be identified that must go through the rigerous approval authority as outlined above? When is it OK to update a data element? Can proposed changes be incorporated into update data mapunits prior to approval for the purpose of printing out reports for review? Proposed changes to published data and changes to update data mapunits that are used by multiple surveys must be routed and approved prior to incorporation into the database. ---------- C. Use of Regional, State, MLRA, or County Subset Legends. Task: Come up with a recommendation for the management of the above types of legends. Group members: Asghar Chowdhery Shane McBurnette Steve Higgins Bennie Clark John Werlein Rick Neilson The consensus of the group was to recommend the building of Major Land Resource Area Legends. The County Subset Legends would be created by picking mapunits from the MLRA Legends. The datamapunits would then be updated and run a subset report for a manuscript. The Data Mapunits will be linked to both the counties and the MLRA legends at the same time. There was no consensus regarding Regional or Statewide legends. At this time there are two statewide legends in MLRA-11. The Indiana and the Illinois state legends exist, however at this time only the Indiana state legend is being maintained. The Indiana State Legend is being maintained by the three MLRA Project Leaders in Indiana. There is no Regional Legend at this time and there is not enough support to create or maintain one at this time. Comments from Charles Love, SDQS concerning MLRA and County Subset Legend: I do support building MLRA Legends to better conduct MLRA Correlation and Soil Business Activities, within MLRA. But first, all MLRA Project Leaders should establish a MLRA Identification Legend steering committee, involving other Project Leaders, Subset Soil Scientist, Resource Soil Scientists and cooperators within their MLRA Survey. This committee will help that MLRA Project Leader(s) to establish the most workable MLRA legend and common data map units for that legend. They would review all the published soil surveys, lab data and historical data within the MLRAs. Then they would eliminate or de-select those map units or data map units that are no longer suitable. Having a committee of soil scientists (totally over 150 years of experience) will be very helpful in facilitating this process. The vision is to have one common map unit symbol legend and possibly one data map unit per map unit to ensure complete soil data sharing and development of seamless soil maps within and across MLRAs. I really think the MLRA legends are needed for facilitating the NASIS database efforts. Fewer legends, map units and data map units stored in NASIS database will better help in linking and building fewer data map unit within those MLRAs and the region. This will promote perfect joins across county, state and MLRA lines and helps achieve soil survey updates and digitization efforts. We do not have the time to update or maintain one county at-a-time, we need to complete these efforts by groups' of counties. This MLRA Legend will help these efforts. ---------- D. Populating Data Elements - Priority Working group members: John Doll Tonie Endres Bill Frederecks Bob Tegeler The work group went through the list of NASIS data elements and identified the following elements as being those that are needed for population. The reason for the need to populate the data elements is often program or project driven. MUG (and the production of other soil survey manuscript materials) is one program that requires the population of many of the elements on the list. The list: Populate the included soils (I guess we were thinking %, kind, and name in addition to attaching data mapunits.) Populate parent material and geomorphic data fields. Populate ponding duration; Populate runoff class Populate data for restrictions Populate data for surface fragments. Populate earth_cover data Populate soil moisture data. Populate particle size fractions for sand and silt. These data elements were orally presented to the NASIS workshop members. During the presentation of work group findings, Russ Kelsea brought up the interp-generator and fuzzy logic. Running interps w/ fuzzy logic will identify data elements that were needed for the interp but were void. To complete the process, the interp generator would insert default values. A report is generated that identifies data elements that used default values. It is activities like this that will help us identify other data voids. Other data elements will be added to the list as they become known. ---------- E. Identification Of Type Locations Work Group Members: Jennifer Berman Rick Robbins Mike Wigginton Randy Leeper Marty Kroell Gary Struben The charge for this work group was to identify a way of indicating in NASIS which Data Mapunit is representative of a given type location, especially OSD type locations. The group listed, in order of priority, the type locations we would like to be able to identify: 1. OSD 2. MLRA by map unit phase 3. Subset by map unit phase The group listed the following options for identifying type locations: 1. Put type location tag in DMU Description 2. Use text fields, probably data mapunit text and set up categories for OSD, MLRA, SUBSET, etc. 3. Use PEDON in NASIS and indicate by pedon type from choice list 4. Create new data element The group preferred not to use Option 1 because of adding length and confusion to the DMU name. Option 2 seemed to be a viable option, particularly for type locations other than the OSD, but needs to be coordinated with the group working on text notes. Option 3 was not preferred because few pedons are currently in NASIS, but could be used more in the future. Option 4 was preferred by the group, especially for OSD type locations. Thus, the group would like to request that a data element be added to indicate, at the minimum, the OSD type locations. This would help NASIS users better identify and evaluate DMU's and give a link between the OSD files and NASIS. The group also recommends that in the REMARKS section of the OSD, the DMU ID or DMU Description be listed that represents the OSD type location. DMU's that represent other phases could also be listed if known. ---------- F. Naming of Data Mapunits Working group members: Dena Marshall Rex Brock Doug Dotson Steve Neyhouse Steve Tardy Charles Love Marie Roberts The following consensus was arrived at by this working group. The data mapunit name should contain the following elements: State code County fips code Map unit symbol Major component names No consensus was agreed upon regarding the inclusion of phase terms, codes indicating the presence of supporting laboratory data, or the inclusion of horizon layers from a Typical Pedon from an Official Series Description. This group did not feel that it had enough experience in NASIS or time enough to tackle this problem in its entirety. Therefore much of the meeting consisted of information gathering and discussion. It would be helpful for this working group to meet again after a few months of practice in NASIS to discuss the issue. Some comments and information for consideration: There are currently 43353 data mapunits in the MLRA-11 NASIS database. One advantage of renaming some of the data mapunits would be to differentiate them from other data mapunits that have not been renamed. This is one good reason for NOT renaming all data mapunits. There is nothing that says that all 43353 data mapunits must or even should follow the same naming convention. Examples of some unique names for data mapunits: No name is certainly valid, but does not tell you anything about the data mapunit. AddC2 Typically this was a data mapunit for an additional symbol. There is no data in the tables nor are there any notes unless they are populated after SSSD conversion. Delaware null This name indicates that there is no data in the data mapunit tables. This type of data mapunit might be considered a place holder to which to link all the mapunits from an older legend for which no attribute data has been populated in NASIS. Adams update null This is a similar instance to the situation above, except in this case the one data mapunit is used to link all of the mapunits for an update legend until specific data mapunits are selected for linking. IN001AddC2 This name indicates that the data mapunit is from Adams county, Indiana and is associated with mapunit AddC2. IN001AddC2 Adco This indicates that the data mapunit is from Adams county, Indiana and that the major component in the data mapunit is Adco soils. IN001AddC2 Adco sil 8 to 12, eroded Same as above except that the phase terms have been added. IN001AddC2 Adco sil 8 to 12, eroded Type Location Same as above except that the word type location has been added. 111 94B 98B These are the MLRA's that this data mapunit is assigned to. There is no description indicating what components are in the data mapunit or which mapunits it is associated with. IN001AddC2 111 94B 98B This name indicates that the data mapunit is from Adams county, Indiana and is associated with mapunit AddC2, and is being used in MLRA's 111 94B and 98B. There are advantages and disadvantages to each naming convention. It is up to the field staffs to experiment with naming their data mapunits in such a way as to help them manage them the most efficiently. Please give these naming conventions some thought and try them out. Which ones work best for you? Remember, more than one naming convention may be appropriate for different situations. We do NOT want to rename all 43353 data mapunits. We only want to rename those data mapunits that are being used on a daily basis and that have particular significance to the update soil survey process. ---------- G. MLRA Legends In Michigan (by Bill Frederick) In Michigan we have developed two MLRA legends so far below the bridge. The first one of these (MLRA 94A) was really developed before the advent of NASIS. We started with the soil survey legend for Alcona County, Michigan and built on it from there. At one of our first Steering Committee Meetings we then reviewed each mapping unit from other modern soil surveys that were published before the start of the MLRA legend to determine if the mapping unit was going to be added to the legend. The mapping unit had to be one that we knew would be used across extensive areas. If there were any questions about the unit, it was not added. With each successive county progress field review mapping unit numbers were reserved and added to the MLRA 94A Legend. The project leader had to document the unit (ie soil descriptions, note cards, etc.) in order for the unit to be added to the legend. We now have a MLRA 94A legend with mapunits, but we have not yet linked the mapunits to the "modal" data mapunit. This was done in this fashion, because we felt we would not know which county type location would be most appropriate one to use to represent the "modal" data mapunit until the MLRA is completed. Each county subset has its own type location in the published soil survey. Now that the initial mapping for the MLRA is nearing completion the MLRA Project Leader will be starting the process of determining Series MLRA type locations and linking all map units that contain that series to the appropriate data map unit. ********** PART VIII. Copy and paste from Word to NASIS Copying a text (or word) document into NASIS text Fields. Exceed icon - right click Select - tools Select - toolbar Select - show Move the edit box off to the side. In NASIS session you need to have text window ZOOMed open. Go to text document. Highlight text you want to copy. Copy or Cut the selected text. (this puts the material onto the clipboard) In the Exceed edit box there is a box w/ an X in the middle of the clipboard. When you put the pointer on it the textbox says Paste Clipboard To X Selection. Simultaneously, at the same time click both the right and left mouse button. Move the pointer to the NASIS text box, and simultaneously at the same time click the right and left mouse button. ######################################################################### Last month, the following x3780 files were sent to offices having SSSD: x3780.420frig on Jun 03 (49 updated OSDs) @ x3780.421mes on Jun 08 (25 updated OSDs) * @ Sent to offices using soils in the frigid soil temperature regime. * Sent to offices using soils in the mesic soil temperature regime. # Sent to all offices. The above x3780s contained the following updated Official Series Descriptions, which can also be obtained at: http://www.statlab.iastate.edu/cgi-bin/osd/osdname.cgi frigid amasa...ault...brimson...burt...chabeneau...channing...dishno...dorset... farquar...frechette...hattie...keewaydin...magnor...malachy...moshawquit ...munising...neconish...net...northland...ortonville...paavola...pecore ... pelissier...pleine...rabe...schweitzer...shoepac...skandia...skanee ...solona...spear...sporley...sturgeon...sundell...sundog...tawas...toimi ...tokiahok...traunik...trenary...tula...two_inlets...vanriper...voelker ... waiska...witbeck...yalmer...yellowdog...zeba mesic aldo...bearpen...boguscreek...boplain...chelsea...drammen...dundas... dunnbot...ella...farrington...forkhorn...gaphill...garne...hayden... hersey ...keltner...kevilar...komro...motark...pepin...plumcreek... prissel... rockbluff...rusktown...scotah ######################################################################## CHANGED ADDRESSES AND PHONE NUMBERS 1. Mike Sucik has accepted the State Soil Scientist position in Iowa. ######################################################################### ACTIVITY SCHEDULE (through August 15--subject to change) MLRA DATE ACTIVITY LOCATION MO 10 STAFF ---- --------- ---------------------------- ----------------- ----------- 88 Aug 02-06 Progress Field Review Int'l Falls Giencke 90 Jul 22-27 Progress Field Review Milaca Giencke 93 Aug 09-13 Initial Field Reviews Gogebic/Ontonagon Jahnke 93 Jul 26-30 Initial Field Review Keweenaw Jahnke 104 Jul 19-23 Initial Field Review Winnesheik Hempel 105 Jul 19-23 Progress Field Review Eau Claire Jahnke 105 Jul 22-23 Field Review Exit Conference Eau Claire McCloskey all Jul 12-15 Digitizing Unit Leaders Mtg Madison McCloskey ######################################################################### CONTRIBUTIONS, IDEAS, SUGGESTIONS, AND QUESTIONS ARE WELCOME Thanks to those individuals who participated this month. It is your efforts that are making this newsletter a success. * * * * * This newsletter is intended to be a forum to distribute information of a general nature that will benefit soil scientists in soil survey project offices. It is hoped that it will foster communications and sharing of knowledge among those soil scientists in MLRA Region 10. * * * * * Articles from other newsletters are included to distribute ideas and comments from other areas of the country; these ideas and comments are not necessarily identical to those used in MLRA Region 10. * * * * * The format of this newsletter is intentionally simple so that it can be received, read, and printed by the project office having the least sophisticated computer setup. * * * * * Please submit your articles at least five days before the end of the month for inclusion in the following month's newsletter. Otherwise it will appear the following month. Occasionally, due to other workload demands, it may be an additional month before the article appears. Generally, articles are inserted in the order they are received. Articles in an electronic format can be submitted to: jfh@mn.nrcs.usda.gov It is best if electronic articles are prepared in a "text only" format. Articles in a paper format can be sent or faxed to: John Handler MLRA Region 10 Office USDA - NRCS 375 Jackson Street - Suite 600 St. Paul, Minnesota 55101-1854 FAX: 1-651-602-7914 * * * * * Previous month's copies of this newsletter are available at: http://www.mn.nrcs.usda.gov/mo10/mo10.html #########################################################################