Maintaining accurate data is a concern of all GIS users. The geodatabase offers you the ability to create geographic features that represent the real world. As the real world changes, you must update these features and their attributes. When creating or updating data, you can add behavior to your features and other objects to minimize the potential for errors.After completing this course, you will be able to:Define the two types of attribute domains and discuss how they differ.Create attribute domains and use them when editing data.Create subtypes and use them when editing data.Explain the difference between an attribute domain and a subtype.

This feature contains vector lines representing the shoreline and coastal habitats of California. Line segments are classified according to the Environmental Sensitivity Index (ESI) classification system and are a compilation of the ESI data from the most recent ESI atlas publications. The ESI data includes information for three main components: shoreline habitats, sensitive biological resources, and human-use resources. This California dataset contains only the ESI shoreline data layer and is a merged set of individual ESI data sets to cover the entire California coast. For many parts of the California shoreline, the NOAA-ESI database lists several shoreline types present at a given location, described from landward to seaward. A simplified singular classification [Map_Class] was created to generalize the most dominant features of the multiple shore type attributes present in the raw data. More information can be found at the source citation at ESI Guidelines | response.restoration.noaa.gov Attributes: Line: Type of geographic feature (H: Hydrography, P: Pier, S: Shoreline) Most_sensitive: If multiple shoreline types appear in ESI classification, this field represents the highest value (most sensitive type); otherwise it is the same value as the ESI field. Shore_code: The ESI shoreline type. In many cases shorelines are ranked with multiple codes, such as "6B/3A" (listed landward to seaward). Source: Original year of ESI data. Esi_description: Concatenation of shore type descriptions (listed landward to seaward) Shoretype_1: Numeric classification for the first (most landward) ESI type. Shoretype_1_name: Physical description for the first ESI type. Shoretype_2: Numeric classification for the second ESI type. Shoretype_2_name: Physical description for the second ESI type Shoretype_3: Numeric classification for the third (most seaward) ESI type. Shoretype_3_name: Physical description for the third ESI type. Map_class: Generalized ESI shoreline type for simplified sym

The Los Angeles County Storm Drain System is a geometric network model representing the storm drain infrastructure within Los Angeles County. The long term goal of this network is to seamlessly integrate the countywide drainage infrastructure, regardless of ownership or jurisdiction. Current uses by the Department of Public Works (DPW) include asset inventory, operational maintenance, and compliance with environmental regulations.

GIS DATA DOWNLOADS: (More information is in the table below)

File geodatabase: A limited set of feature classes comprise the majority of this geometric network. These nine feature classes are available in one file geodatabase (.gdb). ArcMap versions compatible with the .gdb are 10.1 and later. Read-only access is provided by the open-source software QGIS. Instructions on opening a .gdb file are available here, and a QGIS plugin can be downloaded here.

Acronyms and Definitions (pdf) are provided to better understand terms used.

ONLINE VIEWING: Use your PC’s browser to search for drains by street address or drain name and download engineering drawings. The Web Viewer link is: https://dpw.lacounty.gov/fcd/stormdrain/

MOBILE GIS: This storm drain system can also be viewed on mobile devices as well as your PC via ArcGIS Online. (As-built plans are not available with this mobile option.)

More About these Downloads All data added or updated by Public Works is contained in nine feature classes, with definitions listed below. The file geodatabase (.gdb) download contains these eleven feature classes without network connectivity. Feature classes include attributes with unabbreviated field names and domains.

ArcMap versions compatible with the .gdb are 10.1 and later.

Feature Class Download Description

CatchBasin In .gdb Catch basins collect urban runoff from gutters

Culvert In .gdb A relatively short conduit that conveys storm water runoff underneath a road or embankment. Typical materials include reinforced concrete pipe (RCP) and corrugated metal pipe (CMP). Typical shapes are circular, rectangular, elliptical, or arched.

ForceMain In .gdb Force mains carry stormwater uphill from pump stations into gravity mains and open channels.

GravityMain In .gdb Underground pipes and channels.

LateralLine In .gdb Laterals connect catch basins to underground gravity mains or open channels.

MaintenanceHole In .gdb The top opening to an underground gravity main used for inspection and maintenance.

NaturalDrainage In .gdb Streams and rivers that flow through natural creek beds

OpenChannel In .gdb Concrete lined stormwater channels.

PumpStation In .gdb Where terrain causes accumulation, lift stations are used to pump stormwater to where it can once again flow towards the ocean

Data Field Descriptions

Most of the feature classes in this storm drain geometric network share the same GIS table schema. Only the most critical attributes are listed here per LACFCD operations.

Attribute Description

ASBDATE The date the design plans were approved “as-built” or accepted as “final records”.

CROSS_SECTIN_SHAPE The cross-sectional shape of the pipe or channel. Examples include round, square, trapezoidal, arch, etc.

DIAMETER_HEIGHT The diameter of a round pipe or the height of an underground box or open channel.

DWGNO Drain Plan Drawing Number per LACFCD Nomenclature

EQNUM Asset No. assigned by the Department of Public Works’ (in Maximo Database).

MAINTAINED_BY Identifies, to the best of LAFCD’s knowledge, the agency responsible for maintaining the structure.

MOD_DATE Date the GIS features were last modified.

NAME Name of the individual drainage infrastructure.

OWNER Agency that owns the drainage infrastructure in question.

Q_DESIGN The peak storm water runoff used for the design of the drainage infrastructure.

SOFT_BOTTOM For open channels, indicates whether the channel invert is in its natural state (not lined).

SUBTYPE Most feature classes in this drainage geometric nature contain multiple subtypes.

UPDATED_BY The person who last updated the GIS feature.

WIDTH Width of a channel in feet.

Mapping of deicing material storage facilities in the Lake Champlain Basin was conducted during the late fall and winter of 2022-23. 126 towns were initially selected for mapping (some divisions within the GIS towns data are unincorporated “gores”). Using the list of towns, town clerk contact information was obtained from the Vermont Secretary of State’s website, which maintains a database of contact information for each town.Each town was contacted to request information about their deicing material storage locations and methods. Email and telephone scripts were developed to briefly introduce the project and ask questions about the address of any deicing material storage locations in the town, type of materials stored at each site, duration of time each site has been used, whether materials on site are covered, and the type of surface the materials are stored on, if any. Data were entered into a geospatial database application (Fulcrum). Information was gathered there and exported as ArcGIS file geodatabases and Comma Separated Values (CSV) files for use in Microsoft Excel. Data were collected for 118 towns out of the original 126 on the list (92%). Forty-three (43) towns reported that they are storing multiple materials types at their facilities. Four (4) towns have multiple sites where they store material (Dorset, Pawlet, Morristown, and Castleton). Of these, three (3) store multiple materials at one or both of their sites (Pawlet, Morristown, and Castleton). Where towns have multiple materials or locations, the record information from the overall town identifier is linked to the material stored using a unique ‘one-to-many’ identifier. Locations of deicing material facilities, as shown in the database, were based on the addresses or location descriptions provided by town staff members and was verified only using the most recent aerial imagery (typically later than 2018 for all towns). Locations have not been field verified, nor have site conditions and infrastructure or other information provided by town staff.Dataset instructions:The dataset for Deicing Material Storage Facilities contains two layers – the ‘parent’ records titled ‘salt_storage’ and the ‘child’ records titled ‘salt_storage_record’ with attributes for each salt storage site. This represents a ‘one-to-many’ data structure. To see the attributes for each salt storage site, the user needs to Relate the data. The relationship can be accomplished in GIS software. The Relate needs to be built on the following fields:‘salt_storage’: ‘fulcrum_id’‘salt_storage_record: ‘fulcrum_parent_id’This will create a one-to-many relationship between the geographic locations and the attributes for each salt storage site.

Update date: from GISP repository on 2/6/25. This is a static dataset.Data Type: polyline dataAn open channel is digitized from paper or scanned imagery.Subtypes:Improved: An open drainage course confined with lined or unlined embankments.Unimproved: A natural drainage course graded to channelize storm water.Swale: A graded depression with relatively low slope to channelize storm water. Ditch: A trench provided to channelize storm water. Attributes: Most of the feature classes in this storm drain geometric network share the same GIS table schema. Only the most critical attributes per operations of the Los Angeles County Flood Control District are listed below:AttributeDescriptionASBDATEThe date the design plans were approved "as-built" or accepted as "final records".CROSS_SECTION_SHAPEThe cross-sectional shape of the pipe or channel. Examples include round, square, trapezoidal, arch, etc.DIAMETER_HEIGHTThe diameter of a round pipe or the height of an underground box or open channel.DWGNODrain Plan Drawing Number per LACFCD NomenclatureEQNUMAsset No. assigned by the Department of Public Works (in Maximo Database).MAINTAINED_BYIdentifies, to the best of LAFCD's knowledge, the agency responsible for maintaining the structure.MOD_DATEDate the GIS features were last modified.NAMEName of the individual drainage infrastructure.OWNERAgency that owns the drainage infrastructure in question.Q_DESIGNThe peak storm water runoff used for the design of the drainage infrastructure.SOFT_BOTTOMFor open channels, indicates whether the channel invert is in its natural state (not lined).SUBTYPEMost feature classes in this drainage geometric nature contain multiple subtypes. 1 = Improved, 2 = Unimproved, 3 = Ditch, 4 = SwaleUPDATED_BYThe person who last updated the GIS feature.WIDTHWidth of a channel in feet.This Storm Drain Dataset is a work in progress, and all users of this data are STRONGLY ENCOURAGED to obtain the most current copy, available for download at the LA County eGIS Hub site.Terms of UseThis data is derived from the County Cadastral Landbase and features are typically added to this dataset per recorded 'as-built' drawings. Accurate facility locations on the ground must be determined by qualified field personnel. If any errors are found, or if there are general questions, please contact the individuals listed in the Credits.This product is for information purposes and should not be used for legal, engineering, or survey purposes. County assumes no liability for any errors or omissions.

Multiple Types Cultural Non-profits in New Orleans

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. were derived from the NVC. NatureServe developed a preliminary list of potential vegetation types. These data were combined with existing plot data (Cully 2002) to derive an initial list of potential types. Additional data and information were gleaned from a field visit and incorporated into the final list of map units. Because of the park’s small size and the large amount of field data, the map units are equivalent to existing vegetation associations or local associations/descriptions (e.g., Prairie Dog Colony). In addition to vegetation type, vegetation structures were described using three attributes: height, coverage density, and coverage pattern. In addition to vegetation structure and context, a number of attributes for each polygon were stored in the associated table within the GIS database. Many of these attributes were derived from the photointerpretation; others were calculated or crosswalked from other classifications. Table 2.7.2 shows all of the attributes and their sources. Anderson Level 1 and 2 codes are also included (Anderson et al. 1976). These codes should allow for a more regional perspective on the vegetation types. Look-up tables for the names associated with the codes is included within the geodatabase and in Appendix D. The look-up tables contain all the NVC formation information as well as alliance names, unique IDs, and the ecological system codes (El_Code) for the associations. These El_Codes often represent a one-to-many relationship; that is, one association may be related to more than one ecological system. The NatureServe conservation status is included as a separate item. Finally, slope (degrees), aspect, and elevation were calculated for each polygon label point using a digital elevation model and an ArcView script. The slope figure will vary if one uses a TIN (triangulated irregular network) versus a GRID (grid-referenced information display) for the calculation (Jenness 2005). A grid was used for the slope figure in this dataset. Acres and hectares were calculated using XTools Pro for ArcGIS Desktop.

Address Points contain a single dot for each address or point of interest within the County. This feature is used as the primary despatch source in the County's E911 CAD System. The Street Address subtype includes addresses and "0" address placeholders, which represent parcels and addressed structures. If a structure is present the address point appears within the building footprint, otherwise the point is located at the geographic center of the parcel. Multiple non “0” addresses can be associated with a given parcels, where there are multiple structure and or Real Estate Cards. The Point of Interest subtype is reserved for named places and features that are not tied to a parcel. Some examples of a Point of Interest include: bridges, hazardous curves in a road, entrances to subdivisions, and mile markers. Either subtype can contain civic location, coordinate pairs in multiple projections, common name, and site type information.

Digital data from VG2015-3 Springston, G, Thomas, E, and Kim, J, 2015,�Surficial Geologic Map of the Southern Two-Thirds of the Woodbury Quadrangle, Vermont, Washington County, Vermont: Vermont Geological Survey Open File Report VG2015-3. Data may include surficial geologic contacts, isopach contours lines, bedrock outcrop polygons, bedrock geologic contacts, hydrogeologic units and more. The surficial geologic materials data at a scale of 1:24,000 depict types of unconsolidated surficial and glacial materials overlying bedrock in Vermont. Data is created by mapping on the ground using standard geologic pace and compass techniques and/or GPS on a USGS 1:24000 topographic base map. The materials data is selected from the Vermont Geological Survey Open File Report (OFR) publication (https://dec.vermont.gov/geological-survey/publication-gis/ofr). The OFR contains more complete descriptions of map units, cross-sections, isopach maps and other information that may not be included in this digital data set.

When constructing a new building, the Virginia Uniform Statewide Building Code requires the structure to be assigned a Type of Construction based on its combustibility and level of protection against fire. In addition, the building code assigns a Use Group that identifies the occupancy based on how the building is used, i.e., mercantile, assembly, business, industrial and storage. In some cases, buildings may have multiple Types of Construction and Use Groups. Historic building permit applications capture this data as a snapshot in time from the date of initial construction. Building code designations for Type of Construction and Use Group have changed over time and buildings may have undergone tenant and construction updates. Therefore, current designations may be different from the data gathered from historic permit applications.Contact: Land Development Services, Brett MartinData accessibility: PublicUpdate frequency: MonthlyCreation date: 04/19/2019Feature class name: LDSAMGR.BUILDING_CONSTRUCTION_TYPE

An area encompassing all the National Forest System lands administered by an administrative unit. The area encompasses private lands, other governmental agency lands, and may contain National Forest System lands within the proclaimed boundaries of another administrative unit. All National Forest System lands fall within one and only one Administrative Forest Area.

This data is intended for read-only use. These data were prepared to describe Forest Service administrative area boundaries. The purpose of the data is to provide display, identification, and analysis tools for determining current boundary information for Forest Service managers, GIS Specialists, and others.

The Forest Service has multiple types of boundaries represented by different feature classes (layers): Administrative, Ownership and Proclaimed. 1) ADMINISTRATIVE boundaries (e.g. AdministrativeForest and RangerDistrict feature classes) encompass National Forest System lands managed by an administrative unit. These are dynamic layers that should not be considered "legal" boundaries as they are simply intended to identify the specific organizational units that administer areas. As lands are acquired and disposed, the administrative boundaries are adjusted to expand or shrink accordingly. Please note that ranger districts are sub units of National Forests. An administrative forest boundary can contain one or more Proclaimed National Forests, National Grasslands, Purchase Units, Research and Experimental Areas, Land Utilization Projects and various "Other" Areas. If needed, OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) should be reviewed along with these datasets to determine parcels that are federally managed within the administrative boundaries. 2) OWNERSHIP boundaries (e.g. BasicOwnership and SurfaceOwnership feature classes) represent parcels that are tied to legal transactions of ownership. These are parcels of Federal land managed by the USDA Forest Service. Please note that the BasicOwnership layer is simply a dissolved version of the SurfaceOwnership layer. 3) PROCLAIMED boundaries (e.g. ProclaimedForest and ProclaimedForest_Grassland) encompass areas of National Forest System land that is set aside and reserved from public domain by executive order or proclamation. Please note that the ProclaimedForest layer contains only proclaimed forests while ProclaimedForest_Grassland layer contains both proclaimed forests and proclaimed grasslands. For boundaries that reflect current National Forest System lands managed by an administrative unit, see the ADMINISTRATIVE boundaries (AdministrativeForest and RangerDistrict feature classes). For a visual comparison of the different kinds of USFS boundary datasets maintained by the USFS, see the Forest Service Boundary Comparison map at https://usfs.maps.arcgis.com/apps/CompareAnalysis/index.html?appid=fe7b9f56217949a291356f08cfccb119. USFS boundaries are often referenced in national datasets maintained by other federal agencies. Please note that variations may be found between USFS data and other boundary datasets due to differing update frequencies. PAD-US (Protected Areas Database of the United States), maintained by the U.S. Geological Survey, is a "best available" inventory of protected areas including data provided by managing agencies and organizations including the Forest Service. For more information see https://gapanalysis.usgs.gov/padus/data/metadata/. SMA (Surface Management Agency), maintained by the Bureau of Land Management, depicts Federal land for the United States and classifies this land by its active Federal surface managing agency. It uses data provided by the Forest Service and other agencies, combined with National Regional Offices collection efforts. For more information see https://landscape.blm.gov/geoportal/catalog/search/resource/details.page?uuid=%7B2A8B8906-7711-4AF7-9510-C6C7FD991177%7D.

Permit records from the City of Seattle permitting system for building permits that create or demolish housing units. Records begin in 1990 and are through the current year quarter.

The permits in this layer are those that are currently issued. This data does not contain records for those permits that were issued but were not completed, cancelled or withdrawn.

Each record represents the number of units added or demolished for each housing type in the project. Therefore a single building permit may appear multiple times if there are a mix of unit types in the project.

Housing unit types reflect the unit types regulated by the building codes and change through time. There has been no attempt to standardize these types and therefore reflect the unit types that existed at the time the permit was issued.

There may be multiple permits at any given address.

Permit records from the City of Seattle permitting system for building permits that create or demolish attached accessory dwelling units (AADU). Records begin in 1990 and are through the current year quarter.

The permits in this layer are those that have either been completed or are currently issued. This data does not contain records for those permits that were issued but were not completed so are therefore not comparable to statistics that report permit issuance.

Each record represents the number of units added or demolished for each housing type in the project. Therefore a single building permit may appear multiple times if there are a mix of unit types in the project.

Housing unit types reflect the unit types regulated by the building codes and change through time. There has been no attempt to standardize these types and therefore reflect the unit types that existed at the time the permit was issued. Unit types will be visible only for the time period they were in the code. For example, small efficiency dwelling units were not created in the code until 2016 and so will not appear as a type until that year.

There may be multiple permits at any given address.

Summary:

The files contained herein represent green roof footprints in NYC visible in 2016 high-resolution orthoimagery of NYC (described at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_AerialImagery.md). Previously documented green roofs were aggregated in 2016 from multiple data sources including from NYC Department of Parks and Recreation and the NYC Department of Environmental Protection, greenroofs.com, and greenhomenyc.org. Footprints of the green roof surfaces were manually digitized based on the 2016 imagery, and a sample of other roof types were digitized to create a set of training data for classification of the imagery. A Mahalanobis distance classifier was employed in Google Earth Engine, and results were manually corrected, removing non-green roofs that were classified and adjusting shape/outlines of the classified green roofs to remove significant errors based on visual inspection with imagery across multiple time points. Ultimately, these initial data represent an estimate of where green roofs existed as of the imagery used, in 2016.

These data are associated with an existing GitHub Repository, https://github.com/tnc-ny-science/NYC_GreenRoofMapping, and as needed and appropriate pending future work, versioned updates will be released here.

Terms of Use:

The Nature Conservancy and co-authors of this work shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any sale, distribution, loan, or offering for use of these digital data, in whole or in part, is prohibited without the approval of The Nature Conservancy and co-authors. The use of these data to produce other GIS products and services with the intent to sell for a profit is prohibited without the written consent of The Nature Conservancy and co-authors. All parties receiving these data must be informed of these restrictions. Authors of this work shall be acknowledged as data contributors to any reports or other products derived from these data.

Associated Files:

As of this release, the specific files included here are:

• GreenRoofData2016_20180917.geojson is in the human-readable, GeoJSON format, in geographic coordinates (Lat/Long, WGS84; EPSG 4263).
• GreenRoofData2016_20180917.gpkg is in the GeoPackage format, which is an Open Standard readable by most GIS software including Esri products (tested on ArcMap 10.3.1 and multiple versions of QGIS). This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917_Shapefile.zip is a zipped folder containing a Shapefile and associated files. Please note that some field names were truncated due to limitations of Shapefiles, but columns are in the same order as for other files and in the same order as listed below. This dataset is in the New York State Plan Coordinate System (units in feet) for the Long Island Zone, North American Datum 1983, EPSG 2263.
• GreenRoofData2016_20180917.csv is a comma-separated values file (CSV) with coordinates for centroids for the green roofs stored in the table itself. This allows for easily opening the data in a tool like spreadsheet software (e.g., Microsoft Excel) or a text editor.

Column Information for the datasets:

Some, but not all fields were joined to the green roof footprint data based on building footprint and tax lot data; those datasets are embedded as hyperlinks below.

• fid - Unique identifier
• bin - NYC Building ID Number based on overlap between green roof areas and a building footprint dataset for NYC from August, 2017. (Newer building footprint datasets do not have linkages to the tax lot identifier (bbl), thus this older dataset was used). The most current building footprint dataset should be available at: https://data.cityofnewyork.us/Housing-Development/Building-Footprints/nqwf-w8eh. Associated metadata for fields from that dataset are available at https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_BuildingFootprints.md.
• bbl - Boro Block and Lot number as a single string. This field is a tax lot identifier for NYC, which can be tied to the Digital Tax Map (http://gis.nyc.gov/taxmap/map.htm) and PLUTO/MapPLUTO (https://www1.nyc.gov/site/planning/data-maps/open-data/dwn-pluto-mappluto.page). Metadata for fields pulled from PLUTO/MapPLUTO can be found in the PLUTO Data Dictionary found on the aforementioned page. All joins to this bbl were based on MapPLUTO version 18v1.
• gr_area - Total area of the footprint of the green roof as per this data layer, in square feet, calculated using the projected coordinate system (EPSG 2263).
• bldg_area - Total area of the footprint of the associated building, in square feet, calculated using the projected coordinate system (EPSG 2263).
• prop_gr - Proportion of the building covered by green roof according to this layer (gr_area/bldg_area).
• cnstrct_yr - Year the building was constructed, pulled from the Building Footprint data.
• doitt_id - An identifier for the building assigned by the NYC Dept. of Information Technology and Telecommunications, pulled from the Building Footprint Data.
• heightroof - Height of the roof of the associated building, pulled from the Building Footprint Data.
• feat_code - Code describing the type of building, pulled from the Building Footprint Data.
• groundelev - Lowest elevation at the building level, pulled from the Building Footprint Data.
• qa - Flag indicating a positive QA/QC check (using multiple types of imagery); all data in this dataset should have 'Good'
• notes - Any notes about the green roof taken during visual inspection of imagery; for example, it was noted if the green roof appeared to be missing in newer imagery, or if there were parts of the roof for which it was unclear whether there was green roof area or potted plants.
• classified - Flag indicating whether the green roof was detected image classification. (1 for yes, 0 for no)
• digitized - Flag indicating whether the green roof was digitized prior to image classification and used as training data. (1 for yes, 0 for no)
• newlyadded - Flag indicating whether the green roof was detected solely by visual inspection after the image classification and added. (1 for yes, 0 for no)
• original_source - Indication of what the original data source was, whether a specific website, agency such as NYC Dept. of Parks and Recreation (DPR), or NYC Dept. of Environmental Protection (DEP). Multiple sources are separated by a slash.
• address - Address based on MapPLUTO, joined to the dataset based on bbl.
• borough - Borough abbreviation pulled from MapPLUTO.
• ownertype - Owner type field pulled from MapPLUTO.
• zonedist1 - Zoning District 1 type pulled from MapPLUTO.
• spdist1 - Special District 1 pulled from MapPLUTO.
• bbl_fixed - Flag to indicate whether bbl was manually fixed. Since tax lot data may have changed slightly since the release of the building footprint data used in this work, a small percentage of bbl codes had to be manually updated based on overlay between the green roof footprint and the MapPLUTO data, when no join was feasible based on the bbl code from the building footprint data. (1 for yes, 0 for no)

For GreenRoofData2016_20180917.csv there are two additional columns, representing the coordinates of centroids in geographic coordinates (Lat/Long, WGS84; EPSG 4263):

• xcoord - Longitude in decimal degrees.
• ycoord - Latitude in decimal degrees.

Acknowledgements:

This work was primarily supported through funding from the J.M. Kaplan Fund, awarded to the New York City Program of The Nature Conservancy, with additional support from the New York Community Trust, through New York City Audubon and the Green Roof Researchers Alliance.

Permit records from the City of Seattle permitting system for building permits that create or demolish housing units. Records begin from the beginning of the previous decade from the current quarter year.

The permits in this layer are those that have been completed. This data does not contain records for those permits that were issued but were not completed so are therefore not comparable to statistics that report permit issuance.

Each record represents the number of units added or demolished for each housing type in the project. Therefore a single building permit may appear multiple times if there are a mix of unit types in the project.

Housing unit types reflect the unit types regulated by the building codes and change through time. There has been no attempt to standardize these types and therefore reflect the unit types that existed at the time the permit was issued.

There may be multiple permits at any given address.

A cleanup site is a place where a toxic substance is harming or threatening humans or the environment.Toxic substances can include:Petroleum (gasoline, diesel, oil, etc.)Heavy metals (lead, arsenic, etc.)Chemicals and pesticidesPersistent organic pollutants (PCBs, dioxins, furans, etc.)Toxic substances can contaminate multiple types of media, including:SoilSediment (in bays, shorelines, estuaries, lakes, rivers, etc.)Water (groundwater, fresh or marine water, and stormwater or surface runoff)Air (indoor and outdoor air, soil gas, and vapor intrusion)Under state and federal laws, people or entities who pollute the air, land, or water are responsible for cleaning up the contamination.DescriptionContaminated site locations and status. Data contains links to any reports or actions that are required for existing sites and is updated regularly. This data layer is created from a script using data from the Washington Department of Ecology. DATA LINKED FROM Washington Department of EcologyFor more information visit the Department of Ecology's Cleanup site website.

IMPORTANT NOTE: As of June, 2024, the Department of Regional Planning revised this layer with updated field names and information from project specific surveys. See description below. OverviewThis layer identifies historic resources and their attributes located in unincorporated areas or on County owned land and listed, or in some cases eligible for listing, on the National, California and/or County registers. This information supports the County’s Historic Preservation Ordinance, Mills Act Program and CEQA. The LA County Planning"s Historic Preservation Programwebsiteis the central location for all things related to the Historic Preservation efforts in the County.Data Sources Built Environment Resource Directory (BERD) - The Built Environment Resources Directory (BERD) files provide information, organized by county, regarding non-archaeological resources in the Office of Historic Preservation’s (OHP) inventory, and more information can be foundhere.County Adopted Landmarks - these are identified in theCounty Register.County Proposed or Eligible Districts - not yet officially adopted.County Historic Context Statements, Historic Surveys and Preservation programs - these are identified on the Historic Preservation > Resourcessite.DRP - Energov - These are parcels with a Mills Act contract, but are not on any official register.State and National Registers - Landmarks or Districts listed on State and National registers. For more information, please visit the Historic Preservation Programsite.Cal Fire -Flags structures in unincorporated areas that have been damaged by major fires. Field Descriptions Name - Name of the site or district. Note that some of the names listed are generic, or they may not have a name at all.Description - A description of the site or district. Note that not all sites will have a detailed description.APN(s) - Parcel number of the site, or multiple parcel numbers if the site contains multiple parcels. Some sites are within right-of-ways and may not have a parcel number.Address or Location - an address or a description of the location.Year(s) Built - The year a structure was built. Not all built data is available, or may not be applicable.Status Code / Description - The status code and description for a site as established from the Office of Historic Preservation (OHP). For list, clickhere.Potential Themes - For a Historic Context Statement and Survey, themes are a way to categorize patterns of historical development. More information about this and of Historic Contexts and Surveys in general ishere.Architectural Style - Describes the architectural style of the buildings, where applicable.Source - Source agency or database of the site or district; source document of a Historic Context Statement / Survey.Source Date - The date the source material was extracted; date of a Historic Context Statement / Survey.Year Designated - The year a site or district was officially added to a County, State, or National Registry.Mills Act Contract - Whether a site is under a Mills Act contract which is an agreement between a property owner and a local government to preserve the historic resources on their property and receive property tax relief. More information from OHP ishere.Jurisdiction - Identifies whether the site or district is in a city or unincorporated area. Most of the sites in this layer will be in unincorporated areas, but, there are sites within cities that are official County Landmarks (like the Hollywood Bowl).City / Unincorporated Community - Identifies the city or community name of the site or district. See Jurisdiction note above for cities.Notes - Explanatory notes about a site - mostly references to the source materials.File Location (Hyperlink) - Hyperlinks to source materials.County Landmark / District Number - Identification number for the official LA County. More information ishere.County Designation Date - Date that a landmark or district was adopted. More information ishere.CA_TYPE / CA_NUM / CA_DATE - These are the official types, ID numbers, and dates for those sites in the California Registry. Visit the California Historical Resources pagehere.NALANDMARK / NA_TYPE / NA_NUM / NA_DATE - These are the official types, ID numbers, and dates for those sites in the National Registry. A link to the National Register of Historic Places ishere.Legend - These are the general categories of sites and districts that are used in the symbology of GIS-NET.Fire Damage -Flags sites that have structures that were damaged or destroyed from major fires with the following categories per Cal Fire: No Damage (sites within or near a fire perimeter that were not damaged by the fire listed);Affected (1 - 9% damage); Minor (10 - 25 % damage); Major (26 - 50% damage); Destroyed (over 50% damage); Inaccessible (site unable to be assessed)Fire Damage Notes -Lists the name of the fire, and flags those sites that have multiple structures with multiple damage categories. Last Updated: 7/17/25 for the rescission of the County Landmark, Henry Dart Greene House, which was destroyed in the Eaton Fire in January, 2025. NEED MORE FUNCTIONALITY? If you are looking for more layers or advanced tools and functionality, then try our suite ofGIS Web Mapping Applications.

Last Revised: February 2016

Map Information

This nowCOAST™ time-enabled map service provides maps depicting the NWS Multi-Radar Multi-Sensor (MRMS) quantitative precipitation estimate mosaics for 1-, 3-, 6-, 12-, 24-, 48-, and 72-hr time periods at a 1 km (0.6 miles) horizontal resolution for CONUS and southern part of Canada. The precipitation estimates are based only on radar data. The total precipitation amount is indicated by different colors at 0.01, 0.10, 0.25 inches and then at 1/4 inch intervals up to 4.0 inches (e.g. 0.50, 0.75, 1.00, 1.25, etc.), at 1-inch intervals from 4 to 10 inches and then at 2-inch intervals up to 14+ inches. The increments from 0.01 to 1.00 or 2.00 inches are similar to what are used on NCEP's Weather Prediction Center QPF products and the NWS River Forecast Center (RFC) daily precipitation analysis. The 1-hr mosaic is updated every 4 minutes with a latency on nowCOAST™ of about 6-7 minutes from valid time. The 3-, 6-, 12-, and 24-hr QPEs are updated on nowCOAST™ every hour for the period ending at the top of the hour. The 48- and 72-hr QPEs are generated daily for the period ending at 12 UTC (i.e. 7AM EST) and available on nowCOAST™ shortly afterwards. For more detailed information about layer update frequency and timing, please reference the
nowCOAST™ Dataset Update Schedule.

Background Information

The NWS Multi-Radar Multi-Sensor System (MRMS)/Q3 QPEs are radar-only based quantitative precipitation analyses. The 1-hr precipitation accumulation is obtained by aggregating 12 instantaneous rate fields. Missing rate fields are filled with the neighboring rate fields if the data gap is not significantly large (e.g.<=15 minutes). The instantaneous rate is computed from the hybrid scan reflectivity and the precipitation flag fields (both are 2-D derivative products from the National 3-D Reflectivity Mosaic grid which has a 1-km horizontal resolution, 31 vertical levels and a 5-minute update cycle). The instantaneous rate currently uses four Z-R relationships (i.e. tropical, convective, stratiform, or snow). The particular ZR relationship used in any grid cell depends on precipitation type which is indicated by the precipitation flag. The other accumulation products are derived by aggregating the hourly accumulations. The 1-hr QPE are generated every 4 minutes, while the 3-, 6-, 12-, and 24-hr accumulations are generated every hour at the top of the hour. The 48- and 72-hr QPEs are updated daily at approximately 12 UTC. MRMS was developed by NOAA/OAR/National Severe Storms Laboratory and migrated into NWS operations at NOAA Integrated Dissemination Program.

Time Information

This map service is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.

In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.

This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.

This service is configured with time coverage support, meaning that the service will always return the most relevant available data, if any, to the specified time value. For example, if the service contains data valid today at 12:00 and 12:10 UTC, but a map request specifies a time value of today at 12:07 UTC, the data valid at 12:10 UTC will be returned to the user. This behavior allows more flexibility for users, especially when displaying multiple time-enabled layers together despite slight differences in temporal resolution or update frequency.

When interacting with this time-enabled service, only a single instantaneous time value should be specified in each request. If instead a time range is specified in a request (i.e. separate start time and end time values are given), the data returned may be different than what was intended.

Care must be taken to ensure the time value specified in each request falls within the current time coverage of the service. Because this service is frequently updated as new data becomes available, the user must periodically determine the service's time extent. However, due to software limitations, the time extent of the service and map layers as advertised by ArcGIS Server does not always provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time extent of the service:

  Issue a returnUpdates=true request (ArcGIS REST protocol only)
  for an individual layer or for the service itself, which will return
  the current start and end times of available data, in epoch time format
  (milliseconds since 00:00 January 1, 1970). To see an example, click on
  the "Return Updates" link at the bottom of the REST Service page under
  "Supported Operations". Refer to the
  ArcGIS REST API Map Service Documentation
  for more information.


  Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
  the proper layer corresponding with the target dataset. For raster
  data, this would be the "Image Footprints with Time Attributes" layer
  in the same group as the target "Image" layer being displayed. For
  vector (point, line, or polygon) data, the target layer can be queried
  directly. In either case, the attributes returned for the matching
  raster(s) or vector feature(s) will include the following:


      validtime: Valid timestamp.


      starttime: Display start time.


      endtime: Display end time.


      reftime: Reference time (sometimes referred to as
      issuance time, cycle time, or initialization time).


      projmins: Number of minutes from reference time to valid
      time.


      desigreftime: Designated reference time; used as a
      common reference time for all items when individual reference
      times do not match.


      desigprojmins: Number of minutes from designated
      reference time to valid time.




  Query the nowCOAST™ LayerInfo web service, which has been created to
  provide additional information about each data layer in a service,
  including a list of all available "time stops" (i.e. "valid times"),
  individual timestamps, or the valid time of a layer's latest available
  data (i.e. "Product Time"). For more information about the LayerInfo
  web service, including examples of various types of requests, refer to
  the 
  nowCOAST™ LayerInfo Help Documentation

References

For more information about the MRMS/Q3 system, please see http://nmq.ou.edu and http://www.nssl.noaa.gov/projects/mrms.