<?xml version="1.0"?>
<metadata><Source>http://wa-node.gis.washington.edu/waf/uw/dnr/523scd02.xml</Source>
<idinfo>
<citation>
<citeinfo>
<origin></origin>
<pubdate></pubdate>
<pubtime></pubtime>
<title>Snohomish County - School Districts</title>
<edition></edition>
<geoform></geoform>
<serinfo>
<sername></sername>
<issue></issue>
</serinfo>
<pubinfo>
<publish></publish>
</pubinfo>
<othercit></othercit>
<onlink></onlink>
<lworkcit></lworkcit>
</citeinfo>
</citation>
<descript>
<abstract>Consists of school districts in all of Snohomish County, Washington maintained by the Snohomish County Auditor.</abstract>
<purpose>Critical in supporting Snohomish County Auditor business functions including the administration, management, and tracking of County elections.  Very useful in the mapping and analysis of elections results.  Critical in supporting the display, query, mapping and analysis needs of other County agencies as well.</purpose>
<supplinf>
This dataset is a subset of a larger master Snohomish County dataset which holds most of the political and administrative districts (e.g. voter precincts, Congressional districts, Legislative districts, County Council districts, school districts, etc.) maintained by the Snohomish County Auditor.  This master dataset is maintained in its native environment in an ARC/INFO data library (i.e. coverage format).  The ARC/INFO regions data model is employed to facilitate display, query, and analysis of each subclass of political and administrative district.
LAYER LOCATION:         library sca24000_admin
LAYER DATASET NAME:  pads
LAYER SUBCLASS NAME(S):
Does a region or route subclass exist for this layer?  YES
Region Subclasses:            Contents:
REGION.SCHL                School Districts
DATASET TYPE / STORAGE METHOD:  Data Library Layer
GEOGRAPHIC EXTENT OR AREA COVERED:  Snohomish County, Washington
LIMITATIONS / WARNINGS / COMMENTS:  This dataset serves the Snohomish County Auditor for the purposes of the administration, management, and tracking of County elections.  The Auditor is predominantly interested in only those districts which hold elections.  Hence, this dataset may not contain all school districts which exist in the County if these districts do not hold elections.
ARCHIVE STATUS:  Online
COMPLETION STATUS:
Region Subclass:              Completion Status:
REGION.SCHL                Complete
</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate></caldate>
<caldate></caldate>
<time>Multiple_Dates_Times:</time>
<time>Range_of_Dates_Times:</time>
</sngdate>
<rngdates>
<begdate>N/A</begdate>
<begtime></begtime>
<enddate>Present</enddate>
<endtime></endtime>
</rngdates>
</timeinfo>
<current>Ground Condition</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Quarterly</update>
</status>
<spdom>
<bounding>
<westbc>-122.5</westbc>
<eastbc>-120.5</eastbc>
<northbc>48.5</northbc>
<southbc>
47.5
Data_Set_G_Polygon:
Data_Set_G_Polygon_Outer_G_Ring:
G_Ring_Latitude:
G_Ring_Longitude:
Exclusion_Vector:
Data_Set_G_Polygon_Exclusion_G_Ring:
G_Ring_Latitude:
G_Ring_Longitude:
</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>political districts, administrative districts, governmental units, school districts, elections</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Snohomish County, Washington</placekey>
</place>
<stratum>
<stratkt></stratkt>
<stratkey></stratkey>
</stratum>
<temporal>
<tempkt></tempkt>
<tempkey></tempkey>
</temporal>
</keywords>
<accconst>None</accconst>
<useconst>None.  Acknowledgement of the Snohomish County Auditor and/or the Snohomish County GIS would be appreciated in products derived from these data.</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper></cntper>
<cntorg></cntorg>
</cntperp>
<cntorgp>
<cntorg></cntorg>
<cntper></cntper>
</cntorgp>
<cntpos></cntpos>
<cntaddr>
<addrtype></addrtype>
<address></address>
<city></city>
<state></state>
<postal></postal>
<country></country>
</cntaddr>
<cntvoice>Contact_TDD_TTY_Telephone:</cntvoice>
<cntfax></cntfax>
<cntemail></cntemail>
<hours></hours>
<cntinst></cntinst>
</cntinfo>
</ptcontac>
<browse>
<browsen></browsen>
<browsed></browsed>
<browset></browset>
</browse>
<datacred>
Jeff Anderson, GIS Database Administrator, Snohomish County Department of Information Services, GIS Division
Tammi Brown, Elections Mapping Technician, Snohomish County Auditor, Elections Mapping Division
David Fish, Elections Mapping Coordinator, Snohomish County Auditor, Elections Mapping Division
Russ Harlan, Elections Manager (Retired), Snohomish County Auditor
John Henderson, Elections Mapping Coordinator (Retired), Snohomish County Auditor, Elections Mapping Division
Carol Pogson, GIS Technician, Snohomish County Department of Information Services, GIS Division
Joe Smith, Network Administrator, Snohomish County Auditor
</datacred>
<secinfo>
<secsys></secsys>
<secclass>Unclassified</secclass>
<sechandl></sechandl>
</secinfo>
<native>ESRI ARC / INFO version 7 software on a Unix-based Sun Workstation hardware platform.  Dataset size is approximately 5 mb.</native>
<crossref></crossref>
</idinfo>
<dataqual>
<attracc>
<attraccr>
QUALITY ASSURANCE PROCEDURES
OVERVIEW:  A variety of both manual and automated checks were used during the quality assurance process.  QA procedures were used to ensure tabular attribute accuracy.  These procedures include--
1.  PRECINCT CODE VALIDATION -- Precinct numbers were checked at the time when label points were added and the PRECINCT# field was populated in the PAT.  This was done to ensure that values entered fell within parameters set by the Auditors Office.  ADDLABEL.AML performed these checks.
2.  PRECINCT NUMBER CROSS CHECKS -- Precinct numbers in the GIS PAD maintenance dataset (PAD_MASTER) are cross checked against precinct numbers in the Auditors DIMS database (i.e. VRDSKDD file) to identify discrepancies between the two datasets.  Corrections are made in either dataset where necessary.  MAKEDISTRICTS.AML performs these checks and produces the discrepancy report.
</attraccr>
<qattracc>
<attraccv>All attributes in this dataset are estimated to have the following feature attribute accuracy:  Currency Date -- 1/31/97, Estimated Percent Complete -- 100%, Estimated Percent Correct -- 99.5%.</attraccv>
<attracce>Based upon automated PRECINCT NUMBER CROSS CHECKS performed by MAKEDISTRICTS.AML which produces a precinct number validation and cross reference report.  Also based upon qualitative guesstimates made by the Snohomish County GIS Database Administrator and the Snohomish County Elections Mapping Coordinator.</attracce>
</qattracc>
</attracc>
<logic>
QUALITY ASSURANCE PROCEDURES
OVERVIEW:  A variety of both manual and automated checks were used during the quality assurance process.  QA procedures were used to ensure both linework accuracy and tabular attribute accuracy.  These procedures include --
1.  CHECKPLOTS -- Checkplots were used to visually check the accuracy of linework and precinct numbers against the map manuscripts.  Corrections were made where necessary.  PAD_CHECKPLOT.AML was used to generate checkplots.
2.   LABELERRORS -- The ARCPLOT LABELERRORS command was used to ensure that there was one and only one label per polygon.
3.   NODEERRORS -- Dangle nodeerrors were drawn and checked in ARCEDIT to ensure all polygons were clean and closed.
4.   PRECINCT CODE VALIDATION -- Precinct numbers were checked at the time when labels were added and the PRECINCT# field was populated in the PAT.  This was done to ensure that values entered fell within parameters set by the Auditors Office. ADDLABEL.AML performed these checks.
5.   PRECINCT NUMBER CROSS CHECKS -- Precinct numbers in the GIS PAD maintenance dataset (PAD_MASTER) are cross checked against precinct numbers in the Auditors DIMS database (i.e. VRDSKDD file) to identify discrepancies between the two datasets.  Corrections are made in either dataset where necessary.  MAKEDISTRICTS.AML performs these checks and produces the discrepancy report.
6.   DISTRICT BOUNDARY REVIEW / VERIFICATION -- Boundaries of political and administrative districts are reviewed and verified prior to the process of posting the PADS dataset to the Countys central database.
</logic>
<complete>
GEOGRAPHIC EXTENT OR AREA COVERED:  Snohomish County, Washington
DATA ATTRIBUTE COMPLETENESS:  Some attribute fields are only partially populated or not maintained at all.  Detailed information is available in the Attribute Accuracy Value section 2.1 and the Snohomish County GIS data dictionary.
LIMITATIONS / WARNINGS / COMMENTS:  This dataset serves the Snohomish County Auditor for the purposes of the administration, management, and tracking of County elections.  The Auditor is predominantly interested in only those districts which hold elections.  Hence, this dataset may not contain all school districts which exist in the County if these districts do not hold elections.
</complete>
<posacc>
<horizpa>
<horizpar>
ABSOLUTE SPATIAL ACCURACY:   +/- 100 feet in urbanized areas within the geographic extent of the generalized (PUD) parcel base.  +/- 300 feet in rural areas and areas outside the geographic extent of the generalized (PUD) parcel base.
RELATIVE SPATIAL ACCURACY:    + 100 feet in urbanized areas within the geographic extent of the generalized (PUD) parcel base.  Unknown in rural areas and areas outside the geographic extent of the generalized (PUD) parcel base.
MAP SCALE:     1:48,000   (1 inch = 4000 feet)  in urbanized areas.  1:100,000 scale in rural areas and remote areas not covered by the generalized parcel base.
BASEMAP REGISTRATION:
County Boundary and Coastline -- Political and Administrative Districts (PADS) linework is registered first and foremost to the linework in this layer.
Generalized (PUD) Parcel Base -- In areas where the generalized parcel base exists (primarily in the western and central parts of the County corresponding with the Snohomish County PUD service territory), the PADS layer is registered to the linework in this layer.
County Hydrography -- Precinct linework which follows hydrographic features (i.e. lake shores, rivers, streams, etc.) register to those features in the County Hydrography layer (Note: The County Hydrography layer is based upon the Washington DNR Hydro layer.).
Street Centerlines -- Where linework corresponds to the middle of a street or right-of-way, this linework registers to any existing linework in the street centerline layer.
PLSS Grid -- In those areas where no generalized parcel base data exists (primarily in the eastern part of the County), PAD linework registers to the County 1:24,000 scale PLSS grid.
Note:  Political and Administrative District boundary linework does not always perfectly register to lines called out in the legal descriptions for these districts.  For example, where the legal description may place the boundary for a school district on one particular side of a right-of-way, the Auditor may elect to place this line in the middle of the right-of-way on a street centerline for the purposes of managing and administrating elections.  There is one exception to the statement above.  In the case of municipalities, the Auditor has elected to register city boundary lines to the Generalized Parcel layer so that they follow the legal description as closely as possible.  Where municipal boundary lines follow the edge of a right-of-way, the Auditor maps this boundary as such.  Hence, any districts (i.e. fire districts, school districts, etc.) which directly abut up against a municipal boundary will share common linework with this municipality.  This common linework will follow the legal description for the municipality as closely as possible.
</horizpar>
<qhorizpa>
<horizpav>
ABSOLUTE SPATIAL ACCURACY = +/- 100 feet in urban areas.  +/- 300 feet in rural areas.
RELATIVE SPATIAL ACCURACY = +/- 100 feet in urban areas.  Unknown in rural areas.
</horizpav>
<horizpae>
ABSOLUTE SPATIAL ACCURACY figures are based upon spatial accuracy tests performed by Roy F. Weston, Inc. in 1994 comparing positions of selected Public Works survey control points to positions of generalized (PUD) parcel base data in the Mill Creek Pilot Study Area.  In some cases, spatial inaccuracy may exceed the figures listed above.
RELATIVE SPATIAL ACCURACY figures are based upon spatial accuracy tests performed by Roy F. Weston, Inc. in 1994 (referenced above) and upon casual observation of edgematch problems in the generalized (PUD) parcel base between quarter section and section tiles.  In some cases, spatial inaccuracy may exceed the figures listed above.
</horizpae>
</qhorizpa>
</horizpa>
<vertacc>
<vertaccr>N/A</vertaccr>
<qvertpa>
<vertaccv></vertaccv>
<vertacce></vertacce>
</qvertpa>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite></srccite>
<srcscale>48,000</srcscale>
<typesrc>Stable-base material</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate></caldate>
<caldate></caldate>
<time>Multiple_Dates_Times:</time>
<time>Range_of_Dates_Times:</time>
</sngdate>
<rngdates>
<begdate></begdate>
<begtime></begtime>
<enddate></enddate>
<endtime></endtime>
</rngdates>
</timeinfo>
<srccurr></srccurr>
</srctime>
<srccitea></srccitea>
<srccontr></srccontr>
</srcinfo>
<procstep>
<procdesc>
DEVELOPMENT METHODOLOGY
MANUSCRIPTING PROCEDURES:
OVERVIEW:  From February 1994 to November 1994, manuscript maps from the Auditors and Assessors Offices were assembled and prepared using standard procedures in preparation for automation.  Extensive research was performed to find district references and information for Auditors X-code areas (i.e. areas in Snohomish County designated as containing no registered voters).  Regular ongoing maintenance on this layer began in 1995.  New manuscripts and source data to support ongoing maintenance are received regularly in the form of annexation documentation from the Snohomish County Boundary Review Board.  Manuscripting procedures include--
KEYWORD                                        EXPLANATION
1.  LINEWORK HIGHLIGHTING -- Lines on paper copies of Auditor Precinct Mylar Maps were highlighted using yellow and pink highlighter pens to emphasize voter precinct and portion boundaries.  In areas where there were no Auditor Precinct Mylar Maps (predominantly in the eastern part of the County), township plots were generated (using PAD_PREPPLOT.AML) and highlighted.
2.   PRECINCT NUMBER ASSIGNMENT -- Precinct numbers were assigned to voter precincts and portions and marked on paper map manuscripts and plots using a cross reference list from the Auditors Office Elections Mapping Division.  Before the time of map preparation (circa 1994), the Auditors Office had used a different system for numbering precincts.  The Auditor was already in the process of converting to the system which is now being used.  This data conversion project presented the opportunity to implement the new numbering system simultaneously with the process of map preparation and automation.
3.   EDGEMATCHING -- Paper map manuscripts and plots were edgematched during the process of linework highlighting and precinct number assignment.
4.  X-CODE AREA RESEARCH -- Auditor X-code areas (i.e. areas in Snohomish County designated as containing no registered voters) were researched to find proper district cross references.  Prior to this project, the Auditor had never maintained district reference information for areas in the County with no registered voters.  This research and subsequent data entry was absolutely necessary to ensure that all of the geographic areas in the County were identified accurately as belonging in the proper political and administrative districts.
5.   X-CODE AREA PRECINCT NUMBER ASSIGNMENT -- During X-code area research, X-code areas were assigned with regular Auditor precinct and portion numbers.
AUTOMATION PROCEDURES
OVERVIEW:  From April 1994 to December 1994, voter precinct / portion lines, polygons, labels, and numbers were digitally converted using on-screen digitizing methods.  Polygon topology was established.  X-code area research data was key entered into the Auditors DIMS database. The finished GIS dataset was then linked to the Auditors precinct-district cross reference (VRDSKDD) file using the voter precinct number (PRECINCT#) as a relational key.  Using this relational linkage, political and administrative district region subclasses were then created.  Regular ongoing maintenance on this layer began in 1995.  Automation procedures include--
KEYWORD                                    EXPLANATION
1.  LINE DIGITIZING -- Lines were digitized using on-screen digitizing methods.  Background layers used for initial general reference and base registration included (1) generalized (PUD) parcels, (2) street centerlines, (3) PLSS grid, and occasionally (4) TIGER hydrography.  AML programs used to facilitate this process included PAD_SETUP.AML, ADDARC.AML, ADDPUDBACKCOVER.AML, REMOVEPUDBACKCOVER.AML, MOPUP.AML, and REDRAWARCS.AML.
2.   POLYGON CODING -- Labels were added to each polygon.  For each polygon label, the PRECINCT# field was populated with precinct numbers identified on the map manuscripts and assigned during the X-code area research process.  ADDLABEL.AML was used to facilitate this process.
3.  TOPOLOGY GENERATION -- Polygon and line topology was established using the ARC BUILD and CLEAN commands.  Whenever possible, BUILD was used.  When necessary, CLEAN was used with the following TOLERANCES:  fuzzy = 4 feet, dangle = 4 feet.  The GIS dataset which resulted was named PAD_MASTER.  PAD_MASTER is now the name of the version of the PADS dataset to which updates are physically added using ARCEDIT.
4.  X-CODE DATA ENTRY -- Precinct numbers and district cross reference data from the X-code area research process was key entered into the Auditors DIMS database.  This step supported the process of downloading an accurate version of the Auditors precinct-district cross reference (VRDSKDD) file.
5.  MAKEDISTRICTS -- ARC/INFO region subclasses representing each political and administrative district were created by linking the GIS PAD maintenance dataset (PAD_MASTER) to the Auditors precinct-district cross reference (VRDSKDD) file.  MAKEDISTRICTS.AML was used to perform this procedure.  The PADS dataset is the output from running the MAKEDISTRICTS program.  This program is now used periodically as a regular part of the layer maintenance process in the Auditors Office.  MAKEDISTRICTS.AML was revised in October 1996 to facilitate the population of the Precinct Name and Precinct Election Number fields using data from the Auditors DIMS database.
6.   LINE REGISTRATION ENHANCEMENT -- From October 1996 to January 1997 the Auditors Office enhanced the spatial registration of the PADS linework to more exactly coincide with the linework in the General (PUD) Parcels layer, the DNR Hydro layer, the Street Centerline layer, and the County Boundary and Coastline layer.  The Auditor also adjusted municipal boundary linework to more closely follow the legal descriptions for such linework along right-of-way corridors.
CONTROL OR TICS:  Not applicable.
PROBLEMS AND RESOLUTIONS:  Auditor X-code areas (i.e. areas in Snohomish County designated as containing no registered voters) were found during the process of data conversion.  This problem was the most significant one encountered during the course of the conversion project.  To resolve the problem, a short plan was written (see PLAN FOR ASSIGNMENT OF AUDITORS PRECINCT X CODES).  A temporary employee was hired to conduct X-code research.  The necessary research was performed and the data gathered was incorporated into the GIS dataset and the Auditors DIMS database.
</procdesc>
<srcused></srcused>
<procdate>See dates entered in the Process Description field.</procdate>
<proctime>N/A</proctime>
<srcprod></srcprod>
<proccont></proccont>
</procstep>
</lineage>
<cloud></cloud>
</dataqual>
<spdoinfo>
<indspref></indspref>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype></sdtstype>
<ptvctcnt></ptvctcnt>
</sdtsterm>
<vpfterm>
<vpflevel>Vector_Object:</vpflevel>
<vpfinfo>
<vpftype></vpftype>
<ptvctcnt></ptvctcnt>
</vpfinfo>
</vpfterm>
</ptvctinf>
<rastinfo>
<rasttype>N/A</rasttype>
<rowcount></rowcount>
<colcount></colcount>
<vrtcount></vrtcount>
</rastinfo>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>N/A</latres>
<longres>N/A</longres>
<geogunit>N/A</geogunit>
</geograph>
<planar>
<mapproj>
<mapprojn></mapprojn>
<albers>
<stdparll></stdparll>
<longcm></longcm>
<latprjo></latprjo>
<feast></feast>
<fnorth></fnorth>
</albers>
<gvnsp>
<heightpt></heightpt>
<longpc></longpc>
<latprjc></latprjc>
</gvnsp>
<mercator>
<sfequat></sfequat>
</mercator>
<obqmerc>
<sfctrlin></sfctrlin>
<obqlazim>
<azimangl></azimangl>
<azimptl></azimptl>
</obqlazim>
<obqlpt>
<obqllat></obqllat>
<obqllong>Straight_Vertical_Longitude_from_Pole:</obqllong>
</obqlpt>
</obqmerc>
<polarst>
<sfprjorg></sfprjorg>
</polarst>
<spaceobq>
<landsat></landsat>
<pathnum></pathnum>
</spaceobq>
<transmer>
<sfctrmer>Other_Projections_Definition:</sfctrmer>
</transmer>
</mapproj>
<gridsys>
<gridsysn>State Plane Coordinate System 1983</gridsysn>
<utm>
<utmzone>N/A</utmzone>
</utm>
<ups>
<upszone>N/A</upszone>
</ups>
<spcs>
<spcszone>5601</spcszone>
</spcs>
<arcsys>
<arczone>
N/A
Other_Grid_Systems_Definition: N/A
</arczone>
</arcsys>
</gridsys>
<localp>
<localpd>N/A</localpd>
<localpgi>N/A</localpgi>
</localp>
<planci>
<plance></plance>
<coordrep>
<absres></absres>
<ordres></ordres>
</coordrep>
<distbrep>
<distres></distres>
<bearres></bearres>
<bearunit></bearunit>
<bearrefd></bearrefd>
<bearrefm></bearrefm>
</distbrep>
<plandu>feet</plandu>
</planci>
</planar>
<local>
<localdes></localdes>
<localgeo></localgeo>
</local>
<geodetic>
<horizdn></horizdn>
<ellips>Semi_major_Axis:</ellips>
<denflat></denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altdatum>N/A</altdatum>
<altres></altres>
<altunits></altunits>
<altenc></altenc>
</altsys>
<depthsys>
<depthdn>N/A</depthdn>
<depthres></depthres>
<depthdu></depthdu>
<depthem></depthem>
</depthsys>
</vertdef>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl></enttypl>
<enttypd></enttypd>
<enttypds></enttypds>
</enttyp>
<attr>
<attrlabl></attrlabl>
<attrdef></attrdef>
<attrdefs></attrdefs>
<attrdomv>
<edom>
<edomv></edomv>
<edomvd></edomvd>
<edomvds></edomvds>
</edom>
<rdom>
<rdommin></rdommin>
<rdommax></rdommax>
<attrunit></attrunit>
<attrmres></attrmres>
</rdom>
<codesetd>
<codesetn></codesetn>
<codesets></codesets>
</codesetd>
<udom></udom>
</attrdomv>
</attr>
<attr>
<begdatea></begdatea>
<enddatea></enddatea>
<attrvai>
<attrva></attrva>
<attrvae></attrvae>
</attrvai>
<attrmfrq></attrmfrq>
</attr>
</detailed>
<overview>
<eaover>This data layer carries school district area entities and school district lines in Snohomish County, Washington.  Attributes identify and describe these features.  Area attribution includes school district name abbreviations.  Line attribution includes County boundary, County coastline, and open water line coding.</eaover>
<eadetcit></eadetcit>
</overview>
</eainfo>
<distinfo>
<distrib></distrib>
<resdesc></resdesc>
<distliab></distliab>
<stdorder>
<digform>
<digtinfo>
<formname></formname>
<formvern></formvern>
<formverd></formverd>
<formspec></formspec>
<formcont></formcont>
<filedec></filedec>
<transize></transize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr></networkr>
</networka>
<dialinst>
<lowbps></lowbps>
<highbps></highbps>
<numdata></numdata>
<numstop></numstop>
<parity></parity>
<compress></compress>
<dialtel></dialtel>
<dialfile></dialfile>
</dialinst>
</computer>
<accinstr></accinstr>
<oncomp></oncomp>
</onlinopt>
<offoptn>
<offmedia></offmedia>
<reccap>
<recden></recden>
<recdenu></recdenu>
</reccap>
<recfmt></recfmt>
<compat></compat>
</offoptn>
</digtopt>
</digform>
<fees></fees>
<ordering></ordering>
<turnarnd></turnarnd>
</stdorder>
<custom></custom>
<techpreq></techpreq>
<availabl></availabl>
</distinfo>
<metainfo>
<metd>1/31/97</metd>
<metrd></metrd>
<metfrd></metfrd>
<metc></metc>
<metc>
<cntinfo></cntinfo>
</metc>
<metstdn></metstdn>
<metstdv></metstdv>
<mettc></mettc>
<metac></metac>
<metuc></metuc>
<metsi>
<metscs></metscs>
<metsc>Unclassified</metsc>
<metshd></metshd>
</metsi>
</metainfo>
</metadata>
