Polygon layer of major subdivision plats with right-of- ways.View detailed metadata

This GIS data set was derived from a variety of source documents, including plats of survey, subdivision plats, certified survey maps, records of deed and row plats. These documents were of varying scales and from dates ranging from the late 1940's to present. These maps provide a useful representation of the geometry of the tax parcels and is suitable for its intended purpose.This GIS data set was derived from a variety of source documents, including plats of survey, subdivision plats, certified survey maps, records of deed and row plats. These documents were of varying scales and from dates ranging from the late 1940's to present. These maps provide a useful representation of the geometry of the tax parcels and is suitable for its intended purpose. This data was created to serve as an inventory of property owners for use by various county departments to determine septic and building permitting, voter and tax information, planning, social services, and use for the general public.This data was created to serve as an inventory of property owners for use by various county departments to determine septic and building permitting, voter and tax information, planning, social services, and use for the general public.For more information https://gisdownload.buncombecounty.org/parcels.htm

Download In State Plane Projection Here ** In addition to the Tax Parcel polygons feature class, the hyperlink download above also contains a parcel point data layer ** Parcel boundaries are developed from deeds, plats of subdivision and other legal documents going back to the mid 1800's, following generally accepted practices used in Public Land Survey System states, and following guidelines established by the Illinois Department of Revenue and the International Association of Assessment Officials. Lake County's parcel coverage is based on resolving the accumulated evidence of all of the legal documents surrounding a particular parcel or subdivision, and not the result of a countywide resurvey. These parcel boundaries are intended to be a visual inventory of property for tax and other administrative purposes; they are not intended to be used in place of an on-site survey or for the precise determination of property corners or PLSS features based on GIS coordinates. In Illinois, only a registered professional land surveyor is authorized to determine boundary locations. Included are the tax parcel boundaries, represented as polygons and centroids, for all changes resulting from legal records submitted to the Recorder of Deeds up to December 31st of the preceding year, as well as any court orders, municipal annexations and other transactions which impact the tax parcel boundaries. NOTE: The ONLY attribute included is the Property Index Number, or PARCEL_NUM. Additional assessment attribute data can be downloaded here This parcel layer is used for tax assessment purposes and for a variety of other local government functions. It changes often, both spatially and in its attribution, based on divisions or consolidations, the sale of property and other transactions. Example: PIN 08-17-304-014 can be interpreted as follows: Township 08, Section 17, Block 304, Parcel 014. Note that the first digit of block, "3" in this example, signifies that the parcel lies in quarter section 3. The quarter sections are labeled from 1 through 4, representing the northwest, northeast, southwest and southeast quarter sections, respectively. Update Frequency: This dataset is updated on a weekly basis.

DC's Real Property Tax Administration defines assessment and taxation lots, often referred to as A&T lots or simply tax lots. These lots are strictly for real estate taxation purposes and normally defined under two circumstances: When property owners ask for their real property tax bills to be consolidated, after they have bought several contiguous record lots; this is called a combine;When part of a record lot is sold, but no new record lot is yet defined; this is called a split request. Tax lots are not determined by survey, and are therefore not official lots in the same way record lots are. These lots are normally numbered between 800 and 1999within a square to differentiate them from record lots on the property tax maps. When a tax lot is established by RPTA, an A&T Plat is generated by RPTA and forwarded to the surveyor’s office. These A&T Plats are not reviewed but simply filed by the Surveyor; they do not comply with the standards required of subdivision plats, and are not recorded. Tax Lots are not normally acceptable when applying for building permits and must be converted to Record Lots through the normal subdivision process involving the D.C. Surveyor’s Office before permits will be issued. The only exception is if the lot does not face a public street. Furthermore, at the time of their creation and platting, there is no review made of tax lots for compliance with D.C. Zoning, Subdivisions or any other ordinances. These lots are simply pieces of property, owned by somebody, described in deeds, for which tax bills are sent and real estate taxes are collected by the city. Some Record Lots also function in this capacity. Geographically, tax lots typically overlay layers such as record lots or sometimes reservations. There are known instances where tax lots do not overlay these types of layers. Up until approximately 1972, A&T lots were only created by the Tax Assessor out of lands that had been previously Record Lots at some point in their history. For a short period of time in the early to mid 1970’s, a decision was made to start eliminating fractional parcels (see definition below) and make them all into A&T lots. The intent was to do away with Parcels altogether and have all properties in the city be either tax lots or record lots. By doing this, they converted unsubdivided parcels into A&T lots where no underlying record lot exists. There is often little or no historical source information about these types of transactions therefore vectorizing them often required vast amounts of research.

This feature class represents subdivisions located outside the city limits. Unlike subdivisions within the city, county subdivisions have historically been subject to fewer regulations, but documenting their existence remains important for planning, coordination, and development review. The dataset helps city staff and other users identify where recognized, platted subdivisions occur in the county.Data UpdatesCounty subdivisions are updated on a frequent basis as legal information is provided for them.Coverage AreaMidland County, TexasCoordinate SystemNAD 1983 StatePlane Central Texas FIPS 4203

Records pertaining to development projects within Community Development's TRAKiT system. Dataset includes information pertaining to Board of Zoning appeals, conditional use permit applications, Design Review Board, historic preservation, development projects, rezonings, site plan reviews, subdivisions, and right of way vacation. To view locations, please use the spatial version of this data.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)

A line feature class of the Subdivision lines conforming the boundaries of the Subdivision polygons within Miami-Dade County. Created for mapping purposes, using the field LINE_TYPE (sub-typed) in order to differentiate the line type for the subdivisions .(See Attributes -subtypes)Updated: Weekly-Sat The data was created using: Projected Coordinate System: WGS_1984_Web_Mercator_Auxiliary_SphereProjection: Mercator_Auxiliary_Sphere

Polygon geometry with attributes displaying subdivision boundaries in East Baton Rouge Parish, Louisiana.

Metadata

Splitgraph serves as an HTTP API that lets you run SQL queries directly on this data to power Web applications. For example:

See the Splitgraph documentation for more information.

Please click here to view the Data Dictionary, a description of the fields in this table.

This data set contains a variety of easements that are captured from recorded subdivision plats and easement plats. Once a document has been recorded then the GIS Division receives that document and creates any features that are shown on the recorded document. This layer contains the easement type by category and the name of the easement as stated on the plat. For newer easements there is also the deed book and deed page. This is used to perform research on the original document in the Courts system.

This layer does not contain all easements. There are many easements before the GIS Division started capturing all easements that did not get into the layer because they were not on the original mylars where this data was captured from. Also, in 2016 the GIS Division stopped capturing stormwater easements into this layer as there is different layer that contains the stormwater related easements.

Polygon layer of proposed subdivisions in Jefferson County, Kentucky for the last 35 years. View detailed metadata.

Polygon feature layer representing areas of past, present and future subdivision development in the City of Barrie. Relevant fields within the layer include (but not limited to): Development Type, Plan Number, Developer, Location, Status, Area, Number of Units and Dates.The City of Barrie is situated in the heart of Central Ontario, a premier waterfront community on Lake Simcoe, conveniently located an hour north of Toronto. Visit barrie.ca for more information or contact Service Barrie at 705-726-4242 or ServiceBarrie@barrie.ca

We constructed a time-series spatial dataset of parcel boundaries for the period 1962-2005, in roughly 4-year intervals, by digitizing historical plat maps for Dane County and combining them with the 2005 GIS digital parcel dataset. The resulting datasets enable the consistent tracking of subdivision and development for all parcels over a given time frame. The process involved 1) dissolving and merging the 2005 digital Dane County parcel dataset based on contiguity and name, 2) further merging 2005 parcels based on the hard copy 2005 Plat book, and then 3) the reverse chronological merging of parcels to reconstruct previous years, at 4-year intervals, based on historical plat books. Additional land use information such as 1) whether a structure was actually constructed (using the companion digitized aerial photo dataset), 2) cover crop, and 3) permeable surface area, can be added to these datasets at a later date.

A snapshot of Buncombe County parcel data from 2019. This GIS data set was derived from a variety of source documents, including plats of survey, subdivision plats, certified survey maps, records of deed and row plats. These documents were of varying scales and from dates ranging from the late 1940's to present. These maps provide a useful representation of the geometry of the tax parcels and is suitable for its intended purpose.This GIS data set was derived from a variety of source documents, including plats of survey, subdivision plats, certified survey maps, records of deed and row plats. These documents were of varying scales and from dates ranging from the late 1940's to present. These maps provide a useful representation of the geometry of the tax parcels and is suitable for its intended purpose. This data was created to serve as an inventory of property owners for use by various county departments to determine septic and building permitting, voter and tax information, planning, social services, and use for the general public.This data was created to serve as an inventory of property owners for use by various county departments to determine septic and building permitting, voter and tax information, planning, social services, and use for the general public.For more information https://gisdownload.buncombecounty.org/parcels.htm

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and equivalent entities for the reporting of Census Bureau data. They include legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. In MCD states where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2024, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

This dataset is OBSOLETE as of 12/3/2024 and will be removed from ArcGIS Online on 12/3/2025.An updated version of this dataset is available at Land Use FY2024.This data set derives from several sources, and is updated annually with data current through July 1 of the reported year. The primary source is a data dump from the VISION assessing data system, which provided data up to date as of January 1, 2012, and is supplemented by information from subsequent building permits and Development Logs. (Use codes provided by this system combine aspects of land use, tax status, and condominium status. In an effort to clarify land use type the data has been cleaned and subdivided to break the original use code into several different fields.) The data set has further been supplemented and updated with development information provided by building permits issued by the Inspectional Services Department and from data found in the Development Log publication. Information from these sources is added to the data set periodically. Land use status is up to date as of the Last Modified date.Differences From “Official” Parcel LayerThe Cambridge GIS system maintains a separate layer of land parcels reflecting up to date subdivision and ownership. The parcel data associated with the Land Use Data set differs from the “official” parcel layer in a number of cases. For that reason this separate parcel layer is provided to work with land use data in a GIS environment. See the Assessing Department’s Parcel layer for the most up-to-date land parcel boundaries.Table of Land Use CodesThe following table lists all land use code found in the data layer:Land Use CodeLand Use DescriptionCategory0101MXD SNGL-FAM-REMixed Use Residential0104MXD TWO-FAM-RESMixed Use Residential0105MXD THREE-FM-REMixed Use Residential0111MXD 4-8-UNIT-APMixed Use Residential0112MXD >8-UNIT-APTMixed Use Residential0121MXD BOARDING-HSMixed Use Residential013MULTIUSE-RESMixed Use Residential031MULTIUSE-COMMixed Use Commercial0340MXD GEN-OFFICEMixed Use Commercial041MULTIUSE-INDMixed Use Industrial0942Higher Ed and Comm MixedMixed Use Education101SNGL-FAM-RESResidential1014SINGLE FAM W/AUResidential104TWO-FAM-RESResidential105THREE-FM-RESResidential106RES-LAND-IMPTransportation1067RES-COV-PKGTransportation1114-8-UNIT-APTResidential112>8-UNIT-APTResidential113ASSISTED-LIVAssisted Living/Boarding House121BOARDING-HSEAssisted Living/Boarding House130RES-DEV-LANDVacant Residential131RES-PDV-LANDVacant Residential132RES-UDV-LANDVacant Residential1322RES-UDV-PARK (OS) LNVacant Residential140CHILD-CARECommercial300HOTELCommercial302INN-RESORTCommercial304NURSING-HOMEHealth316WAREHOUSECommercial323SH-CNTR/MALLCommercial324SUPERMARKETCommercial325RETAIL-STORECommercial326EATING-ESTBLCommercial327RETAIL-CONDOCommercial330AUTO-SALESCommercial331AUTO-SUPPLYCommercial332AUTO-REPAIRCommercial334GAS-STATIONCommercialLand Use CodeLand Use DescriptionCategory335CAR-WASHCommercial336PARKING-GARTransportation337PARKING-LOTTransportation340GEN-OFFICEOffice341BANKCommercial342MEDICAL-OFFCHealth343OFFICE-CONDOOffice345RETAIL-OFFICOffice346INV-OFFICEOffice353FRAT-ORGANIZCommercial362THEATRECommercial370BOWLING-ALLYCommercial375TENNIS-CLUBCommercial390COM-DEV-LANDVacant Commercial391COM-PDV-LANDVacant Commercial392COM-UDV-LANDVacant Commercial3922CRMCL REC LNDVacant Commercial400MANUFACTURNGIndustrial401WAREHOUSEIndustrial404RES-&-DEV-FCOffice/R&D406HIGH-TECHOffice/R&D407CLEAN-MANUFIndustrial409INDUST-CONDOIndustrial413RESRCH IND CNDIndustrial422ELEC GEN PLANTUtility424PUB UTIL REGUtility428GAS-CONTROLUtility430TELE-EXCH-STAUtility440IND-DEV-LANDVacant Industrial442IND-UDV-LANDVacant Industrial920ParklandsPublic Open Space930Government OperationsGovernment Operations934Public SchoolsEducation940Private Pre & Elem SchoolEducation941Private Secondary SchoolEducation942Private CollegeHigher Education9421Private College Res UnitsEducation Residential943Other Educ & Research OrgHigher EducationLand Use CodeLand Use DescriptionCategory953CemeteriesCemetery955Hospitals & Medical OfficHealth956MuseumsHigher Education957Charitable ServicesCharitable/Religious960ReligiousCharitable/Religious971Water UtilityUtility972Road Right of WayTransportation975MBTA/RailroadTransportation9751MBTA/RailroadTransportation995Private Open SpacePrivately-Owned Open SpaceExplore all our data on the Cambridge GIS Data Dictionary.Attributes NameType DetailsDescription ML type: Stringwidth: 16precision: 0 Map-Lot: This a unique parcel identifier found in the deed and used by the Assessing data system. In a few cases, where parcels have been subdivided subsequent to January 1, 2012, a placeholder Map-Lot number is assigned that differs from that used elsewhere.

MAP type: Stringwidth: 5precision: 0 This Map portion of the unique parcel identifier found in the deed and used by the Assessing data system. In a few cases, where parcels have been subdivided subsequent to January 1, 2012, a placeholder Map-Lot number is assigned that differs from that used elsewhere.

LOT type: Stringwidth: 5precision: 0 This is the Lot portion of the unique parcel identifier found in the deed and used by the Assessing data system. In a few cases, where parcels have been subdivided subsequent to January 1, 2012, a placeholder Map-Lot number is assigned that differs from that used elsewhere.

Location type: Stringwidth: 254precision: 0 In the great majority of cases this is the street address of the parcel as it is recorded in the Registry of Deed record. In instances where edits were made to the base parcel layer the best address available at the time is employed.

LandArea type: Doublewidth: 8precision: 15

LUCode type: Stringwidth: 254precision: 0 The four digit text string in this field indicates the primary usage of a parcel. While the codes are based on the standard Massachusetts assessing land use classification system, they differ in a number of cases; the coding system used here is unique to this data set. Note that other minor uses may occur on a property and, in some cases, tenants may introduce additional uses not reflected here (eg, office space used as a medical office, home based businesses).

LUDesc type: Stringwidth: 254precision: 0 The short description gives more detail about the specific use indicated by the Land Use Code. Most descriptions are taken from the standard Massachusetts assessing land use classification system.

Category type: Stringwidth: 254precision: 0 This broader grouping of land uses can be used to map land use data. You can find the land use data mapped at: https://www.cambridgema.gov/CDD/factsandmaps/mapgalleries/othermaps

ExistUnits type: Doublewidth: 8precision: 15 This value indicates the number of existing residential units as of July 1 of the reported year. A residential unit may be a house, an apartment, a mobile home, a group of rooms or a single room that is occupied (or, if vacant, intended for occupancy) as separate living quarters. This includes units found in apartment style graduate student housing residences and rooms in assisted living facilities and boarding houses are treated as also housing units. The unit count does not include college or graduate student dormitories, nursing home rooms, group homes, or other group quarters living arrangements.

MixedUseTy type: Stringwidth: 254precision: 0 Two flags are used for this field. “Groundfloor” indicates that a commercial use is found on the ground floor of the primary building, and upper floors are used for residential purposes. “Mixed” indicates that two or more uses are found throughout the structure or multiple structures on the parcel, one of which is residential.

GQLodgingH type: Stringwidth: 254precision: 0 A value of “Yes” indicates that the primary use of the property is as a group quarters living arrangement. Group quarters are a place where people live or stay, in a group living arrangement, that is owned or managed by an entity or organization providing housing and/or services for the residents. Group quarters include such places as college residence halls, residential treatment centers, skilled nursing facilities, group homes, military barracks, correctional facilities, and workers’ dormitories.

Most university dormitories are included under the broader higher education land use code, as most dormitories are included in the larger parcels comprising the bulk of higher education campuses.

GradStuden type: Stringwidth: 254precision: 0 A value of “Yes” indicates the parcel is used to house graduate students in apartment style units. Graduate student dormitories are treated as a higher education land use.

CondoFlag type: Stringwidth: 254precision: 0 “Yes” indicates that the parcel is owned as a condominium. Condo properties can include one or more uses, including residential, commercial, and parking. The great majority of such properties in Cambridge are residential only.

TaxStatus type: Stringwidth: 254precision: 0 A value indicates that the parcel is not subject to local property taxes. The following general rules are employed to assign properties to subcategories, though special situations exist in a number of cases.

o Authority: Properties owned the Cambridge Redevelopment Authority and Cambridge Housing Authority. o City: Properties owned by the City of Cambridge or cemetery land owned by the Town of Belmont. o Educ: Includes properties used for education purposes, ranging from pre-schools to university research facilities. (More detail about the level of education can be found using the Land Use Code.) o Federal: Properties owned by the federal government, including the Post Office. Certain properties with assessing data indicating Cambridge Redevelopment Authority ownership are in fact owned by the federal government as part of the Volpe Transportation Research Center and are so treated here. o Other: Nontaxable properties owned by a nonprofit organization and not

Subdivisions, Neighborhoods in Wake County, NC

https://creativecommons.org/licenses/by/4.0/Subdivision outlines were created for Yavapai County, Arizona. Roads that are internal to a specific subdivision are included in the area for a simplified view of the boundary. The polygons are dissolved based on the Subname in the Parcel layer weekly and updated to the web service. This is being hosted on gis.yavapaiaz.gov as a feature web service is in WGS 1984 Web Mercator Auxiliary Sphere (WKID 3857). The name may not match the exact recorded name due to database constraints. This data was intended for general location mapping purposes and is not suitable for legal, engineering, or surveying purposes. Using a Map Service to share for Open Data. Access is granted to public agencies, educational institutions, non-profit organizations and private individuals for non-commercial purpose. For commercial use of the data see Arizona Revised Statutes 39-121.03. But per AGIC, Arizona Revised Statutes 27-178 section B in the Geospatial data sharing, "A public agency that shares geospatial data may exempt the data from commercial use fees prescribed in section 39-121.03, subsection A, paragraph 3." Regarding Arizona Revised Statutes 39-121.03 and the OpenData metadata sentence stating, geospatial data may exempt the data from commercial use fees prescribed in section 39-121.03, subsection A, paragraph 3.