20230208
14301900
1.0
FGDC CSDGM Metadata
FALSE
BayfieldCounty_XLU_2023
294887.594486
773288.286709
225105.521465
734392.093555
1
002
0.000
Projected
GCS_North_American_1983_HARN
Linear Unit: Foot_US (0.304801)
NAD_1983_HARN_WISCRS_Bayfield_County_Feet
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.4.0'><WKT>PROJCS["NAD_1983_HARN_WISCRS_Bayfield_County_Feet",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",750000.001],PARAMETER["False_Northing",487372.659],PARAMETER["Central_Meridian",-91.15277777777779],PARAMETER["Standard_Parallel_1",46.66964837722222],PARAMETER["Scale_Factor",1.0000331195],PARAMETER["Latitude_Of_Origin",46.66964837722222],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",8216]]</WKT><XOrigin>-118376900</XOrigin><YOrigin>-98863600</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>103403</WKID><LatestWKID>8216</LatestWKID></ProjectedCoordinateSystem>
20251009
13483800
20251009
13483800
625000
5000
ItemDescription
Peter Herreid
WLIP - DOA
Grant Administrator to the WLIP
ArcGIS Metadata
1.0
10.3
Enterprise Geodatabase Feature Class
0.000
vector digital data
V7.0.0_WisconsinParcels_2021
2021-06-30T00:00:00
2021-06-30T00:00:00
V7.0.0
20210630
BayfieldCounty_XLU_2023
Existing Land Use
Bayfield County
NWRPC
Comprehensive Plan
Bayfield County Existing Land Use
The layer was created as part of the Bayfield County Comprehensive Plan Update 2023
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data was created through Interpretation of aerial imagery, ownership information, improved value, and acreage, by NWRPC staff. This data was then electronically reviewed by Town residents and changes were made to Existing Land Use classifications, based on local knowledge.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
This data is a product based off of the Statewide Parcel Map Database Project. Created by: The Wisconsin State Cartographer's Office, Administrated by: The Wisconsin Land Information Program (WLIP) at the Department of Administration (DOA)
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data free for public consumption</SPAN></P><P><SPAN>No warranty, expressed or implied, is made regarding accuracy, completeness, or legality of the information herein. The boundaries depicted on this map do not represent the legal ownership boundaries of any property. The delineation of legal boundaries may only be conducted by a licensed surveyor. This map is not a survey of the actual boundary of any property this map depicts.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
Peter Herreid
Wisconsin Department of Administration
2022-06-30T00:00:00
Esri ArcGIS 13.0.3.36057
1
-92.963573
-86.666103
47.083040
42.456897
2021-06-30T00:00:00
This layer is the result of aggregation procedures implemented over parcel and tax roll data provided by Wisconsin's 72 counties.
Contributing Counties:
Adams County
Ashland County
Barron County
Bayfield County
Brown County
Buffalo County
Burnett County
Calumet County
Chippewa County
Clark County
Columbia County
Crawford County
Dane County
Dodge County
Door County
Douglas County
Dunn County
Eau Claire County
Florence County
Fond du Lac County
Forest County
Grant County
Green County
Green Lake County
Iowa County
Iron County
Jackson County
Jefferson County
Juneau County
Kenosha County
Kewaunee County
La Crosse County
Lafayette County
Langlade County
Lincoln County
Manitowoc County
Marathon County
Marinette County
Marquette County
Menominee County
Milwaukee County
Monroe County
Oconto County
Oneida County
Outagamie County
Ozaukee County
Pepin County
Pierce County
Polk County
Portage County
Price County
Racine County
Richland County
Rock County
Rusk County
Sauk County
Sawyer County
Shawano County
Sheboygan County
St. Croix County
Taylor County
Trempealeau County
Vernon County
Vilas County
Walworth County
Washburn County
Washington County
Waukesha County
Waupaca County
Waushara County
Winnebago County
Wood County
False
0
False
0
BayfieldCounty_XLU_2023
Feature Class
0
V7 Wisconsin Statewide Parcel Layer (2021)
SCO
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
SHAPE
Shape
Geometry
8
0
0
Feature geometry.
Esri
Coordinates defining the features.
PARCELID
PARCELID
String
100
0
0
- Unique number or identifier assigned to a parcel by the local authority.
- Examples (this list is not exhaustive):
• 071006113329 • B-600-88
• 010-0640.01
• VH-747-E-28
• 4205 • WA0320124700
- PARCELID is the primary identifier for each record in the statewide database.
- In some cases, PARCELID may be populated with a TAXPARCELID value.
- Either the value in PARCELID or TAXPARCELID should function in the county’s online property search tool(s) to look up more information on the parcel that may be available—such as to download a digital copy of the tax bill.
- Parcel ID format varies across local governments. End users can find an explanation of parcel ID formats from the Wisconsin Department of Revenue’s webpage on State of Wisconsin Municipality Parcel Formats.
- PARCELID can be formatted with special characters like dashes, periods, forward or backslashes, and spaces. To locate a particular parcel on county land information websites or in the Wisconsin Department of Revenue’s
Real Estate Transfer Return (RETR) database, end users may need to either use the PARCELID or TAXPARCELID and include or exclude special characters like dashes.
- PARCELID FOR NON-PARCEL FEATURES – If the attribute element’s geometry is not a parcel, then the PARCELID field should contain a label of the non-parcel feature.
- Rights of way and hydrography polygon labels should be included with parcel feature class submission.
- Examples of PARCELID for non-parcel features (this list is not exhaustive):
• PARCELID = BALSAM LAKE (to label a hydrography/lake polygon)
• PARCELID = LAKE (to label a hydrography/lake polygon)
• PARCELID = HYDRO (to label a hydro polygon)
• PARCELID = WATER (to label a hydro polygon)
• PARCELID = ROW (to label a street right of way polygon)
• PARCELID = GAP (to label a gap in the parcel geometries)
• PARCELID = RAIL (to label a railroad polygon)
SCO
Acres
Acres
Double
8
38
8
TAXPARCELI
TAXPARCELI
String
100
0
0
OWNERNME1
OWNERNME1
String
254
0
0
- The primary owner name of a parcel.
- In the case of multiple owners, if it is not clear which owner is the primary owner, discretion may be used to place an owner in this field.
- If not feasible to parse owners into separate fields, more than one owner may be included in this field.
- 2nd owner goes in OWNERNME2; 3rd owner is omitted.
- If surnames are natively maintained in fields separate from first names, they should be concatenated and placed in the OWNERNME1 field.
- Owner name does not follow formatting syntax and may be provided as is.
- OWNERNME1 can be ordered in any order (First, Last, Middle Initial). It may or may not include middle initial.
- Owner’s first and last names are provided, except in cases when owners share last names, as in “SUE AND JAMES SMITH” or “SMITH, JAMES & SUE”
- OWNERNME1 example formats:
JOHN SMITH SMITH, JOHN R JOHN R and SUE SMITH SMITH,
SUE & JOHN
JOHN R SMITH JOHN R & SUE SMITH JANE, JOHN & SUE SMITH Other(s). . .
- OWNERNME1 – Redaction Policy
• Owner names are necessary for data submittal to be usable by state agencies. Any redaction of owner names, as required by an existing county or municipal policy, should be handled explicitly in the data before it is submitted. If any or all owner names are not included, the county must include the written policy for excluding them as adopted by the county or municipality (by link or full text) within the submission form.
• If redaction of owner name is implemented on the submitted data, these names should be attributed as “NOT AVAILABLE” within each redacted record’s OWNERNME1 and/or OWNERNME2 field.
• The exception is public lands. Public lands that have a government-entity as a primary owner in the OWNERNME1 field shall not be redacted.
- OWNERNME1 – Public Lands Policy
• Public lands should be designated by way of owner name in the OWNERNME1 field
Example: OWNERNME1 = DEPARTMENT OF NATURAL RESOURCES
• All county-owned public parcels must have a value in OWNERNME1
• For publicly owned parcels, the same owner should be designated the same way if they own multiple parcels.
In other words, standardize owner names for public parcels.
Example: “ASHLAND COUNTY FOREST” every time, not interchanged with “Ashland Co. Forest”
• For publicly-owned parcels, the order of words should be natural language order to the extent possible (with contiguous strings of text being next to each other)
Example: DEPARTMENT OF NATURAL RESOURCES
• No redaction of public lands in OWNERNME1. Public lands that have a government-entity (federal, state, county, or local) as a primary owner in the OWNERNME1 field shall not be redacted.
SCO
OWNERNME2
OWNERNME2
String
254
0
0
- If available. The secondary owner name of a parcel.
- 2nd owner goes in OWNERNME2; 3rd owner is omitted.
• If there are more than two total owners exist for the property, discretion may be used to select the first two owners for the purpose of populating OWNERNME1 and OWNERNME2. Remaining owner names will not be included in the dataset.
• In the case of multiple owners, if it is not clear which owner is the secondary owner, discretion may be used to place an owner in this field.
- If it is not feasible to parse owners into separate fields, more than one owner may be included in this field.
- Owner name does not require formatting and may be provided as is.
- When possible, OWNERNME2 should not be an overflow from OWNERNME1.
- OWNERNME2 Redaction Policy– OWNERNME2 adheres to the same redaction policy as that of OWNERNME1.
SCO
SITEADRESS
SITEADRESS
String
200
0
0
- The full physical address (or site address) of a parcel.
- A single field comprised of the following elements (*where applicable):
• ADDNUMPREFIX*
• ADDNUM
• ADDNUMSUFFIX*
• [PREFIX]*
• STREETNAME
• [STREETTYPE]*
• [SUFFIX]*
• [UNITTYPE]*
• UNITID*
CITY, STATE, ZIP SITEADRESS do NOT include “city, state, zip”
• Example: N472.5 N JOHNSON STREET
• Example: 543 CTH MM N SUITE 101
- Only include primary address; 2nd address is omitted.
If there are more than two physical addresses associated with a parcel, such as with an apartment, then a valid primary address is to be used, if available. Such an example of this would be an apartment’s on-site office address. Alternatively, discretion may be used to select one “primary” physical address for the parcel.
- Address ranges are not accepted. Field should not have multiple address numbers.
- Domain standardization optional. Full physical address in SITEADRESS can contain elements with non-standardized domains. However, individual address elements require domain standardization in their respective fields.
• Standard USPS Postal domains/abbreviations are acceptable in SITEADRESS.
- When a true site address does not exist, a value of <Null> may exist.
SCO
PLACENAME
PLACENAME
String
100
0
0
- The name of the authoritative jurisdiction that the parcel belongs to.
- This is not the USPS Postal place name of the parcel, instead, it is the city/village/town where the parcel is actually located; the jurisdictional place name.
The jurisdictional place name for a parcel is not necessarily the same as the USPS postal place name.
Note. The parcel’s USPS Postal place name is not required in this field, nor anywhere else in the V6 schema. USPS place name is a place name listed in the USPS City State file for delivery of mail to an address.
Although preferred for postal operations, USPS place names are often not the best-suited place names for non-postal purposes—such as navigation, public service delivery, emergency response, etc.—where jurisdictional place name may be preferred.
- Each PLACE NAME should be standardized to include the following LSAD descriptors, as appropriate:
LSAD descriptors: CITY OF TOWN OF
VILLAGE OF
PLACENAME examples:
CITY OF CHIPPEWA FALLS
TOWN OF MADISON
CITY OF MADISON
VILLAGE OF LAKE HALLIE
- *All* parcels must have a PLACENAME value, even parcels that have not been assigned an address.
SCO
IMPVALUE
IMPVALUE
Double
8
38
8
- The total value of improvements on the land, in US dollars.
IMPVALUE should be populated for: PROPCLASS = 1, 2, 3, 7
- Use “0” versus <Null> deliberately and with care in IMPVALUE field. 0 and <Null> have distinct meanings.
>0 Taxable parcel with improvements -- A positive number in IMPVALUE
0 Taxable parcel with no improvements -- Value of “0” or 0.00 in IMPVALUE
<Null> Tax exempt parcels, designated by AUXCLASS field --- Value of <Null> in IMPVALUE
<Null> Non-parcel features as labeled in PARCELID --- Value of <Null> in IMPVALUE
<Null> Parcels yet to be assessed (e.g., a new parcel/split) ---Value of <Null> in IMPVALUE
SCO
XLU_ID
Existing Land Use ID
Integer
4
10
0
GEN_XLU
GEN_XLU
String
50
0
0
CODE
CODE
String
100
0
0
Shape.STArea()
Shape.STArea()
Double
0
0
0
Shape.STLength()
Shape.STLength()
Double
0
0
0
dataset
Simple
FALSE
0
TRUE
FALSE
20251009
EPSG
9.1(10.7.0)