Geospatial data about Whatcom County, Washington County Boundary. Export to CAD, GIS, PDF, CSV and access via API.
An interactive 3D map of Bellingham, Washington, our home in the beautiful Pacific Northwest.
This data set shows the municipal boundaries for incorporated cities in Whatcom County, Washington. The boundaries are maintained by Whatcom County, includes current annexations, and are aligned with county parcel boundaries.
This data set contains multiple polygons, both terrestrial and marine, which provides the geographic extent and boundary of Whatcom County, Washington.
The GIS data contains Whatcom County, Washington Agricultural land cover analysis and land cover shapes.
This resource is a subset of the LNWB Ch05 Land Cover Collection Resource.
Abstract: Dataset consists of a polygon coverage repesenting eight intertidal vegetation types, classified according to Nearshore Habitat Program's vegetation mapping procedures. Dataset was generalized from a more detailed raster dataset. Includes information on vegetation type, location and areal extent. Purpose: To provide resource managers, planners and other decision-makers with information about intertidal vegetation. The data were collected as part of the Nearshore Habitat Program's mandate to map the abundance and distribution of nearshore habitats in the Puget Sound for the Puget Sound Ambient Monitoring Program (PSAMP). Supplemental_Information: (1) Washington State is divided into two State Plane zones, north and south. The data set's coordinate values are reported in Washington State Plane south. (2) Imagery was acquired during periods of maximum intertidal exposure (0 -- mean lower low water or below in most areas), and times when sun angle would reduce sun glint. (3) This dataset was generalized from the raster Intertidal Vegetation Inventory 1995. The purpose of generalization was to provide a vector-based version of the dataset with a manageable file size. (4) For overview of source dataset see metadata for Intertidal Vegetation Inventory 1995, Whatcom County Area, Washington. (5) Detailed documentation of methods used to create the nearshore vegetation data set can be found in Berry & Ritter (1997). Revisions 1.0.0 References_Cited Berry, H.D. and R.A. Ritter. 1997. Puget Sound Intertidal Habitat Inventory 1995: Vegetation and Shoreline Characteristics Classification Methods. Washington State Department of Natural Resources, Aquatic Resources Division. Borstad, G. (1996). The Nearshore Habitat Inventory Project Task 7: Project Summary Memorandum. Unpublished report prepared by Borstad Associates Ltd. for Washington State Department of Natural Resources, Aquatic Resources Division, Olympia, WA-USA. The Intertidal Vegetation Inventory attribute codes can be related to classification categories using the separate IVEG_CD table (available from the distributer of this data in dbf format). The following fields are included: IVEG_NAME: description of vegetation type VALUE: numeric code identifying vegetation type classification GRID-CODE: numeric code field created by ARC/INFO identifying vegetation type classification (same as VALUE attribute) IVEG_CD: three letter code identifying vegetation type classification.
Geospatial data about Whatcom County, Washington Mobile Homes. Export to CAD, GIS, PDF, CSV and access via API.
Geospatial data about Whatcom County, Washington Pipelines. Export to CAD, GIS, PDF, CSV and access via API.
These data were automated to provide an accurate high-resolution historical shoreline of Blaine to Bellingham, WA suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://inport.nmfs.noaa.gov/inport/item/39808
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
We assessed habitat suitability for salmonids across selected tributaries upstream from three hydroelectric dams on the upper Skagit River in Whatcom County, northern Washington. We used NetMap, a commercial toolset within the ArcMap geographic information system (GIS), to analyze stream attributes based upon a synthetic stream channel network derived from digital elevation models. The GIS-derived stream attributes—including gradient, bankfull width, valley width index, elevation, and stream flow—allowed us to examine the spatial distribution and relative quality of spawning and rearing habitat for salmonids based on existing intrinsic potential (IP) models. As a first step, we created maps of potential anadromous fish distribution by identifying potential migration barriers within the synthetic stream network. Next, we applied a suite of existing IP models for steelhead, Coho, and Chinook Salmon (Oncorhynchus mykiss, O. kisutch, and O. tshawytscha, respectively) to estimate low, ...
Web Map illustration of certificated service areas described in the certification authority issued to Gas Company by Utilities and Transportation Commission (UTC). Please note that the utility service territory boundaries identified in this map might not reflect up-to-date service territory boundaries. For up-to-date service territory information, please contact the natural gas utility directly.For additional information and question pertaining to natural gas certificate coverage and issuance please, contact the UTC Energy Section, (360) 664-1301.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
Geospatial data about Whatcom County, Washington County Boundary. Export to CAD, GIS, PDF, CSV and access via API.