cadastral publication guideline and template · cadastral publication data components ......

CadastralDataPublicationGuideline–May2009(FinalCorrectionsOctober2009)

CadastralDataPublicationGuideline

May2009FinalCorrections–October2009

FGDCSubcommitteeforCadastralData


Cadastral Data Publication Guideline Table of Contents

1. Purpose.............................................................................................................12. Business Applications ....................................................................................33. Terminology and Key Concepts.....................................................................43.1CadastralDataandTheCadastralNSDI...........................................................43.2Production,PublicationandProjectData .........................................................53.3DataStewards ................................................................................................63.4Organizations .................................................................................................73.5GeographicCoordinateDatabase ....................................................................8

4.TheCadastralPublicationDataComponents..........................................................94.1SampleImplementation ................................................................................11

5.CharacteristicsoftheCadastralPublicationData .................................................136.PoliciesfortheCadastralPublicationData...........................................................137.BusinessProcessesandtheCadastralNSDI ..........................................................158.CadastralPublicationGuideline–ImplementationTemplates ..............................168.1SupplementalInformation.............................................................................168.2CadastralNSDI–CadastralReference ............................................................168.3CadastralNSDICoreDataforParcels .............................................................19

AppendixA–DatabaseImplementationTemplateDetails .......................................21AppendixB–PLSSCornerStandardIdentifier..........................................................47References ............................................................................................................50

Note on this version: The Cadastral Core Data elements were developed over several years of analysis of business requirements for parcel information by the FGDC Cadastral Subcommittee. The data elements in the core data were defined in 2008 and have remained stable through several additional tests and analysis. The updates in this version are grammatical and syntactical.


1

CadastralDataPublicationGuidelineMay2009–FinalCorrectionsOctober2009

1. Purpose TheCadastralDataPublicationGuidelinedescribestheminimumsetofattributesaboutlandparcelsandassociatedreferencedatathatareusedforpublicationanddistributionofcadastralinformationbycadastraldataproducers.Thetemplatesthataccompanytheguidelineprovidephysicalimplementformatsanddatastructuresforthepublicationdatasets.TheFederalGeographicDataCommittee(FGDC)CadastralSubcommitteecompletedtheCadastralDataContentStandard1in1995.Intheyearsthatfollowedthisstandardwassubjectedtonumerousreviewsandvalidationtestsresultinginaseriesofupdatesthatclarifiedthecontentandrefinedthedefinitions.BecausetheContentStandardispresentedasalogicalitdoesnotprovidespecificimplementdirection.In2000theSubcommitteebeganaseriesofstudiesontheusesandapplicationsforcadastraldata.ManybusinessprofileswerestudiedstartingwithtwoforumsinpartnershipwiththeWesternGovernors’Association(WGA)andfollowedwithstudiesofhurricaneandwildlandfireresponse,energymanagementneeds,usesofparceldatabyfederalagenciesandmostrecentlymortgageandrealestateanalysis.FromthisbodyofworktheSubcommitteedefinedalimitedsetofattributesthatprovideaplatformsupportingthesebusinessneeds.Thecadastralpublicationdataisdataprovidedbycadastraldataproducersinastandardformonaregularbasis.Cadastralpublicationdatahastwoprimarycomponents,landparceldataandcadastralreferencedata.Itisimportanttorecognizethatthepublicationdataarenotthesameastheoperationandmaintenanceorproductiondata.Theproductiondataisstructuredtooptimizemaintenanceprocesses,isintegratedwithinternalagencyoperationsandcontainsmuchmoredetailthanthepublicationdata.Thepublicationdataisasubsetofthemorecompleteproductiondataandisreformattedtomeetanationalstandardsodatacanbeintegratedacrossjurisdictionalboundariesandbepresentedinaconsistentandstandardformnationally.Theminimumsetofattributesaboutlandparcelsandthecadastralreferenceprovideaplatformuponwhichapplicationscanbebuiltandbusinessneedscanbemet.Theconceptofadataplatformrecognizesthatcadastraldataisabasisuponwhichmanyotherthemesanddatasetsarereferenced.Forexamplelandparceldatacouldbeusedtospatiallyenablebusinesslicense,voterregistration orhealthstatisticinformation.Theuseofthecadastraldataasaplatformforotherapplicationsistheprimary driver

1 CadastralSubcommittee,FGDCCadastralDataContentStandardversion1.3,May2003,http://www.nationalcad.org/data/documents/CADSTAND.v.1.3.pdf


2

fortheneedforstandardizedattributes.Inorderforapplicationstorelyonandusethelandcadastralinformationitmustbestandardizedacrossjurisdictionalboundaries.Thisalsoemphasizestheimportanceofthestandardizationofthesmallsetofattributes.Jurisdictionsmayexpandupontheminimumsetandsomeapplicationsmayneedadditionalattributes,buthavingashortlistofstandardizedattributesshouldmakelinkageorotherdatasetspossibleandallowfortheexpansionandindividualizationofpublisheddata.Therearetwootherimportantnotesaboutthecadastraldataplatform.Parceldatachangesfrequentlyandneedstobeupdatedregularly.Manyoftheinitialneedsofthebusinessapplicationsstudiedcanbemetwithannualparcelupdates,butintheendallbusinessapplicationsneedcurrentdata.Thereforeunlikemanyotherspatialframeworkdatasets,cadastralinformationiscontinuallyupdated.Thesecondnoteisthatallspatialdatashouldhaveaccompanyingmetadatadescribingtheproductionagency,contactinformation,spatialreferencingandaccuracyandcurrency.Thetemplatesforimplementationarebynecessitybasedonthespecificneedsofsoftwareanddatabasesystems.Thetemplatesareprovidedasimplementationguidanceanddefineaminimumsetofattributesthatcanbeexpectedtobepresent,iftheyexist,foranypublisheddataset.Thetemplatesare“flattened”or“denormalized”tominimizerelatedtablesanddomainsofvaluesandtominimizedatabaseorsoftwaremanipulationthatmaybeneededtousethedata.Thefieldtypesarealsospecifictoimplementationforexamplenon‐numericfieldsmaybetermedstring,nvarchar,characterortext.Similarissuessurroundnumericanddatefields.Thereforeitisexpectedthateverysoftwarewillhaveaslightlydifferentimplementationbutitiftheresultingdataareassimilaraspossibleitshouldbepossibletoreachanationalstandard.ThisdocumentdescribestheCadastralDataPublicationGuidelineanditscomponents.AmorethoroughdiscussionofthebusinessprocessesthatdrovethedefinitionoftheseelementscanbefoundattheSubcommittee’swebsite2.ThisguidelineandmanyotherdocumentsrelatedtotheCadastralNSDIandtheCadastralSubcommitteecanbefoundathttp://www.nationalcad.org.

2 CadastralNSDIReferenceDocument,2007)http://www.nationalcad.org/showdocs.asp?docid=158&navsrc=Report&navsrc2=


3

2. Business Applications ThegoaloftheFGDCCadastralDataSubcommitteeistoprovideauniformcoverageofparceldatathatprovidesamulti‐jurisdictionalvieworprivate,stateandfederallands,theirownership,use,structuresandthevalueofprivateproperty.Figure1showsanexampleofthecharacteristicsofasingleparcelandthetypeofinformationthatwouldbeavailableforanentireregion.GISanalysisofaregionaldatasetallowsuserstoidentifythelocationofpropertieswithspecificcharacteristicswithinaregion.Arecentstudyoftheutilityofparceldatabyemergencyrespondersafterahurricanefoundthatlocalparcelinformationwasuniquelycapableofansweringquestionsthatrangedfromtheidentificationofvacantlandsthatcouldbeusedfordebrisremovaltothelocationoforganicfarmstoavoidsprayingthemwithinsecticides.Asimilarstudyofwildlandfireswhereinterdictioncansavelifeandpropertiesfoundthatknowledgeofthelocationofstructuresandtheirvaluewascriticalintheplanninganddeploymentoflimitedresources.

Figure1‐AParcelwithinFEMAfloodzone.Anillustrationofhowparceldatawouldbeincorporatedintoabusinessapplication.Havingparcellevelofdetailwhenmakingdecisionsastowheretobestallocateresourcesisessential.Theissuethatmustbefacedishowtoensureallcommunitieshavethisdatainadigitalformatandthattheemergencymanagement(fire,hurricane,etc)communityhasaccesstoitwhentheyneedit.


4

3. Terminology and Key Concepts

3.1CadastralDataandTheCadastralNSDICadastraldataistheinformationaboutrightsandinterestinland.Cadastraldatamayalsobeknownasrealestatedataorparcelinformationortaxparcelinformation.Therearemanylegalandhistoricalnuancesandsubtletiessurroundingthemanagementofcadastralinformation.3InpriordocumentsthepublicationofthecadastraldatawasoftenreferredtoastheCadastralNationalSpatialDataInfrastructure(NSDI)orCADNSDI. TheNSDIhasbeendefinedbytheFederalGeographicDataCommittee(FGDC).

ExecutiveOrder12906callsfortheestablishmentoftheNationalSpatialDataInfrastructuredefinedasthetechnologies,policies,andpeoplenecessarytopromotesharingofgeospatialdatathroughoutalllevelsofgovernment,theprivateandnon‐profitsectors,andtheacademiccommunity.ThegoalofthisInfrastructureistoreduceduplicationofeffortamongagencies,improvequalityandreducecostsrelatedtogeographicinformation,tomakegeographicdatamoreaccessibletothepublic,toincreasethebenefitsofusingavailabledata,andtoestablishkeypartnershipswithstates,counties,cities,tribalnations,academiaandtheprivatesectortoincreasedataavailability.TheNSDIhascometobeseenasthetechnology,policies,criteria,standardsandpeoplenecessarytopromotegeospatialdatasharingthroughoutalllevelsofgovernment,theprivateandnon‐profitsectors,andacademia.4

TheCADNSDIortheCadastralDataPublicationGuidelineisthecadastraldatacomponentoftheNSDI.TheCadastralNSDIattemptstosimplifysomeofcomplexitiesofcadastraldataintwoways,firstbyprovidingthecadastralinformationintwocomponents,cadastralreferenceandparcels,andsecondbyprovidingalimitedsetofparcellevelinformationtosupportidentifiedbusinessprocessneeds.Thismeansthatsomeofthemorecomplexlandtenurearrangementssuchascondominiums,fractionalinterestssimilartothosefoundinIndianCountryortimeshareownershipmaynotbefullyrepresentedinthelimitedpublicationdataset.ForProjectLevelrequestswheremoredetailisneededaboutaparticulararea,theauthoritativesourcecanprovidethesemorecomplexelements.sourceoftheCadastralNSDIdataisderivedfromthedatabasesofthedatastewards.

3CadastralNSDIReferenceDocument,(2007)page34http://www.fgdc.gov/nsdi/nsdi.html(lastaccessedSeptember1,2008)


5

3.2Production,PublicationandProjectData

ProductionandPublicationDatawerefirstdefinedanddescribedbytheCadastralSubcommitteein2002.5ItwasmostrecentlydocumentedfortheInternationalAssociationofAssessmentOfficers(IAAO)andCadastralSubcommitteejointparcelneedsworkshopinNewOrleansinFebruary20086.Acommonmisunderstandingbetweenthesourcesofparceldataandtheusersofthedataarethedifferencesandrequirementsforproduction,publicationandprojectdata.TheCadastralSubcommitteehasdevelopedamoreextensivediscussionoftheseconcepts.

ProductionData:Localgovernment’sassessmentorproductiondatacontainsawealthofinformationthatisusedbyassessorstoconducttheirdailybusinessoperations.Thesearecomplicateddatabasesthatincludecompletedescriptionsoftaxableandassessmentattributesandananalysisoftheirvaluefortaxationpurposesthatmayormaynotincludetheparcelgeometryinageographicinformationsystem.LikewiseinStateagenciestherewillbeproductiondatatosupportthecollectionandmaintenanceofstateownedlands,businesslicenseandsalestaxdatathatincludespublicandnon‐publicinformation.

PublicationData:TheFGDCCadastralDataSubcommitteehasfoundthatasmallsubsetoftheproductiondata,knownaspublicationorcoredata,meetsover95%oftheusersneedsforplanningandemergencyresponse.Thiswasdeterminedfromaseriesofin‐depthworkshopsheldoverathree‐yearperiod.7

ProjectData:Moredetailedinformationforpropertiescanbeidentifiedthroughageographicselectionofanareaofinterestthatmaybeanoverlayofastormpath,awildlandfirepredictedpath,amortgagecrisishotspotoranyothereventfootprint.Parcelsofinterestintheaffectedareacanbeidentifiedfromthepublicationdataandmorecurrentanddetailedinformationonthissubsetofparcelscanberequestedfromthesource(s)toverifyownershipandotherinformationaboutaparcel.Thisisknownasprojectdataandwouldbeprovidedbytheauthoritativesourceafteraneventtoensurethatthemostcurrentdataisusedforposteventprocessing.

Figure2illustratesthesethreeconcepts.

5ProductionandPublicationAConceptforGeographicInformationEnvironments,(2002)6IAAOandFGDCCadastralSubcommitteeWorkshop:SharingParcelDatatoProtectandRebuildCommunities,(2008)7CadastralNSDIReferenceDocument,(2007)Summarizesthebusinesspracticeworkshops


6

Figure2–Production,PublicationandProjectData

3.3DataStewards

Datastewardsaretheprovidersofcadastraldata.TheSubcommitteeestimatestherearenearly4,000primaryparcelproducersinfederalandstatelandmanagementagenciesandincountyagencieswherelocalgovernmenttaxassessmentofficesarethestewardsofcadastraldataforprivateproperties.Triballandsaremanagedbyindividualtribesandarenotconsideredpublicland.Adatastewardmayprovidecadastralreferenceinformationorparcelinformationorboth.Thecadastralpublicationdatawillhavedefineddatastewardsbasedongeographicextentandthedatacomponent.Forexampleinthefigurebelow(Figure3)thecadastralreferenceisshownasonelayerofinformationandtheparcelgeometrywithrelatedlandparcelinformationasanotherlayer.Thesetwocomponentsmayhavedifferentstewards,forexampleafederalagency,astateorganizationorasurveyingdepartmentinacountymaymaintainthecadastralreference.Thetaxassessororsomeothercountydepartmentmaymaintainthelandparcels.Inthiscasethegeometryisintegratedbecausetheparcelsaretiedtoanddependentonthecadastralreference,buttherearetwocadastraldatastewardsforthesamearea.However,datastewardsforagivendatacomponentdonotoverlap.Thatis,inanygivengeographicareatherewillonlybeonedatastewardforthecadastralreferenceandonedatastewardforthelandparcels.Thestewardshipboundariesandanychangesalongthoseboundarieswillneedtobeagreedtobythedatastewards.


7

Figure3–Twocadastralcomponentsinthesamegeographicextent.

Adataintegratorcombinesinformationfromproducerstogenerateregionalorstatewideviews.Thedataintegratorswillpublishatleastthecoresetofinformationandprovidelinkagestomoredetailedsourceinformationfromthedataproducers.

3.4Organizations

AuthoritativeSourceisanentityauthorizedbyalegalauthoritytodevelopormanagedataforaspecificbusinesspurpose.Thedatathisentitycreatesareauthoritativedata.Thedatastewardsaretheauthoritativesourceandtheseareconsideredtheprimarysourceforcadastraldata.OneoftheprinciplesoftheCadastralPublicationGuidelinesisthattheauthoritativesourceapprovesandprovidesthepublicationdata.8TrustedSourceThisisaserviceprovideroragencythatpublishesdatafromanumberofauthoritativesources.Thesepublicationsareoftencompilationsandsubsetsofthedatafrommorethanoneauthoritativesource.Thesedataaretrustedbecausethereisanofficialprocessforcompilingthedatafromauthoritativesourcesandthelimitations,currency,andattributesareknownanddocumented.9CadastralReferenceisthesetofinformationthatallowsparcellevelinformationtoberegisteredtootherdatathemesandtobetiedtofeaturesontheground.Cadastralreferenceiscomposedofthespatialreferencedata(geodeticcontrolandorthophotography)andsurveyframeworkssuchasthePublicLandSurveySystem(PLSS),parcelmapgrids,subdivisionboundariesormunicipalboundaries.Landparcelsarenestedintoandtiedtothereferencedataandthecadastralreference.

8 FormoreinformationonthisseetheSubcommitteeReportofAuthoritativeandTrustedSourceshttp://www.nationalcad.org/showdocs.asp?docid=1045&navsrc=Report&navsrc2=9IBID


8

One example of an eastern cadastral framework is in North Carolina where the cadastral reference is provided through the state. In this case the State has developed orthophotography standards to meet a wide range of uses, including cadastral information and other reference data such as county boundaries, municipal boundaries, subdivision boundaries and map grids. The parcels are tied to this framework.

3.5GeographicCoordinateDatabase

TheGeographicCoordinateDatabase(GCDB)isaprogramintheBureauofLandManagement(BLM)thatsupportsthemanagementofpubliclands,principallyinthewesternstatesbymanagingcoordinatevaluesonPublicLandSurveySystem(PLSS)cornersandspecialsurveyareas.IncontrasttotheeasttheGCDBisakeydatasourceforcadastralreferenceinthewest.TheGCDBoftenservesasthefoundationforstateandlocalparcelautomationeffortsaswellassupportfortheBLMandotherfederallandagenciessuchastheU.S.ForestServiceandtheParkService.OnfederallandsBLMCadastralSurveyisthedatastewardforthecadastraldataandinsomepartsofthewesttheyarealsothedatastewardsforthecadastralreferencebeyondfederalboundaries.Moreinformationabouttheseconcepts(datastewardship,GCDB,cadastraldataandongoingactivities)canbefoundathttp://www.nationalcad.org.


9

4.TheCadastralPublicationDataComponents

TheNationalSpatialDataInfrastructure(NSDI)isdefinedbytheFederalGeographicDataCommittee(FGDC)10asthetechnologies,policiesandpeoplenecessarytopromotesharingofgeospatialdatathroughoutalllevelsofgovernment,theprivateandnon‐profitsectorsandtheacademiccommunity.Thecadastralpublicationdata(sometimesreferredtoastheCadastralNSDI)hasbeendefinedbytheFGDCCadastralSubcommitteeasaminimumsetofattributesaboutlandparcelsthatisusedforpublicationanddistributionofcadastralinformationbycadastraldataproducers.Thecadastralpublicationdataisintendedtoprovidesufficientinformationtosupportintegratingbasiclandparcelinformationacrossjurisdictionalboundariesprovidingaregionalviewofpropertyownershipandrights.Thisregionalviewisdesignedtoanswerfundamentalquestionsregardinglandownershipandpropertycharacteristics(structures,landuse,andparcelgeometry)insupportofenduserbusinesslandownershipinformation. Thepublicationdataisextracted(published)fromdataproducersatalllevelsofgovernment,butprimarilyfromlocalgovernments,federallandmanagementagencies,statelandmanagementagenciesorstatedepartmentsofrevenue.Thereareotherdataproducersthatcontributetothecadastraldataincludingcountylandsurveyprograms,privatesurveyors,Tribes,locallandmanagementagenciesandstateGISprograms.Thecadastralpublicationdataisstandardizedsoitcanbeintegratedacrossjurisdictionalboundaries,fromcounty‐to‐countyandfromstate‐to‐stateformingaseamless,non‐overlappingrepresentationoflandparcelsandcadastralreferencedata.Thecadastralpublicationdatahastwocomponents:CadastralReferenceandLandParcels.Supplementalinformationsuchasorthophotographyandgeodeticcontrolareessentialtobuildingandintegratingparcelgeometry.Thesupplementalinformationalsoprovidescontextforthecadastralinformationanddatabasessuchashydrography,transportationandevencontoursinsomecasesthatmaybeessentialforverticalintegrationofparcelmapping.Thestandardsforsupplementalinformationaredefinedbynon‐cadastralgroupsbutareessentialforestablishinganaccurategeographicreferencefortheCadastralNSDIsothatpublisheddatacanbeintegratedwithotherinformation.ThestandardsforthecadastralreferenceandparcelcomponentsaredefinedbytheCadastralSubcommitteeandareintheCadastralDataContentStandard11. Thecadastralreferenceelementsareneededtosupportquery,mappingandnavigationandarepartoflegaldescriptions.Thisincludesinformationaboutsurveysystems,such 10FederalGeographicDataCommittee,NationalSpatialDataInfrastructure,Internet,December2005,http://www.fgdc.gov/nsdi/nsdi.html11CadastralSubcommittee,FGDCCadastralDataContentStandardversion1.3,May2003,http://www.nationalcad.org/data/documents/CADSTAND.v.1.3.pdf


10

assubdivisions,geopoliticalareas,landgrantsandthepubliclandsurveysystem.Figure4illustratesthecadastralreferenceconcepts

Figure4–CadastralNSDI–CadastralReference

Figure4illustratesthatthecadastralreferenceprovideslinkagestomoredetailedinformationwhilemeetingthebasicbusinessneedsformanyapplications.Landparcelsarethedetailedinformationaboutpropertyanditscharacteristicsthatareneededtomeetthebusinessneedsoftheusercommunity.Spatiallytheparcelsaretiedtotheearththroughthecadastralreferenceinformation.Figure5illustratesthelandparcelcomponent.

Figure5‐CadastralNSDI–ParcelInformationTheparcelinformationmaybepolygonsorparcelpoints.TheattributesintheparcelcomponentoftheCadastralNSDIcontainsufficientinformationtolinktotherichattributedatabasesfromthedataproducer.Onfederallymanagedpubliclandstheparcelsrepresenttransactionsordecisionssuchasgrazingleases,mineralsurveysoruseauthorizations.Onprivatelandstheparcelsaretypicallytaxparcelsbutmayincludeuserestrictionssuchaseasementsorrightsofways.MetadataisarequirementforallNSDIthemes.MetadataconformstotheFGDCMetadatastandardandshouldincludethecontactinformationinPart1oftheMetadatastandardasaminimum.TheCadastraldataContentStandardcanbecitedas


11

thethesaurusandattributedefinitionsourceforcadastralpublicationdatasetsinthemetadata.Figure6illustrateshowthemetadataandtheidentificationoftheauthoritativeandtrustedsourcesarespatiallytiedtotheparcelandcadastralreferenceinformation.

Figure6–MetadataandDataStewards

4.1SampleImplementation

Figure7illustratestheopeningpageofademonstrationofthecadastralreferencedatafortheStateofArizona.ThedataonthissitewasgeneratedfromtheBLM’sPublicLandSurveySystemspatialdatasets(GCDB)forthestateasenhancedwithlocallygeneratedcontrol.ThelocalcontrolwasintegratedintotheGCDBhadheldfixedinadjustmentsandcomputations.

Figure7–StateofArizonaDemonstrationCadastralNSDISite


12

Zoominginonaportionofthestate,theCadastralReferenceinformationbecomesvisibleandinFigure8thePLSSTownshipsandsectionsthatformthebasisofthecadastralreferencearevisible.

Figure8–CadastralReferenceInformationwithjurisdictionalanddatastewardshipinformationfromtheArizonaCadastralNSDI


13

5.CharacteristicsoftheCadastralPublicationData

TheFGDCCadastralSubcommitteehasreviewedtheconceptdocumentsfortheNSDIandthecontentanddistributionofotherthemesaswellastheneedsandrequirementsfromthebusinessprocessesthatdrivetheneedforpublishedcadastraldata.Basedonthesefindingsthefollowingarethecommonandessentialcharacteristicsofpublishedcadastraldata.

Publishedcadastraldatawillhaveasinglesourceofauthoritativelandparceldataandasingleauthoritativesourceofcadastralreferencedatawithinasinglegeographicextent.Theupdatesandcontentofthisdatamustbecontrolledandmanagedbydesignateddatastewards(authoritativesources).Accesstothisdataisfacilitatedbycompilingandintegratingtheauthoritativedataintotrusteddatasourcesatstateorregionallevels.Thisreducesduplicationofeffortandassuresthatthebestavailableinformationisusedindecisionmaking.Attributesareasimportantasspatialinformationfordecisionsupport.Thelandparceldatamustbeupdatedatleastannually.Thepublishedcadastraldatamustbestandardizedsothatinformationcanbeintegratedacrossjurisdictionalboundaries.Thepublishedcadastraldatamustprovidelinkagestomoredetailedinformationthatcanbeobtainedfromdataproducers.

6.PoliciesfortheCadastralPublicationData

TheCadastralNSDIfollowsthegeneralpoliciesandguidelinesestablishedforallthemesintheNSDI.TheFGDCSubcommitteeforCadastralDataarticulatedthepoliciesthatwereneededfortheCadastralNSDIattheCadastralSubcommitteeOctober2003meetinginPortlandOregon12.

Goalistoestablishpoliciesthatleadtosharedcooperativedecisionmakingandprioritysetting.Whereas1. Cadastraldataiscollectedatthelocal(localized)level–published,

standardizedandintegratedatthestatelevelandindexedfornationwideaccessatnationallevel.

2. Manyfederallandagenciesandtribescollectlocalparcelinformation(i.e.localdoesn’tmeanjustlocalgovernments)

12 CadastralSubcommitteeMeetingNotes,(2003)


14

3. Weneedtobeabletocompletea“mergeondemand”forcadastraldatawhichmeansdataareassembledfromproducersorintegratorswhenneeded,notstoredormanagedcentrally.

4. NorthCarolinafederalagencyandlocalcooperativegroups,MontanaMappingLiaisonOffice,andOregonfederalagency,regionalandlocalgovernmentcooperationareallgoodexamplesofhowlocalizeddatacollectioncanbecoordinated.

5. NGSStateAdvisorandtheUSGSMappingPartnershipOffice(MPO)programscanserveasmodelsforincreasingcommunicationandcooperationamongfederalagenciesandstateandlocalgovernments.Theseareexamplesoffederalagenciesdesignatingpointsofcontactfordatacollection,datadistribution,andrelatedtechnicalassistance.

6. Legacydataandnon‐automateddataimpedesourgoalandweneedtogetthisinformationautomatedandstandardizedtoachieveourgoal.

7. Werecognizetheimportanceof“thedatathreshold”tohelppeopleunderstandhowlocaldataandcadastraldatacanberelieduponforprograms.Thisisthethresholdofinformationyoumusthavetomakepeopleawareofthebenefits.

8. Weneedtocontinuetoidentifyexistingfederalprogramsthatcouldbenefitfromcooperationwithcadastraldatacollection.Forexample,manyfederalprogramsareverticallyfocusedanddon’trealizethepotentialforpartnerships.

9. Therichdatasourceofcadastralinformationatthelocallevelmeansthatsomestateandfederalagenciesthatformerlyneededtocollectdatacannowrelyondatafromthelocallevelratherthanengageinaseparatedatacollectioneffort.

Thereforeweneedto:

• Establishpolicytofirstuseappropriatelocalinformation,beforestartingnewcollectioninallgeospatialprograms.

• Establishpolicytocomplementlocalorlocalizeddataandnotcompletewithit–useemergencyresponseandplanningasexamplesofbenefitstoidentifycorevalues.

• Encouragebuildingthesepoliciesintoalldatacollectioncontractsandprojectsasacondition.

• EncourageFederalA‐16processestoachievecrossprogrambenefits.Thismeansencouragingfederalagenciestostepawayfromstovepipefundingprogramsandworkcooperativelyacrossagencies.

• Encouragedatacollectorsandintegratorstoexplorethebestinclassandotherexamplesandexistingstandardsbeforestrikingoutontheirownwithaprogramfordatacollection.Wetermedthisa“Lookupratherthanheadsdown”approach.


15

AsaresultofthediscussionofthesepolicyneedsandtheresearchneededatthetimetofullydevelopacadastralcomponentfortheNSDItheSubcommitteeagreedtoandadoptedthefollowingpolicesforcadastraldatathatwouldbepublishedfortheNSDI.

DataPublication• Freelyavailable.*

DataStandardization• ReflectstheCadastralCoreDataStandard.• Provideslinkagestoadditionalsourceinformation.• Canbeintegratedacrossjurisdictionalboundaries.

DataDocumentation• Metadatadocumentationiscurrent.

DataIntegrity(qualityandcurrency)• Maintainedandkeptcurrentbythedataprovider**(atleastannually).• Dataisascompleteandaccurateasthedatastewardcanprovide.• Allowfor“mergeondemand”whichistheabilitytocombineinformationon

anasneededbasisfrommultiplesourcesacrossjurisdictionalboundaries.

*Indeferencetothe50Statesinitiativethepolicyrequiringthatthedatabefreelyavailablehasbeensubsequentlyupdatedtobefreelyavailableforgovernment–to‐governmentsharingtosupportdecisionmaking.Eachstatewillneedadoptanappropriatepolicyforthedatadistribution.**Thisconceptwasfurtherdevelopedtobetheauthoritativesourceasdescribedearlierinthisdocument.

7.BusinessProcessesandtheCadastralNSDI

TheCadastralSubcommittee’sstrategyfordeterminingtherequirementsforthecadastraldataistoassessthebusinessneedsofusercommunities.ThroughthisanalysisitwasdeterminedthatthepublishedcadastraldatahastwocomponentsCadastralReferenceandLandParcels.(SeeSection4ofthisdocument)Supplementalinformationwascriticaltocadastralmaintenanceandtoputthepublishedcadastralinformationincontext.Thecadastralcommunityisresponsibleforthetwocadastralcomponentsandisreliantontheactivitiesofothergroupsforthestandardsandstewardshipofthesupplementalinformation.Thecadastralreferenceistheinformationnecessarytofittheparcelinformationintoacontinuousfabric.Inthepublicdomainstates,thePubliclandSurveySystem(PLSS)isakeycomponentofthecadastralreference.Innon‐publicdomainstatesandinthePLSSstatesthereareothercadastralreferencesystemsthatformahierarchyforparcelinformationanddefineacadastralreference.Thisincludesmunicipalboundaries,hydrography(althoughthistreatedassupplementalinformation),mapgrids,subdivisionplatboundariesandblocksandlots.Thelandparceldatadescribethecharacteristicsofparcelsincludingthepolygonorcentroidandattributesthatdescribeownership,landuse,presenceofstructuresandtypeandvalue.


16

8.CadastralPublicationGuideline–ImplementationTemplates

ThefollowingsectionsdescribetheCadastralNSDIwiththedetailsoftheattributesneededtosupportbusinessapplications.

8.1SupplementalInformation

TheSupplementalInformationincludesgeodeticandgeographiccontrolnecessarytoreferencecadastralinformationtoarealworldcoordinatesystem.EveryapplicationandbusinessprocessthatwasexaminedinthedevelopmentoftheCadastralNSDIimpliedorexplicitlystatedtheneedforthisunderlyingreference.SpatialreferencebeginswithageodeticnetworksystemthatcanbedensifiedwithaHighAccuracyReferenceNetwork(HARN)andfurtherextendedtobasemapsandorthophotography.Onekeypointisthatorthophotographyforcadastralinformationinmosturbanareamustbeatonefootpixelorsmallerresolutionwiththeassociatedverticalinformationtosupportthegenerationoftheorthophotography.Inareasofthecountrywithsevereterrainchangesormoreruralareasthedigitalorthoquarterquadranglestandardsmaybesufficient.

TheNationalGeodeticReferenceSystem(NGRS)ThisiscoordinatedandmanagedbytheNationalGeodeticSurveyandprovidesaconsistentanduniformdefinitionofcoordinatesystem,datumsandmonumentedpointsacrossajurisdiction.TheattributecontentoftheNGRSpointswillbeconsistentwiththestandardssupportedbytheNationalGeodeticSurvey.OrthophotographyandContoursThisisorthophotographythatistiedtotheNGRSandiscurrent.Ideally,theorthophotographyincludestheunderlyingterrainmodeltosupportthegenerationoftheorthophotographyandbasicterraininformationsuchasbreaklines.Theresolutionoforthophotographyrangesfromsixinchesintheurbanareastoasmuchas10metersinsteepslopedwildernessareas.Hydrography–Forthepurposesofcadastralreferencehydrographyisincludedtotheextentneededtosupportthedefinitionofcadastralfeatures.Thesearegenerallymeanderablewaterbodiesorwaterthatmayformtheextentofriparianboundaries.InCoastalareasthismayincludetidallimitdefinitionsaspossible.RoadsManyparcellegaldescriptioncallfortheedgeofroadsortheedgeofrightofrightofways.ThestandardsforroadrightofwayareapartoftheCadastralSubcommittee’smissionsbuttheroadsurfaceortraveledwayisnot.Inparticularthetransportationorroadinformationisoftennecessarytosupportandprovideintegritytoparceladdressinformation.

8.2CadastralNSDI–CadastralReference

TheCadastralNSDICadastralReferencecomponentshavebeendefinedintheFGDCCadastralNationalSpatialDataInfrastructure(NSDI)Standardastheelementsneededtosupportquery,mappingandnavigation.CadastralReferenceitemsareapartoflegaldescriptionsandarecontainedintheCadastralDataContentStandard.


17

CadastralReference‐Thisistheinformationnecessarytofittheparcelinformationintoacontinuousandrelatedfabric.Inthepublicdomainstates,thePubliclandSurveySystem(PLSS)isakeycomponentofthecadastralreference.Innon‐publicdomainstatesandinthePLSSstatesthereareothercadastralreferencesystemsthatformahierarchyforparcelinformationanddefineacadastralreference.Thisincludesmunicipalboundaries,mapgrids,subdivisionplatboundariesandblocksandlots.

AmoredetaileddescriptionoftheelementsoftheCadastralNSDICadastralReferenceisasfollows.

Metadata‐Themetadatawillcontaininformationabouttheentiredatasetsuchthejurisdictionname,thejurisdictioncontact,adescriptionofcoordinatesystems,unitsofmeasure,horizontalandverticaldatumifthisinformationisthesameforallcoordinatesreportedinthedataset.Iftherearevaryingreferencesystemsprovidedinthedatasetthentheseitemsarecapturedatthefeaturelevel.Othermetadataincludesthedateofthefilecodeddomainofvaluesandaccuracyreports.

CornersofCommonUsage–Thesearecornersorreferencepointsthatareusedextensivelybylandsurveyorsandotherstogeneratelegaldescriptionsandsurveys.Thesemightbepointsofcommencing,cornerscommontoseverallanddivisions,orcornersofthePublicLandSurveySystem.Theremayberoadintersections,controlmonumentsorcornersofmunicipalboundariesthatareusedcommonlyasastartingpointforlanddescriptions.Eachjurisdictionthatcollectsandmaintainscadastralinformation(cadastralstewards)willidentifywhattheywouldconsidertobeCornersofCommonUsage.Generallythesecornerswouldbeatonetotwomilespacinginruralareasandblock‐by‐blocktoonehalfmiletospacinginurbanareas.CornersofCommonUsagearealsooftenusedinotherthemestocontrolthosethemessuchaspoliticalboundaries.

Thesuggestedattributesforthecornersofcommonusageareasfollows.

ControlID‐Primarykeyforthecornerofcommonusagethattheproviderassignstothepoint.Thismaybeanameoranumber,suchastheNationalGeodeticSurvey’spointidentifier(PID)ortheBureauofLandManagement’sGCDBstandardcorneridentifier.XCoordinate‐Thisistheeasting,theXcoordinateorthelongitudeofthecornerofcommonusagereportedasanattribute.YCoordinate‐Thisisnorthing,theYcoordinateorthelatitudeofthecornerofcommonusagereportedasanattribute.ZCoordinate–Thisistheheightorelevationofthecornerofcommonusage.CoordinateSurveyor‐Thesurveyorwhoestablishedthecoordinatepositions,whichmaybedifferentthanthemonumentsurveyor.Thismayalsobeanagencyorfirm.CoordinateDate‐Thedateofthecoordinatevalues.CoordinateSystem‐Thecoordinatesystemforthecoordinatevaluesuchaslatitudelongitude,stateplanecoordinateorUTM.Thisshouldincludetheunitsofmeasure.Thisisonlyneededifthecoordinatesystemforthecornerofcommonusagevaries


18

fromthatdescribedinthemetadata.ElevationUnits‐Theunitsofmeasureforthereportedelevation.Thisisonlyneedediftheelevationunitforthecornerofcommonusagevariesfromthatdescribedinthemetadata.HorizontalDatum‐Thehorizontaldatumforthereportedcoordinatevalue.Thisisonlyneededifthehorizontaldatumforthecornerrecordvariesfromthatdescribedinthemetadata.ElevationDatum‐Theverticaldatumisthereferencedatumforthereportedelevationvalue.Thisisonlyneedediftheelevationdatumforthecornerofcommonusagevariesfromthatdescribedinthemetadata.HorizontalAccuracy‐Theaccuracyorreliabilityforthereportedhorizontalcoordinatepositionforthecornerofcommonusage.ElevationAccuracy‐Theaccuracyorreliabilityforthereportedelevationforthecornerofcommonusage.MethodsandProcedures–anindicationonthecollectionmethodsorproceduressuchasdigitizedorGPS.

GridorCellReferenceSystem–Thisisareferencesystemthatisusedtosupportparcelmappingandmaybearegulargridcelloranirregularsetofpolygons.Gridorcellreferencesystemsaremostcommonlyfoundinnon‐publicdomainareasandareoftenusedtosupporttaxmappingortheassignmentoftaxparcelidentifiers.Asexamples,theStatePlaneCoordinateSystemoralandlotgridcellsystemorataxmapsheetsystemmaybeusedtodefineasetofgridsorcells.InthepublicdomainstatesthedivisionsofthePublicLandSurveySystem(township,sectionandsectiondivisions)typicallyformthegridorcellreferencesystemformappingandbecalledanominaldivisionsincetheuseofthePLSSinthismanneristoprovideanindexratherthantosupportlegaldescriptions.Thegridorcellreferencesystemdescriptionshouldbeincludedinthemetadata.SignificantCadastralReferenceFeatures–Theseareareasandfeaturesthatdefineorareusedtoreferencelegaldescriptions.AsexamplesthismightbethePublicLandSurveySystemcomponents,theexteriorboundariesofsubdivisionsortheboundariesoflargepubliclandholdings.Typicallythesearefeaturesthatareimportantforunderstandingandusingparcelinformation.Someexamplesareasfollows.

SurveySystemArea–Asurveysystemareaisgenerallyasimultaneousconveyancethatdefinesanareaoflandwithinwhichthereisaconsistentmethodoflanddescription.Themostcommonlyknownexampleisasubdivisionoracondominium.Surveysystemareastypicallyhaveanameornumber.PublicLandSurveySystemTownship‐InthePublicLandSurveySystemaTownshipreferstoaunitofland,thatarenominallysixmilesonaside,usuallycontaining36sections.PublicLandSurveySystemTownshipFirstDivision‐PublicLandSurveySystemTownshipsfirstdivisionsarenormallysectionsortracts.Buttherecanbeexceptions.


19

SurveyName‐PublicLandsurveyareasinOhioareidentifiedbyaname.ThenamedareashaveanoriginofPublicLandSurveySystemvalueandthenarefurtheridentifiedbySurveyName.ThesewouldbeareasinOhioonly.

SecondarySurveyName‐SecondarySurveyNamefurtheridentifiesnamedareaswithintheOhiosurveys.ThesewouldbeareasinOhioonly.

8.3CadastralNSDICoreDataforParcels

TheattributesfortheCadastralNSDIParcelshavebeendevelopedthroughaseriesofstudiesofbusinessprocesseswiththeparcellevelinformationbeingthedetailedinformationneededbythosebusinessprocesses.TheelementsintheCadastralNSDIParcelaredefinedintheCadastralDataContentStandard.

Thebusinessprocessesthathavebeenexaminedtoidentifytheparcelelementstodateincludenavigationanddiscoveryofparcelinformation,emergencyplanning,emergencyresponse,recovery,mitigation,economicdevelopmentandregionalintegrationandcommunityplanning.Allofthesebusinessprocessesindicatedaneedfindadditionaldetailaboutparcelsthroughlinkagestodataproducers.TheCadastralNSDIParcelalsoknownastheParcelCoreDatahasbeendevelopedtosupportinitialorfirstpassneedsofthesebusinessprocesses.Insomecasesthisisallthedatathesebusinessneedshaveandinothersthisdataidentifieswhichparcelswillneedtohavemoredetailedinformationtosupportcasebycaseprocessing.

AmoredetaileddescriptionoftheelementsoftheCadastralNSDIParcelisasfollows.

Metadata‐Themetadatawillcontaininformationabouttheentiredatasetsuchasthedatasteward,theparcelcontact,adescriptionofthebasisfortheassessmentsystem(saleprice,use,marketvalueetc),thedateofthefile,informationoninterpretationoftheassessmentclassificationsandanyothermetadatathatwouldsupporttheuseandapplicationoftheinformation. ParcelOutline(Polygon)‐Thisisgeographicextentoftheparcel,theparcelboundariesformingaclosedpolygon.Theparcelgeometrymaybeapolygonorapoint.TheParcelcentroidandthepolygonarenotbothrequired.ParcelCentroid(Point)‐Thisisapointwithintheparcelthatcanbeusedtoattachrelatedinformation.Thismaybeavisualcentroidorapointwithintheparcel.Itmaynotbethemathematicalcentroidasthispointneedstobecontainedwithintheparcelpolygon.ParcelID‐Auniqueidentifierfortheparcelasdefinedbythedatastewardordataproducer.Theparcelidentifiershouldprovidealinktoadditionalinformationabouttheparcelandshouldbeuniqueacrossthedatasteward’sgeographicextent.SourceReference–ThisfieldisoftencalledtheVolume/PageorLiber/Pageinlocalrecords.Thisisapointerto,oranattributedescribing,thesourcereferencefortheparcel.Thiscouldbeadeed,plat,orotherdocumentreference.SourceReferenceDate‐ThedateoftheSourceReference,whichisessentiallythelastupdatedateforthisparcel.Theentiredatasetmayhavealastupdateddateoran“unloadedfor


20

publication”datethatisdifferentthanthespecificcurrencyorupdatedateforeachindividualparcel.OwnerType‐Thetypeofownershipistheclassificationofowner.Insomelocalgovernmentstaxparcelsaretaggedaseithertaxableorexemptandtheownerclassificationisnotknown.Improved‐Thisisanattributetoindicatewhetherornotthereisanimprovementontheparcel.OwnerName‐Anindicationoftheprimaryownername,recognizingthattheremaybemultipleownernamesorthatsomeownernamesmaybeblockedforsecurityreasonsorthatsomejurisdictionsmaynotallowthedistributionofownernames.Forpubliclyheldlandstheownernameisthesurfacemanagingagency,suchaBureauofLandManagement,DepartmentofTransportation,etcAssessment/ValueforLandInformation‐Thisisthetotalvalueofthelandonly.Thebasisofthevalue,suchasmarketvalue,resalevalue,salepriceorusevalueshouldbedescribedinthemetadata.Assessment/ValueforImprovementsInformation‐Thisisthetotalvalueofimprovementsontheparcel.Thebasisofthevalue,suchasmarketvalue,resalevalue,salepriceorusevalueshouldbedescribedinthemetadata.Assessment/ValueTotal‐Thisinformationisthetotalvalueofthelandandimprovements.Thebasisofthevalue,suchasmarketvalue,resalevalue,salepriceorusevalueshouldbedescribedinthemetadata.BasisoftheValues–Anindicationofthetypeofvaluesthatareprovided(taxable,market,assessedorother)AssessmentParcelUseCode‐Thisistheparceluseclassificationforthetaxparcel.TaxBillMailingAddress‐ThisistheUSPostalServiceaddressforthetaxbillmailing.SiteAddress–Thisisthestreetaddress(siteaddress)fortheparcel.Ifthereismorethanone,selectthefirstorprimarysiteaddress.ParcelArea‐Theareaoftheparcelexpressedinacres.


21

AppendixA–DatabaseImplementationTemplateDetails ThefollowingdocumentationisatemplateforimplementationusingtheformatESRI’sgeodatabase.Inthelistoftheattributesthereare:

fieldnamewhichisshortenedtoaccommodate8.3standardwhichis11charactersinlength.fieldtypewhichistextorstring,integer(anumberwithoutadecimalplace,ordouble,anumberwithadecimalplace).Insomecasestheearefieldsthatarenumbersbuttheyarelistedasatextattributetype.Thisistopreserveleadingzeros.Lengthwhichistheexpectedlengthbutthisistypicallyaminimum.FieldlengthsmaybelongerAliasnamewhichisalongerandmoreeasilyunderstandnameforthefieldDescriptionwhichisashortdefinitionoftheattribute

AttributenamesinREDareconsideredessential,orbareminimum.Thesearetheattributesthatareexpectedinalldatasets.Howeverevenwithintheessentialorbareminimumitisrecognizedthatifthedatadoesnotexistthejurisdictioncannotprovideit.Theessentialattributesshouldbeprovidedifpossible.Thelessessentialattributeshavebeenidentifiedasneededforanapplicationbutarenotcommontoallthebusinessneeds.Ifatableorfeatureclasshasnoredmarkedattributesthefeatureisnotpartoftheessentialdataset.Therearethreetypesoffeaturesordatatableelementslisted.Afeaturedatasetisacollectionofrelatedfeatureclassesthatshareacommoncoordinatesystem.Featuredatasetsareusedtospatiallyorthematicallyintegraterelatedfeatureclasses.Theirprimarypurposeisfororganizingrelatedfeatureclassesintoacommondatasetforbuildingatopology,anetworkdataset,aterraindataset,orageometricnetwork.Afeatureclassisadatabasetableaboutageospatialfeature.Inthecaseoftheparcelinformationthefeaturesmaybepointsorpolygons.Atableisanattributelisting.Thetablesinthislistarealllookuptablesthatareprovidedfortheconvenienceofdatamigrationformlocalsystemstothestandards.Becausethisisapublicationdatasetandeditingshouldnotbeoccurringagainstthedataset,therearenodomainsofvalues.


22

GeodatabaseDocumentation

FeatureDatasets

CadastralReference‐FeatureDatasetMeanderedWater‐SimpleMetadataGlance‐SimplePLSSFirstDivision‐SimplePLSSIntersected‐SimplePLSSPoint‐SimplePLSSQuarterReference‐SimplePLSSReferenceGrid‐SimplePLSSSecondDivision‐SimplePLSSSpecialSurvey‐SimplePLSSTownship‐SimpleSurveySystem‐Simple

Parcels‐FeatureDatasetNSDICoreParcel‐Simple

TablesandFeatureClasses

LU_Direction‐TableLU_OwnerType‐TableLU_ParcelValueType‐TableLU_PLSSFirstDiv‐TableLU_PLSSSecDiv‐TableLU_PrincipalMeridian‐TableLU_State‐TableLU_SurSysDivision‐TableLU_SurveyNameOhio‐TableLU_SurveySystem‐TableLU_SurveyType‐Table


23

CadastralReference‐FeatureDataset

Name CadastralReference

Description Thesearethecadastralreferencefeaturesthatprovidethebasisandframeworkforparcelmapping.

DataThemecadastral

MeanderedWater‐FeatureClass

Name MeanderedWater

ShapeType Polygon

FeatureTypeSimple

AliasName MeanderedWater

Description TheseareareasofwaterthataredefinedfrommeanderlinesofthePLSSandGLOsurveys.Thesearenottheofficialrepresentationsofcoastorwaterlinesandarerepresentationsofthelinesmarkedbythesurveyalongtheboundariesofmeanderedwateratthetimeofsurvey

Purpose Toprovidethepolygonsoftheoriginallymeanderedwaterareas

DataThemeCadastral

Field DataType Length AliasName Description

SURVTYP String 2 SurveyTypeCodeforMeanderedWater

Surveytypecode.ThesearethesurveytypesfromtheBLMGCDBandforthisdatasettheseshouldbeWforWater

SURVTYPTXT String 50 SurveyTypeDescription

Thesurveytypeasatextstring

MetadataGlance‐FeatureClass

Name MetadataGlance

ShapeType Polygon

FeatureTypeSimple

AliasName MetadataGlance


24

Description ThisisagraphicrepresentationofthedatastewardsforthePLSSData.TheminimumresolutionofthePLSSDataStewardistheTownship.Forwesternstatestheidentificationofthedatastewardsatthetownshiplevelisageneralindicationoftheagencythatwillberesponsibleforupdateswithinthetownship.Inotherimplementationsthismayhavebeentermedthealternativesource,meaningalternativetotheBLM.ButinthesharedenvironmentoftheNSDIthestewardforanareaistheprimarycoordinatororagencyresponsibleformakingupdatesorcausingupdatestobemade.OvertimeitisexpectedthatthedatastewardswillbemorefinelydescribedthanattheTownshiplevel.

Purpose Toprovideavisualreferenceforthemetadataaboutstewardsandrevisiondates

DataTheme Cadastral


PLSSID String 16 PLSSIdentifier Concatenationoftheprincipalmeridian,township,range,andduplicationcodethatformauniqueid.

TWNSHPLAB String 25 LabelforPLSSTownship

Townshiplabelthatisusedforcartographicoutputorwebdisplay.

STEWARD String 50 DataSteward Datastewardforthetownship.

REVISEDDATE Date 8 LastRevisedDate

ThelastdateofanyrevisionintheTownship

PLSSFirstDivision‐FeatureClass

Name PLSSFirstDivision

ShapeType Polygon

FeatureTypeSimple

AliasName PLSSFirstDivision

Description ThePLSSFirstDivisioniscommonlythesection.ThisisthefirstsetofdivisionsforaPLSSTownship.

Purpose toprovidethepolygonsforthefirstdivisionsofthePLSSTownship

DataThemeCadastral


FRSTDIVID String 22 FirstDivision Thisisauniqueidentifierforthefirst


25

Identifier divisionthatisbuiltbyappendingthefirstdivisionelementsontheTownshipidentifier.

FRSTDIVNO String 3 FirstDivisionNumber

Thisisthenumber,letterordesignatorforthefirstdivisionofthePLSSTownship

FRSTDIVDUP String 1 FirstDivisionDuplicate

Thisisacodetoindicatewhetherthefirstdivisionisaduplicatedareaoridentifier

FRSTDIVTYP String 2 FirstDivisionTypeCode

Thisisthetypeoffirstdivisionandiscommonlythesectionbutmaybealot,parcel,tractorotherdivision.

FRSTDIVTXT String 50 FirstDivisionTypeDescription

Thisisthefirstdivisiontypeasatextfield

PLSSID String 16 PLSSIdentifier ThisistheuniqueidentifierforthePLSSTownshipinwhichthefirstdivisionislocated.Concatenationoftheprincipalmeridian,township,range,andduplicationcodethatformauniqueidentifierforthetownship.

FRSTDIVLAB String 5 FirstDivisionLabel

Thisisthelabelforthefirstdivisionthatisusedforcartographicofwebdisplaypurposes.

SURVTYP String 2 SurveyTypeCode

Codeofthetypeofsurvey.Thisindicatesifthetownshipfirstdivisionhasbeensurveyed,protractedorunprotracted(extended)

SURVTYPTXT String 50 SurveyTypeText

Surveytypetextdescription.

PLSSIntersected‐FeatureClass

Name PLSSIntersected

ShapeType Polygon

FeatureTypeSimple

AliasName PLSSIntersected

Description ThefullyintersectdataistheatomiclevelofthePLSSthatissimilartothecoverageorthesmallestpiecesusedtobuildthePLSS.Polygonsmayoverlapinthisfeatureclass.

Purpose Thefullyintersectedpolygonsareusedforconversionandformaintenance.ThiscontainstheatomicandfullyattributedcomponentsoftheotherPLSSfeatures.


26

ThisisausefuldatasetformaintenanceandmaybeneededbyconsumerswhorelyontheNSDIdataforproduction.

DataThemeCadastral


STATEABBR String 2 StateAbbreviation

Stateabbreviationcodetwoletterpostalcode

PRINMERCD String 2 PrimeMeridianCode

PrincipalmeridiancodefromtheBLMPMCodelist

PRINMER String 40 PrimerMeridianDiscussion

Principalmeridiannameasatext

TWNSHPNO String 3 PLSSTownshipNumber

Townshipnumber.TheTownshipNumberindicatesthenumberofrowsoftownships,northorsouthfromaPublicLandSurveySystemOrigin.

TWNSHPFRAC String 1 PLSSTownshipFraction

Townshipfraction.TownshipFractionsarecreatedwhentherearegapsbetweensurveyedTownshipboundariesorduetoexcesssizeinTownshipsthatarosefromexecutingoriginalsurveys.

TWNSHPDIR String 1 PLSSTownshipDirection

Townshipdirection.ThedirectionofarowofTownshipsfromaPublicLandSurveySystemOrigin.ThesearetypicallyNorthandSouthintheWestbutmaybeEastandWestinOhio

RANGENO String 3 PLSSRangeNumber

Rangenumber.TheRangeNumberindicatesthenumberofcolumnsoftownships,eastorwestfromaPublicLandSurveySystemOrigin.

RANGEFRAC String 1 PLSSRangeFraction

Rangefraction.RangeFractionsarecreatedwhentherearegapsbetweensurveyedTownshipboundariesorduetoexcesssizeinTownshipsthatarosefromexecutingoriginalsurveys.

RANGEDIR String 1 PLSSRangeDirection

Rangedirection.ThedirectionofacolumnoftownshipsfromaPublicLandSurveySystemOrigin.ThesearetypicallyEastorWestinthewestbutmaybenorthorsouthinOhio

TWNSHPDPCD String 1 PLSSTownshipDuplicate

IftherearemultipletownshipsinaPublicLandSurveySystemOrigin,Stateand


27

SurveyName,theTownshipDuplicateStatusisusedtoestablishuniqueness.WhenmorethanonePublicLandSurveySystemTownshiphasthesameTownshipandRangenumbersanddirectionsandfractions,andareinthesameState,thisattributeisusedtodistinguishamongduplicatevalues.


STEWARD String 50 PLSSDataSteward

Datastewardforaparticulartownship.

TWNSHPLAB String 20 PLSSTownshipLabel

Townshiplabelthatisusedforcartographicoutputorwebdisplay

FRSTDIVID String 22 PLSSFirstDivisionIdentifier

ThisisauniqueidentifierforthefirstdivisionthatisbuiltbyappendingthefirstdivisionelementsontheTownshipidentifier.

FRSTDIVNO String 3 PLSSFirstDivisionNumber

Thisisthenumber,letterordesignatorforthefirstdivisionofthePLSSTownship

FRSTDIVDUP String 1 PLSSFirstDivisionDuplicate

Thisisacodetoindicatewhetherthefirstdivisionisaduplicatedareaoridentifier

FRSTDIVTYP String 2 PLSSFirstDivisionTypeCode

Thisisthetypeoffirstdivisionandiscommonlythesectionbutmaybealot,parcel,tractorotherdivision.

FRSTDIVTXT String 50 PLSSFirstDivisionTypeText

Thisisthefirstdivisiontypeasatextfield

FRSTDIVLAB String 5 PLSSFirstDivisionTypeLabel

Thisisthelabelforthefirstdivisionthatisusedforcartographicofwebdisplaypurposes.

SECDIVID String 25 PLSSSecondDivisionIdentifier

Uniqueidentifierfortheseconddivision.

SECDIVNO String 50 PLSSSecondDivisionNumber

Seconddivisionnumberoraliquotpartreference.

SECDIVSUF String 10 PLSSSecondDivisionSuffix

Seconddivisionsuffix.

SECDIVTYP String 1 PLSSSecondDivisionType

Codeofthetypeofseconddivision.


28

SECDIVNOTE String 50 PLSSSecondDivisionNote

Codeforthesurveynoteoftheseconddivision

SECDIVTEXT String 50 PLSSSecondDivisionTypeText

Seconddivisiontypetextdescription

SECDIVLAB String 50 PLSSSecondDivisionLabel

PLSSSecondDivisionlabelforcartographicoutputorwebdisplay.

SURVTYP String 1 PLSSSpecialSurveyTypeCode

Codeofthetypeofspecialsurvey.

SURVTYPTEXT String 50 PLSSSpecialSurveyTypeText

Specialsurveytypetextdescription.

SURVNO String 10 PLSSSpecialSurveyNumber

Specialsurveynumber.

SURVSUF String 5 PLSSSpecialSurveySuffix

Specialsurveysuffixdesignationthatmakestheidentificationoftheareaunique.

SURVNOTE String 50 PLSSSpecialSurveyTypeNote

Notesaboutthepolygonfeaturethatareimportantforusingorunderstandingthefeature.FromtheBLMSurvNotesareA=ApproximateAcreage,C=ConflictorQuestionable,D=Non‐addedAcreage

SURVLAB String 50 PLSSSpecialSurveyNote

Labelthatisusedforcartographicoutputorwebdisplay.

ACRES Double 8 PLSSSpecialSurveyAreainAcres

Areaoftheseconddivisioninofficialacres.

QSEC String 4 QuarterSection

Quartersectionreference

GOVLOT String 4 GovernmentLotNumber

ThesearetheGovernmentLots

QQSEC String 4 QuarterQuarterSection

ThisisthequarterquarterPLSSreference

PLSSPoint‐FeatureClass

Name PLSSPoint

ShapeType Point

FeatureTypeSimple

AliasName PLSSPoint


29

Description ThesearethecornersofthePLSS.Thisdatasetcontainssummaryinformationaboutthecoordinatelocationandreliabilityofcornercoordinateinformation.

Purpose ToprovidetheessentialobservedcoordinateinformationforPLSScorners.Thisisnotthecompletedatasetforcorners.Thesearethemostcurrentcoordinates.TheNationalPLSSpointidentifierdocumentationisprovidedinAppendixB.

DataThemeCadastral


POINTLAB String 6 CornerPointLabel

PLSSPointlabelforcartographicoutputorwebdisplay.

POINTID String 24 CornerPointIdentifier

Uniquepointidentifierforthecornerthatfollowsthenationalpointidentificationstandard

PLSSID String 16 PLSSAreaIdentification

Concatenationoftheprincipalmeridian,township,range,andduplicationcodethatformauniqueidentifierforthetownship.Ifacornerisinmultipletownships,onaborder,thisisthePLSSIDforthelowestGCDBnumber.

XCOORD Double 8 XorEastCoordinate

X,longitudeoreastcoordinatevalueforthecorner.

YCOORD Double 8 YorNorthCoordinate

Y,latitudeornorthcoordinatevalueforthecorner

ZCOORD Double 8 ZorHeightCoordinate

Z,Height,ObservedElevationforthecorner

ELEV Double 8 AverageTownshipElevation

ThisisanaverageelevationfortheentirePLSSTownship

ERRORX SmallInteger 2 ErrorinX TheerrorintheXdirection

ERRORY SmallInteger 2 ErrorinY Theerrorintheydirection

ERRORZ SmallInteger 2 ErrorinZ TheerrorintheZdirection

HDATUM String 20 HorizontalDatum

thehorizontaldatumforthecoordinatevalue,thisisthedatumthereportedcoordinatevalueisreportedinandmaybedifferentthantheGIShorizontaldatum

VDATUM String 20 VerticalDatum

TheverticaldatumforanobservedZorheight

STEWARD1 String 50 Stewardfor theprimarydatastewardfortheplss


30

thePLSSPoint

point

STEWARD2 String 50 SecondStewardforPLSSPoint

theseconddatastewardforthePLSSpointifthereisasecondsteward,suchasonacountyboundaryorafederalownershipboundary

LOCAL1 String 25 FirstPLSSPointAlternateName

thefirstaliasforthecontrolpoint,mostcommononPLSSTownshipboundaries

LOCAL2 String 25 SecondPLSSPointAlternateName

thesecondlocalidentifieroralias.MostcommononcornersonPLSStownshipboundaries

LOCAL3 String 25 ThirdPLSSPointAlternateName

thethirdaliasforthecontrolpointmostcommononPLSSTownshipboundaries

LOCAL4 String 25 FourthPLSSPointAlternateName

thefourthaliasforthecontrolpointmostcommonwhenaPLSScorneriscommontoaspecialsurvey

RELY String 15 PLSSPointReliability

Thereliabilityoraccuracyofcoordinatevalueasasingleentry,maybeacodedvalue

COORDPROC String 20 CoordinateComputationProcedure

Thecoordinatecomputationprocedurewhichtypicallyreflectstheadjustmentmethodorastandardfollowedtocomputethecoordinatefromthefieldobservation

COORDSYS String 20 CoordinateSystem

thecoordinatesystemforthecoordinatevalue,thismaybedifferentthantheGIScoordinatesystemifthereportedx,yvaluesaredifferentthantheGIScoordinatesystem.

COORDMETH String 25 CoordinateCollectionMethod

themethodofobservationormeasurementforthecoordinatevalue.ThistypicallyindicatesatechnologysuchasGPS,digitized,lineofsight


ThelastrevisiondateforthecoordinatevalueforthePLSSCorner


31

PLSSQuarterReference‐FeatureClass

Name PLSSQuarterReference

ShapeType Polygon

FeatureTypeSimple

AliasName PLSSFirstDivision

Description ThePLSSQuarterSectionReferenceisacompanionfeatureclassforthePLSSReferenceGridthatprovidesaquartersectiondivisionofthesectionsforreferenceonly.

Purpose Thisisamappedreferencegridusedtosupportsomewebandrapidqueryapplications

DataThemeCadastral


PLSSID String 16 PLSSIdentifier ThisistheuniqueidentifierforthePLSSTownshipinwhichthefirstdivisionislocated.Concatenationoftheprincipalmeridian,township,range,andduplicationcodethatformauniqueidentifierforthetownship.

REFGRIDNO String 20 ReferenceGridNumber

Thenumberforthereferencegrid.SomejurisdictionsassignaletterornumberdivisionsofthePLSS

REFGRIDNOM String 4 ReferenceGridNominalLocation

Thenominallocationofthereferencegridcellorfeature

REFGRIDDUP String 2 ReferencegridDuplication

Aduplicatecodetoindicateifthecellorfeatureofthereferencegridisaduplicate

QSECTION String 16 QuarterSection

thequartersectionlabel

REFSOURCE String 16 SourceReference

ThereferencetothesourcedocumentcouldbeareferencetoamaporplatoradatasetsuchasGCDB


Codeofthetypeofsurvey.Thisindicatesifthetownshipquarterreferencehasbeensurveyed,protractedorunprotracted(extended)




32

PLSSReferenceGrid - FeatureClass

Name PLSSReferenceGrid

ShapeType Polygon

FeatureType Simple

AliasName PLSSReferenceGrid

Description ThereferenceGridisageneralizeddatasetprovidingtheTownshipandFirstDivisionsofthePLSSasaseparatefeatureclasstosupportdatarequests,mappingandindexing.Thespatiallocationandpositionandattributesofthisfeatureclassarethesameasthoseintheprimarydatasetsfromwhichthisdataisbuilt.Thesedataareoftenusedformapsheetlayoutsandgenerallocationreference

Purpose Thisfeatureclasssupportsindexingandrapidreferenceandquerygenerallyforwebapplicationsaswellasmapbookandmapsheetlayouts

DataThemeCadastral



REFGRIDNO String 20 ReferenceGridNumber

Number,letterordesignatorforthefirstdivisionofthePLSSTownship.

REFGRIDNOM String 4 ReferenceGridNominalLocation

Number,letterordesignatorforthenominalfirstdivisionofthePLSSTownship.

REFGRIDDUP String 2 ReferenceGridDuplicateIndicator

Codetoindicatewhetherthefirstdivisionisaduplicated.

EXPIRDATE String 16 ExpirationDate Expirationdateforthedataset.Thisisthedatethedatasetisexpectedtobeupdated.

SOURCEREF String 25 ReferencetoSourceorSteward

ThereferencetothesourcedocumentcouldbeareferencetoamaporplatoradatasetsuchasGCDB


33

PLSSSecondDivision‐FeatureClass

Name PLSSSecondDivision

ShapeType Polygon

FeatureTypeSimple

AliasName PLSSSecondDivision

Description TheseconddivisionofthePLSSisquarter,quarter‐quarter,sixteenthorgovernmentlotdivisionofthePLSS.Thesecondandthirddivisionsarecombinedintothisfeatureclassasanintentionalde‐normalizationofthePLSShierarchicaldata.Thepolygonsinthisfeatureclassrepresentthesmallestdivisiontothesixteenththathasbeendefinedforthefirstdivision.ForexampleInsomecasessectionshaveonlybeendividedtothequarter.DivisionsbelowthesixteenthareintheSpecialSurveyorParcelFeatureClass.

Purpose ThisfeatureclassprovidesthegraphicofthealiquotorgovernmentlotdivisionsofthePLSStownship

DataThemeCadastral


SECDIVID String 25 SecondDivisionIdentifier

Uniqueidentifierfortheseconddivision.

FRSTDIVID String 25 FirstDivisionIdentifier

Uniqueidentifierforthefirstdivision.

SECDIVNO String 50 SecondDivisionNumberorDesignator

Seconddivisionnumberoraliquotpartreference.

SECDIVSUF String 10 SecondDivisionSuffix

Seconddivisionsuffix

SECDIVTYP String 1 SecondDivisionTypeCode

Codeofthetypeofseconddivision.

SECDIVTXT String 50 SecondDivisionTypeText

Seconddivisiontypetextdescription

ACRES Double 8 AreainAcres Areaoftheseconddivisioninofficialacres.

PLSSID String 16 PLSSTownshipIdentifier

Concatenationoftheprincipalmeridian,township,range,andduplicationcodethatformauniqueidentifierforthetownship.

SECDIVLAB String 50 SecondDivisionLabel

PLSSSecondDivisionlabelforcartographicoutputorwebdisplay.


34

PLSSSpecialSurvey‐FeatureClass

Name PLSSSpecialSurvey

ShapeType Polygon

FeatureTypeSimple

AliasName PLSSSpecialSurvey

Description SpecialSurveysarenon‐PLSSsurveyareasfromBLMsurveyrecordswhichrepresentfederalparcels

Purpose Thesearethegraphicrepresentationoflandtransactionsinthefederalgovernmentandmaybethoughtofasthefederalparcels

DataThemeCadastral



Codeofthetypeofspecialsurvey.


Specialsurveytypetextdescription.

SURVNO String 10 SpecialSurveyNumber

Specialsurveynumber.

SURVSUF String 5 SpecialSurveyNumberSuffix

Specialsurveysuffixdesignationthatmakestheidentificationoftheareaunique.

SURVNOTE String 50 SpecialSurveyNote

Notesaboutthepolygonfeaturethatareimportantforusingorunderstandingthefeature.FromtheBLMSurvNotesareA=ApproximateAcreage,C=ConflictorQuestionable,D=Non‐addedAcreage

ACRES Double 8 AreainAcres Officialareaofthesurveyinacresasanumber.

SURVLAB String 50 SpecialSurveyLabel

Labelthatisusedforcartographicoutputorwebdisplay.

REVISEDDATE Date 8 RevisedDate Thelastdateofrevisionforthespecialsurvey,becausespecialsurveysrepresentfederallandtransactionstheymayhavedistinctrevisiondates.


35

PLSSTownship‐FeatureClass

Name PLSSTownship

ShapeType Polygon

FeatureType Simple

AliasName PLSSTownship

Description InthePublicLandSurveySystemaTownshipreferstoaunitoflandthatisnominallysixmilesonaside,usuallycontaining36sections.

Purpose ThesearethegraphicdisplaysofthePLSSTownships.

DataTheme Cadastral


STATEABBR String 2 StateAbbreviation

Stateabbreviationcodetwoletterpostalcode

PRINMERCD String 2 PrimeMeridianCode

PrincipalmeridiancodefromtheBLMPMCodelist

PRINMER String 40 PrimeMeridianText

Principalmeridiannameasatext

TWNSHPNO String 3 PLSSTownshipNumber

Townshipnumber.TheTownshipNumberindicatesthenumberofrowsoftownships,northorsouthfromaPublicLandSurveySystemOrigin.

TWNSHPFRAC String 1 PLSSTownshipFraction

Townshipfraction.TownshipFractionsarecreatedwhentherearegapsbetweensurveyedTownshipboundariesorduetoexcesssizeinTownshipsthatarosefromexecutingoriginalsurveys.

TWNSHPDIR String 1 PLSSTownshipDirection

Townshipdirection.ThedirectionofarowofTownshipsfromaPublicLandSurveySystemOrigin.ThesearetypicallyNorthandSouthintheWestbutmaybeEastandWestinOhio

RANGENO String 3 PLSSRangeNumber

Rangenumber.TheRangeNumberindicatesthenumberofcolumnsoftownships,eastorwestfromaPublicLandSurveySystemOrigin.

RANGEFRAC String 1 PLSSRangeFraction

Rangefraction.RangeFractionsarecreatedwhentherearegapsbetweensurveyedTownshipboundariesorduetoexcesssizeinTownshipsthatarosefromexecutingoriginalsurveys.

RANGEDIR String 1 PLSSRangeDirection

Rangedirection.ThedirectionofacolumnoftownshipsfromaPublicLandSurveySystemOrigin.ThesearetypicallyEastorWestinthewestbutmaybenorthorsouthinOhio


36

TWNSHPDPCD String 1 PLSSTownshipDuplicateCode

IftherearemultipletownshipsinaPublicLandSurveySystemOrigin,StateandSurveyName,theTownshipDuplicateStatusisusedtoestablishuniqueness.WhenmorethanonePublicLandSurveySystemTownshiphasthesameTownshipandRangenumbersanddirectionsandfractions,andareinthesameState,thisattributeisusedtodistinguishamongduplicatevalues.

PLSSID String 16 PLSSTownshipIdentifier

Concatenationoftheprincipalmeridian,township,range,andduplicationcodethatformauniqueid.

STEWARD String 50 DataStewardforPLSSTownshipData

Datastewardforatownship.

TWNSHPLAB String 20 PLSSTownshipLabel

Townshiplabelthatisusedforcartographicoutputorwebdisplay

SRVNAME String 60 SurveyNameforOhioPLSSSurveys

TheOhioNamedsurveyarea,PLSSoriginalsurveyareas

SECSRVNAME String 60 SecondarySurveyNameforOhioSurveys

ThesecondarynameforOhiosurveyarea,PLSSoriginalsurveyareas


Codeofthetypeofsurvey.Thisindicatesifthetownshiphasbeensurveyed,protractedorunprotracted(extended)



SurveySystem‐FeatureClass

Name SurveySystem

ShapeType Polygon

FeatureTypeSimple

AliasName SurveySystem

DataThemeCadastral


SURVSYSTYPE String 50 Survey SurveySystemTypeindicatesthe


37

SystemType categoryormajorclassofthedescription.

SURVSYSNAME String 200 SurveySystemName

TheSurveySystemNameisanidentifyingnameornumberforaspecifictypeofSurveySystemarea.

SURSYSCODE String 50 SurveySystemCodeorIndex

anycodesorindicesfortrackingormanagingthesurveysystemareas

SURSYSNOTE String 50 SurveySystemNote

anynotesontheuse,nameorapplicationofthesurveysystemarea

FIRSTDIVTYPE String 50 SurveySystemFirstDivision

TheFirstDivisionTypedescribestheclassificationoftheFirstSurveySystemDivision

FIRSTDIVNAME String 50 SurveySystemFirstDivisionName

TheSurveySystemFirstDivisionNameisanalpha,numeric,oralpha‐numericdesignatorusedtoidentifytheFirstDivisionoftheSurveySystem

SECDIVTYPE String 50 Survey System Second Division Type

The Second Division Type describes the classification of the Survey System Second Division.

SECDIVNAME String 50 SurveySystemSecondDivisionName

TheSurveySystemSecondDivisionNameisanalpha,numeric,oralpha‐numericdesignatorusedtoidentifytheSecondDivisionoftheSurveySystem.


38

Parcels‐FeatureDataset

Name Parcels

Description Thisfeaturedatasetcontainsinformationabouttherightsandinterestsinlandincludingrealestateassets.Forthepublicationthisfeaturedatasetcontainstheparceldataonly

DataThemeCadastral

NSDICoreParcel - FeatureClass

Name NSDICoreParcel

ShapeType Polygon

FeatureType Simple

AliasName NSDICoreParcel

Description This is the parcel publication Cadastral NSDI or core data set that supports emergency response and other business applications

Purpose This data set is intended to provide the initial information needed to respond to and serve business applications. This data set has been developed by the FGDC Cadastral Subcommittee.

DataTheme Cadastral


STNAME String 2 StateName Thestatename

STFIPS String 2 StateFIPSCode

ThestateFIPScode

CNTYNAME String 50 CountyName Thecountyname

CNTYFIPS String 2 CountyFIPSCode

thecountyFIPScode3digitcode

SOURCEAGENT String 50 DataSourceAgency

Theagencythatprovidedthedata,thedatasteward

PARNO String 30 LocalParcelNumber

Thelocalparcelnumberfortheparcelrecord

NPARNO String 40 NationalParcelNumber

ThelocalparcelnumberwiththestateandcountyFIPSCodeaddedtothebeginningofthenumber

STRUCT String 1 Structure Isthereastructureorimprovementon


39

Indicator theparcel(yesorno)

IMPROVVAL Integer 4 ImprovedValue

Thevalueoftheimprovementsontheparcels

LANDVAL Integer 4 LandValue Thevalueofthelandontheparcel

PARVAL Integer 4 TotalParcelValue

Thetotalvalueoftheparcel

PARVALTYPE String 15 TypeofValueReported

Thetypeofvaluereportedintheparcelvaluefields

PARUSECODE String 10 TaxParcelUseCode

Thelocalassessmentparcelusecode

PARUSEDESC String 50 TaxParcelUseCodeDescription

Thelocalassessmentparcelusedescription

OWNTYPE String 20 OwnerClassificationorType

TheownertypebasedonthetypeslistedintheLU_OWNTYPEtable

AREATXT String 20 AreaofParcelasText

Theareaoftheparcelinacresasatext

AREANO Single 4 AreaofParcelasNumber

Theareaoftheparcelinacresasanumber

OWNNAME String 100 FullOwnerName

Theprimarysurfaceownername,thefullnamemaybepopulatedorthecomponentsofthename(firstandlast)

OWNFRST String 50 OwnerFirstName

Theprimarysurfaceownerfirstname

OWNLAST String 50 OwnerLastName

Theprimarysurfaceownerlastname

SUBSURFOWN String 60 SubsurfaceOwnerName

Thenameofthesubsurfacerightslandowner

SUBOWNTYPE String 20 SubsurfaceOwnerType

ThesubsurfaceownertypebasedonthetypeslistedintheLU_OWNTYPEtable

MAILADD String 65 FullMailingAddress

Thefullmailingaddressasasinglefield,themailingaddressmayalsobebrokenintoitscomponentparts

MADDRNO String 10 MailingAddressNumber

Themailaddressnumber

MADDSTNAME String 55 MailingAddressStreetFullName

Thefullnameofthemailingstreetincludingtheprefix,thename,thesuffixthetypeanddirections


40

MADDPREF String 5 MailingAddressPrefix

Themailingstreetprefix

MADDSTR String 40 MailingAdressStreetName

themailingstreetname,thenamewithoutthetypeanddirections

MADDSTTYP String 5 MailingAddressStreetType

Themailingstreettype,suchasST,AVE,BLVD

MADDSTSUF String 5 MailingAddressStreetSuffix

Themailingstreetsuffix,typicallyadirection

MUNIT String 10 MailingAddressUnitNumber

Themailingaddressunit,suiteorapartmentnumberandmayalsobethehalfnumber

MCITY String 40 MailingAddressCity

Themailingcityname

MSTATE String 2 MailingAddressState

Themailingstatename,twoletterabbreviation

MZIP String 15 MailingAddressZip

Themailingzipcode

SITEADD String 65 FullSiteAddress

Thefullsiteaddressasasinglefield,themailingaddressmayalsobebrokenintoitscomponentparts

SADDNO String 10 SiteAddressNumber

Thesiteaddressnumber

SADDSTNAME String 55 SiteAddressStreetFullName

Thefullnameofthesitestreetincludingtheprefix,thename,thesuffixthetypeanddirections

SADDPREF String 5 SiteAddressPrefix

Thesitestreetprefix

SADDSTR String 40 SiteAddressStreetName

thesitestreetname,thenamewithoutthetypeanddirections

SADDSTTYP String 5 SiteAddressStreetType

Thesitestreettype,suchasST,AVE,BLVD

SADDSTSUF String 5 SiteAddressStreetSuffix

Thesitestreetsuffix,typicallyadirection

SUNIT String 10 SiteAddressUnitNumber

Thesiteaddressunit,suiteorapartmentnumberandmayalsobethehalfnumber

SCITY String 40 SiteAddressCity

Thesiteaddresscityname

LEGDECFULL String 255 FullLegalDescription

Thefulltaxlegaldescription‐thisisgenerallyneededwhentheparceldata


41

doesnotincludeamapoftheparcel

SOURCEDATE Date 8 SourceDocumentDate

Thedateofthesourcedocumentthatwasusedtogeneratetheparcelinformation

SOURCEREF String 25 SourceDocumentLinkorReference

Thereferencetothesourcedocumentcouldbeareferencetoamaporplatoradeed


Thedateofthelastrevisionoftheparcelrecord,thismaybetheinitialcreatedateifthatisthelastrevision

LU_Direction - Table

Name LU_Direction

AliasName LU_Direction

Description Look up table for direction codes N, E, S, W

Purpose To provide a domain for referencing source information or translating incoming data sets

DataTheme Cadastral


DirCode String 1 DirectionCode

theoneletterdirectioncode(N,S,E,W)

Name String 5 Direction Thefulltextforthedirection

LU_OwnerType‐Table

Name LU_OwnerType

AliasNameLU_OwnerType

Description The type of ownership is the classification of owner. In some local governments tax parcels are tagged as either taxable or exempt and the owner classification is not known. In these cases an owner types of taxable and exempt may be added to this list.


DataTheme Cadastral


OwnerTypeCD String 1 OwnerType acodefortheownertype


42

Code

OwnerTypeDesc String 50 OwnerTypeDescription

thefulldescriptionoftheownertype

LU_ParcelValueType - Table

Name LU_ParcelValueType

AliasName LU_ParcelValueType

Description This is a list of the types of values for the parcel value types in the core parcel attributes. Local governments and other data stewards for parcel data may maintain a variety of values such as sales values, current market value taxable value or assessed value. This field indicates what type of value is reported in the core attributes


DataTheme Cadastral Field DataType Length AliasName Description

PARVALTYPE String 15 ParcelValueType

Listofvaluesfortheparcelvaluesforincomingdata

LU_PLSSFirstDiv - Table

Name LU_PLSSFirstDiv

AliasName LU_PLSSFirstDiv

Description The First Division Type of a Public Land Survey System Township is the primary or first subdivision category. If the first division type is fractional section, then the metadata for this data set will need to document how fractional sections are labeled.


DataTheme Cadastral


PLSSFirstDiv String 25 PLSS First Division Type Code

The values for the first division types

PLSSFirstDivDesc String 250 PLSS First Division Type

a description of the division types


43

Description

LU_PLSSSecDiv‐Table

Name LU_PLSSSecDiv

AliasNameLU_PLSSSecDiv

Description TheSecondDivisionTypeofaPublicLandSurveySystemTownshipisthesecondsubdivisioncategory.Theseconddivisionhasbeende‐normalizedslightlytoincludeacompletenon‐overlappingrepresentationofthedivisionsofthePLSS

Purpose Toprovideadomainforreferencingsourceinformationortranslatingincomingdatasets

DataThemeCadastral


PLSSSecDiv String 25 PLSSSecondDivisionTypeCode

Thevaluefortheseconddivisiontypes

PLSSSecDivDesc String 250 PLSSSecondDivisionTypeDescription

Adescriptionoftheseconddivisiontypes

LU_PrincipalMeridian‐Table

Name LU_PrincipalMeridian

AliasNameLU_PrincipalMeridian

Description thecodesandnamesoftheprincipalmeridians


DataThemeCadastral


PrincipalMeridian String 50 PrincipalMeridianFullName

thenameoftheprincipalmeridian

PMCode String 2 PrincipalMeridianCode

theblmtwodigitcodefortheprincipalmeridian

PMShortName String 25 Principal theshortnamefortheprincipalmeridian


44

MeridianShortName

LU_State‐Table

Name LU_State

AliasNameLU_State

Description statenamesandfipscodesandabbreviations


DataThemeCadastral


StateName String 30 StateName thestatename

StateCD String 2 StatePostalAbbreviation

thestate2letterabbreviation

StateFIPSCD SmallInteger 2 StateFIPSCode

thetwodigitstatefipscode

LU_SurSysDivision - Table

Name LU_SurSysDivision

AliasNameLU_SurSysDivision

Description Thistableprovidesthedomainofvaluesforthefirstandseconddivisionsofsurveysystems.Thesewerecombinedbecausethedivisiontypescanbecombinedandmayvaryfromstatetostate.


DataThemeCadastral


SurSystDivCode String 5 SurveySystemDivisionCode

codesforthesurveysystemdivisions

SurSysDivName String 50 SurveySystemDivisionName

thenameofthesurveydivision

SurSysDivDesc String 200 Survey adescriptionofthesurveydivision


45

SystemDivisionDescription

LU_SurveyNameOhio‐Table

Name LU_SurveyNameOhio

AliasNameLU_SurveyNameOhio

DescriptionPublicLandsurveyareasinOhioareidentifiedbyaname.ThenamedareasdonotanoriginofPublicLandSurveySystemvalue.


DataThemeCadastral


SRVNAME String 60 OhioSurveySystemName

ThenamedsurveyareaswithinOhio

SECSRVNAME String 60 OhioSecondarySurveySystemName

thesecondarynameswithinthenamedareas.Thereareonlytwonamedareaswithasecondarysurveynamedareawithinthem

LU_SurveySystem‐Table

Name LU_SurveySystem

AliasNameLU_SurveySystem

Description Thisisalistofsurveysystemtypes


DataThemeCadastral


SurvSysTypeCode String 5 SurveySystemTypeCode

codesforthesurveysystemtypes

SurvSysType String 50 SurveySystemTypeText

thenameofthesurveysystemtype


46

SurvSysDescription String 250 SurveySystemTypeDescription

thedescriptionofthesurveysystemtype

LU_SurveyType‐Table

Name LU_SurveyType

AliasNameLU_SurveyType

DescriptionValuesforthefederalsurveytypes.Thisincludesthespecialsurvey,firstandsecondsurveydivisiontypes.


DataThemeCadastral


SurveyTypeCD String 2 SpecialSurveyTypeCode

thesurveytypecode

SurveyTypeName String 50 SpecialSurveyTypeText

thenameofthesurveytype

Description String 200 SpecialSurveyTypeDescription

thedescriptionofthesurveytype


47

AppendixB–PLSSCornerStandardIdentifier

IntroductionThispaperdescribesastandardpointidentifierforPublicLandSurveySystem(PLSS)corners.ThisstandardpointidentifierconformstotherequirementsoftheFederalGeographicDataCommittee(FGDC)CadastralDataContentStandardrequirementsforauniqueidentifierforcadastralcorners.Thestandardsystempresentedhereallowspublishedcoordinateinformationtoberelatedtosourcedataandtoperpetuatecorneridentifiersascoordinatevaluesforcornersareimprovedovertime.TheuniquenessofthesurveypointidswillhelpfacilitatedatamaintenanceanddatasharingwithintheBureauoflandmanagement(BLM)andotherCadastralReferencedatastewards.Thispaperdescribestheformatandstructureofthecornerpointidentifiersforthepublicationofcornerinformationthatconformstothenationalcadastraldatastandards.PLSSPointsTheGeographicCoordinateDataBase(GCDB)usesasix‐digitnumberingsystemtonamePLSSpointsinatownship.Thissix‐digitcornernumberisonlyuniquewithinaPLSStownship.Thisnumberisrepeatedineachtownship,tomakeiteasiertodeterminethelocationofacornerwithinaTownshipbyitsnumber.Thefirstthreedigitsofthisnumberrefertotheeast‐westpositioninthetownship.Thesecondthreedigitsindicatethenorth‐southpositioninatownship.Thefollowingpictureshowsthecornernumberingconventionforasingletownshipsubdivideddowntosections.Thisnumberingschemeisrepeatedineachtownship.


48

Duetothisnamingconvention,fouradjacenttownshipswillnamethesamecornerfourdifferentways(100100,100700,700700,700100).Eachcornernumbershouldhavetheexactsamecoordinatevaluesbecausethisisinfactthesamecorner.Thefollowingpictureshowsanexampleofthepointduplicationattownshipcornersandtownshiplineswheresectionssubdivisionsarecoincident.


49

UniquePLSSCornerNumbersTomakethecornernumbersunique,theproposalistoaddapointprefixtothePLSScornernumber.ThisprefixisaconcatenationoftheState,PrincipalMeridian,TownshipandRangeinwhichthepointresides.ThispointprefixcanbederivedfromthedirectorystructureoftheoutputdirectoryfromtheBLM’sDataPreparationSoftware(DCCSV1.04)orfromtheattributesinthestandardPLSSTownshipFeatureclassesandisastandard15characterslong.ThisidentifierhasbeentermedthetownshipidentifierorTWIPinothersystems.Theuniquenessisestablishedbymakingabusinessrulethatthelowestsixdigitcornernumberwillbecometheprimarynumberandallothernumberswillbecomealiasesorothercornernumbersforthesamecorner.Thefollowingdiagramshowstheproposedcornernumberingconvention.

Township duplicate (0, A or B) State Township Range

AZ230490N0130W0_240400

GCDB Point ID Principal Meridian (2 digit code) Township and Range ( 5 characters) 3 digits for Township or Range number

1 digit for fraction 0 for no fraction, 1 for ¼ township, 2 for ½ township, 3 for ¾ township

1 letter for direction


50

References

AuthorityandAuthoritativeSources:ClarificationofTermsandConceptsforCadastralData(2008),http://www.nationalcad.org/showdocs.asp?docid=1045&navsrc=Report&navsrc2=

Becauseoflegalissuesrelatedtoownershipandrightsinlandtheuseofthetermsauthorityandauthoritativeforcadastraldataneedtobeclearlyarticulated.Thisdocumentdefinesanddiscussesthetermsauthoritativedata,authoritativedatasource,authoritativesource,authority,authorization,datastewards,trustedsourceandtrusteddataintermsthatcanbeappliedtoanydatasourcewithexamplesthatapplyspecificallytocadastraldata.

CadastralNSDIReferenceDocument,(2007)http://www.nationalcad.org/showdocs.asp?docid=158&navsrc=Report&navsrc2=

Thisdocumentreplacesthecoredatastandard.ThisdocumentdescribesthedataandorganizationalrelationshipsforthemaintenanceofthedatathatistheCadastralNSDI.ThisdocumentservesasastandardfortheCadastralNSDIcontent.

IAAOandFGDCCadastralSubcommitteeWorkshop:SharingParcelDatatoProtectandRebuildCommunities(2008),http://www.nationalcad.org/showdocs.asp?docid=1030&navsrc=Report&navsrc2=

IAAOandFGDCCadastralDataSubcommitteesponsoredaworkshoponFeb25,2008atthe2008GIS/CAMATechnologyConference.Thepurposeoftheworkshopwastoexploretheadvantages,opportunitiesandissuesofsharingparceldatafromgovernmenttogovernment.

NationalSpatialDataInfrastructure(2008)http://www.fgdc.gov/nsdi/nsdi.html

ThiswebpagedefinesthehistoryandprinciplesofthenationalSpatialDataInfrastructure.

ProductionandPublicationAConceptforGeographicInformationEnvironments,(2002),http://www.nationalcad.org/showdocs.asp?docid=22&navsrc=Report&navsrc2=

Theproductionenvironmentistheproductionandmaintenancecomponentforgeographicinformation.Thepublicationenvironmentistheconsumptiveenvironment.Thisdocumentdescribestheseconceptsandenvironments

CadastralSubcommitteeMeetingNotes,(2003)PortlandOregon,hostedbytheForestService,http://www.nationalcad.org/showdocs.asp?docid=1048&navsrc=Organization&navsrc2=MeetingDoc

ThesemeetingnotessummarizesomeoftheearlydiscussionsonthepolicesandneedsforestablishingarobustCadastralPublicationDataStandardfortheNSDI.

cadastral publication guideline and template · cadastral publication data components ......

Documents