This is a guide that describes how to interact with pop ups and the attribute tables in web maps where that functionality is available. Not all widgets or functionality is available in every web map.

This is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the “Data File Organization” section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with “main.” preceding each file name, and an extra column named “geom” defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in “niwot_geospatial_data_list_07012021.pdf/.xlsx”. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or “Arc/Info Binary”) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csv’s can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimble’s GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRI’s compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRI’s latest versions of geospatial software. These details are also noted in the “niwot_geospatial_data_list_07012021” file.

A custom Python Tool Box exclusively for ESRI ArcMap Application. This toolbox contains two tools: 1. Duplicate Value Calculator : - to search duplicate values in a specified Attribute Field of Table /FeautureClass and populate user defined text for such records in another specified Attribute Field of same Table/FeatureClass. If no Attribute Field is selected to populate text, a default Attribute Field will be added with Name as "DUPLICATE_{Name of Field for Search Duplicate values}".

Further, User can imply SQL Expression to limit the records to be searched as per requirement.

Caution : This Tool modifies the SCHEMA of selected Table/FeatureClass if no Attribute Field is selected to populate text for duplicate values. So preconsider to choose both Attribute Fields - One for Duplicate Search and other for Text against duplicate value if You are concerned about to add new field to Your Table/FeatureClass.

1. Delete Rows : - to delete Rows from input Table/FeatureClass. Put an SQL Expression for records filter, otherwise all rows will be deleted.

Web App. Use the tabs provided to discover information about map features and capabilities. Link to Metadata. A variety of searches can be performed to find the parcel of interest. Use the Query Tool to build searches. Click Apply button at the bottom of the tool.Query by Name (Last First) (e.g. Bond James)Query by Address (e.g. 41 S Central)Query by Locator number (e.g. 21J411046)Search results will be listed under the Results tab. Click on a parcel in the list to zoom to that parcel. Click on the parcel in the map and scroll through the pop-up to see more information about the parcel. Click the ellipse in the Results tab or in the pop-up to view information in a table. Attribute information can be exported to CSV file. Build a custom Filter to select and map properties by opening the Parcels attribute table: 1. Click the arrow tab at the bottom middle of the map to expand the attribute table window2. Click on the Parcels tab3. Check off Filter by map extent4. Open Options>Filter5. Build expressions as needed to filter by owner name or other variables6. Select the needed records from the returned list7. Click Zoom to which will zoom to the selected records Please note that as the map zooms out detailed layers, such as the parcel boundaries will not display. In addition to Search capabilities, the following tools are provided:MeasureDrawPrint

This script will prompt the user for a path to a file geodatabase or a sde geodatabase connection file. Then the script will loop through the feature classes\tables and document details about the attribute rules. All of the data gathered is written to a csv file. This is a Jupyter Notebook written using arcpy.Sources used to develop this notebook:Iterate through SDE to find and export FCs with Attribute Rules with python?Attribute Rule propertiesA Python script to Automate Attribute Rules Deployment

Building polygons were created in February 2013 by Geoscience Australia by manually digitising the outline of each building off the 2011 orthophotography. Digitisation was done from scratch off the 2011 orthophotography within Quantum GIS. Using the ArcMap 'zonal statistics' tool the minimum, mean and maximum heights were found for each building polygon from the 2011 digital elevation model and the 2011 digital surface model (DSM). This information was then joined to the building polygon attribute table. To find the building height from ground to roof, the difference between the Mean DSM and mean DEM was calculated and added as a field to the attribute table. To find the maximum height of each building the difference between the Maximum DSM and Mean DEM was calculated. Polygon area, perimeter, and x and y coordinates of each building were also attached as attributes. Accuracy is high as the layer was based on the 2011 orthophotography. Error may have been introduced through the digitisation process. Building lean in the orthophotography may also contribute to polygons which are slightly inaccurately placed. Height attribute accuracy is inaccurate for building polygons which have tree cover above them, as the tree elevation would influence the digital surface model. Particularly the Max_height field may include tree heights rather than building heights in some cases. Attribute accuracy could be improved by using the raw 2011 lidar data (.las files) which are classified at 'buildings' to attach heights. This method was tested and was extremely time consuming - only the height_max field was significantly improved. Disclaimer

Users may use this webapp to find information for City of Burien Work activities recorded in Cityworks. The app allows Users may highlight features from Public Works WorkOrders, Public Works Service Requests, Parks Non-Cyclic Work Orders, and Parks Service Requests. Routine/cyclic work activities from Parks are not included. Parks service requests are configured within the app but are not in use by the Parks department at time of app construction. The data in this app is time gated to 6 months from work orders close or from a service requests initiation to keep the returned records manageable for the end user and ensure performance.Note only work activities that have been geolocated will be displayed as a result.The primary selection tool allows users to indicate which class of work activity they wish to interact with, and draw a selection on a point or line. On pressing review, they can commit the selection to the rest of the map. They are able to export a simple description of the selected work activities as either a pdf or as a CSV file. The app allows you to expand the attribute table by clicking the arrow button at the bottom of the map. By selecting options, the user can show only the selected records. The attribute table also supports export to CSV and has more details than the simple record search. Additionally, a select and filter tool are available to help users specify the information they are looking for underneath the address search bar. The nearby tool, also located beneath the address search bar, also provides similar functionality to the primary selection tool, but allows an address to be input as the starting location. Records identified through this tool will need to be selected via the other options to view in the attribute table.

The US National Park Service manages 84.4 million acres that include the United States" 63 national parks, many national monuments, and other conservation and historical properties. These lands range from the 13 million acre Wrangell-St. Elias National Park and Preserve in Alaska to the 0.02 acre Thaddeus Kosciuszko National Memorial in Pennsylvania.Dataset SummaryPhenomenon Mapped: Administrative boundaries of U.S. National Park Service landsGeographic Extent: 50 United States, District of Columbia, Puerto Rico, US Virgin Islands, Guam, American Samoa, and Northern Mariana IslandsData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: NPS Administrative Boundaries of National Park System Units layerPublication Date: April, 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Park Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "national park service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "national park service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

The US Forest Service manages 193 million acres including the nation's 154 National Forests and 20 National Grasslands. These lands provide a wide variety of recreational opportunities, protect sources of clean water, and supply timber and forage.Dataset SummaryPhenomenon Mapped: United States lands managed by the US Forest ServiceGeographic Extent: Contiguous United States, Alaska, and Puerto RicoVisible Scale: The data is visible at all scales.Source: USFS Surface Ownership ParcelsPublication Date: May 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Forest Service lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this Layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "forest service" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "forest service" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in ProThe data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage..This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

The U.S. Defense Department oversees the USA"s armed forces and manages over 30 million acres of land. With over 2.8 million service members and civilian employees the department is the world"s largest employer.Dataset SummaryPhenomenon Mapped: Lands managed by the U.S. Department of DefenseGeographic Extent: United States, Guam, Puerto RicoData Coordinate System: WGS 1984Visible Scale: The data is visible at all scalesSource: DOD Military Installations Ranges and Training Areas layer. Publication Date: May 2025This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Department of Defense lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "department of defense" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "department of defense" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

One-eighth of the United States (247.3 million acres) is managed by the Bureau of Land Management. As part of the Department of the Interior, the agency oversees the 30 million acre National Landscape Conservation System, a collection of lands that includes 221 wilderness areas, 23 national monuments and 636 other protected areas. Bureau of Land Management Lands contain over 63,000 oil and gas wells and provide forage for over 18,000 grazing permit holders on 155 million acres of land. Dataset SummaryPhenomenon Mapped: United States lands managed by the Bureau of Land ManagementGeographic Extent: Contiguous United States and AlaskaData Coordinate System: WGS 1984Visible Scale: The data is visible at all scales but draws best at scales larger than 1:2,000,000.Source: BLM Surface Management Agency layer, Rasterized by Esri from features May 2025.Publication Date: December 2024This layer is a view of the USA Federal Lands layer. A filter has been used on this layer to eliminate non-Bureau of Land Management lands. For more information on layers for other agencies see the USA Federal Lands layer.What can you do with this layer?This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "bureau of land management" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box expand Portal if necessary then select Living Atlas. Type "bureau of land management" in the search box, browse to the layer then click OK.In both ArcGIS Online and Pro you can change the layer's symbology and view its attribute table. You can filter the layer to show subsets of the data using the filter button in Online or a definition query in Pro.The data can be exported to a file geodatabase, a shape file or other format and downloaded using the Export Data button on the top right of this webpage.This layer can be used as an analytic input in both Online and Pro through the Perform Analysis window Online or as an input to a geoprocessing tool, model, or Python script in Pro.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.Questions?Please leave a comment below if you have a question about this layer, and we will get back to you as soon as possible.

This GIS dataset includes:

1 Point data representing southern elephant seal haulout sites as shown in Figure 1 of the paper J.van den Hoff, R.Davies and H.Burton, 'Origins, age composition and change in numbers of moulting southern elephant seals (Mirounga leonina L.) in the Windmill Islands, Vincennes Bay, east Antarctica: 1988-2001', Wildlife Research vol 30 no 3 2003.

2 Polygon data representing some of the above sites. This data is based on field work by John van den Hoff, Australian Antarctic Division biologist, in 2000/01.

3 Polygon data representing two Weddell seal pupping sites in the Windmill Islands. This data is based on John van den Hoff's knowledge from field work and research.

The data has been formatted according to the SCAR Feature Catalogue.

Data that are part of this dataset have Dataset_id = 179 in the SCAR Feature Catalogue format. Dataset_id is an attribute in the attribute table.

Data quality information for any feature can be searched for at a Related URL by entering the Qinfo number of the feature at the 'Search datasets and quality' tab. Qinfo is an attribute in the attribute table.

State Water Resources Control Board Division of Water Quality staff have developed this map to graphically display the waterbodies assessed in the 2018 California Integrated Report. This map contains waterbodies assessed for 305(b) categorization, including those placed on the 303(d) list of impaired waters.Map Layers and Table:2018 Integrated Report Streams, Rivers, and Beaches: Spatial representation of the assessed linear waterbodies in California.2018 Integrated Report Lakes, Bays, and Reservoirs: Spatial representation of the non-linear (polygon) waterbodies in California. The layers can also be accessed here: https://gispublic.waterboards.ca.gov/portalserver/rest/services/Hosted/CA_2018_Integrated_Report_Assessed_Lines_and_Polys/FeatureServerHow to Use the Map:Navigate to your point of interest by either using the search bar in the upper left-hand corner of the map or by zooming in on the map. You may enter a waterbody name or address into the search bar. Click on a waterbody of interest, such as a river, lake, or beach, and a pop-up box will appear with a summary of the pollutant assessments conducted for that waterbody. Select the ellipsis ("...") in a pop-up window or the layers to view the attribute table. This table can be further filtered and exported in a tabular format. Click on the layers icon in the upper right hand corner to toggle map layers on and off.Click on the filter button in the upper right corner to filter for a specific Regional Board and to select for 303(d) listed waterbodies only. Note, this should be done for both layers.More details on each waterbody can be found by scrolling to the bottom of a waterbody pop-up and selecting “Waterbody Fact Sheet- More information”.Pop Up Description:WBID: Unique identifier for each waterbody used in the Integrated Report. Waterbody Name: Name of the mapped waterbody assessed for the Integrated Report. Waterbody Type: Type of water (Coastal & Bay Shoreline, Freshwater Wetland, Tidal Wetland, Saline Lake, River & Stream, Ocean, Lake and Reservoir, Estuary, and Bay & Harbor).Regional Board: Which Regional Water Quality Control Board has jurisdiction over the waterbody. Waterbody Condition Category: Integrated Report 305(b) Category for the waterbody.Waterbody Listing Status: If the waterbody has been placed on the 303(d) list as impaired for one or more pollutant, it will be identified as "Listed". If it was assessed for one or more pollutant and not determined to be impaired, it will be identified as "Not Listed". Listed Pollutants: Pollutants identified as impairing the waterbody's support of beneficial uses. The Decision ID is included in parentheses. Listings Addressed by a TMDL: Pollutant impairments in the waterbody being addressed by an adopted Total Maximum Daily Load (TMDL)Listings Addressed by Action other than TMDL: Pollutant impairments in the waterbody being addressed by actions other than a TMDL. These may also be referred to as Category “4b” decisions.Pollutants Assessed, Not Listed: Pollutant assessments that did not result in a 303(d) impairment decision for the waterbody.Waterbody Fact Sheet: Link to the Waterbody Fact Sheet for the waterbody, which includes waterbody/pollutant assessment information. For additional data and information about the 2018 Integrated Report assessments, please visit our Data Download page: (coming soon!)For more information about the Integrated Report (the 305(b) Report and the 303(d) List), how it is created, or how this information is used, please see the program webpage: https://www.waterboards.ca.gov/water_issues/programs/water_quality_assessment/Please contact the SWRCB Water Quality Assessment Program with any questions, at WQAssessment@waterboards.ca.gov. Origin Date: July 2, 2021Last edited: July 28, 2021

This GIS dataset includes:

1 Point data representing southern elephant seal haulout sites in the Vestfold Hills.

2 Polygon data representing weddell seal pupping areas in the Vestfold Hills.

The data is based on field work and research by John van den Hoff, AAD biologist.

The data has been formatted according to the SCAR Feature Catalogue.

Data that are part of this dataset have Dataset_id = 289 in the SCAR Feature Catalogue format. Dataset_id is an attribute in the attribute table.

Data quality information for any feature can be searched for at a Related URL by entering the Qinfo number of the feature at the 'Search datasets and quality' tab. Qinfo is an attribute in the attribute table.

This intersection points feature class represents current intersections in the City of Los Angeles. Few intersection points, named pseudo nodes, are used to split the street centerline at a point that is not a true intersection at the ground level. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Intersection layer was created in geographical information systems (GIS) software to display intersection points. Intersection points are placed where street line features join or cross each other and where freeway off- and on-ramp line features join street line features. The intersection points layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a point feature class and attribute data for the features. The intersection points relates to the intersection attribute table, which contains data describing the limits of the street segment, by the CL_NODE_ID field. The layer shows the location of the intersection points on map products and web mapping applications, and the Department of Transportation, LADOT, uses the intersection points in their GIS system. The intersection attributes are used in the Intersection search function on BOE's web mapping application NavigateLA. The intersection spatial data and related attribute data are maintained in the Intersection layer using Street Centerline Editing application. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. List of Fields:Y: This field captures the georeferenced location along the vertical plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, Y = in the record of a point, while the X = .CL_NODE_ID: This field value is entered as new point features are added to the edit layer, during Street Centerline application editing process. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline spatial data layer, then the intersections point spatial data layer, and then the intersections point attribute data during the creation of new intersection points. Each intersection identification number is a unique value. The value relates to the street centerline layer attributes, to the INT_ID_FROM and INT_ID_TO fields. One or more street centerline features intersect the intersection point feature. For example, if a street centerline segment ends at a cul-de-sac, then the point feature intersects only one street centerline segment.X: This field captures the georeferenced location along the horizontal plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, X = in the record of a point, while the Y = .ASSETID: User-defined feature autonumber.USER_ID: The name of the user carrying out the edits.SHAPE: Feature geometry.LST_MODF_DT: Last modification date of the polygon feature.LAT: This field captures the Latitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.OBJECTID: Internal feature number.CRTN_DT: Creation date of the polygon feature.TYPE: This field captures a value for intersection point features that are psuedo nodes or outside of the City. A pseudo node, or point, does not signify a true intersection of two or more different street centerline features. The point is there to split the line feature into two segments. A pseudo node may be needed if for example, the Bureau of Street Services (BSS) has assigned different SECT_ID values for those segments. Values: • S - Feature is a pseudo node and not a true intersection. • null - Feature is an intersection point. • O - Intersection point is outside of the City of LA boundary.LON: This field captures the Longitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.

The Australian Antarctic Data Centre's topographic GIS data for the Windmill Islands, Antarctica were originally mapped mainly from aerial photography: refer to the metadata record 'Windmill Islands 1:50000 Topographic GIS Dataset'. Since then features from various sources have been added to this data.

The data are available for download as part of the Windmill Islands GIS dataset from a Related URL.

The data are formatted according to the SCAR Feature Catalogue (see Related URL). Data that are part of this dataset have Dataset_id = 164 in the SCAR Feature Catalogue format. Dataset_id is an attribute in the attribute table. Data quality information for any feature can be searched for at the Related URL by entering the Qinfo number of the feature at the 'Search datasets and quality' tab. Qinfo is an attribute in the attribute table.

This data package includes an ArcMap geodatabase for the Chihuahuan Desert Rangeland Research Center (CDRRC) pastures 1, 4, 14, and 15: one polygon feature class, one point feature class, associated attribute tables and metadata. The spatial data, CDRRC1_4_14_15_StateMap_v1.gdb.zip, represents the ecological sites and states on Pastures 1, 4, 14 and 15 on the Chihuahuan Desert Rangeland Research Center, and includes field traverse data. CDRRC1_4_14_15_StateMapMetadata.pdf and TraversePointsMetadata.pdf contain the geospatial metadata provided by ArcMap. CDRRC1_4_14_15_StateMap_v1.csv is the attribute table associated with the state map’s polygon feature class, and TraversePoints.xlsx is the attribute table associated with the traverse points feature class and includes a sheet containing detailed attribute metadata.

A point feature layer with the locations and names of street intersections within Stark County, Ohio. This layer was initially developed so that police, fire, and EMS would be able to identify the closest street intersection for emergency calls. Within the attribute table, you will find the names for the intersecting streets; the primary and secondary streets are the only attributes that are populated. This data is a work in progress and will be updated periodically as new streets are added to our data. It is planned for each street intersection point to be eventually filled out for the whole county.

The Windmill Islands 1:50000 dataset details topographic features along a strip of rocky islands about 11 km wide, parallel to the coast and extending north for about 28 km from Vanderford Glacier. The dataset includes five metre interval contours. The dataset also contains penguin colonies.

The data were originally formatted according to the Australian Antarctic Spatial Data Model and are included in the GIS data for the Windmill Islands available for download from a Related URL. The data has been reformatted according to the SCAR Feature Catalogue which superseded the Australian Antarctic Spatial Data Model. Data that are part of this dataset have Dataset_id = 138 in the SCAR Feature Catalogue format. Dataset_id is an attribute in the attribute table. Data quality information for any feature can be searched for at a Related URL by entering the Qinfo number of the feature at the 'Search datasets and quality' tab. Qinfo is an attribute in the attribute table.