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

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.

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.

A lookup of wards to local authority districts to county to county electoral divisions in England as at 4 May 2017. (File Size - 2 MB).

Field Names – WD17CD, WD17NM, LAD17CD, LAD17NM, CTY17CD, CTY17NM, CED17CD, CED17NM, FID Field Types – Text, Text, Text, Text, Text, Text, Text, Text, Number Field Lengths – 9, 56, 9, 28, 9, 28, 9, 55, 4REST URL of Feature Access Service – https://services1.arcgis.com/ESMARspQHYMw9BZ9/arcgis/rest/services/Ward_to_LAD_to_County_to_County_Electoral_Division_May_2017_Lookup_for_England/FeatureServer

We are also including 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). There are approximately 200 records that don't join to the spatial parcel file and some additional that are null in the spatial parcel file, altogether around 560 total. This Excel file can be downloaded HERE, and does not contain the latitude and longitude information.Data Dictionary:Attribute LabelDefinitionSourceTAX_IDUnique 26 character property tax identification numberOnondaga County PlanningPRINTKEYAbbreviated tax identification number (section-block-lot)Onondaga County PlanningADDRESSNUMProperty’s physical street addressOnondaga County PlanningADDRESSNAMProperty’s physical street nameOnondaga County PlanningTAX_ID_1City Tax ID number (26 digit number used for parcel mapping)City of Syracuse - AssessmentSBLProperty Tax Map Number (Section, Block, Lot)City of Syracuse - AssessmentPNUMBRProperty Number (10 digit number)City of Syracuse - AssessmentStNumParcel street numberCity of Syracuse - AssessmentStNameParcel street nameCity of Syracuse - AssessmentFullAddressStreet number and street nameCity of Syracuse - AssessmentZipParcel zip codeCity of Syracuse - Assessmentdesc_1Lot description including dimensionsCity of Syracuse - Assessmentdesc_2Lot description including dimensionsCity of Syracuse - Assessmentdesc_3Lot description including dimensionsCity of Syracuse - AssessmentSHAPE_IND City of Syracuse - AssessmentLUC_parcelNew 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.htmCity of Syracuse - AssessmentLU_parcelNew York State property type classification nameCity of Syracuse - AssessmentLUCat_OldLegacy land use category that corresponds to the overarching NYS category, i.e. all 400s = commercial, all 300s = vacant land, etc.NAland_avLand assessed valueCity of Syracuse - Assessmenttotal_avFull assessed valueCity of Syracuse - AssessmentOwnerProperty owner name (First, Initial, Last, Suffix)City of Syracuse - AssessmentAdd1_OwnPOBoxProperty owner mailing address (PO Box)City of Syracuse - AssessmentAdd2_OwnStAddProperty owner mailing address (street number, street name, street direction)City of Syracuse - AssessmentAdd3_OwnUnitInfoProperty owner mailing address unit info (unit name, unit number)City of Syracuse - AssessmentAdd4_OwnCityStateZipProperty owner mailing address (city, state or country, zip code)City of Syracuse - AssessmentFRONTFront footage for square or rectangular shaped lots and the effective front feet on irregularly shaped lots in feetCity of Syracuse - AssessmentDEPTHActual depth of rectangular shaped lots in feet (irregular lots are usually measured in acres or square feet)City of Syracuse - AssessmentACRESNumber of acres (where values were 0, acreage calculated as FRONT*DEPTH)/43560)City of Syracuse - Assessmentyr_builtYear 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 - Assessmentn_ResUnitsNumber of residential unitsNA - Calculated fieldIPSVacantIs it a vacant structure? ("Commercial" or "Residential" = Yes; null = No)City of Syracuse - Division of Code EnforcementIPS_ConditionProperty Condition Score assigned to vacant properties by housing inspectors during routine vacant inspections (1 = Worst; 5 = Best)City of Syracuse - Division of Code EnforcementNREligibleNational Register of Historic Places Eligible ("NR Eligible (SHPO)," or "NR Listed")City of Syracuse - Neighborhood and Business DevelopmentLPSSLocally Protected Site Status ("Eligible/Architecturally Significant" or "Local Protected Site or Local District")City of Syracuse - Neighborhood and Business DevelopmentWTR_ACTIVEWater activity code ("I" = Inactive; "A" = Active)City of Syracuse - WaterRNIIs property located in Resurgent Neighborhood Initiative (RNI) Area? (1 = Yes; 0 = No)City of Syracuse - Neighborhood and Business DevelopmentDPW_QuadGeographic 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 WorksTNT_NAMETNT Sector property is located inCity of Syracuse - Neighborhood and Business DevelopmentNHOODCity NeighborhoodSyracuse-Onondaga County Planning Agency (SOCPA)NRSAIs property located in Neighborhood Revitalization Strategy Area (NRSA)? (1 = Yes; 0 = No)City of Syracuse - Neighborhood and Business DevelopmentDOCE_AreaGeographic boundary use to assign Division of Code Enforcement casesCity of Syracuse - Neighborhood and Business DevelopmentZONE_DIST_PREVFormer zoning district codeSyracuse-Onondaga County Planning Agency (SOCPA)REZONEReZone designation (adopted June 2023)City of Syracuse - Neighborhood and Business DevelopmentNew_CC_DISTCurrent Common Council District property is located inOnondaga County Board of ElectionsCTID_2020Census Tract ID (2020)U.S. Census BureauCTLAB_2020Census Tract Label (2020)U.S. Census BureauCT_2020Census Tract (2020)U.S. Census BureauSpecNhoodIs property located in a special Neighborhood historic preservation district? (1 = Yes; 0 or null = No)Syracuse-Onondaga County Planning Agency (SOCPA)InPDIs property located in preservation district? (1 = Yes; 0 or null = No)Syracuse-Onondaga County Planning Agency (SOCPA)PDNAMEPreservation District nameSyracuse-Onondaga County Planning Agency (SOCPA)ELECT_DISTElection district numberOnondaga County Board of ElectionsCITY_WARDCity ward numberOnondaga County Board of ElectionsCOUNTY_LEGOnondaga County Legislative District number (as of Dec 2022)Onondaga County Board of ElectionsNYS_ASSEMBNew York State Assembly District number (as of Dec 2022)Onondaga County Board of ElectionsNYS_SENATENew York State Senate District number (as of Dec 2022)Onondaga County Board of ElectionsUS_CONGRUnited States Congressional District numberOnondaga County Board of Elections

description: Election Districts and Precincts dataset current as of 2013. Brown County maintains County Supervisor and Voting Ward map layers..; abstract: Election Districts and Precincts dataset current as of 2013. Brown County maintains County Supervisor and Voting Ward map layers..

Attributes (Fields) Defined:Site Name: A name for the site. Each parcel is part of a site. Sites are an assemblage of one or more parcels that generally share geographic proximity and are marketed together as a unit. Many sites are just one parcel, but when they are more than one parcel, the parcel name (above) reflects this. Parcels within a site will share the same basic name, but be differentiated by a "#1", "#2", "#3", etc. appended to the end of the parcel name. The site name is the parcel name without the numbering at the end. In this way, in ArcGIS, a dissolve on the site name field can be run to produce an analysis by site, instead of by parcel.Alternate Site Names: Names that have been commonly used for the site, beyond the name specified in the "Site Name" field.Address: An address for a site shared by all parcels that comprise a site. This is derived from one of the parcel addresses for parcels that comprise the site, or from the addresses assigned by Public Works within a parcel, as can be seen in AMANDA or the PED Staff Map. If all parcel addresses have a street number of "0" because they are vacant, this field is to include a rough description of where the site is located in the city.Alternate Site Addresses: Additional addresses used to describe the site. This is derived from one of the parcel addresses for parcels that comprise the site. Ward: The Ward in which the site is located. This field is updated every ten years to reflect changes to Ward boundaries due to redistricting. CHOICES: 1 • 2 • 3 • 4 • 5 • 6 • 7Planning District: The number of the Planning District in which the Site is located. The City is divided into seventeen planning districts, each served by a city-funded and city-recognized District Council. CHOICES: 1 • 2 • 3 • 4 • 5 • 6 • 7 • 8 • 9 • 10 • 11 • 12 • 13 • 14 • 15 • 16 • 17General Description: A general description of the site, its history, current circumstances, and anything else of a summary nature that would not easily fit in other fields.Classification: This is the core means of classifying HRA-owned properties, the way the sites are marketed or not marketed, and the HRA's intended destiny for the parcels. CHOICES: Commercial - Pending Sale: Properties that are generally zoned to allow a range of commercial uses, and currently have an active offer, option, or tentative developer status.Commercial - Sold: Properties that were generally zoned to allow a range of commercial uses when last owned by the HRA, were previously owned by the HRA but that have been sold, and where the HRA retains no ownership interest.Commercial - Vacant Land: Properties that are generally zoned to allow a range of commerical uses, and have no known building or other structure.Commercial - with Building(s): Properties that are generally zoned to allow a range of commercial uses, and contain a building or other structure.Long-Term Hold: Properties that, per contractual obligations, or for other reasons, are expected to be held by the City of Saint Paul for many years, and not generally available for purchase.Long-Term Hold - Parking: Properties that are expected to be held by the City of Saint Paul for many years as parking facilities, and are not generally available for purchaseResidential - Pending Sale: Properties that are generally zoned to allow mainly residential uses, and currently have an active offer, option, or tentative developer status.Residential - Sold: Properties that were generally zoned to allow mainly residential uses when last owned by the HRA, that were previously owned by the HRA but that have been sold, and where the HRA retains no ownership interest.Residential - Vacant Land: Properties that are generally zoned to allow mainly residential uses, and have no known building or other structure.Residential - With Building(s): Properties that are generally zoned to allow mainly residential uses, and contain a building or other structure.Transfer to Other Ownership: Properties that are intended for conveyance to other ownership, such as parkland that is ultimately intended to be conveyed to the Department of Parks & Recreation, or right-of-way that most appropriately would be held by the Department of Public Works.Current Project Manager: The name of the staff responsible for managing the parcel and its future. CHOICES: Names of PED staff.SharePoint Link: A link to SharePoint storage for files related to this specific site.CharacteristicsCharacteristics - Land Assembly Considerations: Are there special considerations that apply to this site around land assembly? CHOICES: Yes • No.Characteristics - Land Assembly Considerations - Challenges & Resolutions: A description of challenges and potential resolutions around land assembly.Characteristics - Title Type: A description of the type of legal title document(s) that apply to the site. A site may have multiple title documents because it can be comprised of multiple parcels. CHOICES: Abstract • Abstract & Unknown • Torrens • Torrens & Unknown • UnknownCharacteristics - Title Issues: Are there concerns with establishing appropriate title to the project? CHOICES: Yes • NoCharacteristics - Title Challenges and Resolutions: A description of the challenges and potential resolutions around title issues.Characteristics - Estimated Market Value - Tax Year: The year for which the estimated market values (EMVs) shown in subsequent fields is used to calculate the site's total tax liability.Characteristics - Estimated Market Value - EMV Year: The year to which the estimated market values (EMVs) shown in subsequent fields applied as a representation of the site's value.Characteristics - Estimated Market Value - Land: The estimated market value (EMV) of the site's land, as determined by the Ramsey County Assessor's office, and derived from the Ramsey County Parcel Service. The Site EMV Land is obtained by adding together the individual EMV Land values for each parcel within the site. This is updated at least once per year in order to stay reasonably current with any data updates.Characteristics - Estimated Market Value - Building: The estimated market value (EMV) of the site's built structure(s), as determined by the Ramsey County Assessor's office, and derived from the Ramsey County Parcel Service. The Site EMV Building is obtained by adding together the individual EMV Building values for each parcel within the site. This is updated at least once per year in order to stay reasonably current with any data updates.Characteristics - Estimated Market Value - Total: The estimated market value (EMV) of the site's land and built structure(s), added together, as determined by the Ramsey County Assessor's office and derived from the Ramsey County Parcel Service. The Site EMV Total is obtained by adding together the individual EMV Total values for each parcel within the site. This is updated at least once per year in order to stay reasonably current with any data updates.Characteristics - Estimated Market Value - Challenges & Resolutions: A description of challenges and potential resolutions around the site's estimated market value.Characteristics - Access to Site - Support for Redevelopment: Are there issues with site accessibility? CHOICES: Yes • NoCharacteristics - Access to Site - Challenges & Resolutions: A description of challenges and potential resolutions around how site access inhibits redevelopment.Characteristics - Dimensions - Acres: The acreage of the site, as derived from the parcel geometry in GIS.Characteristics - Dimensions - Maximum Depth: The maximum depth of the site(generally measured back perpendicular from the primary street frontage).Characteristics - Dimensions - Maximum Width: The maximum width of the site (generally measured as the distance parallel to the primary street frontage).Characteristics - Dimensions - Rectangular: Is the site generally rectangular in shape? CHOICES: Yes • NoCharacteristics - Dimensions - Challenges and Resolutions: A description of challenges and potential resolutions around how site dimensions may inhibit redevelopment.Characteristics - Existing Buildings - Total Square Feet: The total square footage of the existing building(s) on the site.Characteristics - Existing Buildings - Footprint Square Feet: The building footprint square footage of the existing building(s) on the site.Characteristics - Existing Buildings - Challenges & Resolutions: A description of challenges and potential resolutions around existing buildings on the site.Characteristics - Uses - Current Use: A description of the current use on the site's parcel(s) pulled from the "LandUseCodeDescription" in the parcel feature class of the parcels that are part of the site.Characteristics - Uses - Neighboring Uses: A description of the current use directly adjacent to the site's parcel(s) pulled from the "LandUseCodeDescription" in the parcel feature class of the parcels that are part of the site.Characteristics - Uses - Restrictions: A description of any use restrictions applicable to the site upon sale.Characteristics - Uses - Funds Used: A description of the funds used and amounts on the site for acquisition and other purposes. The date on which this analysis is valid is to be denoted within the narrative description. This field is a stopgap measure until we develop better reporting mechanisms from Quickbooks and/or Infor that would more optimally pull live data from these systems of record.Characteristics - Amount of CDBG Used: The total amount of CDBG funding that has been used by the HRA on the site(which should also be accounted for in the prior field). This field is a stopgap measure until we develop better reporting mechanisms from Quickbooks and/or Infor that would more optimally pull live data from these systems of record.Characteristics - Uses - Challenges & Resolutions: A description of challenges and potential resolutions related to the existing use of the

Field DefinitionsPIN13 digit tax ID for parcelANUMBERAddress numberANUMBERSUFAddress number suffixST_PRE_DIRStreet direction that comes before street nameST_NAMEStreet nameST_TYPEType of street (Ave, St, Ln etc.)ST_POST_DIRStreet direction that comes after the street nameAUNITUnit number of addressZIPCODEPostal codeFORMATTED_ADDRESSFull mailing addressOWNERNAMEName of property ownerTAXPAYER1Taxpayer nameTAXPAYER2Taxpayer name and addressTAXPAYER3Taxpayer name and address continuedTAXPAYER4Taxpayer name and address continuedASSESSMENT_YEARYear for which the property value is assessedTAX_YEARYear for which the property taxes are duePLATPlat numberPROPERTY_TYPEType of propertyMAIN_PTProperty type on primary use of parcelSUB_PT1Property type of secondary use of parcelSUB_PT2Property type of tertiary use of parcelSUB_PT3Property type of quaternary use of parcelMULTIPLE_USESIndicates whether parcel has multiple uses or notTAX_EXEMPTIndicates whether parcel is tax exemptEXEMPTCD1Exempt code for first tax exempt portionEXEMPTCD2Exempt code for second tax exempt portionEXEMPTCD3Exempt code for third tax exempt portionEXEMPTCD4Exempt code for fourth tax exempt portionPARCEL_AREA_SQFTLand area of parcel in square feetXX coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)YY coordinate of parcel centroid (uses NAD 83 HARN Hennepin County coordinate system)NEIGHBORHOODName of neighborhood the property is inCOMMUNITYName of community the property is inWARDName of ward the property is inZONINGName of zoning district the property is inLANDUSEProperty's land use designationLANDVALUEProperty's assessed land value as of January 2 of its assessment yearBUILDINGVALUEProperty's assessed building value as of January 2 of its assessment yearTOTALVALUEProperty's total assessed value as of January 2 of its assessment yearEXEMPTSTATUSIndicates the status of property (if exempt)HOMESTEADIndicates whether property is homesteadedBLDG_IDUnique identifier for buildingsBUILDINGUSEUse classification of buildingYEARBUILTYear that the building was constructedBELOWGROUNDAREATotal square footage below gradeABOVEGROUNDAREATotal square footage above gradeNUM_STORIESNumber of stories in buildingGARAGE_PRESENTIndicates whether property has a garagePRIMARYHEATINGPrimary type of heating in buildingCONSTRUCTIONTYPEStyle of constructionEXTERIORTYPEExterior finish of buildingROOFStyle of roofTOTAL_UNITSTotal number of unitsFIREPLACESNumber of fireplacesBATHROOMSNumber of bathroomsBEDROOMSNumber of bedrooms

The map shows the targeted number of households by sub-county and ward for the planned and ongoing multi-purpose cash program implemented by the ASAL Humanitarian Network in reponse to the 2021 drought in the ASAL counties in Kenya.

DATA LAYER DETAILS: Legislative District Boundaries for Sullivan County, NY. This data layer includes all current Sullivan County legislative district boundaries effective for the 2023 voting period.

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.

In November of 2006 Napa County voters approved Measure I establishing the Napa County Regional Park and Open Space District. The District is authorized to protect and preserve natural areas, wildlife habitat and other open space resources, and to plan, improve and operate a system of public parks, trails, outdoor recreational facilities, and outdoor science and conservation education programs. Its jurisdiction includes all of Napa County.The District is governed by a Board of Directors whose members are directly elected by the public in each of five wards. Ward boundaries coincide with the County’s Board of Supervisors’ districts. Ward boundaries and a full map of all District Wards can be found here.Funding for the District currently comes from a mix of program income and a share of the County of Napa’s transient occupancy tax as set by the Board of Supervisors. The District is also empowered to obtain grants, accept gifts, and collect fees for services provided. Subject to voter approval, the District is authorized to raise revenues through some types of property assessments and taxes.The District has no power to regulate private land use, is subject to all applicable city and county regulations, and may only acquire property from willing sellers.For more information about our work, please contact us here. A full board and staff directory is available here.

The Onondaga County Election District geographic dataset was last updated by the Syracuse-Onondaga County Planning Agency (SOCPA) in February, 2013. The shapefile consists of polygon features representing election districts in Onondaga County as determined by the Onondaga County Board of Elections (BOE). This dataset was created by extracting features from the Onondaga County digital street file for use as election district boundaries.The attribute included in this shapefile is the city ward number.

Pursuant to R.C. 731.06 (C), which permits the legislative authority of a city to redivide the city into wards at any time, the Long Range and Strategic Planning Committee of Council voted 3-0 Wednesday to forward the redistricting map as prepared by Jason Gillow to the law director for preparation of an ordinance so that it can be forwarded to city council with a recommendation for passage.

The Committee would like to present the ordinance to Council for first consideration on September 18.

The Committee made no changes to the map, deciding to leave the triangular shaped census block bounded by Mound, Main and Eastmoor Ave. in the second ward. The group previously had slotted it for the Fourth Ward. It was noted that the total population was slightly different in the latest iteration. The committee felt that, barring a major discrepancy in total population from the original data set (13,672) to the revised data set (13,542), that the population in each ward is substantially balanced (i.e., +/-

East Bay Regional Park District with ward boundaries, within the extent of Alameda County; boundaries have been updated to show 2011-2012 redistricting changes. Boundaries represent voting districts (i.e., district designation for each address) and therefore may align with parcel boundaries in cases where parcels (and sometimes residences) are divided by the true city/district boundary.

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

DATA LAYER DETAILS: Electoral Village Boundaries for Sullivan County, NY. This data layer includes all current Sullivan County electoral village boundaries effective as of the 2023 voting period.

DATA COLLECTION DETAILS: Electoral Boundaries for Sullivan County, NY. This data collection includes all current Sullivan County electoral boundaries effective as of the 2024 voting period. Data includes:Electoral Municipalities (Towns)Electoral VillagesLegislative DistrictsElection DistrictsWards

Wisconsin municipal ward data collected in January 2025 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 GIS Hub website.This data has been collected with the LTSB GeoData Collector.*with the exception of years ending in “01” where data collection will align closer to typical redistricting timelines of March and October 15.

This item is in mature support and is no longer updated. Available for historical reference only. This dataset contains polygons representing Election District 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.