Officel repository of parcel lines transcribed from recorded plats. Coordinate Geometry (COGO) and an accuracy code to evaluate the accuracy to the plat began in 2009 on all new recorded plats. This also was the beginning of a parcel realignment project that is reviewing each subdivision to improve accuracy. Contact Glynn County GIS Department (912)554-7418 at 1725 Reynolds St Suite 205 Brunswick, GA 31520.
Historically, the earliest Bakersfield “urban” subdivisions were not called tracts. The downtown area was subdivided into blocks and lots. Early citywide maps show the city blocks numbered from 1 to over 700. Some blocks were designated by letters rather than numbers. Each block was further subdivided into numbered lots. Thereafter housing subdivisions were called tracts and initially were named (example; Lowell Addition). Many of these “Named” tracts were also subdivided into blocks and lots. The earliest rural land subdivisions are the Sales Map Lands of J. B. Haggin and the Sales Map Lands of the Kern County l Land Company. The legal description of most modern lots is comprised of some combination of the fields: Document Type, Map Number, Phase and Lot Number. A “Block” field should be added for old parcels whose legal description is comprised of tract, block and lot (or just block and lot). The legal description fields for most of the older parcels are not populated at this time. PARCEL FEATURE CLASS ATTRIBUTES Document Type (Domain)Aliquot – subdivision of a public land survey system section i.e. the northeast quarter of the south east quarter of the southwest quarter of section 10 of T28S, R27ETract MapParcel Map Lot Line Adjustment (ex. LLA17-0684)Parcel Map Waiver (ex. PMW17-0398)Parcel Merger (ex. LM17-0695)Map Number Tracts – Old named tracts and numbered tracts, currently into the 7000’sParcel maps – numbered, currently into the 12,000’sMinor land subdivisions (lot line adjustments, parcel map waivers, parcel mergers) format YY-NNNN, where YY is a 2-digit designation of the year and NNNN is a zero-filled number (county files is reversed, ex. NN – YY)Phase Applicable to tract and parcel maps only; i.e. 1, 2, 3 etc. or A, B, C etc. Lot Number i.e. 1, 2, 3 etc. or A, B, C etc. Quality (Domain)In reference to the geometric and positional accuracy of the parcel features. All COGO’d parcels are considered “Excellent” quality User Flag This field is for temporary data storage. However the following user flag values provide information about how the parcel features originally built or subsequently edited: CAD CONVERSION - parcels were developed from georeferenced CAD data. Quality is considered excellent. COGO - parcels were first developed employing COGO editing tools. Quality is considered excellent REBUILT - parcels were originally Valleywide GIS features that were rebuilt using COGO and other editing tools. Quality is considered excellent except parcels that were rebuilt where only assessor maps were available. SHIFTED - original parcels were considered geometrically adequate but required a slight positional shift. Whole blocks of contiguous lots were shifted together. Quality is considered good. Class(Domain)This field provides an opportunity to classify lots for specific purposes. The Private road lot class was created so these lots could be neglected when exporting parcels for the Community Maps Project. Landscape lot Private road lot School lot Sump lot Water Well lot Additional classes could be developed. For the vast majority of parcels the class field is not populated. Address The street address of a lot can be populated if the address point feature class objects have already been created and populated by the GIS Analyst at Community Development. Where there are multiple addresses on a parcel, this data is captured on the Address Point feature class. Assessor Parcel Number (APN) and Assessor Tax Numbers (ATN)The most important parcel layer attributes are the APN and ATN values that are assigned by the Kern County Assessor. An 8 digit APN is assigned to a property that has a specific geometry as defined by a legal description. If any new change occurs such as a lot line adjustment, then the geometry of the parcel(s) are changed and the APN’s for the affected properties are dropped and are never re-assigned. New unique APN’s are assigned to the affected properties and remain as long as the legal description of the geometry does not change. It usually takes at least a few months after a tract is recorded and the parcel feature class objects are developed before the County assigns APN’s to those parcels. The APN field is populated with “NEW” until such time as values are assigned. Parcel APNs can be acquired from the following sources: https://kernpublicworks.com/maps/parcel-maps/, Preliminary (January) and final (July) Kern County parcel GIS releases. Some Condominium common areas do not have an APN. The APN field is populated with “CONDOLOT”. These parcels are retained in order to preserve road right of ways. Compare City parcel layer features with County features to visualize why we retain these parcels.
ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
Internal view of the parcel layer. This view contains all the attributes that can be seen by County employees.There are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.SFAP & CFAP DISCLAIMER: Per the California Code, RTC 606. some legal parcels may have been combined for assessment purposes (CFAP) or separated for assessment purposes (SFAP) into multiple parcels for a variety of tax assessment reasons. SFAP and CFAP parcels are assigned their own APN number and primarily result from a parcel being split by a tax rate area boundary, due to a recorded land use lease, or by request of the property owner. Assessor parcel (APN) maps reflect when parcels have been separated or combined for assessment purposes, and are one legal entity. The goal of the GIS parcel fabric data is to distinguish the SFAP and CFAP parcel configurations from the legal configurations, to convey the legal parcel configurations. This workflow is in progress. Please be advised that while we endeavor to restore SFAP and CFAP parcels back to their legal configurations in the primary parcel fabric layer, SFAP and CFAP parcels may be distributed throughout the dataset. Parcels that have been restored to their legal configurations, do not reflect the SFAP or CFAP parcel configurations that correspond to the current property tax delineations. We intend for parcel reports and parcel data to capture when a parcel has been separated or combined for assessment purposes, however in some cases, information may not be available in GIS for the SFAP/CFAP status of a parcel configuration shown. For help or questions regarding a parcel’s SFAP/CFAP status, or property survey data, please visit Napa County’s Surveying Services or Property Mapping Information. For more information you can visit our website: When a Parcel is Not a Parcel | Napa County, CA
This Feature Class was created in 2014 as part of a Connecticut Office of Policy and Management/The original parcel layer was digitized from tax maps originally created by General Mapping , Inc. of Youngwood, PA in 1970, last revised in 1999. These maps were drawn over unrectified aerial photos, resulting in significant distortion. More current orthophotos, specifically those from the 2009 CCROG flight and the 2012 State flight were used to refine the property lines using obvious indications of property lines such as fences and hedgerows. In addition, over 100 parcels were drawn by Coordinate Geography (COGO) using as-built maps. These points are used for assigning attributes to parcel polygons.Condominiums are drawn as individual polygons with their own points.updated April 2018
Polygon feature class of the Parcel boundaries in Chesterfield County, VA.
Originally obtained in 1992 from Landmark.
Daily COGO'd into GIS from recorded plats.
This Feature Class was created in 2014 as part of a Connecticut Office of Policy and Management grant to the Central Connecticut Regional Planning Association. This Feature Class was created in 2014 as part of a Connecticut Office of Policy and Management grant to the Central Connecticut Regional Planning Association. The original parcel layer was digitized from tax maps of uncertain origin and date. These maps were drawn over unrectified aerial photos, resulting in significant distortion. More current orthophotos, specifically those from the 2009 CCROG flight and the 2012 State flight were used to refine the property lines using obvious indications of property lines such as fences and hedgerows. In addition, over 194 parcels were drawn by Coordinate Geography (COGO) or digitized using as-built maps. These points are used for assigning attributes to parcel polygons. Updated 11/15/2018
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This layer contains polygons representing parcel ownership for Allamakee County, Iowa. It represents map features similar to those previously shown on hand drawn tax maps. The geometry was created by the Schneider Corporation using coordinate geometry (COGO) software in an ArcGIS environment. Individual parcel features were digitized from official recorded documents when available. Special care was taken to correlate map features with survey controlled coordinate values of the Public Land Survey System (PLSS).
ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. Parcel boundaries in GIS are created and maintained by the Assessor’s Division Mapping section and Information Technology Services. There are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.SFAP & CFAP DISCLAIMER: Per the California Code, RTC 606. some legal parcels may have been combined for assessment purposes (CFAP) or separated for assessment purposes (SFAP) into multiple parcels for a variety of tax assessment reasons. SFAP and CFAP parcels are assigned their own APN number and primarily result from a parcel being split by a tax rate area boundary, due to a recorded land use lease, or by request of the property owner. Assessor parcel (APN) maps reflect when parcels have been separated or combined for assessment purposes, and are one legal entity. The goal of the GIS parcel fabric data is to distinguish the SFAP and CFAP parcel configurations from the legal configurations, to convey the legal parcel configurations. This workflow is in progress. Please be advised that while we endeavor to restore SFAP and CFAP parcels back to their legal configurations in the primary parcel fabric layer, SFAP and CFAP parcels may be distributed throughout the dataset. Parcels that have been restored to their legal configurations, do not reflect the SFAP or CFAP parcel configurations that correspond to the current property tax delineations. We intend for parcel reports and parcel data to capture when a parcel has been separated or combined for assessment purposes, however in some cases, information may not be available in GIS for the SFAP/CFAP status of a parcel configuration shown. For help or questions regarding a parcel’s SFAP/CFAP status, or property survey data, please visit Napa County’s Surveying Services or Property Mapping Information. For more information you can visit our website: When a Parcel is Not a Parcel | Napa County, CA
The parcel layer is continuously updated & added to over time. In 2003 Premier Data Services, scanned Natrona County Assessors Tax maps to initiate the parcel layer, maps were scanned & digitized. Cleanup was done by Natrona County GIS dept & City of Casper GIS dept. Parcel Data is updated by either importing digital as-built drawings (.dwg CAD format) into the parcel layer or by using the Traverse tool (COGO) to digitally draw in the polygon from a legal description or hard copy of a plat. Digital as-built data is provided by developing companies as a requirement of their contract with the Natrona County Planning department. The digital data is imported into the parcel layer (feature class) first as a polyline data, then polygons are created from the line information using a process within ArcMAP. Accuracy varies based on origin of the source data. The more recent process of using digital as-built CAD data, allows for adjusting older parcel data to the newer data which provides a continuous improvement of the parcel polygon feature class across the coverage area of Natrona County, City of Casper, Bar Nunn, Evansville, Mills, Midwest & Edgerton.
Attribution-NoDerivs 3.0 (CC BY-ND 3.0)https://creativecommons.org/licenses/by-nd/3.0/
License information was derived automatically
The seamless, county-wide parcel layer was digitized from official Assessor Parcel (AP) Maps which were originally maintained on mylar sheets and/or maintained as individual Computer Aided Design (CAD) drawing files (e.g., DWG). The CRA office continues to maintain the official AP Maps in CAD drawings and Information Systems Department/Geographic Information Systems (ISD/GIS) staff apply updates from these maps to the seamless parcel base in the County’s Enterprise GIS. The seamless parcel layer is updated and published to the Internet on a monthly basis.The seamless parcel layer was developed from the source data using the general methodology outlined below. The mylar sheets were scanned and saved to standard image file format (e.g., TIFF). The individual scanned maps or CAD drawing files were imported into GIS software and geo-referenced to their corresponding real-world locations using high resolution orthophotography as control. The standard approach was to rescale and rotate the scanned drawing (or CAD file) to match the general location on the orthophotograph. Then, appropriate control points were selected to register and rectify features on the scanned map (or CAD drawing file) to the orthophotography. In the process, features in the scanned map (or CAD drawing file) were transformed to real-world coordinates, and line features were created using “heads-up digitizing” and stored in new GIS feature classes. Recommended industry best practices were followed to minimize root mean square (RMS) error in the transformation of the data, and to ensure the integrity of the overall pattern of each AP map relative to neighboring pages. Where available Coordinate Geometry (COGO) & survey data, tied to global positioning systems (GPS) coordinates, were also referenced and input to improve the fit and absolute location of each page. The vector lines were then assembled into a polygon features, with each polygon being assigned a unique identifier, the Assessor Parcel Number (APN). The APN field in the parcel table was joined to the corresponding APN field in the assessor property characteristics table extracted from the MPTS database to create the final parcel layer. The result is a seamless parcel land base, each parcel polygon coded with a unique APN, assembled from approximately 6,000 individual map page of varying scale and accuracy, but ensuring the correct topology of each feature within the whole (i.e., no gaps or overlaps). The accuracy and quality of the parcels varies depending on the source. See the fields RANK and DESCRIPTION fields below for information on the fit assessment for each source page. These data should be used only for general reference and planning purposes. It is important to note that while these data were generated from authoritative public records, and checked for quality assurance, they do not provide survey-quality spatial accuracy and should NOT be used to interpret the true location of individual property boundary lines. Please contact the Sonoma County CRA and/or a licensed land surveyor before making a business decision that involves official boundary descriptions.
The approach and process to create the regional, standardized parcel data for the project involved the following steps. First convert the collected parcel data from its current format into the required Esri Geodatabase format, and the CT Cadastral Standard file Geodatabase template. All pre-existing parcel polygon attributes and parcel line attributes (including any feature level metadata) that were both part of the standard and also those that are not part of the standard attributes, were preserved as appended fields in the attribute tables. Next the GIS Link currently employed by the town was determined and if there was not an existing link, then AppGeo created one. If necessary, an Intersection table was created to establish the “many-to-one” relationship of condos and these special types of parcels. Analyze the data and report the mismatches for parcels with no CAMA as well as CAMA with no parcels. Analyze the parcels data for duplicate IDs. Document and submit to the towns, the analyses results and a map depicting the parcels that do not have a matching CAMA record, and work with the town to resolve the issues found. Goal was to accurately resolve as many of the mismatches as possible in order to meet at least the minimum required match rate of 90% per the CT Cadastral Standard. Incorporate necessary changes to resolve mismatches into the GIS data. In some cases this involved completely redrawing new parcel boundaries from recorded plans that were located during the resolution step, for changes such as lot splits or merges that will resolve a mismatch. The Coordinate Geometry (COGO) method was employed for creating or updating parcels lines when a recorded plan with the bearings or angles and distances are provided.The next step in the process was to assess the overall quality of the linework, flag areas of major concern with Errata Points, and attempt to acquire additional plans or other input from the town to address these areas. AppGeo adjusted the parcel linework using the more accurate boundaries depicted on plans that were made available. The surrounding (less accurate) parcels were then adjusted to the new (more accurate) parcels. The remaining parcels were visually inspected for alignment to the orthophotos. If determined necessary, the right of way lines and interior lot lines for each block of parcels were adjusted to visually match base map features on a block by block basis. If a town had, and provided to AppGeo, a dimension text layer, then the parcel lines were adjusted while maintaining parcel line lengths as defined by the dimension text per the best fit. If any of the original parcels had been created or maintained using Coordinate Geometry (COGO) and are identified as such in the existing parcel attributes, those parcels’ boundaries were held firmly as is and were not modified during the alignment process. Feature level metadata for all parcels edited during this process were updated in the parcel layers’ attributes according to the CT Cadastral Standard attribution guidelines. Internal QA/QC was done by AppGeo and then the data were reviewed by CRCOG.
This shapefile represents the School District Boundaries of Anoka County. The data was derived from the Anoka County COGO Parcel data layer using the Levy Code field from the property records tax extract.
The approach and process to create the regional, standardized parcel data for the project involved the following steps. First convert the collected parcel data from its current format into the required Esri Geodatabase format, and the CT Cadastral Standard file Geodatabase template. All pre-existing parcel polygon attributes and parcel line attributes (including any feature level metadata) that were both part of the standard and also those that are not part of the standard attributes, were preserved as appended fields in the attribute tables. Next the GIS Link currently employed by the town was determined and if there was not an existing link, then AppGeo created one. If necessary, an Intersection table was created to establish the “many-to-one” relationship of condos and these special types of parcels. Analyze the data and report the mismatches for parcels with no CAMA as well as CAMA with no parcels. Analyze the parcels data for duplicate IDs. Document and submit to the towns, the analyses results and a map depicting the parcels that do not have a matching CAMA record, and work with the town to resolve the issues found. Goal was to accurately resolve as many of the mismatches as possible in order to meet at least the minimum required match rate of 90% per the CT Cadastral Standard. Incorporate necessary changes to resolve mismatches into the GIS data. In some cases this involved completely redrawing new parcel boundaries from recorded plans that were located during the resolution step, for changes such as lot splits or merges that will resolve a mismatch. The Coordinate Geometry (COGO) method was employed for creating or updating parcels lines when a recorded plan with the bearings or angles and distances are provided.The next step in the process was to assess the overall quality of the linework, flag areas of major concern with Errata Points, and attempt to acquire additional plans or other input from the town to address these areas. AppGeo adjusted the parcel linework using the more accurate boundaries depicted on plans that were made available. The surrounding (less accurate) parcels were then adjusted to the new (more accurate) parcels. The remaining parcels were visually inspected for alignment to the orthophotos. If determined necessary, the right of way lines and interior lot lines for each block of parcels were adjusted to visually match base map features on a block by block basis. If a town had, and provided to AppGeo, a dimension text layer, then the parcel lines were adjusted while maintaining parcel line lengths as defined by the dimension text per the best fit. If any of the original parcels had been created or maintained using Coordinate Geometry (COGO) and are identified as such in the existing parcel attributes, those parcels’ boundaries were held firmly as is and were not modified during the alignment process. Feature level metadata for all parcels edited during this process were updated in the parcel layers’ attributes according to the CT Cadastral Standard attribution guidelines. Internal QA/QC was done by AppGeo and then the data were reviewed by CRCOG.
Subdivision Maps, including Final Maps and Parcel Maps. A Final map is a major subdivision with 5 or more lots, and a Parcel Map is 4 or fewer lots.Subdivision map boundaries are based on Lot Lines COGO feature class where available. If Lot Lines COGO features are not available, boundaries are approximate.Attribute table contains field with link to a scanned copy of the recorded map, hosted on the internet.If Lot Lines COGO features are not available for a subdivision, Subdivision Lot features will not exist.
The geometry of parcels were created by Sherburne County's Public Works department using COGO in an AutoCad environment. The AutoCad lines have been imported into a ArcGIS Geodatabase and polygons built. These polygons are attributed with a Parcel Identification Number (PID). The GIS polygons are joined by PID to the Assessor's tax database to show attributes of the property.
The geometry of parcels were created by Carver County's Survey department using COGO in an AutoCad environment. The AutoCad lines have been imported into a ArcGIS Geodatabase and polygons built. These polygons are attributed with a Parcel Identification Number (PID). The GIS polygons are joined by PID to the Assessor's CAMA system and Taxpayer Services tax database to show attributes of the property.
The Adams County Parcel Database was derived from a variety of source maps including survey plats, deed descriptions, subdivision plats, certified survey maps and right-of-way plats. All new parcels are entered into the database using coordinate geometry (COGO). Note that the End_Date column is used to identify retired parcels. Current parcels have no End_Date value and can be viewed by setting a definition query like this: SELECT * FROM Parcel WHERE End_Date IS NULL.
Open Government Licence - Canada 2.0https://open.canada.ca/en/open-government-licence-canada
License information was derived automatically
Surveyed Land Parcel Boundaries consist of the lines required to form the boundaries of the Land Parcels. COGO attributes are associated to the lines and depict the adjusted framework of the cadastral fabric.Distributed from GeoYukon by the Government of Yukon. Discover more digital map data and interactive maps from Yukon’s digital map data collection.For more information: geomatics.help@gov.yk.ca
This data is a depiction of approximate parcel boundaries within Madison County, Idaho. The parcels are formatted to match the Idaho "Parcel Data Exchange Standard". The data is in a "NAD 1983 State Plane, Idaho East Zone (US Feet)" coordinate system. It was developed using COGO and other traditional mapping methods, and is maintained as a combined effort of the Madison County Assessor's Office and the Madison County-City of Rexburg GIS Department.
Officel repository of parcel lines transcribed from recorded plats. Coordinate Geometry (COGO) and an accuracy code to evaluate the accuracy to the plat began in 2009 on all new recorded plats. This also was the beginning of a parcel realignment project that is reviewing each subdivision to improve accuracy. Contact Glynn County GIS Department (912)554-7418 at 1725 Reynolds St Suite 205 Brunswick, GA 31520.