The Chicago Historic Resources Survey (CHRS), completed in 1995, was a decade-long research effort by the City of Chicago to analyze the historic and architectural importance of all buildings, objects, structures, and sites constructed in the city prior to 1940. During 12 years of field work and follow-up research that started in 1983, CHRS surveyors identified approximately 9,900 properties which were considered to have some historic or architectural importance. Please note that this CHRS dataset is limited and does not include the entire survey: A color-coded ranking system was used to identify historic and architectural significance relative to age, degree of external physical integrity, and level of possible significance. This dataset only includes buildings identified with the two highest color codes: "Red" and "Orange." Buildings and structures coded "Red" or "Orange" (unless designated as a Chicago Landmark or located within a Chicago Landmark District) are subject to the City of Chicago’s Demolition-Delay Ordinance (link to: http://www.cityofchicago.org/city/en/depts/dcd/supp_info/demolition_delay.html), adopted by City Council in 2003. Only buildings are included in this dataset; structures and objects such as bridges, park structures, monuments and mausoleums, generally are not represented. Likewise, garages, coach houses, and other secondary structures associated with a building may not be consistently depicted or color-coded. If an “Orange”- or “Red”-rated building was demolished after 2008, it may still appear in the map. The CHRS occasionally rated only part of a building or part of a group of joined buildings as “Orange” or “Red;” however the entire building or group of joined buildings may be incorrectly identified as “Orange” or “Red.” Additional information about the CHRS is available at www.cityofchicago.org/Landmarks/ or by contacting the Historic Preservation Division at (312) 744-3200. To view or use these shapefiles, compression software and special GIS software, such as ESRI ArcGIS or QGIS, is required. To download this file, right-click the "Download" link above and choose "Save link as."

This service was last updated September 2016. This map service draws attention to your thematic content by providing a neutral background with minimal colors, labels, and features. Only key information is represented to provide geographic context, allowing your data to come to the foreground. This light gray basemap supports any strong colors and labels for your theme, creating a visually compelling map graphic which helps your reader see the patterns intended. See these blog posts for more information on how to use this map: Esri Canvas Maps Part I: Author Beautiful Web Maps With Our New Artisan Basemap Sandwich and Esri Canvas Maps Part II: Using the Light Gray Canvas Map effectively. The map shows populated places, water, roads, urban areas, parks, building footprints, and administrative boundaries. Alignment of boundaries is a presentation of the feature provided by our data vendors and does not imply endorsement by Esri or any governing authority. This map was compiled by Esri using HERE data, DeLorme basemap layers, MapmyIndia data, and Esri basemap data. The basemap includes boundaries, city labels and outlines, and major roads worldwide from 1:591M scale to 1:72k scale. More detailed nationwide coverage is included in North America, Europe, Africa, South America and Central America, the Middle East, India, Australia, and New Zealand to be fully consistent with the World Street Map and World Topo map down to the 1:9k scale. Data for select areas of Africa and Pacific Island nations from ~1:288k to ~1:9k was sourced from OpenStreetMap contributors. Specific country list and documentation of Esri's process for including OSM data is available to view.In addition, some of the data in the World Light Gray Base map service has been contributed by the GIS community. You can contribute your data to this service and have it served by Esri. For details, see the Community Maps Program. For details on data sources in this map service, view the list of Contributors for the World Light Gray Base map.View the coverage map below to learn more about the levels of detail:World coverage map: Shows the levels of detail throughout the world. The World Light Gray Reference is designed to be drawn on top of this map and provides selected city labels throughout the world. This web map lets you view the Light Gray Base with the Reference service drawn on top. This sample web map contains several examples of thematic content in the light gray canvas basemap with its reference overlay. Note: This map service is not supported in ArcGIS for Desktop 9.3.1 or earlier because it uses the mixed format cache format. Scale Range: 1:591,657,528 down to 1:9,028Coordinate System: Web Mercator Auxiliary Sphere (WKID 102100)Tiling Scheme: Web Mercator Auxiliary SphereMap Service Name: World_Light_Gray_Base

Important Note: This item is in mature support as of July 2021. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version.This map layer draws attention to your thematic content by providing a neutral background with minimal colors, labels, and features. Only key information is represented to provide geographic context, allowing your data to come to the foreground. The dark gray map supports bright colors, creating a visually compelling map graphic which helps your reader see the patterns intended.The World Dark Gray Base is designed to be drawn on top of this base map and provides selected city labels throughout the world. This web map lets you view the Dark Gray Base with the Reference layer drawn on top. See this blog for more information on how to use the canvas maps: Esri Canvas Maps Part I: Author Beautiful Web Maps With Our New Artisan Basemap Sandwich. The map shows populated places, water, roads, urban areas, parks, building footprints, and administrative boundaries. Alignment of boundaries is a presentation of the feature provided by our data vendors and does not imply endorsement by Esri or any governing authority. This map was compiled by Esri using HERE data, Garmin basemap layers, and Esri basemap data. The basemap includes boundaries, administrative labels, and major roads worldwide from 1:591M scale to 1:577k scale. More detailed coverage is included in North America, Europe, Africa, South America and Central America, the Middle East, India, Australia, and New Zealand down to the 1:9k scale. Data for select areas of Africa and Pacific Island nations from ~1:288k to ~1:9k was sourced from OpenStreetMap contributors. Specific country list and documentation of Esri's process for including OSM data is available to view.In addition, some of the data in the World Dark Gray Base map layer has been contributed by the GIS community. For details, see the Community Maps Program. For details on data sources in this map layer, view the list of Contributors for the World Dark Gray Base map.

Update information can be found within the layer’s attributes and in a table on the Utah Parcel Data webpage under LIR Parcels.In Spring of 2016, the Land Information Records work group, an informal committee organized by the Governor’s Office of Management and Budget’s State Planning Coordinator, produced recommendations for expanding the sharing of GIS-based parcel information. Participants in the LIR work group included representatives from county, regional, and state government, including the Utah Association of Counties (County Assessors and County Recorders), Wasatch Front Regional Council, Mountainland and Bear River AOGs, Utah League of Cities and Towns, UDOT, DNR, AGRC, the Division of Emergency Management, Blue Stakes, economic developers, and academic researchers. The LIR work group’s recommendations set the stage for voluntary sharing of additional objective/quantitative parcel GIS data, primarily around tax assessment-related information. Specifically the recommendations document establishes objectives, principles (including the role of local and state government), data content items, expected users, and a general process for data aggregation and publishing. An important realization made by the group was that ‘parcel data’ or ‘parcel record’ products have a different meaning to different users and data stewards. The LIR group focused, specifically, on defining a data sharing recommendation around a tax year parcel GIS data product, aligned with the finalization of the property tax roll by County Assessors on May 22nd of each year. The LIR recommendations do not impact the periodic sharing of basic parcel GIS data (boundary, ID, address) from the County Recorders to AGRC per 63F-1-506 (3.b.vi). Both the tax year parcel and the basic parcel GIS layers are designed for general purpose uses, and are not substitutes for researching and obtaining the most current, legal land records information on file in County records. This document, below, proposes a schedule, guidelines, and process for assembling county parcel and assessment data into an annual, statewide tax parcel GIS layer. gis.utah.gov/data/sgid-cadastre/ It is hoped that this new expanded parcel GIS layer will be put to immediate use supporting the best possible outcomes in public safety, economic development, transportation, planning, and the provision of public services. Another aim of the work group was to improve the usability of the data, through development of content guidelines and consistent metadata documentation, and the efficiency with which the data sharing is distributed.GIS Layer Boundary Geometry:GIS Format Data Files: Ideally, Tax Year Parcel data should be provided in a shapefile (please include the .shp, .shx, .dbf, .prj, and .xml component files) or file geodatabase format. An empty shapefile and file geodatabase schema are available for download at:At the request of a county, AGRC will provide technical assistance to counties to extract, transform, and load parcel and assessment information into the GIS layer format.Geographic Coverage: Tax year parcel polygons should cover the area of each county for which assessment information is created and digital parcels are available. Full coverage may not be available yet for each county. The county may provide parcels that have been adjusted to remove gaps and overlaps for administrative tax purposes or parcels that retain these expected discrepancies that take their source from the legally described boundary or the process of digital conversion. The diversity of topological approaches will be noted in the metadata.One Tax Parcel Record Per Unique Tax Notice: Some counties produce an annual tax year parcel GIS layer with one parcel polygon per tax notice. In some cases, adjacent parcel polygons that compose a single taxed property must be merged into a single polygon. This is the goal for the statewide layer but may not be possible in all counties. AGRC will provide technical support to counties, where needed, to merge GIS parcel boundaries into the best format to match with the annual assessment information.Standard Coordinate System: Parcels will be loaded into Utah’s statewide coordinate system, Universal Transverse Mercator coordinates (NAD83, Zone 12 North). However, boundaries stored in other industry standard coordinate systems will be accepted if they are both defined within the data file(s) and documented in the metadata (see below).Descriptive Attributes:Database Field/Column Definitions: The table below indicates the field names and definitions for attributes requested for each Tax Parcel Polygon record.FIELD NAME FIELD TYPE LENGTH DESCRIPTION EXAMPLE SHAPE (expected) Geometry n/a The boundary of an individual parcel or merged parcels that corresponds with a single county tax notice ex. polygon boundary in UTM NAD83 Zone 12 N or other industry standard coordinates including state plane systemsCOUNTY_NAME Text 20 - County name including spaces ex. BOX ELDERCOUNTY_ID (expected) Text 2 - County ID Number ex. Beaver = 1, Box Elder = 2, Cache = 3,..., Weber = 29ASSESSOR_SRC (expected) Text 100 - Website URL, will be to County Assessor in most all cases ex. webercounty.org/assessorBOUNDARY_SRC (expected) Text 100 - Website URL, will be to County Recorder in most all cases ex. webercounty.org/recorderDISCLAIMER (added by State) Text 50 - Disclaimer URL ex. gis.utah.gov...CURRENT_ASOF (expected) Date - Parcels current as of date ex. 01/01/2016PARCEL_ID (expected) Text 50 - County designated Unique ID number for individual parcels ex. 15034520070000PARCEL_ADD (expected, where available) Text 100 - Parcel’s street address location. Usually the address at recordation ex. 810 S 900 E #304 (example for a condo)TAXEXEMPT_TYPE (expected) Text 100 - Primary category of granted tax exemption ex. None, Religious, Government, Agriculture, Conservation Easement, Other Open Space, OtherTAX_DISTRICT (expected, where applicable) Text 10 - The coding the county uses to identify a unique combination of property tax levying entities ex. 17ATOTAL_MKT_VALUE (expected) Decimal - Total market value of parcel's land, structures, and other improvements as determined by the Assessor for the most current tax year ex. 332000LAND _MKT_VALUE (expected) Decimal - The market value of the parcel's land as determined by the Assessor for the most current tax year ex. 80600PARCEL_ACRES (expected) Decimal - Parcel size in acres ex. 20.360PROP_CLASS (expected) Text 100 - Residential, Commercial, Industrial, Mixed, Agricultural, Vacant, Open Space, Other ex. ResidentialPRIMARY_RES (expected) Text 1 - Is the property a primary residence(s): Y'(es), 'N'(o), or 'U'(nknown) ex. YHOUSING_CNT (expected, where applicable) Text 10 - Number of housing units, can be single number or range like '5-10' ex. 1SUBDIV_NAME (optional) Text 100 - Subdivision name if applicable ex. Highland Manor SubdivisionBLDG_SQFT (expected, where applicable) Integer - Square footage of primary bldg(s) ex. 2816BLDG_SQFT_INFO (expected, where applicable) Text 100 - Note for how building square footage is counted by the County ex. Only finished above and below grade areas are counted.FLOORS_CNT (expected, where applicable) Decimal - Number of floors as reported in county records ex. 2FLOORS_INFO (expected, where applicable) Text 100 - Note for how floors are counted by the County ex. Only above grade floors are countedBUILT_YR (expected, where applicable) Short - Estimated year of initial construction of primary buildings ex. 1968EFFBUILT_YR (optional, where applicable) Short - The 'effective' year built' of primary buildings that factors in updates after construction ex. 1980CONST_MATERIAL (optional, where applicable) Text 100 - Construction Material Types, Values for this field are expected to vary greatly by county ex. Wood Frame, Brick, etc Contact: Sean Fernandez, Cadastral Manager (email: sfernandez@utah.gov; office phone: 801-209-9359)