{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "This feature class is VERY IMPORTANT! It is used on all of our apps (internal and public). This data includes all details on parcels in Douglas County, MN.\n\nIt is updated twice a week (Tuesdays & Thursdays 4:45AM) by a model builder script (03_Fabric_Parcels_Pro) that has been converted into a python script that runs via Windows Task Scheduler (Fabric Parcel Model). Once this model is done running a SQL query is scheduled to run (Tuesdays & Thursdays 5:30AM) in which updates the tax portion of this feature class. The SQL MUST RUN AFTER the model builder/python script runs otherwise crucial data will not be included into the feature class.\n\nThe model builder script takes Parcel Fabric Parcels, goes through many processes of merging valid and non-valid pins, adding fields, creating unions, calculating fields, and then appending data to the feature class and rebuilding indexes.\n\nKatie Reitter, with the help of Brian Bjelland (Pro West and Associates) added rebuild indexes at the end of the model due to an indexing problem in SQL in which took down all applications. This will help speed up the process and cause less issues.\n\nJim: Parcels for Douglas County are usually updated on a weekly basis from activity for the week before. They are COGO entered from Deeds, Surveys, and other documents. The data set is in Douglas County Coordinates.", "description": "

DOUGLAS COUNTY SURVEY/GIS <\/SPAN>GIS PARCEL MAPPING GUIDELINES <\/SPAN><\/A>FOR PARCEL DISCREPANCIES.<\/SPAN><\/P>

It is the intent of the Douglas County GIS Parcel Mapping to accurately identify the areas of land parcels to be valued and taxed.<\/SPAN><\/P>

1. Discrepancies in areasThe Auditor/Assessor (tax) acreage areas started with the original US General Land Office (GLO) township plat maps created from the Public Land Survey (PLS) that was done between 1858 and 1871. The recovery of the PLS corners and the accurate location of these corners with GPS obtained coordinates has allowed for accurate section subdivisions, which results in accurate areas for parcels based on legal descriptions, which may be significantly different than the original areas. (See Example 2). Any parcel bordering a meandered lake and/or a water boundary will likely have a disparity of area between the Auditor/Assessor acreages and the GIS acreages because of the inaccuracy of the original GLO meander lines from which the original areas were determined. Water lines are not able to be drafted to the same accuracy as the normal parcel lines. The water lines are usually just sketched on a survey and their dimensions are not generally given on a land record. The water boundaries of our GIS parcels are located from aerial photography. This is a subjective determination based on the interpretation by the Survey/GIS technician of what is water. Some lakes fluctuate significantly and the areas of all parcels bordering water are subject to constant change. In these cases the ordinary high water line (OHW) is attempted to be identified. Use of 2-foot contours will be made, if available. (See Example 1)Some land records do not accurately report the area described in the land description and the description area is ignored. (See Example 3)The parcel mapping has made every attempt to map the parcels based on available survey information as surveyed and located on the ground. This may conflict with some record legal descriptions.SolutionsIf an actual survey by a licensed Land Surveyor is available, it will be utilized for the tax acreage.If the Auditor/Assessor finds a discrepancy between the tax and GIS areas, they will request a review by the County Survey/GIS department.As a starting guideline, the County Survey/GIS department will identify all parcels that differ in tax area versus GIS parcel area of 10 % or more and a difference of at least 5 acres. (This could be expanded later after the initial review.)Each of these identified parcels will be reviewed individually by the County Survey/GIS department to determine the reason for the discrepancy and a recommendation will be made by the County Survey/GIS department to the Auditor/Assessor if the change should be made or not.If a change is to be made to the tax area, a letter will be sent to the taxpayer informing them that their area will be changed during the next tax cycle, which could affect their property valuation. This letter will originate from the Auditor/Assessor with explanation from the County Survey/GIS department.<\/SPAN><\/P>

2. Gaps and OverlapsLand descriptions for adjoining parcels sometimes overlap or leave a gap between them.In these instances the Survey/GIS technician has to make a decision where to place this boundary. A number of circumstances are reviewed to facilitate this decision as these dilemmas are usually decided on a case by case basis. All effort will be made to not leave a gap, but sometimes this is not possible and the gap will be shown with \u201cunknown\u201d ownership. (Note: The County does not have the authority to change boundaries!)Some of the circumstances reviewed are:Which parcel had the initial legal description?Does the physical occupation of the parcel line as shown on the air photo more closely fit one of the described parcels?Interpretation of the intent of the legal description.Is the legal description surveyable?Note: These overlaps will be shown on the GIS map with a dashed \u201csurvey line\u201d and accompanying text for the line not used for the parcel boundary.<\/SPAN><\/P>

3. Parcel lines that do not match location of buildingsStructures on parcels do not always lie within the boundaries of the parcel. This may be a circumstance of building without the benefit of a survey or of misinterpreting these boundaries. The parcel lines should be shown accurately as surveyed and/or described regardless of the location of structures on the ground. NOTE: The GIS mapping is not a survey, but is an interpretation of parcel boundaries predicated upon resources available to the County Survey/GIS department.<\/SPAN><\/P><\/DIV><\/DIV><\/DIV>", "summary": "This feature class is VERY IMPORTANT! It is used on all of our apps (internal and public). This data includes all details on parcels in Douglas County, MN.\n\nIt is updated twice a week (Tuesdays & Thursdays 4:45AM) by a model builder script (03_Fabric_Parcels_Pro) that has been converted into a python script that runs via Windows Task Scheduler (Fabric Parcel Model). Once this model is done running a SQL query is scheduled to run (Tuesdays & Thursdays 5:30AM) in which updates the tax portion of this feature class. The SQL MUST RUN AFTER the model builder/python script runs otherwise crucial data will not be included into the feature class.\n\nThe model builder script takes Parcel Fabric Parcels, goes through many processes of merging valid and non-valid pins, adding fields, creating unions, calculating fields, and then appending data to the feature class and rebuilding indexes.\n\nKatie Reitter, with the help of Brian Bjelland (Pro West and Associates) added rebuild indexes at the end of the model due to an indexing problem in SQL in which took down all applications. This will help speed up the process and cause less issues.\n\nJim: Parcels for Douglas County are usually updated on a weekly basis from activity for the week before. They are COGO entered from Deeds, Surveys, and other documents. The data set is in Douglas County Coordinates.", "title": "CemeteryPublic", "tags": [ "Parcel", "metadata" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 150000000, "maxScale": 5000, "spatialReference": "", "accessInformation": "Katie Reitter, Brian Bjelland (Pro West and Associates)", "licenseInfo": "" }