<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20230831</CreaDate>
<CreaTime>14543000</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
<itemName Sync="TRUE">parcels_sd2</itemName>
<itemSize Sync="TRUE">0.000</itemSize>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_California_VI_FIPS_0406_Feet</projcsn>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.9.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_California_VI_FIPS_0406_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,6561666.666666666],PARAMETER[&amp;quot;False_Northing&amp;quot;,1640416.666666667],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-116.25],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,32.78333333333333],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,33.88333333333333],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,32.16666666666666],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2230]]&lt;/WKT&gt;&lt;XOrigin&gt;-118608900&lt;/XOrigin&gt;&lt;YOrigin&gt;-91259500&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121918&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102646&lt;/WKID&gt;&lt;LatestWKID&gt;2230&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<SyncDate>20230817</SyncDate>
<SyncTime>10505400</SyncTime>
<ModDate>20230817</ModDate>
<ModTime>10505400</ModTime>
</Esri>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdDateSt Sync="TRUE">20230817</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
<distributor>
<distorCont>
<rpOrgName>SanGIS</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(858) 874-7000</voiceNum>
<faxNum>(858) 874-7002</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>5510 Overland Avenue, Suite 230</delPoint>
<city>San Diego</city>
<adminArea>California</adminArea>
<postCode>92123</postCode>
<country>US</country>
<eMailAdd>webmaster@sangis.org</eMailAdd>
</cntAddress>
</rpCntInfo>
<displayName>SanGIS</displayName>
<role>
<RoleCd value="005"/>
</role>
<rpIndName>Data Librarian</rpIndName>
<rpPosName>Data Librarian</rpPosName>
</distorCont>
<distorOrdPrc>
<ordInstr>Refer to SanGIS website (www.sangis.org) to obtain
further information on mapping and data extraction services available from SanGIS.</ordInstr>
</distorOrdPrc>
</distributor>
<distTranOps>
<transSize Sync="TRUE">0.000</transSize>
</distTranOps>
</distInfo>
<dataIdInfo>
<idCitation>
<resTitle Sync="TRUE">parcels_sd2</resTitle>
<resRefDate>
<refDate>20060930</refDate>
<refDateType>
<DateTypCd value="001"/>
</refDateType>
</resRefDate>
<resEdDate>20060930</resEdDate>
<citRespParty>
<rpOrgName>SD County- SanGIS</rpOrgName>
</citRespParty>
<date>
<pubDate>2023-07-24T00:00:00</pubDate>
</date>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Parcels represent taxable pieces of property. A parcel is created by the San Diego County Assessor/Recorder/County Clerk (ARCC) to identify a specific portion of real property that is taxed at a certain rate for a certain owner. Tax parcels are typically the same as a legally subdivided lot but are not necessessarily so. For example, a single owner may own a legally subdivided piece of property but there may be two or more tax parcels covering that property. Legal subdivisions are shown in the LOTS layer.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;The SanGIS parcel layers are “stacked” parcels. That means that for any piece of ground there may be multiple parcels. For example, a condominium building in downtown San Diego may have 200 individual condos. Each condo is a separate taxable parcel. All 200 parcels will be associated with the same physical lot on the ground. When the SanGIS parcel layer is created each individual condo has a polygon representing the physical location of the parent parcel. In this example there will be 200 polygons all stacked on top of each other that represent the taxable parcels and each polygon will have the same physical characteristics (shape, size, area, location) – they are, essentially, copies of each other. However, other associated information (owner, document numbers, etc) will be different for each. In this case, each condo unit will have its own parcel number and there will be no single parcel representing the lot on the ground. &lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Besides condominiums there are two other cases where you will see stacked parcels – possessory interest and mobile homes. Possessory interests have Assessor Parcel Numbers (APNs) that start with 76x. A possessory interest (or PI) parcel represents a taxable interest in the underlying, or parent, parcel but not necessarily ownership. For instance, a private company may have an arrangement with a University to operate a business on campus – a coffee shop or gift shop for example. The private business is taxable and is assigned a 76x APN and that APN is associated with the parent parcel which is owned by the University. Possessory interests do not represent ownership on the parcel, only a taxable interest in the underlying parent parcel.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Mobile home parcel APNs start with 77x. In a manner similar to the possessory interests, mobile home owners own their home (coach) but not the underlying property on which the house sits. The actual mobile home is a separate taxable parcel associated with the mobile home park parent parcel. These taxable parcels all have the same polygon as the underlying parent parcel and will show as stacked parcels as well.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;This dataset contains parcels as shown on the Assessor Parcel Maps (APM). However, parcels shown in this layer may lag that of the official APM by a number of weeks due to how SanGIS is notified of the newly created parcel and the timing of publication of the parcel layer.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in thier Master Property Record (MPR file) and Parcel Assessment Record (PAR file). In addition to the MPR and PAR data assigned by ARCC, SanGIS may add situs address information if it has been provided by the addressing authority in which the parcel is situated. The situs address information provided by SanGIS may not be the same as the SITUS address data in the MPR.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include:&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Land use information provided in the NUCLEUS_USE_CD field (225 types with a 3-digit domain). The ASR_LANDUSE field is an older version of this field but comprises more generalized land uses (91 types). &lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Generalized land use zoning information is provided in the NUCLEUS_ZONE_CD field. The ASR_ZONE field is an older version of this field. Land use zoning is generalized comprising 9 zone types. This can provide a useful approximation for parcels that are outside of the San Diego City and County zoning jurisdictions.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Please note that land use and zoning fields are not regularly maintained by the Assessor's Office and should only be used as an approximate guide. Updates are only made when there is new construction, or a change in ownership. They are not updated when the County and Local Cities update their zoning data or when permit changes to properties are completed. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data. &lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;NOTE: If the name of this layer includes "_NORTH", "_SOUTH", or "_EAST" it represents a subset of the entire San Diego County Parcel Base. That is, the "_NORTH" layer includes only parcels generally in the Northwestern portion of the County. The "_SOUTH" layer includes parcels in the Southwestern portion. And the "_EAST" layer includes parcels in the approximate Eastern half of the County.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;While we constantly seek to improve accuracy, SanGIS are not a replacement for the services and products of a Licensed Land Surveyor for ground data. SanGIS creates and maintains parcels to aid the County Assessor’s Office for TAX PURPOSES. Our data CANNOT be used in place of the legal description of a property—legal descriptions are the pervue of a Licensed Land Surveyor.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Additional note on Parcels: There are over 1 million parcels in the SanGIS database, and much of the data (and inaccuracies inherent therein) is old and unverified. SanGIS editors can only adjust parcel boundaries in specific areas where a licensed survey has been completed with the use of control points recorded in NAD 83 State Plane. Therefore, the accuracy of data varies&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<descKeys>
<thesaName uuidref="723f6998-058e-11dc-8314-0800200c9a66"/>
</descKeys>
<searchKeys>
<keyword>Parcel</keyword>
<keyword>San Diego County</keyword>
<keyword>Parcels</keyword>
<keyword>Property</keyword>
<keyword>Tax Parcel</keyword>
<keyword>Boundary</keyword>
</searchKeys>
<idPurp>Polygons representing current taxable parcels in San Diego County and some non-taxable parcels. Taxable parcels that cannot be represented by a polygon (i.e. possessory interest parcels) may not be shown. </idPurp>
<idCredit>SanGIS using legal recorded data provided by the County Recorders and Assessor's Office. See the County ARCC website at https://arcc.sdcounty.ca.gov/Pages/default.aspx for more information about tax parcels</idCredit>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Data is generalized and created for use in regional projects. Please refer to SanGIS data end user use agreement and disclaimer which is available on the SanGIS website (www.sangis.org).&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Parcels shown in this layer may lag the official Assessor Parcel Map due to timing of data transmissions and publication schedules.&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN&gt;Please note that land use, zoning and property description fields are not regularly maintained and should only be used as an approximate guide. Please refer to city and County official zoning datasets for official zoning information, and to SANDAG for more current land use data. &lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;While we constantly seek to improve accuracy, SanGIS are not a replacement for the services and products of a Licensed Land Surveyor for ground data. SanGIS creates and maintains parcels to aid the County Assessor’s Office for TAX PURPOSES. Our data CANNOT be used in place of the legal description of a property—legal descriptions are the pervue of a Licensed Land Surveyor.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Additional note on Parcels: There are over 1 million parcels in the SanGIS database, and much of the data (and inaccuracies inherent therein) is old and unverified. SanGIS editors can only adjust parcel boundaries in specific areas where a licensed survey has been completed with the use of control points recorded in NAD 83 State Plane. Therefore, the accuracy of data varies&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 0 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<envirDesc Sync="FALSE">Esri ArcGIS 12.9.10.32739</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<themeKeys>
<keyword>Parcel, Land, taxable parcel, property, boundaries, lots</keyword>
</themeKeys>
<placeKeys>
<keyword>California, County of San Diego, Carlsbad, Coronado, Chula Vista, Del Mar, El Cajon, Encinitas, Escondido, Imperial Beach, Lemon Grove, La Mesa, National City, Oceanside, Poway, San Diego, San Marcos, Solana Beach, Santee, Vista</keyword>
</placeKeys>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<idStatus>
<ProgCd value="004"/>
</idStatus>
<dataExt>
<exDesc>The spatial extent of this dataset is San Diego County. The temporal extent is variable.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2023-07-22T00:00:00</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<idPoC>
<rpOrgName>SanGIS</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(858) 874-7000</voiceNum>
<faxNum>(858) 874-7002</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>5510 Overland Avenue, Suite 230</delPoint>
<city>San Diego</city>
<adminArea>California</adminArea>
<postCode>92123</postCode>
<country>US</country>
<eMailAdd>webmaster@sangis.org</eMailAdd>
</cntAddress>
<cntHours>8:00 AM - 4 PM Monday thru Friday</cntHours>
</rpCntInfo>
<rpIndName>Operations Manager</rpIndName>
<rpPosName>Operations Manager</rpPosName>
<displayName>SanGIS</displayName>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="003"/>
</maintFreq>
</resMaint>
<tpCat>
<TopicCatCd value="003"/>
</tpCat>
<tpCat>
<TopicCatCd value="013"/>
</tpCat>
<tpCat>
<TopicCatCd value="015"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="003"/>
</maintFreq>
</mdMaint>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="parcels_sd2">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem dimension="">
<refSysID>
<identCode Sync="TRUE" code="2230" value="2230"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">5.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="parcels_sd2">
<enttyp>
<enttypl Sync="TRUE">parcels_sd2</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
<enttypd>All tax parcels in the County of San Diego, California, USA</enttypd>
<enttypds>SanGIS</enttypds>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">APN</attrlabl>
<attalias Sync="TRUE">APN</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<attrdef>Assessor Parcel Number (APN) - Full 10 digit
APN is of the form: BBB-PPx-yy-zz where:
BBB = Assessor Map Book number
PP = Assessor Map Book Page number
x = Assessor Map Book Block number
yy = Parcel number
zz = Subunit number (for condos)
This is the key field for linking to the Assessor's Master Property Record (MPR) and Property Assessment Record (PAR) files as well as links to other SanGIS data sets.</attrdef>
<attrdefs>County Assessor's Office</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">MULTI</attrlabl>
<attalias Sync="TRUE">MULTI</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">1</attwidth>
<attrdef>The Multi attribute is used by the Assessor’s Mapping Division to indicate “base” Parcels with more than one Assessor Parcel Number (APN). This typically happens when there are more than 99 units on said base Parcels requiring more than one APN to accommodate their individual Sub IDs.
This attribute is used when labeling these “base” parcels during the creation of Assessor Parcel Maps (APMs).
CODE, Description
Y, Yes - more than one APN
N, No - only one APN (default)</attrdef>
<attrdefs>SanGIS</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">SUB_TYPE</attrlabl>
<attalias Sync="TRUE">SUB_TYPE</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<attrdef>Type of parcel as maintained by SanGIS. Right-of-way parcels (sub-type 5) are not published in SanGIS parcel layers. See RIGHT_OF_WAY layer for dedicated rights-of-way.
Code; Sub-Type
1; Regular parcel with APN number
2; Unparcelled Private Road
3; Unparcelled Government Land
4; Unparcelled Common Area
5; Right-of-Way
6; PendParcel
7; Tideland Parent Parcel
8; Parceled Right-of-Way</attrdef>
<attrdefs>SanGIS</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<attalias Sync="TRUE">Shape</attalias>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">taz</attrlabl>
<attalias Sync="TRUE">taz</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">typology</attrlabl>
<attalias Sync="TRUE">typology</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">tpa</attrlabl>
<attalias Sync="TRUE">tpa</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">MOBILITY_Z</attrlabl>
<attalias Sync="TRUE">MOBILITY_Z</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">cpa</attrlabl>
<attalias Sync="TRUE">cpa</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">census_tra</attrlabl>
<attalias Sync="TRUE">census_tra</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">mgra_zone</attrlabl>
<attalias Sync="TRUE">mgra_zone</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">res_densit</attrlabl>
<attalias Sync="TRUE">res_densit</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">emp_densit</attrlabl>
<attalias Sync="TRUE">emp_densit</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">vmt_per_ca</attrlabl>
<attalias Sync="TRUE">vmt_per_ca</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PctMean_re</attrlabl>
<attalias Sync="TRUE">PctMean_re</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">vmt_per_em</attrlabl>
<attalias Sync="TRUE">vmt_per_em</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">PctMean_em</attrlabl>
<attalias Sync="TRUE">PctMean_em</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">vmt_effici</attrlabl>
<attalias Sync="TRUE">vmt_effici</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">vmt_effi_1</attrlabl>
<attalias Sync="TRUE">vmt_effi_1</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">vmt_effi_2</attrlabl>
<attalias Sync="TRUE">vmt_effi_2</attalias>
<attrtype Sync="TRUE">Integer</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Leng</attrlabl>
<attalias Sync="TRUE">Shape_Leng</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">SHAPE_AREA</attrlabl>
<attalias Sync="TRUE">Shape_Area</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<attrdef Sync="TRUE">Area of feature in internal units squared.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
</detailed>
<overview>
<eadetcit>SanGIS using legal recorded data provided by the County Assessor/Recorder/County Clerk's (ARCC) Office. See the County ARCC website at https://arcc.sdcounty.ca.gov/Pages/default.aspx for more information about tax parcels</eadetcit>
<eaover>This dataset contains over 50 attributes with the key, unique, field being APN (full Assessor Parcel Number). The majority of the attributes come from the Assessor's Master Property Record (MPR) or Parcel Assessment Record (PAR). Attributes maintained by SanGIS are:
APNID; PARCELID; OVERLAY_JURIS; X_COORD; Y_COORD; SUB_TYPE
All other attributes are from the Assessor's MPR or PAR data. Attributes that are from the Assessor's Office will include the wording "Field updated weekly from Assessor's Master Property Record (MPR) file.", or something similar in the attribute description.
Attributes fall into three general categories:
Parcel Characteristics - fields related to the tax parcel itself, how it is identified, how it was created, and what jurisidictions and tax rate areas it falls within. Data may come from the MPR or PAR files or be applied by SanGIS as part of the polygon creation and maintenance process. Property Characteristics - fields related to land use, improvements, and assessed valuations. All fields in this category are from the Assessor's MPR or PAR data.
Addresses - there are three sets of address fields - Owner mailing address and MPR SITUS address
Owner address fields provide mailing address information for the property owner. Owner address field names all begin with OWN_. Owner addresses may be in state or out of state and do not reflect site loction.
SITUS addresses are the site location and come from the Assessor's MPR. SITUS addresses are intended to show the actual, physical, location of the parcel and may not be the same as the resident mailing address. All SITUS address fields begin with either SITUS_ or NUCLEUS_SITUS_</eaover>
</overview>
</eainfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="parcels_sd2">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="4"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">TRUE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
