The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. A total of 39 classes of land cover were mapped on Fire Island and the William Floyd Estate (Table 6.). These are comprised of 24 types mapped to NVCS association, 1 complex of 2 NVCS alliances, and 14 non-NVCS classes (Figure 5a-d.). Four associations were identified on Fire Island and the William Floyd Estate but do not appear on the map due to their rarity, small relative size, and/or difficulties in identifying them with aerial photography. These types were Oligohaline Marsh, Brackish Marsh, Salt Panne, and North Atlantic Upper Ocean Beach.

ArcGIS and QGIS map packages, with ESRI shapefiles for the DSM2 Model Grid. These are not finalized products. Locations in these shapefiles are approximate.

Monitoring Stations - shapefile with approximate locations of monitoring stations.

DSM2 Grid 2025-05-28 Historical

FC_2023.01

DSM2 v8.2.0, calibrated version:

• dsm2_8_2_grid_map_calibrated.mpkx - ArcGIS Pro map package containing all layers and symbology for the calibrated grid map.
• dsm2_8_2_grid_map_calibrated.mpk - ArcGIS Desktop map package containing all layers and symbology for the calibrated grid map.
• dsm2_8_2_0_calibrated_grid_map_qgis.zip - QGIS map package containing all layers and symbology for the calibrated grid map.
• dsm2_8_2_0_calibrated_gridmap_shapefiles.zip - A zip file containing all the shapefiles used in the above map packages:
• dsm2_8_2_0_calibrated_channels_centerlines - channel centerlines, follwing the path of CSDP centerlines
• dsm2_8_2_0_calibrated_network_channels - channels represented by straight line segments which are connected the upstream and downstream nodes
• dsm2_8_2_0_calibrated_nodes - DSM2 nodes
• dsm2_8_2_0_calibrated_dcd_only_nodes - Nodes that are only used by DCD
• dsm2_8_2_0_calibrated_and_dcd_nodes - Nodes that are shared by DSM2 and DCD
• dsm2_8_2_0_calibrated_and_smcd_nodes - Nodes that are shared by DSM2 and SMCD
• dsm2_8_2_0_calibrated_gates_actual_loc - The approximate actual locations of each gate in DSM2
• dsm2_8_2_0_calibrated_gates_grid_loc - The locations of each gate in the DSM2 model grid
• dsm2_8_2_0_calibrated_reservoirs - The approximate locations of the reservoirs in DSM2
• dsm2_8_2_0_calibrated_reservoir_connections - Lines showing connections from reservoirs to nodes in DSM2

DSM2 v8.2.1, historical version:

• DSM2 v8.2.1, historical version grid map release notes (PDF), updated 7/12/2022
• DSM2 v8.2.1, historical version grid map, single zoom level (PDF)
• DSM2 v8.2.1, historical version grid map, multiple zoom levels (PDF) - PDF grid map designed to be printed on 3 foot wide plotter paper.
• DSM2 v8.2.1, historical version map package for ArcGIS Desktop: A map package for ArcGIS Desktop containing the grid map layers with symbology.
• DSM2 v8.2.1, historical version grid map shapefiles (zip): A zip file containing the shapefiles used in the grid map.

Change Log

7/12/2022: The document "DSM2 v8.2.1, historical version grid map release notes (PDF)" was corrected by removing section 4.4, which incorrectly stated that the grid included channels 710-714, representing the Toe Drain, and that the Yolo Flyway restoration area was included.

The list of study sites, meteorological stations and locations of interest that are shown on the Bonanza Creek Long Term Ecological Research site (BNZ LTER) internet map server (IMS, available at http://www.lter.uaf.edu/ims_intro.cfm) is generated from the LTER study sites database. The information is converted into a shapefile and posted to the IMS. Some study sites shown on the main LTER website will not appear on the IMS because they do not have location coordinates. In all cases the most up-to-date information will be found on the (study sites website ).

The spatial information represented on the IMS is available to the public according to the restrictions outlined in the LTER data policy. The dataset represented here consists of the map layers shown on the IMS. The information consists of shapefiles in Environmental Systems Research Institute (ESRI) format. Users of this dataset should be aware that the contents are dynamic. Portions of the information shown on the IMS are derived from the Bonanza Creek LTER databank and are constantly being updated.

Special Service Areas (SSA) boundaries in Chicago. The Special Service Area program is a mechanism used to fund expanded services and programs through a localized property tax levy within contiguous industrial, commercial and residential areas. The enhanced services and programs are in addition to services and programs currently provided through the city. SSA-funded projects could include, but are not limited to, security services, area marketing and advertising assistance, promotional activities such as parades and festivals, or any variety of small scale capital improvements that could be supported through a modest property tax levy. The data can be viewed on the Chicago Data Portal with a web browser. However, to view or use the files outside of a web browser, you will need to use compression software and special GIS software, such as ESRI ArcGIS (shapefile) or Google Earth (KML or KMZ).

This data set provides four related spatial data products for four study areas across the Brazilian Amazon: Manaus, Amazonas; Tapajos National Forest, Para Western (Santarem); Rio Branco, Acre; and Rondonia, Rondonia. Products include vector data showing (1) roads, (2) rivers, and (3) hypsography and (4) digital elevation model (DEM) images that were encoded from the hypsography vectors. There are 15 data files with this data set which includes 12 compressed *.zip files containing ArcInfo shape files and 3 GeoTIFFS.

This data set contains vector data showing roads, rivers, and hypsography for each study area in ESRI ArcGIS shapefile format. The vectors were hand-digitized by the Images Company in Brazil from paper maps produced by the Brazilian government. Depending on the scale of the original maps, the digitization errors vary. For some maps, some vectors are missing. Data were manually checked for duplicate or extra vectors. These data sets were derived from several map sheets produced from aerial coverages dating from 1974 to 1978.

The DEM images were encoded from the hypsography vectors and are provided in GeoTIFF format. The attribute value associated with each line and point in the vector segment is encoded into the image channel; the image channel is then filled in by interpolating image data between encoded vector data. For each DEM: 1 image channel with pixel resolution = 25m x 25m. DEM images are provided for Manaus, Tapajos National Forest, and Rondonia. The files for Rio Branco were unusable due to a documentation error.

DATA QUALITY STATEMENT: The Data Center has determined that there are questions about the quality of the data reported in this data set. The data set has missing or incomplete data, metadata, or other documentation that diminishes the usability of the products.

KNOWN PROBLEMS:

The data providers note that due to limited resources, these data have been neither validated nor quality-assured for general use. For that reason, extreme caution is advised when considering the use of these data.

• Any use of the derived data is not recommended because the results have not been validated.

• However, the DEM, vectors, and orthorectified SAR data (related data set) can be used if the user understands how these were produced and accepts the limitations.

OUTDATED. See the current data at https://data.cityofchicago.org/d/kjav-iyuj - Special Service Areas (SSA) boundaries in Chicago. The Special Service Area program is a mechanism used to fund expanded services and programs through a localized property tax levy within contiguous industrial, commercial and residential areas. The enhanced services and programs are in addition to services and programs currently provided through the city. SSA-funded projects could include, but are not limited to, security services, area marketing and advertising assistance, promotional activities such as parades and festivals, or any variety of small scale capital improvements that could be supported through a modest property tax levy. The data can be viewed on the Chicago Data Portal with a web browser. However, to view or use the files outside of a web browser, you will need to use compression software and special GIS software, such as ESRI ArcGIS (shapefile) or Google Earth (KML or KMZ).

Tidal Datum GIS outputsShapefiles are provided that present the approximate shore-parallel extent of tidal datums across coastal Massachusetts. These shapefiles are provided for 2030, 2050, and 2070 sea level rise scenarios. Individual shapefiles are provided for the north and south model domains for a total of 6 tidal datum shapefiles (2 model domains, 3 sea level rise scenarios). The results presented within these polygons are based upon tidal model simulations conducted using the MC-FRM, with north shapefiles created using the north model domain, and south using the south model domain. Separate polygons (zones) are provided for approximate location where MHW values vary to the nearest 0.1 ft interval. These zones are derived based on the variation in the MHW datum, and as such other datums (MHHW, MTL, MLW, and MLLW) may vary withineach segmented polygon, especially in areas of varied bathymetry. Data are presented in units of feet relative to the NAVD88 datum.These shapefiles contain the following fields: FID, Shape, Hatch, MHHW, MHW, MTL, MLW, and MLLW. The MHHW, MHW, MTL, MLW, and MLLW fields contain float type values representing the tidal datums calculated for each polygon rounded to the nearest tenth of a foot. The Hatch field contains a binary value (0 or 1), with 1 representing zones of uncertainty for tidal datums. These uncertain zones are either dynamic in terms of geomorphology or are restricted by smaller anthropogenic features (culverts, tide gates, etc.) that were not fully resolved in the MC-FRM. Zones with a 1 Hatch value may or may not contain tidal datum information. It is recommended that care be taken when utilizing the tidal benchmark information in these hatched zones and site-specific data observations (tide data) are recommended to verify the values in these areas. If datum information is not available 9999 values are located in the datum fields for that polygon. The FID and Shape fields contain an ID number and shape type contained in each polygon.The shapefiles provided are not intended to represent a spatial extent of the tidal benchmark (i.e., they do not present the geospatial location of water level). Rather, these shapefiles provide the tidal benchmark values that should be applied over each of the geospatial zones.

Buildings_BACI

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   Buildings, structures, ruins, storage tanks, silos, water towers, Baltimore City Planimetric, Biophysical Resources, Land, Socio-Economic Resources, Capital




   Summary


   This data was created as a landbase feature as part of the planimetric data.


   Description


   This dataset represents photogrammetrically captured Building footprints => 100sq. ft. including storage tanks, silos, water towers, power plants, substations, and structures under construction and ruins. Feature capture rules:


   Buildings - Outline edge of roofline. All buildings shall be captured as polygons. In commercial areas especially, it is important that the plotted building represent the face of the building where it meets the sidewalk. Polygons shall be created for the outer boundary of the building when a partywall exists. Does not include sheds and small temporary structures. Attached garages shall be represented as part of the building structure. Large structures such as stadiums shall also be represented.

   Structures under construction or demolition - Delineate the rooflines of all buildings under construction as interpreted from aerial photography. If roofline is not visible compile visible foundation or walls

   Ruins - Delineate old overgrown areas of old structures that have been demolished or are in disrepair. Original data will be reclassified to define as separate subtype.

   Storage tanks, silos, and water towers - Outlines of all storage tanks, silos and water towers. . Original data will be reclassified to define as separate subtype.

   Power plants and substations - Outline of power plant and substation structure. . Original data will be reclassified to define as separate subtype.


   Credits

   There are no credits for this item.


   Use limitations


   Every reasonable effort has been made to ensure the accuracy of these data. The City of Baltimore, Maryland makes no representations nor warranties, either express or implied, regarding the accuracy of this information or its suitability for any particular purpose whatsoever. The data is licensed "as is" and the City of Baltimore will not be liable for its use or misuse by any party. Reliance of these data is at the risk of the user.


   Extent



   West -76.714715  East -76.525355 

   North 39.375162  South 39.193953 




   Scale Range

   There is no scale range for this item.

PROW_2003_BACI

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   Biophysical Resources, Land, BES, PROW, Urparian, Public Right-of-Way, Roads




   Summary


   BES research


   Description


   Public Right-of-Way (PROW) land in Baltimore City (previously referred to as the "urparian" area). PROW land generally consists of all roads and rights of way along roads. This area was delineated using Baltimore City parcel data by identifying all "non-parcel" areas. A cursory analysis of the PROW land indicated that errors of omission were present due to insufficient parcel data. These errors were present in the following census block groups: 245102503031, 245102503032, 245102503033. The parcel data used in this dataset is current as of June 2001.


   Credits


   UVM Spatial Analysis Lab


   Use limitations


   BES use only.


   Extent



   West -76.713430  East -76.526155 

   North 39.374452  South 39.196871 




   Scale Range

   There is no scale range for this item.

This feature service is derived from the Esri "United States Zip Code Boundaries" layer, queried to only CA data.For the original data see: https://esri.maps.arcgis.com/home/item.html?id=5f31109b46d541da86119bd4cf213848Published by the California Department of Technology Geographic Information Services Team.The GIS Team can be reached at ODSdataservices@state.ca.gov.U.S. ZIP Code Boundaries represents five-digit ZIP Code areas used by the U.S. Postal Service to deliver mail more effectively. The first digit of a five-digit ZIP Code divides the United States into 10 large groups of states (or equivalent areas) numbered from 0 in the Northeast to 9 in the far West. Within these areas, each state is divided into an average of 10 smaller geographical areas, identified by the second and third digits. These digits, in conjunction with the first digit, represent a Sectional Center Facility (SCF) or a mail processing facility area. The fourth and fifth digits identify a post office, station, branch or local delivery area.As of the time this layer was published, in January 2025, Esri's boundaries are sourced from TomTom (June 2024) and the 2023 population estimates are from Esri Demographics. Esri updates its layer annually and those changes will immediately be reflected in this layer. Note that, because this layer passes through Esri's data, if you want to know the true date of the underlying data, click through to Esri's original source data and look at their metadata for more information on updates.Cautions about using Zip Code boundary dataZip code boundaries have three characteristics you should be aware of before using them:Zip code boundaries change, in ways small and large - these are not a stable analysis unit. Data you received keyed to zip codes may have used an earlier and very different boundary for your zip codes of interest.Historically, the United States Postal Service has not published zip code boundaries, and instead, boundary datasets are compiled by third party vendors from address data. That means that the boundary data are not authoritative, and any data you have keyed to zip codes may use a different, vendor-specific method for generating boundaries from the data here.Zip codes are designed to optimize mail delivery, not social, environmental, or demographic characteristics. Analysis using zip codes is subject to create issues with the Modifiable Areal Unit Problem that will bias any results because your units of analysis aren't designed for the data being studied.As of early 2025, USPS appears to be in the process of releasing boundaries, which will at least provide an authoritative source, but because of the other factors above, we do not recommend these boundaries for many use cases. If you are using these for anything other than mailing purposes, we recommend reconsideration. We provide the boundaries as a convenience, knowing people are looking for them, in order to ensure that up-to-date boundaries are available.

This data set contains a variety of data and products from the National Interagency Fire Center (NIFC) ftp site for fires that were flown by the WE-CAN and/or BB-FLUX field projects. The data and products can vary by day and fire, but typically include GIS (Geographic Information Systems) data and products as well as fire map products from the Forest Service National Infrared Operations. There are also occasional photographs and other documents sometimes included. A small number of the documents are password protected (we do not have the password). The GIS data are typically in ArcGIS shapefiles and most of the documents are in PDF format.

Inventory of Historic Properties for Howard County. The Maryland Inventory of Historic Properties vector layers are depictions of the approximate locations of historic structures, monuments, districts, and other properties that are listed on the Maryland Inventory of Historic Properties. No attribute information is available for this dataset.

   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.


   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Polygons depict properties in Maryland listed on the National Register of Historic Places, a listing maintained by the U.S. Department of Interior. The number of National Register listings in Maryland as of March 21, 2000 is 1230. Of the 1,230 listings, the following were not digitized: Queen City Hotel in Allegany County, demolished; and Steamship Nobska, which was moved to Massachusetts; Timonium Mansion in Baltimore county,demolished; the Messina Archeological Site in Cecil County, delisted; 100 Hopkins Place in Baltimore City, delisted; and the William Costen House in Somerset County, delisted.

   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.


   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Inventory of Historic Properties for Carroll County. The Maryland Inventory of Historic Properties vector layers are depictions of the approximate locations of historic structures, monuments, districts, and other properties that are listed on the Maryland Inventory of Historic Properties. No attribute information is available for this dataset.

   This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase.


   The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive.


   The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders.


   Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The "Map Imager Layer - Administrative Boundaries" is a Map Image Layer of Administrative Boundaries. It has been designed specifically for use in ArcGIS Online (and will not directly work in ArcMap or ArcPro). This data has been modified from the original source data to serve a specific business purpose. This data is for cartographic purposes only.The Administrative Boundaries Data Group contains the following layers: Populated Places (USGS)US Census Urbanized Areas and Urban Clusters (USCB)US Census Minor Civil Divisions (USCB)PLSS Townships (MnDNR, MnGeo)Counties (USCB)American Indian, Alaska Native, Native Hawaiian (AIANNH) Areas (USCB)States (USCB)Countries (MPCA)These datasets have not been optimized for fast display (but rather they maintain their original shape/precision), therefore it is recommend that filtering is used to show only the features of interest. For more information about using filters please see "Work with map layers: Apply Filters": https://doc.arcgis.com/en/arcgis-online/create-maps/apply-filters.htmFor additional information about the Administrative Boundary Dataset please see:United States Census Bureau TIGER/Line Shapefiles and TIGER/Line Files Technical Documentation: https://www.census.gov/programs-surveys/geography/technical-documentation/complete-technical-documentation/tiger-geo-line.htmlUnited States Census Bureau Census Mapping Files: https://www.census.gov/geographies/mapping-files.htmlUnited States Census Bureau TIGER/Line Shapefiles: https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html and https://www.census.gov/cgi-bin/geo/shapefiles/index.php

These line shapefiles trace apparent topographic and air-photo lineaments in various counties in Colorado. It was made in order to identify possible fault and fracture systems that might be conduits for geothermal fluids, as part of a DOE reconnaissance geothermal exploration program.

Geothermal fluids commonly utilize fault and fractures in competent rocks as conduits for fluid flow. Geothermal exploration involves finding areas of high near-surface temperature gradients, along with a suitable "plumbing system" that can provide the necessary permeability. Geothermal power plants can sometimes be built where temperature and flow rates are high.

This line shapefile is an attempt to use desktop GIS to delineate possible faults and fracture orientations and locations in highly prospective areas prior to an initial site visit. Geochemical sampling and geologic mapping could then be centered around these possible faults and fractures.

To do this, georeferenced topographic maps and aerial photographs were utilized in an existing GIS, using ESRI ArcMap 10.0 software. The USA_Topo_Maps and World_Imagery map layers were chosen from the GIS Server at server.arcgisonline.com, using a UTM Zone 13 NAD27 projection. This line shapefile was then constructed over that which appeared to be through-going structural lineaments in both the aerial photographs and topographic layers, taking care to avoid manmade features such as roads, fence lines, and utility right-of-ways. Still, it is unknown what actual features these lineaments, if they exist, represent.

Although the shapefiles are arranged by county, not all areas within any county have been examined for lineaments. Work was focused on either satellite thermal infrared anomalies, known hot springs or wells, or other evidence of geothermal systems. Finally, lineaments may be displaced somewhat from their actual location, due to such factors as shadow effects with low sun angles in the aerial photographs.

Credits: These lineament shapefile was created by Geothermal Development Associates, as part of a geothermal geologic reconnaissance performed by Flint Geothermal, LLC, of Denver Colorado.

Use Limitation: These shapefiles were constructed as an aid to geothermal exploration in preparation for a site visit for field checking. We make no claims as to the existence of the lineaments, their location, orientation, and/or nature.

This shapefile contains tax parcel polygons for Eaton County, Michigan, USA. Because tax parcel information changes daily, this shapefile contains only geometry, the parcel identifier and a URL link to the current information for each parcel. Parcel geometries are not survey-grade and should not be used to make important decisions like where to build a structure or install a fence. In their current form, they are only useful in spatial terms for getting an inexact idea of where a parcel is located. If you need to know exactly where a property line falls, please consult a certified land surveyor. Parcel geometries will be updated either annually or bi-annually. New splits and combinations are typically not visible in the parcel geometry until changes become official via Board of Review in the following April.

The IPUMS National Historical Geographic Information System (NHGIS) provides free online access to summary statistics and GIS files for U.S. censuses and other nationwide surveys from 1790 through the present. NHGIS boundary files are derived primarily from the U.S. Census Bureau's TIGER/Line files with numerous additions to represent historical (1790-1980) boundaries that do not appear in TIGER/Line files. For more recent boundary files (1990 or later), NHGIS typically makes only a few key changes to the TIGER/Line source: (1) we merge files that are available only for individual states or counties to produce new nationwide or statewide files, (2) we project the data into Esri's USA Contiguous Albers Equal Area Conic Projected Coordinate System, (3) we add a GISJOIN attribute field, which supplies standard identifiers that correspond to the GISJOIN identifiers in NHGIS data tables, (4) we rename files to use the NHGIS naming style and geographic-level codes, (5) we add NHGIS-specific metadata, and (6) most substantially, we erase coastal water areas to produce polygons that terminate at the U.S. coasts and Great Lakes shores.NHGIS derived this shapefile from the U.S. Census Bureau's 2023 TIGER/Line Shapefiles.

Contains:World HillshadeWorld Street Map (with Relief) - Base LayerLarge Scale International Boundaries (v11.3)World Street Map (with Relief) - LabelsDoS Country Labels DoS Country LabelsCountry (admin 0) labels that have been vetted for compliance with foreign policy and legal requirements. These labels are part of the US Federal Government Basemap, which contains the borders and place names that have been vetted for compliance with foreign policy and legal requirements.Source: DoS Country Labels - Overview (arcgis.com)Large Scale International BoundariesVersion 11.3Release Date: December 19, 2023DownloadFor more information on the LSIB click here: https://geodata.state.gov/ A direct link to the data is available here: https://data.geodata.state.gov/LSIB.zipAn ISO-compliant version of the LSIB metadata (in ISO 19139 format) is here: https://geodata.state.gov/geonetwork/srv/eng/catalog.search#/metadata/3bdb81a0-c1b9-439a-a0b1-85dac30c59b2 Direct inquiries to internationalboundaries@state.govOverviewThe Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.3 (published 19 December 2023). The 11.3 release contains updates to boundary lines and data refinements enabling reuse of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control.National Geospatial Data AssetThis dataset is a National Geospatial Data Asset managed by the Department of State on behalf of the Federal Geographic Data Committee's International Boundaries Theme.DetailsSources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process involves analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground.Attribute StructureThe dataset uses thefollowing attributes:Attribute NameCC1COUNTRY1CC2COUNTRY2RANKSTATUSLABELNOTES These attributes are logically linked:Linked AttributesCC1COUNTRY1CC2COUNTRY2RANKSTATUS These attributes have external sources:Attribute NameExternal Data SourceCC1GENCCOUNTRY1DoS ListsCC2GENCCOUNTRY2DoS ListsThe eight attributes listed above describe the boundary lines contained within the LSIB dataset in both a human and machine-readable fashion. Other attributes in the release include "FID", "Shape", and "Shape_Leng" are components of the shapefile format and do not form an intrinsic part of the LSIB."CC1" and "CC2" fields are machine readable fields which contain political entity codes. These codes are derived from the Geopolitical Entities, Names, and Codes Standard (GENC) Edition 3 Update 18. The dataset uses the GENC two-character codes. The code ‘Q2’, which is not in GENC, denotes a line in the LSIB representing a boundary associated with an area not contained within the GENC standard.The "COUNTRY1" and "COUNTRY2" fields contain human-readable text corresponding to the name of the political entity. These names are names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the list of Independent States in the World and the list of Dependencies and Areas of Special Sovereignty maintained by the Department of State. To ensure the greatest compatibility, names are presented without diacritics and certain names are rendered using commonly accepted cartographic abbreviations. Names for lines associated with the code ‘Q2’ are descriptive and are not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS are names of independent states. Other names are those associated with dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user.The following fields are an intrinsic part of the LSIB dataset and do not rely on external sources:Attribute NameMandatoryContains NullsRANKYesNoSTATUSYesNoLABELNoYesNOTESNoYesNeither the "RANK" nor "STATUS" field contains null values; the "LABEL" and "NOTES" fields do.The "RANK" field is a numeric, machine-readable expression of the "STATUS" field. Collectively, these fields encode the views of the United States Government on the political status of the boundary line.Attribute NameValueRANK123STATUSInternational BoundaryOther Line of International Separation Special Line A value of "1" in the "RANK" field corresponds to an "International Boundary" value in the "STATUS" field. Values of "2" and "3" correspond to "Other Line of International Separation" and "Special Line", respectively.The "LABEL" field contains required text necessarily to describe the line segment. The "LABEL" field is used when the line segment is displayed on maps or other forms of cartographic visualizations. This includes most interactive products. The requirement to incorporate the contents of the "LABEL" field on these products is scale dependent. If a label is legible at the scale of a given static product a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field is not a line labeling field but does contain the preferred description for the three LSIB line types when lines are incorporated into a map legend. Using the "CC1", "CC2", or "RANK" fields for labeling purposes is prohibited.The "NOTES" field contains an explanation of any applicable special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, any limitations regarding the purpose of the lines, or the original source of the line. Use of the "NOTES" field for labeling purposes is prohibited.External Data SourcesGeopolitical Entities, Names, and Codes Registry: https://nsgreg.nga.mil/GENC-overview.jspU.S. Department of State List of Independent States in the World: https://www.state.gov/independent-states-in-the-world/U.S. Department of State List of Dependencies and Areas of Special Sovereignty: https://www.state.gov/dependencies-and-areas-of-special-sovereignty/The source for the U.S.—Canada international boundary (NGDAID97) is the International Boundary Commission: https://www.internationalboundarycommission.org/en/maps-coordinates/coordinates.phpThe source for the “International Boundary between the United States of America and the United States of Mexico” (NGDAID82) is the International Boundary and Water Commission: https://catalog.data.gov/dataset?q=usibwcCartographic UsageCartographic usage of the LSIB requires a visual differentiation between the three categories of boundaries. Specifically, this differentiation must be between:- International Boundaries (Rank 1);- Other Lines of International Separation (Rank 2); and- Special Lines (Rank 3).Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary.Additional cartographic information can be found in Guidance Bulletins (https://hiu.state.gov/data/cartographic_guidance_bulletins/) published by the Office of the Geographer and Global Issues.ContactDirect inquiries to internationalboundaries@state.gov.CreditsThe lines in the LSIB dataset are the product of decades of collaboration between geographers at the Department of State and the National Geospatial-Intelligence Agency with contributions from the Central Intelligence Agency and the UK Defence Geographic Centre.Attribution is welcome: U.S. Department of State, Office of the Geographer and Global Issues.Changes from Prior ReleaseThe 11.3 release is the third update in the version 11 series.This version of the LSIB contains changes and accuracy refinements for the following line segments. These changes reflect improvements in spatial accuracy derived from newly available source materials, an ongoing review process, or the publication of new treaties or agreements. Notable changes to lines include:• AFGHANISTAN / IRAN• ALBANIA / GREECE• ALBANIA / KOSOVO• ALBANIA/MONTENEGRO• ALBANIA / NORTH MACEDONIA• ALGERIA / MOROCCO• ARGENTINA / BOLIVIA• ARGENTINA / CHILE• BELARUS / POLAND• BOLIVIA / PARAGUAY• BRAZIL / GUYANA• BRAZIL / VENEZUELA• BRAZIL / French Guiana (FR.)• BRAZIL / SURINAME• CAMBODIA / LAOS• CAMBODIA / VIETNAM• CAMEROON / CHAD• CAMEROON / NIGERIA• CHINA / INDIA• CHINA / NORTH KOREA• CHINA / Aksai Chin• COLOMBIA / VENEZUELA• CONGO, DEM. REP. OF THE / UGANDA• CZECHIA / GERMANY• EGYPT / LIBYA• ESTONIA / RUSSIA• French Guiana (FR.) / SURINAME• GREECE / NORTH MACEDONIA• GUYANA / VENEZUELA• INDIA / Aksai Chin• KAZAKHSTAN / RUSSIA• KOSOVO / MONTENEGRO• KOSOVO / SERBIA• LAOS / VIETNAM• LATVIA / LITHUANIA• MEXICO / UNITED STATES• MONTENEGRO / SERBIA• MOROCCO / SPAIN• POLAND / RUSSIA• ROMANIA / UKRAINEVersions 11.0 and 11.1 were updates to boundary lines. Like this version, they also contained topology fixes, land boundary terminus refinements, and tripoint adjustments. Version 11.2 corrected a few errors in the attribute data and ensured that CC1 and CC2 attributes are in alignment with an updated version of the Geopolitical Entities, Names, and Codes (GENC) Standard, specifically Edition 3 Update 17.LayersLarge_Scale_International_BoundariesTerms of

Neighborhood boundaries in Chicago, as developed by the Office of Tourism. These boundaries are approximate and names are not official. To view or use these files, compression software and special GIS software, such as ESRI ArcGIS, is required.