11/22/2024- County-wide road updates were completed in Golden Valley and Billings Counties. Intersecting routes throughout the state were cartographically realigned in preparation of MIRE intersections 6/27/2024 - The data was prepared for HPMS submittal which included updated 2023 AADT values and to keep certain segments consistent with HPMS segments, mainly sample sections and the NHS, values of "BOTH", "NHS" and "SAMPLE" were added to the field HPMS_ROUTE_ID to distinguish these segments from other segments. 3/19/2024 - Miscellaneous updates were done in Dunn County. County wide updates to Grand Forks and Golden Valley counties along with route realignments at intersections throughout the state.12/04/2023 - County wide updates to Walsh, Dunn and Grand Forks Counties and various updates to county/local roads throughout the state including street names in Westhope8/23/2023 - Function Class changes were updated in McLean and Mountrail Counties. Function Class updates also occurred in the cities of Fargo, Valley City, West Fargo and Williston. County-wide updates completed for: Towner, Cavalier, Pembina, Pierce, Benson, Ramsey. 2022 AADTs updated. A road was also removed in Bottineau County at the request off a landowner.5/19/22 - Dunn County contacted the NDDOT with data updates ,Rolette County was updated, and the 2021 AADT's were updated. 2/14/22 - Contacted by the Dunn County Road Dept., updates were made on newly paved road segments. 1/20/2022 - Since the August 2021 update, Morton, Stark, Hettinger, Bowman, Adams, Slope, Grant and Sioux Counties have been updated using 2020 imagery. Surface type has been checked and updated on all functionally classified roads statewide. Function Class changes have been made in the Bismarck/Mandan Metro, Grand Forks County and Burleigh County.6/15/21 - Since the 2019 update, trails and seldom used trails were updated statewide using 2018,and 2019 imagery. Steele, Traill and Griggs Counties have also been updated using 2020 imagery. Surface type has been checked and updated on all functionally classified roads statewide New roads added includes roads in the Fargo, West Fargo, Grand Forks, Jamestown, Bismarck, Mandan, Minot, Dickinson, Watford City and Williston. Ownership on Federal jurisdiction roads were also updated based on an dataset received for FHWA in conjunction with the HPMS submittal. HPMS (Highway Performance Monitoring System) fields were also added in an effort to integrate the roads county data into HPMS and MIRE (Model Inventory Roadway Elements). 9/14/20 - Added the following fields - AADT, AADT_YR, HPMS_MAINTENANCE_OPERATIONS, HPMS_THROUGH_LANES, FUNCTIONAL_CLASS (replaces FUNCTION_CLASS)8/13/19 - The following counties were updated by using a variety of aerial photography: Eddy, Foster and Barnes. Seldom used trails have been added to Barnes, Benson, Billings, Bottineau, and Bowman Counties. Mercer County had (2) 61STAvenues, this has been corrected.12/26/18 - The following counties have had their roads updated by a variety of aerial photography, McHenry, Wells, Kidder, Cass (with aid of Cass county website) and McKenzie (with aid of McKenzie County GIS Coordinator)8/14/18 - Counties updated using 2017 NAIP Imagery are Ward, Mountrail, Burke and Renville counties. Seldom used trails are also being digitized into the dataset. They are being added as counties are being checked, so it will take some time for all seldom used trails to be added statewide. Also since the last update, all local roads that are in the corporate boundaries have been broken at the boundaries so it is easier to query to determine which roads go with each community.5/21/18 - removed CITY_INT_ID column - no longer used because of CITY_FIPS and HPMS_URBAN_CODE attributes. Removed SERVICE_LEVEL field, never used/maintained.4/19/18 - added HPMS_OWNERSHIP and HPMS_FACILITY fields for HPMS submittal1/24/18 - added CITY_FIPS and HPMS_URBAN_CODE attributes/domains. These columns will replace CITY_INT_ID and SOURCE_ID columns (eventually).11/15/17 - Williams, Divide and Bottineau counties have been updated. Great effort has been taken to update attributes and QC null fields. Functional Classified roads in Bismarck and Mandan have been updated as have local roads in Bismarck, Mandan, Williston, Fargo – West Fargo and Minot. 1/25/17 - started to maintain roads in Esri's Road and Highways. The shapes now contain measures in miles along with the associated linear referencing/roads and highways fields. Removed INSET_ASSOC field and added COUNTY_FIPS field.Updates include the counties of Emmons, Logan, McIntosh, Lamoure, Dickey, Ransom, Sargent and Richland. These counties were updated using a combination of the available NAIP aerials, the DES aerials, and by car within the insets. In addition to these updates, the whole county dataset was edited using Data Reviewer checks. The checks ran included unnecessary nodes, non-linear segments, invalid geometry, Duplicate vertices with a tolerance of .5 meters, polyline closes of self, checked for cutbacks using a 15 degree minimum angle, checked for polyline length check using a distance less than 10 meters, checked for multipart lines, inspected dangles with a tolerance of 10 meters, and checked for orphans. All checks were inspected and fixed where appropriate.7/16/14 - updates include: Traill, Barnes, Stutsman, Kidder, Bowman, Slope, Stark, Hettinger, Adams, Grant, Sioux and Morton. These datasets were updated using a combination of the available NAIP aerials, the DES aerials, and by car within the insets.10/22/12 - city streets were updated in Bismarck, Dickinson, Minot and Williston. GIS data from the city of Bismarck was used to update Bismarck, GIS data and 2012 aerial photography was used to update the city of Williston, Minot’s city map and the 2010 aerial photography from Ward County was used to update Minot, and 2011 aerial photography and Dickinson’s "working" city map was used to update Dickinson. The counties updated were Williams, Burke, Bottineau, Mountrail, Ward, Wells, Eddy, Foster, Griggs, Steele, and Cass. At the time of this updated, approximately 50% of Stutsman and 50% of Traill Counties are updated. Williams, Bottineau, Ward, and Mountrail roads were inspected from the air and the 2009 NAIP photos were also used to assist the updates. The roads in Williams County were also recoded to match Williams County naming conventions. Williams County CADD map which is on the Williams county web site was used in updating the road names. In Ward County, the 2010 image from Ward County was used to assist in updating Ward County. The 2010 NAIP photos were used to update Wells, Eddy, Foster, Griggs and Steele Counties. Cass was updated with the assistance of the Cass County GIS layer and the 2011 Cass county imagery. 10/3/2011 - County roads were edited in the cities of Fargo, West Fargo, Horace, Minot, Bismarck, Devils Lake, Grafton, Williston, Valley City, and Dickinson. Also, a part of Ward and Mchenry Counties was edited and the county of Renville has been updated. The business routes through Bismarck and Jamestown were also edited. 5/9/2011 - Updated streets in Bismarck, Mandan, Jamestown, Dickinson, West Fargo ( not quite finished yet), and Valley City. Also, corrected the north - south roads in Township 144N Ranges 49 - 53 E, (in Traill County) 10/5/10 - The original Roads_County data was maintained in two separate ArcInfo coverages and then combined each year and exported to the NDHUB infrastructure. These two coverages have now been combined into one SDE feature class and is being edited within the SDE environment. The following changes have been made to feature class. Deleted all the A1 and A2 Fields so a person would have to hunt back and forth to find a road name. Road names consist of the following fields: RTE_ID, STR_TYP, SUF_DIR, & LAN_DIR. The CMC route numbers were moved from the A1_ prefixed fields to the CMC field to better track the CMC route. Created a County Highway field so we can enter the county road number. It consists of the counties name and number. This is still a work in progress. Created FS_RD_Number and FS_RD_Name fields to better track Forest Service roads. Created Bia-RD_Number and BIA_RD_Name fields to better track Bureau of Indian Affairs roads. The following field changes are used for NDDOT specific processes: Created a service level field which is something that may be used in the future. Currently it contains how Walsh County prioritizes their roads. Created a Through and Connecting Route field so we can so select routes through the towns and cities. This was created exclusively for the county base maps. Created an Inset Associated field. This was created so the information in the rd_misc would come into the county routes. In the future, it is planned to be deleted. 6/18/09 - Updated county routes from aerial observation and photo interpretation using 2003, 2005, 2006 NAIP photos and 2008 photography from Designs camera. Counties updated were Golden Valley, Billings, McKenzie, Dunn, Mercer, Oliver, McLean, Sheridan and Burleigh. City streets were rectified in these counties using the 2003 NAIP photos. Observations were performed by Steven Nelson. 4/17/08 - Updated road surface types in NE. Rolette, Pierce, Benson, Towner, Ramsey, Cavalier, Pembina, Walsh, Grand Forks and Nelson from the 2006 aerial observations by Dewaine Olson 2/13/07 - Updated via 2004 NAIP photos: Barnes, Cass, Eddy, Foster, Griggs, Kidder, Steele, Stutsman, Traill, Wells. Combined Misc Roads and County Roads. Blank fields mean unknown attribute. Use P_STREET_NAME for dynamic labeling. We are also in the process of removing all proposed roads. 12/28/05 - Counties updated: Emmons, Logan, Mcintosh, Lamoure, Dickey, Ransom, Sargent, Richland, Divide, Williams, Burke, Mountrail, Ward, Renville, Bottineau, and Mchenry This data came from the NDDOT's Mapping Section. The original data was digitized from hand scribed maps and registered

The Digital Geologic-GIS Map of Fredericksburg and Spotsylvania County Battlefields Memorial National Military Park and Vicinity, Virginia is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) an ESRI file geodatabase (frsp_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro 3.X map file (.mapx) file (frsp_geology.mapx) and individual Pro 3.X layer (.lyrx) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (frsp_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (frsp_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (frsp_geology_metadata_faq.pdf). Please read the frsp_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri.htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (frsp_geology_metadata.txt or frsp_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS Pro, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

City council/ward districts. Boundaries were obtained from the jurisdiction and used to generate the present data set to be spatially accurate and adjusted to the County's parcel base map. Boundaries will be updated as annexations occur, and adjusted as needed to the parcel map.

We are also including a tabular version that’s slightly more comprehensive (would include anything that didn’t join to the parcel basefile due to lot alterations or resubdivisions since 2023 and/or due to parcels comprised of condos). This Excel file can be downloaded HERE, and does not contain the latitude and longitude information.Data Dictionary: Attribute Label Definition Source

TAX_ID Unique 26 character property tax identification number Onondaga County Planning

PRINTKEY Abbreviated tax identification number (section-block-lot) Onondaga County Planning

ADDRESSNUM Property’s physical street address Onondaga County Planning

ADDRESSNAM Property’s physical street name Onondaga County Planning

LAT Latitude Onondaga County Planning

LONG Longitude Onondaga County Planning

TAX_ID_1 City Tax ID number (26 digit number used for parcel mapping) City of Syracuse - Assessment

SBL Property Tax Map Number (Section, Block, Lot) City of Syracuse - Assessment

PNUMBR Property Number (10 digit number) City of Syracuse - Assessment

StNum Parcel street number City of Syracuse - Assessment

StName Parcel street name City of Syracuse - Assessment

FullAddress Street number and street name City of Syracuse - Assessment

Zip Parcel zip code City of Syracuse - Assessment

desc_1 Lot description including dimensions City of Syracuse - Assessment

desc_2 Lot description including dimensions City of Syracuse - Assessment

desc_3 Lot description including dimensions City of Syracuse - Assessment

SHAPE_IND

City of Syracuse - Assessment

LUC_parcel New York State property type classification code assigned by assessor during each roll categorizing the property by use. For more details: https://www.tax.ny.gov/research/property/assess/manuals/prclas.htm City of Syracuse - Assessment

LU_parcel New York State property type classification name City of Syracuse - Assessment

LUCat_Old Legacy land use category that corresponds to the overarching NYS category, i.e. all 400s = commercial, all 300s = vacant land, etc. NA

land_av Land assessed value City of Syracuse - Assessment

total_av Full assessed value City of Syracuse - Assessment

Owner Property owner name (First, Initial, Last, Suffix) City of Syracuse - Assessment

Add1_OwnPOBox Property owner mailing address (PO Box) City of Syracuse - Assessment

Add2_OwnStAdd Property owner mailing address (street number, street name, street direction) City of Syracuse - Assessment

Add3_OwnUnitInfo Property owner mailing address unit info (unit name, unit number) City of Syracuse - Assessment

Add4_OwnCityStateZip Property owner mailing address (city, state or country, zip code) City of Syracuse - Assessment

FRONT Front footage for square or rectangular shaped lots and the effective front feet on irregularly shaped lots in feet City of Syracuse - Assessment

DEPTH Actual depth of rectangular shaped lots in feet (irregular lots are usually measured in acres or square feet) City of Syracuse - Assessment

ACRES Number of acres (where values were 0, acreage calculated as FRONT*DEPTH)/43560) City of Syracuse - Assessment

yr_built Year built. Where year built was "0" or null, effective year built is given. (Effective age is determined by comparing the physical condition of one building with that of other like-use, newer buildings. Effective age may or may not represent the actual year built; if there have been constant upgrades or excellent maintenance this may be more recent than the original year built.) City of Syracuse - Assessment

n_ResUnits Number of residential units NA - Calculated field

IPSVacant Is it a vacant structure? ("Commercial" or "Residential" = Yes; null = No) City of Syracuse - Division of Code Enforcement

IPS_Condition Property Condition Score assigned to vacant properties by housing inspectors during routine vacant inspections (1 = Worst; 5 = Best) City of Syracuse - Division of Code Enforcement

NREligible National Register of Historic Places Eligible ("NR Eligible (SHPO)," or "NR Listed") City of Syracuse - Neighborhood and Business Development

LPSS Locally Protected Site Status ("Eligible/Architecturally Significant" or "Local Protected Site or Local District") City of Syracuse - Neighborhood and Business Development

WTR_ACTIVE Water activity code ("I" = Inactive; "A" = Active) City of Syracuse - Water

RNI Is property located in Resurgent Neighborhood Initiative (RNI) Area? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DPW_Quad Geographic quadrant property is located in. Quadrants are divided Northwest, Northeast, Southwest, and Southeast based on property location in relation to I-81 and I-690. DPW uses the quad designation for some types of staff assignments. City of Syracuse - Department of Public Works

TNT_NAME TNT Sector property is located in City of Syracuse - Neighborhood and Business Development

NHOOD City Neighborhood Syracuse-Onondaga County Planning Agency (SOCPA)

NRSA Is property located in Neighborhood Revitilization Strategy Area (NRSA)? (1 = Yes; 0 = No) City of Syracuse - Neighborhood and Business Development

DOCE_Area Geographic boundary use to assign Division of Code Enforcement cases City of Syracuse - Neighborhood and Business Development

ZONE_DIST_PREV Former zoning district code Syracuse-Onondaga County Planning Agency (SOCPA)

REZONE ReZone designation (adopted June 2023) City of Syracuse - Neighborhood and Business Development

New_CC_DIST Current Common Council District property is located in Onondaga County Board of Elections

CTID_2020 Census Tract ID (2020) U.S. Census Bureau

CTLAB_2020 Census Tract Label (2020) U.S. Census Bureau

CT_2020 Census Tract (2020) U.S. Census Bureau

SpecNhood Is property located in a special Neighborhood historic preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

InPD Is property located in preservation district? (1 = Yes; 0 or null = No) Syracuse-Onondaga County Planning Agency (SOCPA)

PDNAME Preservation District name Syracuse-Onondaga County Planning Agency (SOCPA)

ELECT_DIST Election district number Onondaga County Board of Elections

CITY_WARD City ward number Onondaga County Board of Elections

COUNTY_LEG Onondaga County Legislative District number (as of Dec 2022) Onondaga County Board of Elections

NYS_ASSEMB New York State Assembly District number (as of Dec 2022) Onondaga County Board of Elections

NYS_SENATE New York State Senate District number (as of Dec 2022) Onondaga County Board of Elections

US_CONGR United States Congressional District number Onondaga County Board of Elections

Dataset Contact InformationOrganization: Neighborhood & Business DevelopmentPosition:Data Program ManagerCity:Syracuse, NYE-Mail Address:opendata@syrgov.netPlease note there is a data quality issue in this iteration with the preservation district (“InPD,” “PDNAME”) and special neighborhood historic district (“SpecNhood”) fields erroneously showing null results for all parcels.

This dataset demarcates municipal voting districts in Allegheny County. Allegheny County Elections Districts were updated in 2019 to match municipal boundaries. Coordinate System: Pennsylvania State Plane South Zone 3702; U.S. Survey Foot Data Dictionary: https://docs.google.com/spreadsheets/d/1HR24LyBNpLwvJZoaGp-tBGRw0HRoXNIef6nU4UQQMMo/edit?usp=sharing CHANGELOG 2023-03-29: This dataset was harvested on a weekly basis from Allegheny County’s GIS data portal until March of 2023, when it was removed from the Allegheny County’s GIS portal.

This item is in mature support and is no longer updated. Available for historical reference only. This dataset contains polygons representing voting Ward boundaries within all municipalities in the state of New Jersey. The statewide dataset was created from existing vector data maintained by Remington & Vernick Engineers, under contract with the NJ Department of State, Division of Elections and KNOWiNK, for eleven counties (in part or in whole) and from county and municipal Election District and Ward maps, tax assessment parcel GIS data, and other data sources, for the balance of the state.

12/06/2024 - Updates to Ellendale, Fargo, Kindred, Lincoln, Mandan, Rugby and Tappen.12/06/2024 - Update to Lincoln and Bismarck Corporate Boundaries based on requests from Lincoln.6/27/2024 - Update to the Valley City and Dickinson Corporate Boundary based on requests from their GIS personal.4/8/2024 - Update to the Valley City Corporate Boundary12/04/2023 - Update to Fargo City Boundary7/23/2023 - Removed Church’s Ferry due to proclamation and notice of dissolution.7/01/2023 - Changes to Binford - Ordinance 51; Lidgerwood - Ordinance 2022-1; Killdeer Golf Course annexation; Bismarck based on current City of Bismarck GIS boundary9/26/2022 - Changes to Steele boundary per Kidder County 911 coordinator.9/23/2022 - Updates to Grand Forks, Mandan and Fargo7/01/2022 - Updates to Killdeer, Mandan and Williston per State Tax Dept changes. 2/14/2022- Updates to Minot -13th ST SE/31st AVE SE, Updates to Elgin, Horace and St. John.11/16/2021 -Updates to Bismarck, Fargo and Killdeer based on city ordinances.7/2/21 – Changes were made to the City of Bismarck, Fargo and Hillsboro to include local taxing jurisdiction boundary changes from the State Tax Commissioner.5/4/21 - Updates were made to the City of Wahpeton due to an annexation.4/29/21 - Updated Minot and Makoti3/5/21 - Updated an annexation to Arnegard that was submitted to the DOT by Mackenzie's County Public Works GIS Coordinator.1/21/21 - Update to Sentinel Butte per Golden Valley 911 Coordinator7/17/20 - Updates to Bismarck, Linton and Stanley6/1/20 - Updates to Killdeer, New Town and Surrey1/17/2020 - Boundary changes have been updated for Bismarck, Bowman Fargo, Garrison, Linton, and New Salem.3/5/19 - The corporate boundary of Surrey has been updated.12/26/18 - The following corporate boundaries have been updated: Bismarck, Lincoln, Grand Forks, Horace, Casselton, Fargo, Oxbow, Tioga and Stanley.6/19/18 - City of Maza is not incorporated based on the 2011-2013 North Dakota Blue book. Removed Maza.5/14/18 - Updated Dickinson, Watford City, Berthold, Minnewauken, and Cavalier.1/31/18 - Updated Dickinson, Mandan, Minot, Tioga, Devils Lake, Belfield, Washburn, Mohall, Minnewauken, Lincoln, Bismarck and Casselton. 10/24/17 - Updated Watford City and Makoti10/16/17 - The following cities have been updated: Jamestown, Milnor, Bismarck, Carrington, Casselton, Mandan, Minot, Stanley, Larimore, Crosby, and Watford City.1/10/17 - The following cities have been updated: Lehr, Grand Forks, Langdon, Drayton, Flasher, Glen Ullin, Watford City, Zap, Lignite, Hankinson, Beach, Underwood, South Heart, Devils Lake, all cities in Ward County, Cavalier, Bismarck, Lincoln, Fargo, West Fargo, Ayr, Briarwood, Casselton, Davenport, Enderlin, Grandin, Horace, and North River.9/19/16 - Updated the following cities: Watford City, Steele, Richardton, Berthold, Carpio, Burlington, Des Lacs, Donnybrook, Douglas, Kenmare, Makoti, Ryder, Sawyer, and Surrey.6/23/16 - Updated cities are as follows: All cities in Pembina, Morton, Richland, and Williams Counties. The cities of Bismarck, West Fargo, Harwood, Oxbow, Beach, Minot, Stanley, Jamestown, Fargo, Dickinson and New Town.9/28/15 - The following cites have had annexation: Stanley, Bottineau, Minot, Casselton, Belfield and Watford City.7/24/15 - Updated Grafton, Stanley, Bismarck, Williston, Horace, Fargo, Grand Forks, Watford City, Turtle Lake, Leeds, Maxbass and Medora1/16/15 - Updated Grafton, Stanley and Bismarck.11/3/2014 - Updated Bismarck, Mandan, Minot, Stanley, and Watford City7/16/14 - Corporate limits updated include: Mandan, Towner, Fargo, West Fargo, Grand Forks, Bismarck, Bowman, Watford City, Stanley, Tioga, Kenmare, Casselton, Minot, Carrington, Kindred, and Killdeer. The corporate limit updates consisted of receiving from the cities, shape files, CADD files, scanned images of annexations or by converting pdf files into images, rectifying them within ArcGIS, then heads-up digitizing. 7/29/13 - updated Stanley, Williston, Minot, and Bismarck.4/30/13 - updated Williston, Hazen, Minot, Dickinson, Valley City, Velva, Rugby, Bismarck, and Lincoln1/28/13 - updated Valley City, Grand Forks, Bismarck, Williston, Jamestown, Harvey, Mohall, Park River, Ray, Rugby, Stanley, Tioga, Mayville and Glenfield10/9/12 - updated Williston and Dickinson6/20/12 - updated Williston via shapefile from city.3/20/12 - updated Bismarck and Minot10/3/2011 - Edited corporate limits for Bottineau, Grand Forks, Bismarck, Grafton, Fargo, West Fargo, Horace, Dickinson, Williston, Valley City and Devils Lake.2/4/11 - Removed urban areas so only corporate boundaries remain. Removed boolean field named URBAN_AREA. Updated corporate limist in Dickinson and cities with Cass county. 6/24/10 - Stanley, Lincoln, Oakes, Hankinson, Enderlin, Ellendale, Linton, Carrington, Minot, and Kulm corportate limits were changed 6/18/09 - Stanley, Wahpeton, Center, Watford City, Williston, Grand Forks, Killdeer, Beulah, Beach, Hazen, Garrison, Washburn, Bismarck and Lincoln corporate limits were changed 3/24/08 - Added Milton, Drayton, and Cavalier Boudaries updated: Park River 1/16/08 - Boundaries updated: Devils Lake, Glen Ullin, Langdon, Minnewaukan, Northwood, Thompson 2/13/07 - Boundaries updated: Amenia, Arthur, Bismarck, Bottineau, Buffalo, Casstleton, Davenport, Dickinson, Enderlin, Gardner, Grand Forks, Grandin, Harvey, Harvey, Hillsboro, Horace, Hunter, Jamestown, Kindred, Mapleton, Mayville, New Rockford, Oxbox, Page, Prairie Rose, Relies Acres, Tappen, Towner City 1/10/06 - Boundaries updated: Wishek, Fargo, Lincoln, Bottineau, Williston, Grand Forks, Granville, Velva, Stanley, urban areas in Fargo, West Fargo, Bismarck and Mandan. Deleted Larson This data came from the NDDOT's Mapping Section. The original data was digitized from hand scribed maps and registered to the 1:24000 USGS PLSS data. It was converted from a projection (NAD 1983 UTM Zone 14N) to a Geographic coordinate system.

This dataset contains the Maricopa County, Arizona City Council District boundaries for those cities with council districts. This includes Phoenix, Surprise, Buckeye, Peoria, Glendale and Mesa.

The cities annex feature class is intended to track city and town annexations in Maricopa County, Arizona.

This is an ESRI shapefile of State-wide municipal ward boundaries for the State of Oklahoma. Boundaries are based on information provided by the Oklahoma Tax Commission and Oklahoma County Election Boards. This State-wide shape file is created by merging the individual municipal ward boundary shapefiles for any municipalites in the State which vote by ward.

Wisconsin municipal boundaries (cities, towns, and villages) downloaded in January 2024. This data has been collected in regards to state statute 15(4)(br)1. County clerks will transmit municipal, municipal ward, and county supervisory districts in GIS format to LTSB by January 15th and July 15th per statute 5.15(4)(br)1: "...no later than January 15 and July 15 of each year*, the county clerk shall transmit to the Legislative Technology Services Bureau a report confirming the boundaries of each municipality, ward, and supervisory district in the county together with a map of the county, in an electronic format approved by the Legislative Technology Services Bureau. Each report shall be current to the nearest January 1 or July 1* preceding the date of the report”. Municipal clerks need to notify the county clerk within 5 days of any boundary change per statute 5.15(4)(b): "Within 5 days after adoption or enactment of an ordinance or resolution under this section or any amendment thereto, the municipal clerk shall transmit one copy of the ordinance or resolution or the amendment to the county clerk of each county in which the municipality is contained, accompanied by the list and map specified in par. (a). Each copy shall identify the name of the municipality and the county or counties in which it is located." Geographic Data can be downloaded here:https://data-ltsb.opendata.arcgis.com/Census Data can be downloaded here: Census Bureau Search Income Data

B19013 MEDIAN HOUSEHOLD INCOME IN THE PAST 12 MONTHS (IN 2019 INFLATION-ADJUSTED DOLLARS) 2018-2022American Community Survey 5-Year Estimates

Sex by Age

B01001 SEX BY AGE 2018-2022American Community Survey 5-Year Estimates

Race

B02001 RACE2018-2022American Community Survey 5-Year Estimates

Wisconsin municipal ward data collected in July 2024 by LTSB that was dissolved into municipal boundaries (cities, towns, and villages). [Attribute Definitions]. This data has been collected in regards to state statute 15(4)(br)1. County clerks will transmit municipal, municipal ward, and county supervisory districts in GIS format to LTSB by January 15th and July 15th* per statute 5.15(4)(br)1: "...no later than January 15 and July 15 of each year*, the county clerk shall transmit to the Legislative Technology Services Bureau a report confirming the boundaries of each municipality, ward, and supervisory district in the county together with a map of the county, in an electronic format approved by the Legislative Technology Services Bureau. Each report shall be current to the nearest January 1 or July 1* preceding the date of the report”. (*with the exception of years ending in “01” where data collection will align closer to typical redistricting timelines of March and October 15)Municipal clerks need to notify the county clerk within 5 days of any boundary change per statute 5.15(4)(b): "Within 5 days after adoption or enactment of an ordinance or resolution under this section or any amendment thereto, the municipal clerk shall transmit one copy of the ordinance or resolution or the amendment to the county clerk of each county in which the municipality is contained, accompanied by the list and map specified in par. (a). Each copy shall identify the name of the municipality and the county or counties in which it is located."Municipal data collected in the January collections will be used by LTSB to update municipal boundaries the U.S. Census Bureau’s TIGER database via the Boundary Annexation Survey (BAS). Counties and municipalities are no longer required to submit boundary changes directly to the Census Bureau. LTSB will submit data to the Census Bureau for the state as a whole.Section 13.96(1)(b) of the Wisconsin Statutes requires LTSB to “upon receipt of municipal boundary information at each reporting interval, reconcile and compile the information received to produce a statewide data base consisting of municipal boundary information for the entire state”.Section 13.96(1)(c) states that LTSB shall “Participate, on behalf of this state, in geographic boundary information programs when offered by the U.S. bureau of the census”.LTSB will publish Municipal Wards, Municipal Boundaries (cities, towns, villages), and County Supervisory Districts to the LTSB HUB Data Portal.This data has been collected with the LTSB GeoData Collector.

This data has been collected in regards state statute 5.15(4)(br)1. Municipal clerks within 5 days of any boundary change need to notify the county clerk.5.15(4)(b)Within 5 days after adoption or enactment of an ordinance or resolution under this section or any amendment thereto, the municipal clerk shall transmit one copy of the ordinance or resolution or the amendment to the county clerk of each county in which the municipality is contained, accompanied by the list and map specified in par. (a). Each copy shall identify the name of the municipality and the county or counties in which it is located.County clerks will transmit municipal, municipal ward and county supervisory districts in GIS format to LTSB by January 15thand July 15th. ”no later than January 15 and July 15 of each year, the county clerk shall transmit to the legislative technology services bureau a report confirming the boundaries of each municipality, ward, and supervisory district in the county together with a map of the county, in an electronic format approved by the legislative technology services bureau. Each report shall be current to the nearest January 1 or July 1 preceding the date of the report”.Municipal data collected in January will be used by LTSB to update municipal boundaries the U.S. Census Bureau’s TIGER database via the Boundary Annexation Survey (BAS). Counties and municipalities are no longer required to submit boundary changes directly to the Census Bureau. LTSB will submit data to the Census Bureau for the state as a whole.Section 13.96(1)(b)of the Wisconsin Statutes requires LTSB to “upon receipt of municipal boundary information at each reporting interval under s. 5.15 (4) (bg), reconcile and compile the information received to produce a statewide data base consisting of municipal boundary information for the entire state”.13.96(1)(c)LTSB shall “Participate, on behalf of this state, in geographic boundary information programs when offered by the U.S. bureau of the census”.LTSB will publish Municipal Ward, Municipal Boundaries and County Supervisory Districts to the LTSB Open Data Portal located at http://data.ltsb.opendata.arcgis.com/.This data has been collected with the WISE-Decade software platform. For more information on this system please visit http://legis.wisconsin.gov/ltsb/gis/wise-decade/.

LTSB dissolves municipal ward data into county supervisory districts. Wisconsin municipal ward data was collected in July 2024. [Attribute Definitions]. This data has been collected in regards to state statute 15(4)(br)1. County clerks will transmit municipal, municipal ward, and county supervisory districts in GIS format to LTSB by January 15th and July 15th* per statute 5.15(4)(br)1: "...no later than January 15 and July 15 of each year*, the county clerk shall transmit to the Legislative Technology Services Bureau a report confirming the boundaries of each municipality, ward, and supervisory district in the county together with a map of the county, in an electronic format approved by the Legislative Technology Services Bureau. Each report shall be current to the nearest January 1 or July 1* preceding the date of the report”. (*with the exception of years ending in “01” where data collection will align closer to typical redistricting timelines of March and October 15)Municipal clerks need to notify the county clerk within 5 days of any boundary change per statute 5.15(4)(b): "Within 5 days after adoption or enactment of an ordinance or resolution under this section or any amendment thereto, the municipal clerk shall transmit one copy of the ordinance or resolution or the amendment to the county clerk of each county in which the municipality is contained, accompanied by the list and map specified in par. (a). Each copy shall identify the name of the municipality and the county or counties in which it is located."Municipal data collected in the January collections will be used by LTSB to update municipal boundaries the U.S. Census Bureau’s TIGER database via the Boundary Annexation Survey (BAS). Counties and municipalities are no longer required to submit boundary changes directly to the Census Bureau. LTSB will submit data to the Census Bureau for the state as a whole.Section 13.96(1)(b) of the Wisconsin Statutes requires LTSB to “upon receipt of municipal boundary information at each reporting interval, reconcile and compile the information received to produce a statewide data base consisting of municipal boundary information for the entire state”.Section 13.96(1)(c) states that LTSB shall “Participate, on behalf of this state, in geographic boundary information programs when offered by the U.S. bureau of the census”.LTSB will publish Municipal Wards, Municipal Boundaries (cities, towns, villages), and County Supervisory Districts to the LTSB HUB Data Portal.This data has been collected with the LTSB GeoData Collector.

Historical map showing streets, railroads, lot and concession numbers, ward boundaries and county boundaries.Scale 10 chains to an inchMap date: 1879Map is page 21 of the Atlas of the province of Ontario by counties / published by Miles and Company, TorontoDigital reproduction of map (23 x 29 cm.) in the Brock University Map, Data & GIS Library collection. Georeferenced and modified from Brock call # G 3464 S35 1879 M55 by Map, Data and GIS Library, Brock University. (verso map)

This data includes new data delivered in 2024 by R&V. This dataset uses a new schema that was provided with the new data. Data was loaded by Smalley in March 2024. Data provided was only included for warded towns. The remainder of the towns were loaded from existing data, which the majority of the metadata is based on. For important metadata on the new data source, contact Middlesex County Office of IT. Description from source: Remington & Vernick Engineers computer-generated and currently maintains, all or in part, the ward/election maps for eleven (11) New Jersey County Boards of Election utilizing AutoCAD software and Esri ArcGIS software applications. We will utilize and reference these resources along with GIS resources available through local, county, state and federal sources, including, but not limited tax assessment parcel data. We will use these resources to create, update, maintain and verify the State-wide GIS dataset comprised of polygon shape files representing the current ward boundaries and election district boundaries for all constituent municipalities in the twenty-one (21) counties in the state of New Jersey. Description from target data.Municipal voting district boundaries 2011-2020. The segmentation of a municipality for voting purposes is based on their type of government. In Middlesex County seven municipalities are divided into Ward/Districts and the balance of eighteen are divided into Districts only. In Warded towns, the geographical area is divided into equally sized wards based on registered voters. Every 10 years, after a Census, each Ward must be examined and “re‑balanced” so that each of the Wards contains an equal amount of voters, within a certain percentage. Each Ward is sub-divided into Districts or Voting districts where each district is analyzed after 2 consecutive General elections so that the votes cast were no more than 750 votes or less than 250. If there are more, the county considers a split of a district, or if less than 250, merging with an adjacent district is considered. Based on the numbers mentioned above, the list of registered voters is reviewed and as close as possible boundaries are drawn to contain the appropriate amount of voters. Physically, boundaries can be centers of streets, fence lines, waterways, etc.

Feature Type: PolygonMetadata: https://gis.dutchessny.gov/data-catalog/#1103