Name: Parcels
Display Field: OWNRNAME
Type: Feature Layer
Geometry Type: esriGeometryPolygon
Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>DOUGLAS COUNTY SURVEY/GIS </SPAN><A href="\\pubworks2116\gis\GIS_PARCEL_PROCED.pdf"><SPAN STYLE="font-weight:bold;font-size:14pt">GIS PARCEL MAPPING GUIDELINES </SPAN></A><SPAN>FOR PARCEL DISCREPANCIES.</SPAN></P><P><SPAN>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><P><SPAN>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><P><SPAN>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 “unknown” 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 “survey line” and accompanying text for the line not used for the parcel boundary.</SPAN></P><P><SPAN>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>
Service Item Id: 2483c3cf4d16432fb6cec97088ec568e
Copyright Text: Katie Reitter, Brian Bjelland (Pro West and Associates)
Default Visibility: true
MaxRecordCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 24000.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: true
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Extent:
XMin: -1.0661236761508346E7
YMin: 5741419.621955072
XMax: -1.0590263229820793E7
YMax: 5797996.580318513
Spatial Reference: 102100
(3857)
LatestVCSWkid(0)
Drawing Info:
Renderer:
Simple Renderer:
Symbol: Style: esriSFSSolid
Color: [130, 130, 130, 0]
Outline:
Style: esriSLSSolid
Color: [78, 78, 78, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 35
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: N/A
Use Coded Values: true
Symbol:
Color: [78, 78, 78, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 8
Font Family: Tahoma
Font Style: normal
Font Weight: normal
Font Decoration: none
Min. Scale: 24000.0
Max. Scale: 0.0
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
HasZ: true
HasM: false
Has Attachments: false
HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText
Type ID Field: null
Fields:
-
OBJECTID
(
type: esriFieldTypeOID, alias: OBJECTID
)
-
PIN
(
type: esriFieldTypeString, alias: PIN, length: 16
)
-
CODE
(
type: esriFieldTypeSmallInteger, alias: CODE
)
-
GIS_ACRES
(
type: esriFieldTypeDouble, alias: GIS_ACRES
)
-
WATER_AC
(
type: esriFieldTypeDouble, alias: WATER_AC
)
-
Parcel_AC
(
type: esriFieldTypeDouble, alias: Parcel_AC
)
-
ROW_AC
(
type: esriFieldTypeDouble, alias: ROW_AC
)
-
Shape
(
type: esriFieldTypeGeometry, alias: Shape
)
-
TXOTXT_NAM
(
type: esriFieldTypeString, alias: TXOTXT_NAM, length: 30
)
-
OWNRNAME
(
type: esriFieldTypeString, alias: OWNRNAME, length: 50
)
-
TXTNAM
(
type: esriFieldTypeString, alias: TXTNAM, length: 30
)
-
TX_LOTBLOK
(
type: esriFieldTypeString, alias: TX_LOTBLOK, length: 7
)
-
TXPLATD
(
type: esriFieldTypeString, alias: TXPLATD, length: 42
)
-
TX_DSC_1_8
(
type: esriFieldTypeString, alias: TX_DSC_1_8, length: 343
)
-
TX_SSTTTRR
(
type: esriFieldTypeString, alias: TX_SSTTTRR, length: 9
)
-
RVSDOWNR
(
type: esriFieldTypeString, alias: RVSDOWNR, length: 50
)
-
OWNRADDR1
(
type: esriFieldTypeString, alias: OWNRADDR1, length: 50
)
-
OWNRADDR2
(
type: esriFieldTypeString, alias: OWNRADDR2, length: 50
)
-
OWNRADDR3
(
type: esriFieldTypeString, alias: OWNRADDR3, length: 50
)
-
OWNRADDR4
(
type: esriFieldTypeString, alias: OWNRADDR4, length: 50
)
-
MAIL_CITY
(
type: esriFieldTypeString, alias: MAIL_CITY, length: 50
)
-
MAIL_STATE
(
type: esriFieldTypeString, alias: MAIL_STATE, length: 50
)
-
MAIL_ZIP
(
type: esriFieldTypeString, alias: MAIL_ZIP, length: 50
)
-
TXCITYD
(
type: esriFieldTypeString, alias: TXCITYD, length: 28
)
-
TXSCHL
(
type: esriFieldTypeString, alias: TXSCHL, length: 41
)
-
CODE_ADD
(
type: esriFieldTypeSmallInteger, alias: CODE_ADD
)
-
TXPLAT
(
type: esriFieldTypeSmallInteger, alias: TXPLAT
)
-
TXPADR1
(
type: esriFieldTypeString, alias: TXPADR1, length: 38
)
-
TXANAM
(
type: esriFieldTypeString, alias: TXANAM, length: 30
)
-
TXONAM
(
type: esriFieldTypeString, alias: TXONAM, length: 30
)
-
TXDESC
(
type: esriFieldTypeString, alias: TXDESC, length: 42
)
-
SRCRV1
(
type: esriFieldTypeString, alias: SRCRV1, length: 8
)
-
DOCUMENT_INFO
(
type: esriFieldTypeString, alias: DOCUMENT_INFO, length: 1073741822
)
-
appxtender_info
(
type: esriFieldTypeString, alias: appxtender_info, length: 1073741822
)
-
TXFLAG
(
type: esriFieldTypeString, alias: TXFLAG, length: 255
)
-
Shape.STArea()
(
type: esriFieldTypeDouble, alias: Shape.STArea()
)
-
Shape.STLength()
(
type: esriFieldTypeDouble, alias: Shape.STLength()
)
Supported Operations:
Query
Query Attachments
Query Analytic
Generate Renderer
Return Updates
Iteminfo
Thumbnail
Metadata