20250619 10492700 1.0 ISO 19139 Metadata Implementation Specification GML3.2 FALSE substation_parcel 294887.613100 773288.286600 225105.521500 734392.093500 1 002 0.000 Projected GCS_North_American_1983 Linear Unit: Foot_US (0.304801) NAD_1983_StatePlane_Wisconsin_South_FIPS_4803_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_StatePlane_Wisconsin_South_FIPS_4803_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",1968500.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-90.0],PARAMETER["Standard_Parallel_1",42.73333333333333],PARAMETER["Standard_Parallel_2",44.06666666666667],PARAMETER["Latitude_Of_Origin",42.0],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2289]]</WKT><XOrigin>-118121300</XOrigin><YOrigin>-97418300</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102754</WKID><LatestWKID>2289</LatestWKID></ProjectedCoordinateSystem> 20250609 08404200 20250609 08404200 625000 5000 FGDC Peter Herreid WLIP - DOA Grant Administrator to the WLIP ArcGIS Metadata 1.0 10.3 File Geodatabase Feature Class 0.000 vector digital data V10.0.0_WisconsinParcels_2024 2024-06-30T00:00:00 2024-06-30T00:00:00 V10.0.0 20240630 substation_parcel V10 Parcels V9 Parcels V8 Parcels V7 Parcels V6 Parcels V5 Parcels V4 Parcels V3 Parcels V2 Parcels V1 Parcels United States Wisconsin WLIP Act 20 Parcels Parcel ID Tax Parcel ID Parcel Source Parcel Source FIPS Load Date County Name GIS Acres Assessed Acres Deeded Acres Auxiliary Class of Property Class of Property Gross Property Tax Net Property Tax Estimated Fair Market Value Assessed Value of MFL/FCL Land Assessed Value of Improvements Assessed Value of Land Total Assessed Value School District Number School District State Zip Code Zip Code Plus 4 Place Name Unit ID Unit Type Landmark Name Suffix Street Type Street Name Prefix Address Number Suffix Address Number Address Number Prefix Full Physical Address Full Mailing Address Secondary Owner Name Primary Owner Name Parcel Date Tax Roll Year State ID Wisconsin Statewide Parcel Layer Version 10.0.0 (V10.0.0) The layer was created as the final deliverable to the V10 Parcel Project, which is the eighth development cycle of the Statewide Parcel Map Initiative. See https://doa.wi.gov/Pages/LocalGovtsGrants/Parcel-Initiative.aspx for more information on this project. <DIV STYLE="text-align:Left;"><DIV><DIV>This is the final deliverable for the Version 10 Statewide Parcel Map Database Project (V10). This feature class represents a comprehensive, spatially referenced collection of parcel geometries as recognized by local-level governments within the State of Wisconsin (the feature class is aggregated from county level and municipal-level data). See the V10 Project Homepage for more detail on the parameters for how data was prepared and submitted to this project: <A href="http://www.sco.wisc.edu/parcels/submission/" STYLE="text-decoration:underline;">https://www.sco.wisc.edu/parcels/submission/</A>.Schema documentation can be found within this feature class metadata and here: <A href="http://www.sco.wisc.edu/parcels/data/assets/V3/V3_Wisconsin_Statewide_Parcels_Schema_Documentation.pdf" STYLE="text-decoration:underline;">https://www.sco.wisc.edu/parcels/data/assets/V10/V10_Wisconsin_Statewide_Parcels_Schema_Documentation.pdf</A>.Change log and known issues can be found here: <A href="http://www.sco.wisc.edu/parcels/data/assets/Wisconsin_Statewide_Parcels_Change_Log.pdf" STYLE="text-decoration:underline;">https://www.sco.wisc.edu/parcels/data/assets/Wisconsin_Statewide_Parcels_Change_Log.pdf</A>.</DIV></DIV></DIV> Product of the Version 10 Statewide Parcel Map Database Project (V10). 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>This data free for public consumption as of: 06/30/2024Access and Use ConstraintsThe information shown on this map was obtained from Wisconsin’s counties and cities in 2024 and thus may not be the most current, comprehensive data available. Source data for parcel polygons was collected between January–June of 2024. However, the tax roll year for most records is 2023, as the assessment cycle lags a year behind. To ensure the most current, comprehensive parcel data, consult the local government’s land information websites first, or contact the city or county land information office directly. The next release of the statewide parcel layer, V11, is tentatively scheduled for June 30, 2025.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.</DIV></DIV></DIV> Peter Herreid Wisconsin Department of Administration 2025-06-30T00:00:00 Esri ArcGIS 13.4.0.55405 1 -92.963573 -86.666103 47.083040 42.456897 2025-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 substation_parcel Feature Class 0 V10 Wisconsin Statewide Parcel Layer (2024) SCO OBJECTID OBJECTID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. SHAPE Shape Geometry 0 0 0 Feature geometry. Esri Coordinates defining the features. STATEID STATEID String 100 0 0 - This string field contains the contributing jurisdiction’s FIPS code appended to the PARCELID (the unique number or identifier assigned to a parcel by the local authority). Calculate the STATEID by the following syntax: • <PARCELFIPS>+<PARCELID> Example: If PARCELFIPS = "083" and PARCELID = "123456789," then: STATEID = 083123456789 - Where PARCELFIPS is the three-digit county FIPS code, with leading zeros maintained in PARCELFIPS, and PARCELID is as defined below. SCO 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 TAXPARCELI TAXPARCELI String 100 0 0 PARCELDATE PARCELDATE String 25 0 0 - Modification date for parcel geometry, describing when the individual parcel geometry was last edited or revised. Such geometric edits include the following: • Parcel creation (date the digital geometry for the parcel came into existence) • Parcel division or merge • Change of parcel vertices • Spatial adjustment of parcel - Do not populate with the “cut date” or date the data was extracted/exported for V8 submission, NOR the parcel dataset’s last known geometric editing date. - If no attribute is maintained for the date of last geometric revision, enter a true SQL <Null> - Parcels migrated to (Esri) parcel fabric without a geometric edit date/GIS parcel creation date: Enter <Null> • For parcels that have been revised or added to the parcel fabric since migrating, include the date of last geometric edit or creation date. - Do not include a timestamp at the end of the calendar date in PARCELDATE. - Dates must be formatted as follows: • Syntax: MM/DD/YYYY • Example: 01/20/1984 SCO TAXROLLYEA TAXROLLYEA String 10 0 0 OWNERNME1 OWNERNME1 String 254 0 0 - The primary owner name of a parcel. - Owner name should be the most current in the county land information system. - 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 •JOHN R SMITH •SMITH, JOHN R •JOHN R & SUE SMITH •JOHN R and SUE SMITH •JANE, JOHN & SUE SMITH •SMITH, SUE & JOHN •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 PSTLADRESS PSTLADRESS String 200 0 0 - The primary owner’s full mailing address or the full mailing address for the tax bill associated with the parcel, whichever is available. - PSTLADRESS may have nothing to do with the physical location of a parcel, and may be outside of Wisconsin. - PSTLADRESS is a single field comprised of: • Address Number Prefix*, Address Number, Address Number Suffix*, Prefix*, Street Name, Street Type*, Suffix*, Unit Type*, Unit ID*, USPS Postal Place Name, State, and Zip Code (*where applicable) • If owner mailing address is maintained as two lines (e.g., as two separate mailing label lines), it should be concatenated into one field. • A comma (“,”) is the preferred separator element, or a space (“ “) is an acceptable separator element. • Example– Single-line with comma separator: 123 N MAIN ST, MIDTOWN, WI, 53611 • Example– Single-line concatenated from 2 lines: 123 N MAIN ST MIDTOWN WI 53611 - Domain standardization optional. Owner’s mailing address can contain elements with non-standardized domains. • Standard USPS Postal domains/abbreviations are acceptable in the owner’s mailing address. - No partial addresses. If mailing address in the native data is partial and not a full mailing address, do not submit mailing addresses for those specific parcels. Incorrect: CITY, STATE, ZIP enter <Null> instead Incorrect: GILMAN, WI, 54433 enter <Null> instead Incorrect: NA, NA, GILMAN, WI, 54433 enter <Null> instead Incorrect: STATE, ZIP enter <Null> instead Incorrect: STATE, 00000 enter <Null> instead - If there is no full owner mailing address, PSTLADRESS should be populated with a true SQL <Null> - PSTLADRESS – Public Lands Policy • For publicly owned parcels, enter a full mailing address for the parcel owner’s agency or department with as much specificity as possible. • Enter the address uniformly if the same entity owns more than one parcel. • If mailing address in the native data is partial and not a full mailing address, do not submit partial mailing addresses for those specific parcels. Full mailing addresses only. • If no mailing address is available for publicly-owned parcels, a value of <Null> may exist. 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* •SITEADRESS do NOT include “city, state, zip” - If site address is maintained as elements in multiple fields, it should be concatenated into one field. Line breaks/carriage returns are not accepted. • 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, populate with <Null>. SCO ADDNUMPREF ADDNUMPREF String 50 0 0 ADDNUM ADDNUM String 50 0 0 - The whole number component of a posted building identifier. - Address numbers should always be whole numbers. - Examples: • 2554 • 4215 • 8085 • 10 - ADDNUM should not be a range. • If there are multiple address numbers, the primary address number (such as the first number in the range) is selected. SCO ADDNUMSUFF ADDNUMSUFF String 50 0 0 PREFIX PREFIX String 50 0 0 SCO - One letter street direction or abbreviation that precedes the street name. - This field also contains the highway jurisdiction indicator for any Wisconsin highways. See examples below for highway classification context and standardization. - PREFIX domains for street name pre directionals (abbreviated): • N • NW • S • SW • E • NE • W • SE - PREFIX domains for highways (Abbreviated as below or fully spelled out as below): • CTH • N CTH • E CTH • S CTH • W CTH • COUNTY HIGHWAY • N COUNTY HIGHWAY • E COUNTY HIGHWAY • S COUNTY HIGHWAY • W COUNTY HIGHWAY • COUNTY ROAD • N COUNTY ROAD • E COUNTY ROAD • S COUNTY ROAD • W COUNTY ROAD • STH • N STH • E STH • S STH • W STH • STATE HIGHWAY • N STATE HIGHWAY • E STATE HIGHWAY • S STATE HIGHWAY • W STATE HIGHWAY • STATE ROAD • N STATE ROAD • E STATE ROAD • S STATE ROAD • W STATE ROAD • USH • N USH • E USH • S USH • W USH • US HIGHWAY • N US HIGHWAY • E US HIGHWAY • S US HIGHWAY • W US HIGHWAY • INTERSTATE ● Highways – highway prefixes can either be fully spelled-out or abbreviated as above. ● Highways – any of the following are acceptable in PREFIX: • COUNTY HIGHWAY / COUNTY ROAD / CTH (“COUNTY” by itself is not an acceptable prefix) • STATE HIGHWAY / STATE ROAD / STH • US HIGHWAY / USH ● Usage should be consistent throughout the countywide dataset. - Highway classification examples in context: •For address: 2554 COUNTY HIGHWAY C --> PREFIX = COUNTY HIGHWAY; STREETNAME = C •For address: 2554 COUNTY HIGHWAY C/H --> PREFIX = COUNTY HIGHWAY; STREETNAME = C/H •For address: 2554 S STATE HIGHWAY XX --> PREFIX = S STATE HIGHWAY; STREETNAME = XX - HIGHWAY is an acceptable PREFIX when varying jurisdictional highways run concurrently. •Example: W7010 HIGHWAY 10 & 114 (“10” is the US highway and “114” is the concurrently running state highway) - Road “alias” names should not be included in the STREETNAME field alongside a highway PREFIX and route ID. •For example, for address: “2554 COUNTY HIGHWAY C/MAIN ST” •PREFIX = COUNTY HIGHWAY; STREETNAME = C • (The street name here would be incorrect as “C/MAIN”) or: •STREETNAME = MAIN; STREETTYPE = STREET - Note that “OLD” is not a prefix value. See STREETNAME for placement of Street Name Pre Modifiers like OLD. STREETNAME STREETNAME String 50 0 0 - Primary street name. - The legal street name as assigned by local address authority. - STREETNAME does not include the street type of a named street. - STREETNAME does not include the suffix direction of a coordinate street. Suffix direction belongs in SUFFIX. - STREETNAME might incorporate a Street Name Pre Modifier and/or a Street Name Post Modifier (which do not have their own separate fields). In some cases, Street Name Pre Modifier might be acceptable in PREFIX field. - For highways or county roads that share more than one route number or letter (e.g., USH 151/51), these routes are listed with a delimiter ● A forward slash ("/") is the preferred route delimiter, or a hyphen ("-") is an acceptable delimiter. - STREETNAME does not include street aliases. ● Example: 2554 STH 23/MAIN ST • STREETNAME should contain a state highway street name ("23") or the local street name ("MAIN"), but not both. •"23/MAIN" would be incorrect as the street name. - STREETNAME is a somewhat flexible field, and can hold a wide variety of values. They can incorporate a Street Name Pre Modifier (but see PREFIX notes). ● For "old" retired highways and countyr roads, in the statewide parcel schema, the STREETNAME field holds Street Name Pre Modifies. ● Example: OLD STATE HIGHWAY 87 ROAD •STREETNAME = OLD STATE HIGHWAY 87 •STREETTYPE = ROAD - STREETNAME sometimes holds "impostor" PREFIX values, but because they are not authoritive highway jurisdictions they cannot be a PREFIX. Instead, some specific impostor prefix values belong to the STREETNAME field, as in these examples: ● 2554 TOWN ROAD AA •STREETNAME = TOWN ROAD AA •PREFIX = <Null> •STREETTYPE = <Null> ● Example: 2554 TOWN ROAD •STREETNAME = TOWN ROAD •PREFIX = <Null> •STREETTYPE = ROAD ● Example: 2554 OLD HIGHWAY 40 •STREETNAME = OLD HIGHWAY 40 •PREFIX = <Null> •STREETTYPE = <Null> SCO STREETTYPE STREETTYPE String 50 0 0 - Street type of a named street (for the site address) written to full name of type: • E WASHINGTON ROAD - Fully spell-out STREETTYPE domains. - Abbreviations are not acceptable in STREETTYPE (even if they are USPS street suffix abbreviations). - STREETTYPE example domains (this list is not exhaustive): • ACCESS • ALLEY • AVENUE • BAY • BEACH • BEND • BLUFF • BOULEVARD • BRANCH • BYPASS • CAPE • COMMON • COURT • COVE • CREEK • CREST • CROSSING • CURVE • DALE • DRIVE • END • ESTATE • EXTENSION • FIELDS • FOREST • FORK • GARDENS • HIGHWAY* • KNOLL • KNOLLS • LAKE • LANDING • LANE • LOOP • PATHWAY • PIKE • PLACE • PLAZA • POINT • SPRINGS • SPUR • SQUARE • STREET • STRIP • SUMMIT • VALLEY • VIEW • VISTA • WALK • WAY - *Note that “Highway” is seldom a STREETTYPE, as it is most often a PREFIX. - In rare cases, STREETTYPE can hold a Street Name Post Modifier. When a Street Name Post Modifier exists in an address, a word that resembles a STREETTYPE sometimes belongs instead in the STREETNAME field in order to allow the STREETTYPE field to hold the Street Name Post Modifier, as in the following examples: ● Example: 2554 GREER ROAD EXTENSION •STREETNAME = GREER ROAD •STREETTYPE = EXTENSION ● Example: 2554 GREER ROAD PRIVATE DRIVE •STREETNAME = GREER ROAD •STREETTYPE = PRIVATE DRIVE SCO SUFFIX SUFFIX String 50 0 0 - Street name post directional. - One letter street direction that follows the street name. •MAIN STREET NW •W3506 CTH A S (where "S" stands for "SOUTH" and belongs in the SUFFIX field—not spelled out) - In rare cases, SUFFIX field may incorporate a Street Name Post Modifier. - SUFFIX accepted domains (this list is not exhaustive): •N - North •S - South •E - East •W - West •NW - North West •SW - South West •NE - North East •SE - South East SCO LANDMARKNA LANDMARKNA String 50 0 0 UNITTYPE UNITTYPE String 50 0 0 - Indicates the unit type associated with a parcel feature (e.g., apartment, room, suite, unit, etc.). Provided as available. - UNITTYPE should not contain any type of extraneous property/structure descriptor. - Abbreviations are not acceptable in UNITTYPE (even if they are USPS unit designator abbreviations, which appear in gray with a line through them in the list below). - UNITTYPE example domains (this list is not exhaustive): -ACCEPTABLE - - - - - NOT ACCEPTABLE (USPS) -APARTMENT - - - - - APT -BASEMENT - - - - - BSMT -BUILDING - - - - - BLDG -CONDOMINIUM -DEPARTMENT - - - - - DEPT -FLOOR - - - - - FL -FRONT - - - - - FRNT -HANGAR -HANGER - - - - - HNGR -KEY -LOBBY - - - - - LBBY -LOT -LOWER - - - - - LOWR -OFFICE - - - - - OFC -PENTHOUSE - - - - - PH -PIER -REAR -ROOM - - - - - RM -SIDE -SLIP -SPACE - - - - - SPC -STOP -SUITE - - - - - STE -TOWER -TRAILER - - - - - TRLR -UNIT -UPPER - - - - - UPPR SCO UNITID UNITID String 50 0 0 - UNITID includes the number or letter identification string for a building, apartment, room, suite, unit, or room (as well as other examples). - Not to be confused with ADDNUMSUFFIX, which is a component to the address number. - UNITID delineates a unit within an address. Example: 123 ½ APARTMENT A •ADDNUM = 123 •ADDNUMSUFFIX = ½ •UNITTYPE = APARTMENT •UNITID = A - If parcels such as condos have distinct PARCELIDs and the same SITEADRESS values, UNITID should be populated for these records as appropriate. - UNITID should not contain any property/structure descriptions. - UNITID should not contain any values which belong in UNITTYPE (e.g., words like "APARTMENT" or "UNIT"). 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 V8 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 ZIPCODE ZIPCODE String 50 0 0 - The 5-digit zip code for the parcel’s site address. - This is the mailing zip code for the parcel itself (not the owner, whose zip code is provided in PSTLADRESS and may be out-of-state). - Provided where available. - A value of <Null> may exist if no zip code for the parcel’s site address is maintained. SCO ZIP4 ZIP4 String 50 0 0 - The 4 additional digits appended to the 5-digit zip code for the parcel’s site address. - This is the mailing zip4 for the parcel itself (not the owner, whose zip code is provided in PSTLADRESS and may be out-of-state). - Provided where available. - A value of <Null> may exist if no zip4 for the parcel’s site address is maintained. SCO STATE STATE String 50 0 0 - Two letter state abbreviation of a parcel feature’s physical site address. • WI - This is the state where the parcel itself is located (not the owner, whose mailing address in PSTLADRESS may be out-of-state). - Unless parcels are outside of the state of Wisconsin, this value will be "WI" SCO SCHOOLDIST SCHOOLDIST String 50 0 0 - The school district name, listed in the authoritative file at: sco.wisc.edu/parcels/Parcel_Domain_List.xlsx ● Example: LITTLE CHUTE AREA SCHOOL DISTRICT - All parcels for a given county should be populated with SCHOOLDIST domains (with the possible exception of non-parcel features, designated as such in the PARCELID field). - Domains must remain in UPPERCASE. - Domain for district name should exactly match the domain list. Include the words "SCHOOL DISTRICT" at the end, separated by a space. - A parcel should never contain multiple school districts. ● For areas that apply a Union High School (UHS) district, the UHS district should be the district populating this field. Elementary districts within a UHS are known as "children" of the "parent" UHS district and should not be included in the data submission. SCO SCHOOLDI_1 SCHOOLDI_1 String 50 0 0 CNTASSDVAL CNTASSDVAL Double 8 0 0 LNDVALUE LNDVALUE Double 8 0 0 - The total assessed value of land, without improvements, in US dollars. - LNDVALUE is an approximation of market value for land, with some notable exceptions, as Wisconsin has other “value standards” for real property in addition to market value (see CNTASSDVALUE for value standards). - LNDVALUE should be populated for property classes that are assessed at any value standard. LNDVALUE should be populated for: • PROPCLASS = 1, 2, 3, 4, 5, 5M, 6, 7 - Entirely MFL/FCL lands – LANDVALUE should not be populated for entirely MFL/FCL parcels • AUXCLASS = W1, W2, W3, W5, W6, W7, W8, W9 • Do not include values for enrolled MFL/FCL lands in Assessed Value of Land (LNDVALUE)—as they belong in the field MFLVALUE instead. For parcels that have entirely MFL/FCL lands, this field will be <Null> • Parcels with both MFL/FCL enrolled andand regular taxable portions (PROPCLASS = 1-7) should have a value in LNDVALUE that represents only the land value for the regular taxable portion of the parcel. - Tax exempt parcels – LNDVALUE should not be populated for tax exempt parcels. • AUXCLASS = X1, X2, X3, X4, W4 - For tax exempt properties, enter <Null> in LNDVALUE. - The value should be provided without currency formatting such as the dollar sign and without comma separators such as the thousands delimiter. Decimal values should be limited to two decimal places. ● 300000.00 (Not $300,000.00) ● 100800.00 (Not 100800.000) SCO IMPVALUE IMPVALUE Double 8 0 0 - 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 MFLVALUE MFLVALUE Double 8 0 0 - The total assessed value of private land enrolled in either the Managed Forest Law (MFL) or Forest Crop Law programs (FCL), in US dollars. - The assessed value of lands enrolled in MFL/FCL programs is entered because it is necessary for calculating the tax amount due if land is withdrawn from the MFL/FCL program. - Landowners with land in the MFL/FCL programs pay MFL/FCL tax rates in lieu of regular property tax rates. - To have a value present in MFLVALUE, parcels/portions of parcels must have a specific AUXCLASS designation. MFLVALUE should be populated for: • AUXCLASS = W1, W2, W3, or W5, W6, W7, W8, W9 • MFLVALUE does not include properties with AUXCLASS value of W4 (County Forest Crop Land), because County Forest Crop Land is county-owned and tax exempt. - On the property tax bill this value can be found in the column for Total Assessed Value, specifically in the row designated for PFC/MFL, Managed Forest, or an equivalent. - MFLVALUE is not included in or any part of the calculation for the LNDVALUE nor the CNTASSDVALUE fields. • MFLVALUE is the field that should contain the value representing the total assessed value of enrolled MFL/FCL lands—not LNDVALUE. - A similar but distinct former field was called "FORESTVALUE" (Assessed Forest Value) in the statewide parcel map database versions V1-V5, but MFLVALUE has a different definition than the defunct FORESTVALUE. - For parcels not enrolled in the Managed Forest Law or Forest Crop Law programs, this field will be <Null> SCO ESTFMKVALU ESTFMKVALU Double 8 0 0 NETPRPTA NETPRPTA Double 8 0 0 - The net amount of annual property tax, in US dollars. - This is the sum of the taxes levied on real property according to the assessed value of the property by all local taxing jurisdictions, after the First Dollar Credit and Lottery & Gaming Credit are applied. ● NETPRPTA = GRSPRPTA (Gross Property Tax) minus the First Dollar Credit and Lottery & Gaming Credit. - What to include when calculating NETPRPTA: ● NETPRPTA = [STATE TAX] + [COUNTY TAX] + [SPECIAL DISTRICT TAX WHERE APPLICABLE] + [MUNICIPAL TAX] + [SCHOOL DISTRICT TAX]* + [TECHNICAL/COMMUNITY COLLEGE TAX] – [LOTTERY & GAMING CREDIT] – [FIRST DOLLAR CREDIT] * School district tax must be net of school levy tax credit as shown on tax bills. According to s. 74.09(3)(b)(3), tax bills must display the tax levied on the property by the school district where the property is located minus the school levy tax credit allocable to the property (s. 79.10(4)). - What to exclude from NETPRPTA (NETPRPTA should *not* include): ● Special assessments. Special assessment examples include those for capital improvements, such as street improvements like sidewalks and storm sewers. Drainage district assessments—the amount of assessment issued by a drainage board under s. 88.42—are considered special assessments and therefore should not be included in NETPRPTA. ● Special charges. Special charges examples include charges for services, such as refuse and garbage collection (if garbage is not included in the municipal tax), fencing, and snow removal. Delinquent utility charges are considered a special charge and therefore should not be included in NETPRPTA. ● Special taxes. MFL/FCL per acre taxes. ● Delinquent general property taxes. ● These special assessments/charges/taxes can make NETPRPTA erroneously appear larger than GRSPRPTA. If NETPRPTA cannot be provided without delinquent general property taxes/special taxes/special charges/special assessments/drainage district notifications, do one of two things: 1) <Null> out NETPRPTA for the appropriate records, or 2) Populate NETPRPTA, but provide an explanation of delinquent charges, noting that “non-annual tax” values are included in the Explain-Certification.txt section of the submission form. - NETPRPTA should always be less than or equal to GRSPRPTA for any given property. - The value should be provided without currency formatting such as the dollar sign and without comma separators such as the thousands delimiter. Decimal values should be rounded to the nearest hundredth (two decimal places to the right of the decimal). ● 3670.98 (Not $3,670.98) ● 1780.65 (Not 1780.649) - For tax exempt properties, enter <Null> - Provide at least one—NETPRPTA or GRSPRPTA. ● NETPRPTA may be <Null> if GRSPRPTA is populated for a given county. SCO Shape_Area Shape_Area Double 8 0 0 Area of feature in internal units squared. Esri Positive real numbers that are automatically generated. GRSPRPTA GRSPRPTA Double 8 0 0 - The gross amount of annual general property taxes, in US dollars. - This is the sum of the taxes levied on real property according to the assessed value of the property by all local taxing jurisdictions (before the First Dollar Credit and Lottery & Gaming Credit are applied). - What to include when calculating GRSPRPTA: ● GRSPRPTA = [STATE TAX] + [COUNTY TAX] + [SPECIAL DISTRICT TAX WHERE APPLICABLE] + [MUNICIPAL TAX] + [SCHOOL DISTRICT TAX]* + [TECHNICAL/COMMUNITY COLLEGE TAX] * School district tax must be net of school levy tax credit as shown on tax bills. According to s. 74.09(3)(b)(3), tax-bills must display the tax levied on the property by the school district where the property is located minus the school levy tax credit allocable to the property (s. 79.10(4)). - Another way of calculating GRSPRPTA: ● GRSPRPTA = [TOTAL ASSESSED VALUE] × [NET ASSESSED VALUE RATE] The net assessed value rate is also referred to as the “mill rate” or tax rate per $1,000 of assessed value (before the First Dollar Credit and Lottery & Gaming Credit are applied). - What to exclude from GRSPRPTA (GRSPRPTA should *not* include): ● Special assessments. Special assessment examples include those for capital improvements, such as street improvements like sidewalks and storm sewers. Drainage district assessments—the amount of assessment issued by a drainage board under s. 88.42—are considered special assessments and therefore should not be included in GRSPRPTA. ● Special charges. Special charges examples include charges for services, such as refuse and garbage collection (if garbage is not included in the municipal tax), fencing, and snow removal. Delinquent utility charges are considered a special charge and therefore should not be included in GRSPRPTA. ● Special taxes. MFL/FCL per acre taxes. ● Delinquent general property taxes. - GRSPRPTA should always be more than or equal to NETPRPTA for any given property. - The value should be provided without currency formatting such as the dollar sign and without comma separators such as the thousands delimiter. Decimal values should be rounded to the nearest hundredth (two decimal places to the right of the decimal). ● 3670.98 (Not $3,670.98) ● 1780.65 (Not 1780.649) - For tax exempt properties, enter <Null> - Provide at least one—NETPRPTA or GRSPRPTA. - GRSPRPTA may be <Null> if NETPRPTA is populated for a given county SCO PROPCLASS PROPCLASS String 150 0 0 - The General class of property for taxable real estate, as specified in Wisconsin s. 70.32(2)(a). - Wisconsin law requires assessors to classify land on the basis of use. Sometimes this involves a judgment of the predominant use. There are eight statutory classifications for real property. - Domains should either match the 8 classes listed as PROPCLASS domains for taxable properties, or have a <Null> value for PROPCLASS and a value in AUXCLASS field for tax exempt/special properties (with the exception of non-parcel features, designated as such in PARCELID field). - Multiple values. If more than one class exists for a parcel, each class is listed in PROPCLASS delimited by commas, as in: 1,3,4 3,4,5M List each class once only. No duplicate values. No spaces in between values. - If the native data contains a preceding “G” in front of the numeric ID, this “G” should be omitted (“3” not “G3”). - Native PROPCLASS domains that do not exactly match standard schema domains should be standardized to match standard PROPCLASS domains. - PROPCLASS accepted domains and definitions for “General – Taxable Real Estate”: 1 - Residential 2 - Commercial 3 - Manufacturing 4 - Agricultural 5 - Undeveloped 5M - Agricultural forest 6 - Productive Forest Land 7 - Other SCO AUXCLASS AUXCLASS String 150 0 0 - This field contains domains for properties classified in the tax roll as tax exempt or special, and domains that are listed in the native dataset as a class of property that does not fit those specified in s. 70.32(2)(a). • EXEMPT – defined as federal, state, county, and other tax-exempt • SPECIAL – designating PrivateForestCropland, Managed Forest Land, and County Forest Crop property - Standard domains apply to properties in the EXEMPT and SPECIAL classifications. - Domains should either match those listed as AUXCLASS domains, or have a <Null> value for AUXCLASS and a value in PROPCLASS field (with the exception of non-parcel features, designated as such in PARCELID field). • Any native domains other than those listed within the standard EXEMPT/SPECIAL fields should be standardized to match standard PROPCLASS/AUXCLASS domains. - Multiple values. If multiple classes exist for a parcel, each is listed in AUXCLASS, delimited by commas, as in: "X1,W3,X4" or "X3,W5" - AUXCLASS EXEMPT accepted domains and definitions for "Exempt from General Property Taxes" • X1 = Federal • X2 = State • X3 = Count • X4 = Other Exempt - AUXCLASS SPECIAL accepted domains and definitions for Special – FCL, MFL and County Forest Crop Land: • W1= Forest Cropland Before 01/01/1972 • W2 = Forest Cropland After 12/31/1971 • W3 = Forest Cropland Special • W4 = County Forest Crop Land • W5 = MFL Entered After 2004 Open • W6 = MFL Entered After 2004 Closed • W7 = MFL Entered Before 2005 Open • W8 = MFL Entered Before 2005 Closed • W9 = MFL Ferrous Mining - AUXCLASS <NULL>: • <NULL> Non-parcel features in some cases may be null in AUXCLASS - AUXCLASS FOR PARCELS ASSESSED WITH OTHER PARCELS • AW or AWO = Used to designate parcels "assessed with" other parcels under s.70.23(2), explains why these records might lack tax roll data in the tax roll-specific attribute fields: CNTASSDVALUE, LNDVALUE, IMPVALUE, MFLVALUE, ESTFMKVALUE, ETPRPTA, GRSPRPTA, PROPCLASS, AUXCLASS, ASSDACRES SCO ASSDACRES ASSDACRES Double 8 0 0 - The parcel area, in acres, specified as total assessed acres for taxation purposes. - ASSDACRES is not to be confused with DEEDACRES or GISACRES, but may match either or both. - A value of <Null> may exist if the local assessor does not provide acre calculations for small parcels. • Parcels less than 1 acre may have a value of <Null> (or in some cases may appear as legitimate values of "0") SCO DEEDACRES DEEDACRES Double 8 0 0 - The parcel area, in acres, as specified within the legal property description. SCO GISACRES GISACRES Double 8 0 0 - The calculated GIS parcel area, in acres, derived directly from GIS features. - If available, GISACRES may be populated for non-parcel features. - GISACRES is optional and may be left <Null> SCO CONAME CONAME String 50 0 0 - The name of the county which the parcel is administratively part of. - Counties should be the only entity submitting data. ● If a municipality stewards 1) parcel polygon data and/or 2) tax roll data separately from the county, the county should request, integrate, and submit data for the municipality that has been standardized. - Periods are not permitted in county names in the CONAME field. Spaces are acceptable. See Table below in PARCELFIPS for county spelling conventions. - Do not include the word “_County” in CONAME. SCO LOADDATE LOADDATE String 10 0 0 - The date (MM/DD/YYYY) when a parcel feature is submitted to the Parcel Initiative from the data contributor. This field will be populated by the parcel aggregation team. SCO PARCELFIPS PARCELFIPS String 10 0 0 - Indicates the 3-digit FIPS code of the county (the contributing jurisdiction of the parcel dataset). See list below. - Populate PARCELFIPS for all records. The value should be the same for all records. - Maintain FIPS code leading zeros in PARCELFIPS. - Domain example: • 009 (for Brown County) ADAMS FIPS: 001 ASHLAND FIPS: 003 BARRON FIPS: 005 BAYFIELD FIPS: 007 BROWN FIPS: 009 BUFFALO FIPS: 011 BURNETT FIPS: 013 CALUMET FIPS: 015 CHIPPEWA FIPS: 017 CLARK FIPS: 019 COLUMBIA FIPS: 021 CRAWFORD FIPS: 023 DANE FIPS: 025 DODGE FIPS: 027 DOOR FIPS: 029 DOUGLAS FIPS: 031 DUNN FIPS: 033 EAU CLAIRE FIPS: 035 FLORENCE FIPS: 037 FOND DU LAC FIPS: 039 FOREST FIPS: 041 GRANT FIPS: 043 GREEN FIPS: 045 GREEN LAKE FIPS: 047 IOWA FIPS: 049 IRON FIPS: 051 JACKSON FIPS: 053 JEFFERSON FIPS: 055 JUNEAU FIPS: 057 KENOSHA FIPS: 059 KEWAUNEE FIPS: 061 LA CROSSE FIPS: 063 LAFAYETTE FIPS: 065 LANGLADE FIPS: 067 LINCOLN FIPS: 069 MANITOWOC FIPS: 071 MARATHON FIPS: 073 MARINETTE FIPS: 075 MARQUETTE FIPS: 077 MENOMINEE FIPS: 078 MILWAUKEE FIPS: 079 MONROE FIPS: 081 OCONTO FIPS: 083 ONEIDA FIPS: 085 OUTAGAMIE FIPS: 087 OZAUKEE FIPS: 089 PEPIN FIPS: 091 PIERCE FIPS: 093 POLK FIPS: 095 PORTAGE FIPS: 097 PRICE FIPS: 099 RACINE FIPS: 101 RICHLAND FIPS: 103 ROCK FIPS: 105 RUSK FIPS: 107 ST CROIX FIPS: 109 SAUK FIPS: 111 SAWYER FIPS: 113 SHAWANO FIPS: 115 SHEBOYGAN FIPS: 117 TAYLOR FIPS: 119 TREMPEALEAU FIPS: 121 VERNON FIPS: 123 VILAS FIPS: 125 WALWORTH FIPS: 127 WASHBURN FIPS: 129 WASHINGTON FIPS: 131 WAUKESHA FIPS: 133 WAUPACA FIPS: 135 WAUSHARA FIPS: 137 WINNEBAGO FIPS: 139 WOOD FIPS: 141 SCO PARCELSRC PARCELSRC String 50 0 0 - Indicates name of the county (the contributing jurisdiction of the parcel dataset), standardized as shown above in the Table in PARCELFIPS. - Populate PARCELSRC for all records. The value should be the same for all records. - Periods are not permitted in county names in the PARCELSRC field. Spaces are acceptable. - Do not include the word “_County” in PARCELSRC. SCO LONGITUDE LONGITUDE Double 8 0 0 - The longitude, in decimal degrees, of the parcel’s centroid. The centroid of a parcel shape is calculated as is the average position of all the points that participate in the shape. - This point is also calculated as an "inside" centroid, meaning that the point is subject to the following contextual qualities: • A non-convex (concave) feature might have a centroid that is outside of the feature itself. The “inside” calculation ensures that this does not happen and that the point resides within the respective polygon’s geometry. • A donut-shaped feature might have a centroid that is outside of the feature itself. The “inside” calculation ensures that this does not happen and that the point resides within the respective polygon’s geometry. • A multi-part feature might have a centroid that is outside of the feature itself. The “inside” calculation ensures that this does not happen and that the point resides within the respective polygon’s geometry. - In the final statewide parcel layer, LONGITUDE and LATITUDE for parcel centroids are provided in decimal degrees. The parcel centroids are calculated using an ArcGIS ArcPy script, created using ArcGIS’s default WGS 84 parameters: • GCS_WGS_1984 • WKID: 4326 Authority: EPSG • Angular Unit: Degree (0.0174532925199433) • Prime Meridian: Greenwich (0.0) • Datum: D_WGS_1984 • Spheroid: WGS_1984 • Semimajor Axis: 6378137.0 • Semiminor Axis: 6356752.314245179 • Inverse Flattening: 298.257223563 SCO Shape_Leng Shape_Leng Double 8 0 0 LATITUDE LATITUDE Double 8 0 0 - The latitude, in decimal degrees, of the parcel’s centroid. The centroid of a parcel shape is calculated as is the average position of all the points that participate in the shape. - This point is also calculated as an "inside" centroid, meaning that the point is subject to the following contextual qualities: • A non-convex (concave) feature might have a centroid that is outside of the feature itself. The “inside” calculation ensures that this does not happen and that the point resides within the respective polygon’s geometry. • A donut-shaped feature might have a centroid that is outside of the feature itself. The “inside” calculation ensures that this does not happen and that the point resides within the respective polygon’s geometry. • A multi-part feature might have a centroid that is outside of the feature itself. The “inside” calculation ensures that this does not happen and that the point resides within the respective polygon’s geometry. - In the final statewide parcel layer, LONGITUDE and LATITUDE for parcel centroids are provided in decimal degrees. The parcel centroids are calculated using an ArcGIS ArcPy script, created using ArcGIS’s default WGS 84 parameters: • GCS_WGS_1984 • WKID: 4326 Authority: EPSG • Angular Unit: Degree (0.0174532925199433) • Prime Meridian: Greenwich (0.0) • Datum: D_WGS_1984 • Spheroid: WGS_1984 • Semimajor Axis: 6378137.0 • Semiminor Axis: 6356752.314245179 • Inverse Flattening: 298.257223563 SCO Shape_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. Source Source String 254 0 0 dataset EPSG 5.3(9.0.0) Simple FALSE 0 TRUE FALSE 20250609