<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20260908</CreaDate>
<CreaTime>09310400</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">CannabisPC_Selection_20260514_1640</itemName>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
</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/3.1.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.0060960121928&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>
<SyncDate>20260514</SyncDate>
<SyncTime>16400700</SyncTime>
<ModDate>20260514</ModDate>
<ModTime>16400700</ModTime>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</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">20260514</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpOrgName>SanGIS</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(858) 874-7000</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>5500 Overland Avenue, Suite 310</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>Data can be downloaded in multiple formats (FileGDB, Shapefile, CSV, GeoJSON and JSON) from the SanGIS Data Warehouse at https://gis-sangis1.hub.arcgis.com/pages/download-data
Refer to SanGIS website (www.sangis.org) to obtain further information on mapping and data extraction services available from SanGIS.
</ordInstr>
</distorOrdPrc>
</distributor>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<resRefDate>
<refDate>20060930</refDate>
<refDateType>
<DateTypCd value="001"/>
</refDateType>
</resRefDate>
<resEdDate>20060930</resEdDate>
<citRespParty>
<rpOrgName>SD County- SanGIS</rpOrgName>
</citRespParty>
<resTitle Sync="TRUE">CannabisPC_Selection_20260514_1640</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;This dataset contains certain information that has not been authorized for release to the general public. This data is for use of the SanGIS JPA member users only.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&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&gt;&lt;SPAN&gt;The complete SanGIS parcel layer (PARCELS_ALL) contains “stacked” parcels. That means that for any piece of ground there may be multiple parcels - for example, a condominium building may have 200 individual parcels representing each condo and a geospatial analysis would show multiple polygons and caluculate multiple areas for a single area of ground. This dataset provides a one-to-one correspondence between a polygon and a tax parcel. For each property there will be only one parcel associated with the polygon. This provides for better calculations when determining areas and other geospatial analysis.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Only one set of parcel data is associated with each polygon. However, the parcel data is programatically selected and may not be consistent from one publication date to another. Also, the parcel data shown may or may not represent the "parent" parcel. Not all Assessor Parcel Numbers (APNs) will be found in this dataset.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Parcels in this dataset are keyed to the parcel polygon identifier (PARCELID).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&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&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&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&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&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&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. 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&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>
<keyword>PARCEL UNSTACKED</keyword>
<keyword>SanGIS</keyword>
</searchKeys>
<idPurp>Polygons representing current taxable parcels in San Diego County and some non-taxable parcels. Contains a one-to-one correspondence between parcel polygons and parcel numbers. Does not contain all tax parcels in the County. Primarily to be used for area calculations and geospatial processing of where stacked parcels would create errors. See PARCELS_ALL dataset for all parcel data. For use by SanGIS JPA member users only. Not for release to the public.</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&gt;&lt;SPAN&gt;This dataset contains certain property characteristics that has not been authorized for release to the general public by the County Assessor/Recorder/County Clerk's Office. This data is for use of the SanGIS JPA member users only.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&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&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&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&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;</useLimit>
</Consts>
</resConst>
<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>
<idPoC>
<rpOrgName>SanGIS</rpOrgName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">(858) 874-7000</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>5530 Overland Avenue, 4th Floor</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>
<envirDesc Sync="FALSE">Esri ArcGIS 13.1.3.41833</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<exDesc>Publication date
Date published from SanGIS edit environment.</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2026-05-02T00:00:00</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<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="CannabisPC_Selection_20260514_1640">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem>
<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="CannabisPC_Selection_20260514_1640">
<enttyp>
<enttypl Sync="TRUE">CannabisPC_Selection_20260514_1640</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>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">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="CannabisPC_Selection_20260514_1640">
<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">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
</metadata>
