Layers:

Layer: Churches (1)

Name: Churches

Display Field: OBJECTID

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description:

Service Item Id: 07297683c1e74581a1ab880a07375188

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 587212.1681687683
YMin: 106275.2613337636
XMax: 729070.1752986312
YMax: 221926.05250546336
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
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: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID_1 ( type: esriFieldTypeOID, alias: OBJECTID_1 )
• OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• FIRST_TAXP ( type: esriFieldTypeString, alias: FIRST_TAXP, length: 39 )
• DESCRIPTIO ( type: esriFieldTypeString, alias: DESCRIPTIO, length: 60 )
• Address ( type: esriFieldTypeString, alias: Address, length: 50 )
• GlobalID ( type: esriFieldTypeString, alias: GlobalID, length: 38 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )

Layer: Cemeteries (2)

Name: Cemeteries

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description:

Service Item Id: 07297683c1e74581a1ab880a07375188

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 574610.1385828555
YMin: 100984.45646263659
XMax: 733138.409616217
YMax: 222035.13562062383
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
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: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID_1 ( type: esriFieldTypeOID, alias: OBJECTID_1 )
• OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
• SORT ( type: esriFieldTypeString, alias: SORT, length: 4 )
• NAME ( type: esriFieldTypeString, alias: NAME, length: 100 )
• Cem_Name ( type: esriFieldTypeString, alias: Cem_Name, length: 50 )
• Map_Number ( type: esriFieldTypeString, alias: Map_Number, length: 10 )
• GlobalID ( type: esriFieldTypeString, alias: GlobalID, length: 38 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )

Layer: Cemetery-Private (3)

Name: Cemetery-Private

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: 07297683c1e74581a1ab880a07375188

Copyright Text: Katie Reitter, Brian Bjelland (Pro West and Associates)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 650060.7130751014
YMin: 206312.87129750848
XMax: 650212.17504251
YMax: 206463.4024925083
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [189, 130, 148, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 60
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• FID ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• CODE ( type: esriFieldTypeInteger, 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 )
• 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: 254 )
• 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: esriFieldTypeInteger, alias: CODE_ADD )
• TXPLAT ( type: esriFieldTypeInteger, 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_I ( type: esriFieldTypeString, alias: DOCUMENT_I, length: 254 )
• appxtender ( type: esriFieldTypeString, alias: appxtender, length: 254 )
• TXFLAG ( type: esriFieldTypeString, alias: TXFLAG, length: 254 )

Layer: Cemetery- Public (4)

Name: Cemetery- Public

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: 07297683c1e74581a1ab880a07375188

Copyright Text: Katie Reitter, Brian Bjelland (Pro West and Associates)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 574484.206748113
YMin: 100858.93850502372
XMax: 725396.6549225897
YMax: 222095.6520678401
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [255, 0, 0, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 60
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• FID ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• CODE ( type: esriFieldTypeInteger, 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 )
• 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: 254 )
• 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: esriFieldTypeInteger, alias: CODE_ADD )
• TXPLAT ( type: esriFieldTypeInteger, 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_I ( type: esriFieldTypeString, alias: DOCUMENT_I, length: 254 )
• appxtender ( type: esriFieldTypeString, alias: appxtender, length: 254 )
• TXFLAG ( type: esriFieldTypeString, alias: TXFLAG, length: 254 )

Layer: Church Property- Service Enterprises (5)

Name: Church Property- Service Enterprises

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: 07297683c1e74581a1ab880a07375188

Copyright Text: Katie Reitter, Brian Bjelland (Pro West and Associates)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 671680.6111081839
YMin: 149671.8602359295
XMax: 682755.2562816739
YMax: 183177.48056051135
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [255, 209, 89, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 60
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• FID ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• CODE ( type: esriFieldTypeInteger, 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 )
• 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: 254 )
• 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: esriFieldTypeInteger, alias: CODE_ADD )
• TXPLAT ( type: esriFieldTypeInteger, 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_I ( type: esriFieldTypeString, alias: DOCUMENT_I, length: 254 )
• appxtender ( type: esriFieldTypeString, alias: appxtender, length: 254 )
• TXFLAG ( type: esriFieldTypeString, alias: TXFLAG, length: 254 )

Layer: Church Property-Other Residences and Parsonages (6)

Name: Church Property-Other Residences and Parsonages

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: 07297683c1e74581a1ab880a07375188

Copyright Text: Katie Reitter, Brian Bjelland (Pro West and Associates)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 680447.820607841
YMin: 151006.9884711802
XMax: 681288.1447145939
YMax: 151316.2729575932
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [51, 227, 200, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 60
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• FID ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• CODE ( type: esriFieldTypeInteger, 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 )
• 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: 254 )
• 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: esriFieldTypeInteger, alias: CODE_ADD )
• TXPLAT ( type: esriFieldTypeInteger, 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_I ( type: esriFieldTypeString, alias: DOCUMENT_I, length: 254 )
• appxtender ( type: esriFieldTypeString, alias: appxtender, length: 254 )
• TXFLAG ( type: esriFieldTypeString, alias: TXFLAG, length: 254 )

Layer: Church Property- Rectory (7)

Name: Church Property- Rectory

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: 07297683c1e74581a1ab880a07375188

Copyright Text: Katie Reitter, Brian Bjelland (Pro West and Associates)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 590018.2560605258
YMin: 106929.25641685724
XMax: 727839.8413091749
YMax: 217468.15377692878
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [224, 59, 153, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 60
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• FID ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• CODE ( type: esriFieldTypeInteger, 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 )
• 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: 254 )
• 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: esriFieldTypeInteger, alias: CODE_ADD )
• TXPLAT ( type: esriFieldTypeInteger, 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_I ( type: esriFieldTypeString, alias: DOCUMENT_I, length: 254 )
• appxtender ( type: esriFieldTypeString, alias: appxtender, length: 254 )
• TXFLAG ( type: esriFieldTypeString, alias: TXFLAG, length: 254 )

Layer: Church Property- Sanctuaries and Edu Facilities (8)

Name: Church Property- Sanctuaries and Edu Facilities

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: 07297683c1e74581a1ab880a07375188

Copyright Text: Katie Reitter, Brian Bjelland (Pro West and Associates)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: false

Supports Statistics: false

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 587054.7026044428
YMin: 105789.87614968419
XMax: 729124.7298155129
YMax: 222095.6520678401
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 112, 255, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 60
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: false
Supports OrderBy: false
Supports Distinct: false
Supports Pagination: false
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: false
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• FID ( type: esriFieldTypeOID, alias: FID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• CODE ( type: esriFieldTypeInteger, 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 )
• 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: 254 )
• 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: esriFieldTypeInteger, alias: CODE_ADD )
• TXPLAT ( type: esriFieldTypeInteger, 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_I ( type: esriFieldTypeString, alias: DOCUMENT_I, length: 254 )
• appxtender ( type: esriFieldTypeString, alias: appxtender, length: 254 )
• TXFLAG ( type: esriFieldTypeString, alias: TXFLAG, length: 254 )

Layer: Parcel Labels (9)

Name: Parcel Labels

Display Field: PIN

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description:

Service Item Id: 07297683c1e74581a1ab880a07375188

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 16000.0

Max Scale: 100.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: 571084.055083856
YMin: 100468.60824893415
XMax: 732369.4431423396
YMax: 228175.33938349783
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [240, 240, 240, 0]
Outline:
N/A
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
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:
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS_ACRES )
• TXTNAM ( type: esriFieldTypeString, alias: TXTNAM, length: 30 )
• TXOTXT_NAM ( type: esriFieldTypeString, alias: TXOTXT_NAM, length: 30 )
• OWNRNAME ( type: esriFieldTypeString, alias: OWNRNAME, length: 50 )
• 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 )
• Parcel_AC ( type: esriFieldTypeDouble, alias: PARCEL_AC )
• ROW_AC ( type: esriFieldTypeDouble, alias: ROW_AC )
• WATER_AC ( type: esriFieldTypeDouble, alias: WATER_AC )
• 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 )
• CODE ( type: esriFieldTypeSmallInteger, alias: CODE )
• 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 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• 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 )

Layer: E911 Address (10)

Name: E911 Address

Display Field: ADDRESS

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description:

Service Item Id: 07297683c1e74581a1ab880a07375188

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 4000.0

Max Scale: 100.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.188342E8
YMin: -9.88767E7
XMax: 743486.9002502263
YMax: 227953.79128022492
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Label Placement: esriServerPointLabelPlacementAboveRight
Label Expression: [HNUM_HALF]
Use Coded Values: true
Symbol:
Color: [230, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: baseline
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 10
Font Family: Gadugi
Font Style: normal
Font Weight: normal
Font Decoration: none

Min. Scale: 0.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: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• Location ( type: esriFieldTypeString, alias: Location, length: 50 )
• ADDRESS ( type: esriFieldTypeString, alias: ADDRESS, length: 50 )
• HNUM_HALF ( type: esriFieldTypeString, alias: HNUM_HALF, length: 15 )
• STREET ( type: esriFieldTypeString, alias: STREET, length: 50 )
• TOWNSHIP ( type: esriFieldTypeString, alias: TOWNSHIP, length: 20 )
• LATITUDE ( type: esriFieldTypeDouble, alias: LATITUDE )
• LONGITUDE ( type: esriFieldTypeDouble, alias: LONGITUDE )
• Dir_P1 ( type: esriFieldTypeString, alias: Dir_P1, length: 4 )
• Name_P2 ( type: esriFieldTypeString, alias: Name_P2, length: 50 )
• Type_P3 ( type: esriFieldTypeString, alias: Type_P3, length: 10 )
• Sfx_P4 ( type: esriFieldTypeString, alias: Sfx_P4, length: 4 )
• DNR_ACCESS ( type: esriFieldTypeString, alias: DNR_ACCESS, length: 10 )
• CM ( type: esriFieldTypeString, alias: CM, length: 10 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• SD ( type: esriFieldTypeString, alias: SD, length: 10 )
• MCD ( type: esriFieldTypeString, alias: MCD, length: 6 )
• CELL_TOWER ( type: esriFieldTypeString, alias: CELL_TOWER, length: 20 )
• ELEMNAME ( type: esriFieldTypeString, alias: ELEMNAME, length: 10 )
• WD ( type: esriFieldTypeString, alias: WD, length: 10 )
• JD ( type: esriFieldTypeString, alias: JD, length: 10 )
• LG ( type: esriFieldTypeString, alias: LG, length: 10 )
• SN ( type: esriFieldTypeString, alias: SN, length: 10 )
• CG ( type: esriFieldTypeString, alias: CG, length: 10 )
• FTG_Permit ( type: esriFieldTypeString, alias: FTG_Permit, length: 12 )
• PARCELID ( type: esriFieldTypeString, alias: PARCELID, length: 20 )
• OWNAME ( type: esriFieldTypeString, alias: OWNAME, length: 30 )
• OWNAME_HOLD ( type: esriFieldTypeString, alias: OWNAME_HOLD, length: 30 )
• HNUM_PROPOSED ( type: esriFieldTypeString, alias: HNUM_PROPOSED, length: 6 )
• HNUM_OLD ( type: esriFieldTypeString, alias: HNUM_OLD, length: 10 )
• Flagged_for_911 ( type: esriFieldTypeString, alias: Flagged_for_911_Number_Change, length: 254 )
• E911_Sign_Status ( type: esriFieldTypeString, alias: E911_Sign_Status, length: 15 )
• Proposed_Set_Date ( type: esriFieldTypeString, alias: Proposed_Set_Date, length: 20 )
• Physical_Set_Date ( type: esriFieldTypeString, alias: Physical_Set_Date, length: 20 )
• E911_Sign_Notes ( type: esriFieldTypeString, alias: E911_Sign_Notes, length: 50 )
• A_COMMENTS ( type: esriFieldTypeString, alias: Address Comments, length: 254 )
• FP_id ( type: esriFieldTypeString, alias: FP_id, length: 5 )
• PDF ( type: esriFieldTypeString, alias: PDF, length: 3 )
• FLOOR_PLANS ( type: esriFieldTypeString, alias: FLOOR_PLANS, length: 200 )
• VESN ( type: esriFieldTypeInteger, alias: VESN )
• FIRE_STATION ( type: esriFieldTypeString, alias: FIRE_STATION, length: 20 )
• ALASD ( type: esriFieldTypeString, alias: ALASD, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• Z_last_edited_user ( type: esriFieldTypeString, alias: Z_last_edited_user, length: 10 )
• Z_last_edited_date ( type: esriFieldTypeDate, alias: Z_last_edited_date, length: 8 )
• PCT_Name ( type: esriFieldTypeString, alias: PCT_Name, length: 25 )
• PCT_Code ( type: esriFieldTypeString, alias: PCT_Code, length: 10 )
• MCD_Code_Voters ( type: esriFieldTypeString, alias: MCD_Code_Voters, length: 10 )
• ADD_ID ( type: esriFieldTypeString, alias: Address Unique Identifier, length: 36 )
• ANUMBER ( type: esriFieldTypeInteger, alias: Address Number )
• ANUMBERSUF ( type: esriFieldTypeString, alias: Address Number Suffix, length: 15 )
• ST_PRE_DIR ( type: esriFieldTypeString, alias: Street Name Pre Directional, length: 9 )
• ST_PRE_TYP ( type: esriFieldTypeString, alias: StreetPreType, length: 35 )
• ST_NAME ( type: esriFieldTypeString, alias: Street Name, length: 60 )
• ST_POS_TYP ( type: esriFieldTypeString, alias: Street Name Post Type, length: 15 )
• ST_POS_DIR ( type: esriFieldTypeString, alias: Street Name Post Directional, length: 9 )
• SUB_TYPE1 ( type: esriFieldTypeString, alias: SUB_TYPE1, length: 12 )
• SUB_ID1 ( type: esriFieldTypeString, alias: SUB_ID1, length: 30 )
• ZIP ( type: esriFieldTypeString, alias: ZIP Code, length: 5 )
• ZIP4 ( type: esriFieldTypeString, alias: ZIP Plus 4, length: 4 )
• CTU_NAME ( type: esriFieldTypeString, alias: CTU_NAME, length: 100 )
• CTU_ID_TXT ( type: esriFieldTypeString, alias: CTU_ID_TXT, length: 8 )
• POSTCOMM ( type: esriFieldTypeString, alias: POSTCOMM, length: 40 )
• CO_CODE ( type: esriFieldTypeString, alias: County Code, length: 5 )
• CO_NAME ( type: esriFieldTypeString, alias: County Name, length: 40 )
• STATE_CODE ( type: esriFieldTypeString, alias: State Code, length: 2 )
• COUNTRY ( type: esriFieldTypeString, alias: Country, length: 5 )
• CEN_GEO ( type: esriFieldTypeString, alias: Centerline Geocodable, length: 10 )
• UNI_WO_SUB ( type: esriFieldTypeString, alias: Unique Without Subaddresses, length: 10 )
• GIS911POC ( type: esriFieldTypeString, alias: 911 GIS Point-of-Contact, length: 75 )
• ESN ( type: esriFieldTypeString, alias: Emergency Service Number, length: 5 )
• PSAP_CODE ( type: esriFieldTypeString, alias: PSAP_CODE, length: 5 )
• MSAG_C ( type: esriFieldTypeString, alias: MSAG Community Name, length: 30 )
• VERROR_911 ( type: esriFieldTypeString, alias: 911 Validation Error, length: 10 )
• LST_PREDIR ( type: esriFieldTypeString, alias: Legacy Street Name Pre Directional, length: 2 )
• LST_NAME ( type: esriFieldTypeString, alias: Legacy Street Name, length: 75 )
• LST_TYPE ( type: esriFieldTypeString, alias: Legacy Street Name Type, length: 4 )
• LST_POSDIR ( type: esriFieldTypeString, alias: Legacy Street Name Post, length: 2 )
• AAUTHORITY ( type: esriFieldTypeString, alias: Address Authority, length: 40 )
• EDIT_ORG ( type: esriFieldTypeString, alias: Editing Organization, length: 40 )
• EDIT_DATE ( type: esriFieldTypeDate, alias: Edit Date, length: 8 )
• COMMENTS ( type: esriFieldTypeString, alias: COMMENTS, length: 254 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Layer: Parcels (11)

Name: Parcels

Display Field: OWNRNAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description:

Service Item Id: 07297683c1e74581a1ab880a07375188

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 64000.0

Max Scale: 100.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 571084.055083856
YMin: 100468.60824893415
XMax: 732369.4431423396
YMax: 228175.33938349783
Spatial Reference: 103728  (103728)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [104, 104, 104, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
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:
• PIN ( type: esriFieldTypeString, alias: PIN, length: 16 )
• OWNRNAME ( type: esriFieldTypeString, alias: 99!Taxpayer, length: 50 )
• TXTNAM ( type: esriFieldTypeString, alias: Taxpayer, length: 30 )
• TX_LOTBLOK ( type: esriFieldTypeString, alias: Lot-Block, length: 7 )
• TXPLATD ( type: esriFieldTypeString, alias: Plat Description, length: 42 )
• TX_DSC_1_8 ( type: esriFieldTypeString, alias: Description, length: 343 )
• GIS_ACRES ( type: esriFieldTypeDouble, alias: GIS Acres )
• TX_SSTTTRR ( type: esriFieldTypeString, alias: Sec-Twp-Rng, length: 9 )
• ROW_AC ( type: esriFieldTypeDouble, alias: Acres Under ROW )
• WATER_AC ( type: esriFieldTypeDouble, alias: Acres Under Water )
• TXPADR1 ( type: esriFieldTypeString, alias: Property Address, length: 38 )
• TXCITYD ( type: esriFieldTypeString, alias: Jurisdiction, length: 28 )
• TXSCHL ( type: esriFieldTypeString, alias: ISD, length: 41 )
• RVSDOWNR ( type: esriFieldTypeString, alias: Mail Name 1, length: 50 )
• OWNRADDR1 ( type: esriFieldTypeString, alias: Mail Name 2, length: 50 )
• OWNRADDR2 ( type: esriFieldTypeString, alias: Mail Name 3, length: 50 )
• OWNRADDR3 ( type: esriFieldTypeString, alias: Mail Name 4, length: 50 )
• OWNRADDR4 ( type: esriFieldTypeString, alias: Mail Name 5, length: 50 )
• CODE_ADD ( type: esriFieldTypeSmallInteger, alias: 99!CODE_ADD )
• CODE ( type: esriFieldTypeSmallInteger, alias: 99!CODE )
• TXANAM ( type: esriFieldTypeString, alias: 99!TXANAM, length: 30 )
• TXONAM ( type: esriFieldTypeString, alias: 99!TXONAM, length: 30 )
• TXDESC ( type: esriFieldTypeString, alias: 99!Lake, length: 42 )
• SRCRV1 ( type: esriFieldTypeString, alias: 99!SRCRV1, length: 8 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )
• 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 )