Description: The Office of the Assessor maintains assessment records of real and personal property in the County of Los Angeles. Many of these records are available for sale. The data is available in the form of CD-ROM, DVD, hardcopy, and on-line access. The Office of the Assessor also offers a GIS Tax Parcel Base Map.Some layers included (not an exhaustive list):parcel boundary map (shapefile format) local roll LA County wall map publicly owned parcels sales list unsecured roll and labels (for mailings) A discussion of parcel accuracy occasionally questions about the spatial accuracy of parcel information come up. In general, it is important to note that the parcels are for tax assessment purposes only, come from many sources, some historical, and are not necessarily survey grade. That said, they are in general extremely reliable.Here is a longer description from Emilio Solano, former Chief Cadastral Engineer of the Assessor Mapping and GIS Services:The very short answer is this: our data is in its majority accurate within a couple of feet, in other cases will not be so accurate.The issue of accuracy when applied to assessor’s data is very subjective. Our data is very accurate if we consider that all the information matches recorded information, we try our best to keep recent data as it was recorded, and older data gets slightly adjusted to match the most recent data. Another factor to consider is that about one third of the total number of new parcels created every year comes from deeds, not subdivision maps, that is, there is not, in the majority of the cases, any new survey data, more likely general descriptions of where the new boundaries should exist, or references to adjacent properties, even calls to documents recorded many years ago, referring to them just by the document number. In those cases we have to consider the intent of the owner when describing the property in the deed. Another couple of factors that have an impact in the accuracy of our data comes from the fact that we assembled this vast amount of information with digital data provided from at least a dozen of cities, Los Angeles, Long Beach, Torrance, etc. plus all the data gathered by the Los Angeles County Dept. Public Works in CAD format. We had to compile all that data, rectify it and adjusted as needed, always keeping in mind that the integrity of the data should be maintained by matching RECORDED information. Another factor is that the data was also coming from tens of thousands of individual recordings, it wasn’t as clean cut as when you look at a single subdivision, no matter how big, where every line is clearly identified by a bearing and a distance within a perfectly traced boundary. Our original data sources even go back as far as remainder pieces of land described by Spanish grants and ranchos, section land plus newer surveys.Even though we always input our data based on survey records using COGO tools, whenever possible, a lot of the data is not. Considering all that, our GIS layer is by far, the most accurate data set of its size available anywhere in the county, both in positional accuracy, and conformity to the information provided by legal sources. All that being said, the resulting fact is that, as mark mentioned, in some areas our data will be very accurate, in others it won’t. The most important thing to keep in mind is that given that our responsibility is to reflect property information as recorded, we do not use anything else as a guide, for example we never use an aerial image to change the position of a line just because it doesn’t fall on top of a fence shown on a photo; remember that many people build their fenced, especially the ones made out of concrete blocks, a couple of inches inside the property boundary because is difficult to dig a trench along an existing wooden or wire fence, now multiply those little variances spread out over a 4000+ square miles of land and you will get a picture of what we are up to.That’s why we continually try to stress in anybody using our data that, if they need total accuracy they will need to hire a surveyor to get it. Our 11 by 17 maps are our only official source of information and should only be used for assessment purposes, or in the case of other uses, just for information, to get an accurate idea of how close to the real location a line could be.
Service Item Id: 5d895b87bff44bee937912389b2dcf8f
Copyright Text: James Kulbacki
jkulbacki@assessor.lacounty.gov
Los Angeles County Assessor Mapping & GIS Services
500 W Temple Street Los Angeles, CA 90012
Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 7 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Description: The Orange County School District is the only source for this information. The school codes must be unique and match the school codes entered in the study area feature class.Required Fields for SchoolSite Desktop or SchoolSite Locator:NAME: A field containing the unique name of the school, defined as data type "Text" with a length of 50. Each school name should be unique. For example, if you have a Main Street Elementary and Main Street High, do not enter "Main Street" for both schools.ELEM_: A field containing the elementary school code number, defined as data type "Short Integer.MID_: A field containing the middle school code number, defined as data type "Short Integer".INT_: A field containing the intermediate school code number, defined as data type "Short Integer".HIGH_: A field containing the high school code number, defined as data type "Short Integer".CAPACITY: A field containing the maximum capacity of the school, defined as data type "Short Integer".PERM_CLRM: A field containing the number of permanent class rooms, defined as data type "Short Integer".PORT_CLRM: A field containing the number of portable class rooms, defined as data type "Short Integer".SCHL_CODE: A field containing the school code of each school, must match codes used to populate the ELEM_, MID_, INT_, and HIGH_ fields defined as data type "Short Interger".GRD_RANGE: A field containing the grade range that each school facility serves; K-5, 6-8, 9-12 etc), defined as "Text" with length 5.STRT_GRD: A field containing the lowest grade range that each school facility serves, defined as "Short Integer".END_GRD: A field containing highest grade range that each school facility serves, defined as "Short Integer".For elementary schools, the ELEM_ field would be filled in with an ID value while the MID_, INT_ and HIGH_ fields will usually contain 0.For middle or junior high schools, ELEM_ and HIGH_ will be 0 and the INT or MID_ field contain the schools ID number (i.e. will have a value other than 0). The same general rule applies if you are working with a high schoolIn the cases of K-8 schools where a site might house what is normally considered both elementary and intermediate school students, the ELEM_ and INT_ fields would have the same ID number and HIGH_ would be 0
Description: Study Areas (polygons) are the building blocks of a school district. Study areas grouped together (and coded to specific school ID numbers) form attendance boundaries. Study Areas are geographically defined, following logical boundaries of a neighborhood and are used for boundary planning and generating small area enrollment forecasts. SchoolSite Desktop™ does not use separate feature classes for each set of school attendance areas. Using a unique field coding method, all attendance areas are stored within the Study Area feature class attribute table. Required Fields for SchoolSite Desktop or SchoolSite Locator:STDYAREA: A field containing the unique number of the study area, defined as data type "Text" with a length of 6.ELEM_: A field containing the Elementary School number the study area is assigned to, defined as data type "Short Integer".MID_: A field containing the number of the Middle School number the study area is assigned to, defined as data type "Short Integer".INT_: A field containing the number of the Intermediate School number the study area is assigned to, defined as data type "Short Integer".HIGH_: A field containing the High School number the study area is assigned to, defined as data type "Short Integer".DISTRICT: A field containing a six letter code used to report and summarize portions of the District, defined as data type "Text".MOBILITY: A field containing a 1 letter code used to indicate the Study Areas inclusion in the Mobility calculation. Y = Yes included in Mobility calculation and N = No do not include in the Mobility calculations. Defined as data type "Text". The MOBILITY field should be defined as data type "Text" with a length of 1.Although the following fields are not required, they are HIGHLY recommended. It’s not just for Locator and Matrices, those fields are used for automated mobility calculations and adding historical student information to resident projections.Suggested But Not Required Fields, which are helpful to set up SchoolSite Locator or Attendance Matrices:ELEM_DESC; A field containing the name of the Elementary School that the study area is assigned to. The ELEM_DESC field should be defined as data type "Text" with a length of 50.MID_DESC: A field containing the name of the Middle School that the study area is assigned to. The MID_DESC field should be defined as data type "Text" with a length of 50.INT_DESC: A field containing the name of the Intermediate School that the study area is assigned to. The INT_DESC field should be defined as data type "Text" with a length of 50.HIGH_DESC: A field containing the name of the High School that the study area is assigned to. The HIGH_DESC field should be defined as data type "Text" with a length of 50.REGION1: A field containing the name of a region the study area is assigned to that a user would like to be able to report on, i.e. Board Trustee Areas, Transportation Service Areas, Zip Code, etc. The REGION1 field should be defined as data type "Text" with a length of 50.REGION2: A field containing the name of a second region the study area is assigned to that a user would like to be able to report on, i.e. Board Trustee Areas, Transportation Service Areas, Zip Code, etc. The REGION2 field should be defined as data type "Text" with a length of 50.Districts with established Study Areas need to map and enter the information into a geodatabase feature class or a shapefile.
Description: The School District is the only source for this information. The school codes must be unique and match the school codes entered in the study area feature class.Required Fields for SchoolSite Desktop or SchoolSite Locator:NAME: A field containing the unique name of the school, defined as data type "Text" with a length of 50. Each school name should be unique. For example, if you have a Main Street Elementary and Main Street High, do not enter "Main Street" for both schools.ELEM_: A field containing the elementary school code number, defined as data type "Short Integer.MID_: A field containing the middle school code number, defined as data type "Short Integer".INT_: A field containing the intermediate school code number, defined as data type "Short Integer".HIGH_: A field containing the high school code number, defined as data type "Short Integer".CAPACITY: A field containing the maximum capacity of the school, defined as data type "Short Integer".PERM_CLRM: A field containing the number of permanent class rooms, defined as data type "Short Integer".PORT_CLRM: A field containing the number of portable class rooms, defined as data type "Short Integer".SCHL_CODE: A field containing the school code of each school, must match codes used to populate the ELEM_, MID_, INT_, and HIGH_ fields defined as data type "Short Interger".GRD_RANGE: A field containing the grade range that each school facility serves; K-5, 6-8, 9-12 etc), defined as "Text" with length 5.STRT_GRD: A field containing the lowest grade range that each school facility serves, defined as "Short Integer".END_GRD: A field containing highest grade range that each school facility serves, defined as "Short Integer".For elementary schools, the ELEM_ field would be filled in with an ID value while the MID_, INT_ and HIGH_ fields will usually contain 0.For middle or junior high schools, ELEM_ and HIGH_ will be 0 and the INT or MID_ field contain the schools ID number (i.e. will have a value other than 0). The same general rule applies if you are working with a high schoolIn the cases of K-8 schools where a site might house what is normally considered both elementary and intermediate school students, the ELEM_ and INT_ fields would have the same ID number and HIGH_ would be 0
Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 8 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none
Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 7 Font Family: Arial Black Font Style: normal Font Weight: normal Font Decoration: none
Description: Structures data contains name and location data for selected manmade facilities. These data are designed to be used in general mapping and analysis of structure related activities using a geographic information system (GIS) For mapping purposes, structures can be used with other GIS data themes to produce general reference maps as a base map dataset.
Service Item Id: 5d895b87bff44bee937912389b2dcf8f
Copyright Text: Maine Office of Geographic Information Systems
Description: 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 necessarily 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.Parcels are keyed to the Assessor Parcel Number (APN) and the parcel polygon identifier (PARCELID).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. 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.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.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.This dataset contains the parcel polygon and associated parcel information provided by the County ARCC in the 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.This dataset contains site address information along with owner names and addresses, and other property information. Key fields in this dataset include: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). 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.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.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 purvue of a Licensed Land Surveyor.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
Service Item Id: 5d895b87bff44bee937912389b2dcf8f
Copyright Text: 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
Description: Parcels for the entire county Source: COGO: COGO is a computer program that is used to calculate coordinate geometry. It is used to solve the geometric problems encountered in civil engineering applications including: property boundary and right of way surveys highway and interchange design construction layout bridge geometry.
Color: [255, 255, 255, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: center Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 7 Font Family: Arial Font Style: normal Font Weight: normal Font Decoration: none