Layers:

Layer: Local Elected Representatives (0)

Name: Local Elected Representatives

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Previously, The City's Council Districts were established in 2002 after the population growth and shifts in the 2000 Census. The City Charter requires an analysis of the Council District lines within 180 days of a general election in which the Mayor is regularly elected to get the districts as nearly equal in population as is practicable. The City experienced population growth and population shifts in the 2020 Census that necessitates adjusting the Council districts.The City Charter requires a review of the district councilmember lines within 180 days of a general election in which the Mayor regularly elected. This is to be done so that the population in each of the districts will be as nearly equal as practicable. In 2002, the City Council passed Ordinance No 15219 establishing the current City Council Districts. This redistricting was due to population growth and shifts causing the existing Council districts to not be nearly equal in population. An analysis of the Council districts was conducted after the 2010 Census but no changes were made.The official population provided by the US Census for the City in 2020 is 123,011, an increase of approximately 6,200 people. Based on the 2020 Census population, the ideal district norm for the Council districts would be the population divided by four (4). This equals 30,753 people per district. Using the 2020 Census population and the current Council district boundaries, the population of each district is shown in the table below. If the current Council district boundaries were to remain, the deviation to the norm would be 7.28% (above the norm) to -9.36% (below the norm).The Council district boundaries were adjusted to get the population in each of the districts will be as nearly equal as practicable. Staff used Census Blocks, the smallest geographic area for which the Bureau of the Census collects and tabulates decennial census data, in adjusting the district boundaries. Census Blocks are formed by streets, roads, railroads, streams and other bodies of water, other visible physical and cultural features, and are the legal boundaries shown on Census Bureau maps. The boundaries were adjusted while maintaining the Noland and 23rd Street intersection. Staff started with District 4 as it was closest to the norm and moved counterclockwise adjusting the boundaries to get the population of each district as close to the norm as practicable. See the included Council District Map that highlights the changes to the current boundaries in blue crosshatch:The crosshatch area between Districts 2 and 3 indicates the highlighted area will move from District 3 to District 2.The crosshatch area between Districts 1 and 2 indicates the highlighted area will move from District 2 to District 1.The population of each proposed district is shown in the table below. The deviation to the norm has been significantly reduced to from 0.0001% to 0.1236%. Staff used population estimates out to 2026 to test whether the proposed Council district population holds. Based on population estimates provided by ESRI, the district population remains similar when projected out to 2026.

Service Item Id: db2df76757f046fa858bd28695817001

Copyright Text: City of Independence, MO

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 170752.40524865474

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 2793957.844637001
YMin: 1038082.4044480026
XMax: 2869353.9303869996
YMax: 1082838.9016980007
Spatial Reference: 102698  (102698)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: NAME
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: District 1
  Label: District 1
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [85, 204, 217, 114]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
• Value: District 2
  Label: District 2
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [245, 87, 247, 114]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
• Value: District 3
  Label: District 3
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [245, 250, 95, 114]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
• Value: District 4
  Label: District 4
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [191, 79, 71, 114]
  Outline:
  Style: esriSLSSolid
  Color: [110, 110, 110, 255]
  Width: 0
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: N/A
Use Coded Values: true
Symbol:
Color: [0, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 10
Font Family: Tahoma
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 170752.40524865474
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:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• DISTRICTID ( type: esriFieldTypeString, alias: District ID, length: 10 , Coded Values: [1: COUNCIL DISTRICT 1] , [2: COUNCIL DISTRICT 2] , [3: COUNCIL DISTRICT 3] , ...1 more... )
• NAME ( type: esriFieldTypeString, alias: District Name, length: 50 )
• REPNAME ( type: esriFieldTypeString, alias: Representative Name, length: 255 )
• DISTRICTURL ( type: esriFieldTypeString, alias: District Website, length: 100 )
• LASTUPDATE ( type: esriFieldTypeDate, alias: Last Update Date, length: 8 )
• LASTEDITOR ( type: esriFieldTypeString, alias: Last Editor, length: 50 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• PhotoLink ( type: esriFieldTypeString, alias: Photo Link, length: 255 )
• Email ( type: esriFieldTypeString, alias: Email, length: 255 )
• PhoneNumber ( type: esriFieldTypeString, alias: Phone Number, length: 255 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• 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 )
• SHAPE.STArea() ( type: esriFieldTypeDouble, alias: SHAPE.STArea() )
• SHAPE.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )

Layer: Local Elected Representatives-At Large (1)

Name: Local Elected Representatives-At Large

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Previously, The City's Council Districts were established in 2002 after the population growth and shifts in the 2000 Census. The City Charter requires an analysis of the Council District lines within 180 days of a general election in which the Mayor is regularly elected to get the districts as nearly equal in population as is practicable. The City experienced population growth and population shifts in the 2020 Census that necessitates adjusting the Council districts.The City Charter requires a review of the district councilmember lines within 180 days of a general election in which the Mayor regularly elected. This is to be done so that the population in each of the districts will be as nearly equal as practicable. In 2002, the City Council passed Ordinance No 15219 establishing the current City Council Districts. This redistricting was due to population growth and shifts causing the existing Council districts to not be nearly equal in population. An analysis of the Council districts was conducted after the 2010 Census but no changes were made.The official population provided by the US Census for the City in 2020 is 123,011, an increase of approximately 6,200 people. Based on the 2020 Census population, the ideal district norm for the Council districts would be the population divided by four (4). This equals 30,753 people per district. Using the 2020 Census population and the current Council district boundaries, the population of each district is shown in the table below. If the current Council district boundaries were to remain, the deviation to the norm would be 7.28% (above the norm) to -9.36% (below the norm).The Council district boundaries were adjusted to get the population in each of the districts will be as nearly equal as practicable. Staff used Census Blocks, the smallest geographic area for which the Bureau of the Census collects and tabulates decennial census data, in adjusting the district boundaries. Census Blocks are formed by streets, roads, railroads, streams and other bodies of water, other visible physical and cultural features, and are the legal boundaries shown on Census Bureau maps. The boundaries were adjusted while maintaining the Noland and 23rd Street intersection. Staff started with District 4 as it was closest to the norm and moved counterclockwise adjusting the boundaries to get the population of each district as close to the norm as practicable. See the included Council District Map that highlights the changes to the current boundaries in blue crosshatch:The crosshatch area between Districts 2 and 3 indicates the highlighted area will move from District 3 to District 2.The crosshatch area between Districts 1 and 2 indicates the highlighted area will move from District 2 to District 1.The population of each proposed district is shown in the table below. The deviation to the norm has been significantly reduced to from 0.0001% to 0.1236%. Staff used population estimates out to 2026 to test whether the proposed Council district population holds. Based on population estimates provided by ESRI, the district population remains similar when projected out to 2026.

Service Item Id: db2df76757f046fa858bd28695817001

Copyright Text: City of Independence, MO

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 170752.40524865474

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 2793957.844637001
YMin: 1038082.4044480026
XMax: 2869353.9303869996
YMax: 1082838.9016980007
Spatial Reference: 102698  (102698)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: NAME
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: At Large
  Label: At Large
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [130, 130, 130, 0]
  Outline:
  Style: esriSLSSolid
  Color: [0, 0, 0, 255]
  Width: 1
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: N/A
Use Coded Values: true
Symbol:
Color: [0, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 10
Font Family: Tahoma
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 170752.40524865474
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:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• DISTRICTID ( type: esriFieldTypeString, alias: District ID, length: 10 , Coded Values: [1: COUNCIL DISTRICT 1] , [2: COUNCIL DISTRICT 2] , [3: COUNCIL DISTRICT 3] , ...1 more... )
• NAME ( type: esriFieldTypeString, alias: District Name, length: 50 )
• REPNAME ( type: esriFieldTypeString, alias: Representative Name, length: 255 )
• DISTRICTURL ( type: esriFieldTypeString, alias: District Website, length: 100 )
• LASTUPDATE ( type: esriFieldTypeDate, alias: Last Update Date, length: 8 )
• LASTEDITOR ( type: esriFieldTypeString, alias: Last Editor, length: 50 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• PhotoLink ( type: esriFieldTypeString, alias: Photo Link, length: 255 )
• Email ( type: esriFieldTypeString, alias: Email, length: 255 )
• PhoneNumber ( type: esriFieldTypeString, alias: Phone Number, length: 255 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• 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 )
• SHAPE.STArea() ( type: esriFieldTypeDouble, alias: SHAPE.STArea() )
• SHAPE.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )

Layer: Local Elected Representatives- Mayor (2)

Name: Local Elected Representatives- Mayor

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Previously, The City's Council Districts were established in 2002 after the population growth and shifts in the 2000 Census. The City Charter requires an analysis of the Council District lines within 180 days of a general election in which the Mayor is regularly elected to get the districts as nearly equal in population as is practicable. The City experienced population growth and population shifts in the 2020 Census that necessitates adjusting the Council districts.The City Charter requires a review of the district councilmember lines within 180 days of a general election in which the Mayor regularly elected. This is to be done so that the population in each of the districts will be as nearly equal as practicable. In 2002, the City Council passed Ordinance No 15219 establishing the current City Council Districts. This redistricting was due to population growth and shifts causing the existing Council districts to not be nearly equal in population. An analysis of the Council districts was conducted after the 2010 Census but no changes were made.The official population provided by the US Census for the City in 2020 is 123,011, an increase of approximately 6,200 people. Based on the 2020 Census population, the ideal district norm for the Council districts would be the population divided by four (4). This equals 30,753 people per district. Using the 2020 Census population and the current Council district boundaries, the population of each district is shown in the table below. If the current Council district boundaries were to remain, the deviation to the norm would be 7.28% (above the norm) to -9.36% (below the norm).The Council district boundaries were adjusted to get the population in each of the districts will be as nearly equal as practicable. Staff used Census Blocks, the smallest geographic area for which the Bureau of the Census collects and tabulates decennial census data, in adjusting the district boundaries. Census Blocks are formed by streets, roads, railroads, streams and other bodies of water, other visible physical and cultural features, and are the legal boundaries shown on Census Bureau maps. The boundaries were adjusted while maintaining the Noland and 23rd Street intersection. Staff started with District 4 as it was closest to the norm and moved counterclockwise adjusting the boundaries to get the population of each district as close to the norm as practicable. See the included Council District Map that highlights the changes to the current boundaries in blue crosshatch:The crosshatch area between Districts 2 and 3 indicates the highlighted area will move from District 3 to District 2.The crosshatch area between Districts 1 and 2 indicates the highlighted area will move from District 2 to District 1.The population of each proposed district is shown in the table below. The deviation to the norm has been significantly reduced to from 0.0001% to 0.1236%. Staff used population estimates out to 2026 to test whether the proposed Council district population holds. Based on population estimates provided by ESRI, the district population remains similar when projected out to 2026.

Service Item Id: db2df76757f046fa858bd28695817001

Copyright Text: City of Independence, MO

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 170752.40524865474

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 2793957.844637001
YMin: 1038082.4044480026
XMax: 2869353.9303869996
YMax: 1082838.9016980007
Spatial Reference: 102698  (102698)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: NAME
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: Mayor
  Label: Mayor
  Description: N/A
  Symbol:
  Style: esriSFSSolid
  Color: [130, 130, 130, 0]
  Outline:
  Style: esriSLSSolid
  Color: [0, 0, 0, 255]
  Width: 1
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: N/A
Use Coded Values: true
Symbol:
Color: [0, 0, 0, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 10
Font Family: Tahoma
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 170752.40524865474
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:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• DISTRICTID ( type: esriFieldTypeString, alias: District ID, length: 10 , Coded Values: [1: COUNCIL DISTRICT 1] , [2: COUNCIL DISTRICT 2] , [3: COUNCIL DISTRICT 3] , ...1 more... )
• NAME ( type: esriFieldTypeString, alias: District Name, length: 50 )
• REPNAME ( type: esriFieldTypeString, alias: Representative Name, length: 255 )
• DISTRICTURL ( type: esriFieldTypeString, alias: District Website, length: 100 )
• LASTUPDATE ( type: esriFieldTypeDate, alias: Last Update Date, length: 8 )
• LASTEDITOR ( type: esriFieldTypeString, alias: Last Editor, length: 50 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• PhotoLink ( type: esriFieldTypeString, alias: Photo Link, length: 255 )
• Email ( type: esriFieldTypeString, alias: Email, length: 255 )
• PhoneNumber ( type: esriFieldTypeString, alias: Phone Number, length: 255 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• 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 )
• SHAPE.STArea() ( type: esriFieldTypeDouble, alias: SHAPE.STArea() )
• SHAPE.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )