View In:
ArcGIS JavaScript
ArcGIS Online Map Viewer
ArcGIS Earth
ArcMap
ArcGIS Pro
View Footprint In:
ArcGIS Online Map Viewer
Service Description: Attribute Field Definitions
Ward Data Overview:
July 2022 municipal wards were collected in July 2022 by LTSB through the WISE-Decade system. Current statutes require each county clerk, or board of election commissioners, no later than January 15 and July 15 of each year, to transmit to the LTSB, in an electronic format (approved by LTSB), a report confirming the boundaries of each municipality, ward and supervisory district within the county as of the preceding “snapshot” date of January 1 or July 1 respectively. Population totals for 2022 wards were estimated by aggregating 2020 US Census PL94-171 population data. LTSB has NOT topologically integrated the data.
Election Data Overview:The 2022 Wisconsin election data that is included in this file was collected by LTSB from the *Wisconsin Elections Commission (WEC) after the general election. A disaggregation process was performed on this election data based on the municipal ward layer that was available at the time of the election. Disaggregation of Election Data:Election data is first disaggregated from reporting units to wards, and then to census blocks. Next, the election data is aggregated back up to wards, municipalities, and counties. The disaggregation of election data to census blocks is done based on total population.
Detailed Methodology:Data is disaggregated first from reporting unit (i.e. multiple wards) to the ward level proportionate to the population of that ward. The data then is distributed down to the block level, again based on total population. When data is disaggregated to block or ward, we restrain vote totals not to exceed population 18 numbers, unless absolutely required.This methodology results in the following: Election data totals reported to the WEC at the state, county, municipal and reporting unit level should match the disaggregated election data total at the same levels. Election data totals reported to the WEC at ward level may not match the ward totals in the disaggregated election data file. Some wards may have more election data allocated than voter age population. This will occur if a change to the geography results in more voters than the 2020 historical population limits.
Other things of note…We use a static, official ward layer (in this case created in 2022) to disaggregate election data to blocks. Using this ward layer creates some challenges. New wards are created every year due to annexations and incorporations. When these new wards are reported with election data, an issue arises wherein election data is being reported for wards that do not exist in our official ward layer. For example, if Cityville has four wards in the official ward layer, the election data may be reported for five wards, including a new ward from an annexation. There are two different scenarios and courses of action to these issues: When a single new ward is present in the election data but there is no ward geometry present in the official ward layer, the votes attributed to this new ward are distributed to all the other wards in the municipality based on population percentage. Distributing based on population percentage means that the proportion of the population of the municipality will receive that same proportion of votes from the new ward. In the example of Cityville explained above, the fifth ward may have five votes reported, but since there is no corresponding fifth ward in the official layer, these five votes will be assigned to each of the other wards in Cityville according the percentage of population.Another case is when a new ward is reported, but its votes are part of reporting unit. In this case, the votes for the new ward are assigned to the other wards in the reporting unit by population percentage; and not to wards in the municipality as a whole. For example, Cityville’s ward 5 was given as a reporting unit together with wards 1, 4, and 5. In this case, the votes in ward five are assigned to wards 1 and 4 according to population percentage.
Map Name: Layers
Legend
All Layers and Tables
Dynamic Legend
Dynamic All Layers
Layers:
Description:
Copyright Text: LTSB
Spatial Reference:
102100
(3857)
Single Fused Map Cache: false
Initial Extent:
XMin: -1.0520879539076887E7
YMin: 5452879.3638039045
XMax: -9521810.87427289
YMax: 6022263.8359061815
Spatial Reference: 102100
(3857)
Full Extent:
XMin: -1.03404043816E7
YMin: 5234951.630599998
XMax: -9658522.9674
YMax: 5955268.0986
Spatial Reference: 102100
(3857)
Units: esriMeters
Supported Image Format Types: PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP
Document Info:
Title:
Author:
Comments: Attribute Field Definitions
Ward Data Overview:
July 2022 municipal wards were collected in July 2022 by LTSB through the WISE-Decade system. Current statutes require each county clerk, or board of election commissioners, no later than January 15 and July 15 of each year, to transmit to the LTSB, in an electronic format (approved by LTSB), a report confirming the boundaries of each municipality, ward and supervisory district within the county as of the preceding “snapshot” date of January 1 or July 1 respectively. Population totals for 2022 wards were estimated by aggregating 2020 US Census PL94-171 population data. LTSB has NOT topologically integrated the data.
Election Data Overview:The 2022 Wisconsin election data that is included in this file was collected by LTSB from the *Wisconsin Elections Commission (WEC) after the general election. A disaggregation process was performed on this election data based on the municipal ward layer that was available at the time of the election. Disaggregation of Election Data:Election data is first disaggregated from reporting units to wards, and then to census blocks. Next, the election data is aggregated back up to wards, municipalities, and counties. The disaggregation of election data to census blocks is done based on total population.
Detailed Methodology:Data is disaggregated first from reporting unit (i.e. multiple wards) to the ward level proportionate to the population of that ward. The data then is distributed down to the block level, again based on total population. When data is disaggregated to block or ward, we restrain vote totals not to exceed population 18 numbers, unless absolutely required.This methodology results in the following: Election data totals reported to the WEC at the state, county, municipal and reporting unit level should match the disaggregated election data total at the same levels. Election data totals reported to the WEC at ward level may not match the ward totals in the disaggregated election data file. Some wards may have more election data allocated than voter age population. This will occur if a change to the geography results in more voters than the 2020 historical population limits.
Other things of note…We use a static, official ward layer (in this case created in 2022) to disaggregate election data to blocks. Using this ward layer creates some challenges. New wards are created every year due to annexations and incorporations. When these new wards are reported with election data, an issue arises wherein election data is being reported for wards that do not exist in our official ward layer. For example, if Cityville has four wards in the official ward layer, the election data may be reported for five wards, including a new ward from an annexation. There are two different scenarios and courses of action to these issues: When a single new ward is present in the election data but there is no ward geometry present in the official ward layer, the votes attributed to this new ward are distributed to all the other wards in the municipality based on population percentage. Distributing based on population percentage means that the proportion of the population of the municipality will receive that same proportion of votes from the new ward. In the example of Cityville explained above, the fifth ward may have five votes reported, but since there is no corresponding fifth ward in the official layer, these five votes will be assigned to each of the other wards in Cityville according the percentage of population.Another case is when a new ward is reported, but its votes are part of reporting unit. In this case, the votes for the new ward are assigned to the other wards in the reporting unit by population percentage; and not to wards in the municipality as a whole. For example, Cityville’s ward 5 was given as a reporting unit together with wards 1, 4, and 5. In this case, the votes in ward five are assigned to wards 1 and 4 according to population percentage.
Subject: 2022 Wisconsin Election Data with July 2022 Wards.
Category:
Keywords: Municipal Wards,2022,Election Data,LTSB,Wisconsin
AntialiasingMode: None
TextAntialiasingMode: Force
Supports Dynamic Layers: true
Resampling: false
MaxRecordCount: 1000
MaxImageHeight: 4096
MaxImageWidth: 4096
Supported Query Formats: JSON, geoJSON, PBF
Supports Query Data Elements: true
Min Scale: 0
Max Scale: 0
Supports Datum Transformation: true
Child Resources:
Info
Dynamic Layer
Supported Operations:
Export Map
Identify
QueryLegends
QueryDomains
Find
Return Updates