This draft data is being submitted to FEMA to update the National Flood Hazard Layer (NFHL) and Flood Insurance Rate Maps (FIRMs). It is subject to change until FEMA issues the final data. The Layer is symbolized by the field, "ZONE_SUBTY" showing the following:"1% Annual Chance Flood Hazard" = blank and null values"Future Conditions 1% Annual Chance Flood Hazard" = 0300"0.2% Annual Chance Flood Hazard" = 0500"Regulatory Floodway" = 1100Workspace: \srvrgisfs1-1\gisdata\WebApps\WSE_DraftFloodplainViewer\DraftFloodplainViewer_CloudSource data: Database Connections\OS@gisAncillary@gissql.sde\gisAncillary.DBO.AppData\Published in Feb 2023 by the GIS Team to update the symbology. Published to ArcGIS Online Cloud

The establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making. BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions. Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself. For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise. Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer. This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery. See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt

Intermodal Passenger Connectivity DatabaseThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the Bureau of Transportation Statistics (BTS), displays the Intermodal Passenger Connectivity Database (IPCD). According to BTS, IPCD is a "nationwide database of passenger transportation terminals, with data on the availability of connections among the various scheduled public transportation modes at each facility." The types of passenger transportation terminals include:Scheduled airline service airportsIntercity bus stationsIntercity and transit ferry terminalsLight-rail transit stationsHeavy-rail transit stationsPassenger-rail stationsBike-share stationsThe data describes the availability and locations of the above types of passenger transportation terminals. Note, transit bus service locations are not specifically included.Collins Avenue 5300 Block (Miami Beach, FL)Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Intermodal Passenger Connectivity Database IPCD) and will support mapping, analysis, data exports and OGC API – Feature access.Data.gov: Intermodal Passenger Connectivity Database (IPCD) (National) - National Geospatial Data Asset (NGDA) Intermodal (Passenger)Geoplatform: Intermodal Passenger Connectivity Database (IPCD) (National) - National Geospatial Data Asset (NGDA) Intermodal (Passenger)OGC API Features Link: (Intermodal Passenger Connectivity Database - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information: Intermodal Passenger Connectivity Database IPCDFor feedback please contact: Esri_US_Federal_Data@esri.comThumbnail image courtesy of: Metropolitan Transportation Authority of the State of New YorkNGDA Data SetThis data set is part of the NGDA Transportation Theme Community. Per the Federal Geospatial Data Committee (FGDC), Transportation is defined as the "means and aids for conveying persons and/or goods. The transportation system includes both physical and non-physical components related to all modes of travel that allow the movement of goods and people between locations".For other NGDA Content: Esri Federal Datasets

The pathway representation consists of segments and intersection elements. A segment is a linear graphic element that represents a continuous physical travel path terminated by path end (dead end) or physical intersection with other travel paths. Segments have one street name, one address range and one set of segment characteristics. A segment may have none or multiple alias street names. Segment types included are Freeways, Highways, Streets, Alleys (named only), Railroads, Walkways, and Bike lanes. SNDSEG_PV is a linear feature class representing the SND Segment Feature, with attributes for Street name, Address Range, Alias Street name and segment Characteristics objects. Part of the Address Range and all of Street name objects are logically shared with the Discrete Address Point-Master Address File layer. Appropriate uses include: Cartography - Used to depict the City's transportation network location and connections, typically on smaller scaled maps or images where a single line representation is appropriate. Used to depict specific classifications of roadway use, also typically at smaller scales. Used to label transportation network feature names typically on larger scaled maps. Used to label address ranges with associated transportation network features typically on larger scaled maps. Geocode reference - Used as a source for derived reference data for address validation and theoretical address location Address Range data repository - This data store is the City's address range repository defining address ranges in association with transportation network features. Polygon boundary reference - Used to define various area boundaries is other feature classes where coincident with the transportation network. Does not contain polygon features. Address based extracts - Used to create flat-file extracts typically indexed by address with reference to business data typically associated with transportation network features. Thematic linear location reference - By providing unique, stable identifiers for each linear feature, thematic data is associated to specific transportation network features via these identifiers. Thematic intersection location reference - By providing unique, stable identifiers for each intersection feature, thematic data is associated to specific transportation network features via these identifiers. Network route tracing - Used as source for derived reference data used to determine point to point travel paths or determine optimal stop allocation along a travel path. Topological connections with segments - Used to provide a specific definition of location for each transportation network feature. Also provides a specific definition of connection between each transportation network feature. (defines where the streets are and the relationship between them ie. 4th Ave is west of 5th Ave and 4th Ave does intersect with Cherry St) Event location reference - Used as source for derived reference data used to locate event and linear referencing.Data source is TRANSPO.SNDSEG_PV. Updated weekly.

The Intermodal Passenger Connectivity Database (IPCD) dataset was compiled on August 10, 2021 and was updated October 19, 2022 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The IPCD is a nationwide database of passenger transportation terminals, with data on the availability of connections among the various scheduled public transportation modes at each facility. IPCD is no longer being updated, the latest information is from 2022. The IPCD data covers the following types of passenger transportation terminals/stops: 1. Scheduled airline service airports. 2. Intercity bus stations (includes stations served by regular scheduled intercity bus service such as Greyhound, Trailways, code sharing buses such as Amtrak Thruway feeder buses, supplemental buses that provide additional frequencies along rail routes, and airport bus services from locations that are outside of the airport metropolitan area). 3. Intercity and transit ferry terminals. 4. Light-rail transit stations. 5. Heavy-rail transit stations. 6. Passenger-rail stations on the national rail network served by intercity rail and/or commuter rail services. 7. Bikeshare stations belonging to bikeshare systems that are open to the general public, IT-automated, and station based (contain hubs to which users can grab and return a bike). The bikeshare stations only include those from the latest IPCD data collection in 2022. Please consult the latest bikeshare layer (https://doi.org/10.21949/1522020) for the most current information. The IPCD includes data elements describing the location of the above types of terminals as well as the availability of intercity, commuter, and transit rail; scheduled air service; intercity and transit bus; intercity and transit ferry services; and bikeshare availability. Transit bus service locations are not specifically included in the database. However, the status of transit bus as a connecting mode is included for each bikeshare facility in the database. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529035

The California Natural Resources Agency’s Access for All Initiative and 30x30 set a goal of equitable access for all to the state’s natural and open spaces. This dashboard helps illustrate the current challenges and highlights opportunities.

The Access Explorer shows statewide measures of the population living within a half mile of any open space such as a park with public access contained within the Conserved Areas database, whether it meets the 30x30 definition of conserved or not.

You can then compare those measures to areas that meet the 30x30 definition or to the population overall.

The Access Explorer is a work in progress. Enhancements will be informed by an Outdoors for All roadmap due out in early 2023.

The demographics were compiled from 'https://doc.arcgis.com/en/esri-demographics/' target='_blank' rel='nofollow ugc noopener noreferrer'>ESRI Demographics in March 2022.

Background HealthCyberMap aims at mapping parts of health information cyberspace in novel ways to deliver a semantically superior user experience. This is achieved through "intelligent" categorisation and interactive hypermedia visualisation of health resources using metadata, clinical codes and GIS. HealthCyberMap is an ArcView 3.1 project. WebView, the Internet extension to ArcView, publishes HealthCyberMap ArcView Views as Web client-side imagemaps. The basic WebView set-up does not support any GIS database connection, and published Web maps become disconnected from the original project. A dedicated Internet map server would be the best way to serve HealthCyberMap database-driven interactive Web maps, but is an expensive and complex solution to acquire, run and maintain. This paper describes HealthCyberMap simple, low-cost method for "patching" WebView to serve hypermaps with dynamic database drill-down functionality on the Web. Results The proposed solution is currently used for publishing HealthCyberMap GIS-generated navigational information maps on the Web while maintaining their links with the underlying resource metadata base. Conclusion The authors believe their map serving approach as adopted in HealthCyberMap has been very successful, especially in cases when only map attribute data change without a corresponding effect on map appearance. It should be also possible to use the same solution to publish other interactive GIS-driven maps on the Web, e.g., maps of real world health problems.

This is a detailed GIS database of public access locations (point features) along coastal shorelines. It contains a rich variety of information such as amenities (boat launches, toilets, ADA accessible, etc.) and activities (tidepooling, hiking, shellfishing, etc.) that are available at each access point.The information was collected using a GPS in the field between 2008-2010 and is updated as resources allow.For more information, contact Christina Kellum, Washington State Department of Ecology GIS Manager, gis@ecy.wa.gov.

Tempe Census Census Tracts and internet access by household. Data source: U.S. Census Bureau, 2013-2017 American Community Survey 5-Year Estimates, table BD28011 (Internet Subscription in Household). Also includes "low response scores" from the the Census Bureau's data from the 2018 Planning Database (PDB), which was established to prepare for the upcoming 2020 Census.For more information on the low response score, see the United States Census Bureau 2018 Planning Database:https://www.census.gov/topics/research/guidance/planning-databases.htmlLayer generally supports 2020 Census story map Ensuring a Complete Count in the 2020 Census.

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.

The Digital Geologic-GIS Map of Olympic National Park and Vicinity, Washington is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (olym_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (olym_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (olym_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (olym_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (olym_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (olym_geology_metadata_faq.pdf). Please read the olym_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Washington Division of Geology and Earth Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (olym_geology_metadata.txt or olym_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

DownloadA daily extract of the NPDES Structures dataset is available for download as a zipped file geodatabase.BackgroundAs a government agency that owns and maintains separate storm sewer systems, the Maryland State Highway Administration (SHA) is mandated to file a National Pollutant Discharge Elimination System (NPDES) permit with the Maryland Department of the Environment (MDE). The permit requires the inventory, inspection, and maintenance of SHA stormwater infrastructure. SHA is responsible for maintaining storm drain infrastructure on more than 5,000 miles of roadway statewide. SHA has developed a program consisting of SHA personnel, data managers, and subject matter experts to support the permit requirements and maintain these roadways. The tasks involved in the SHA NPDES data collection program are often completed by engineering consultants for SHA. The data are organized into a series of drainage systems with stormwater management facilities that are interconnected, allowing for flow-tracing function through distinct systems. A drainage system is defined as a series of storm drain structures or point features (i.e., manholes, inlets, endwalls) that connect hydraulically through conveyance features such as pipes and / or ditches. Closed and open storm drain structures are connected by pipe and ditch conveyance to create the drainage system. Stormwater management facilities (SWMF), also known as stormwater best management practices (BMP) are inventoried with the storm drain system. A system can include both open and closed storm drain features. StructuresPhysical stormwater structures to be identified and inventoried include headwalls, endwalls, cross culverts, pumping stations, stormwater risers and weirs, inlets, pipe connections, and manholes. Storm drain structures are represented as point features in the database. Several database features are included that are not existing physical structures, but are employed to facilitate connection of drainage systems in the database. For detailed descriptions of each feature, refer to the SHA Book of Standard for Highway & Incidental Structures, Category 3 “Drainage.” Storm drain structures within SHA ROW are inventoried. Information on private storm drain structures will need to be collected if a private system ties into SHA-owned storm drain features. The only structures that are not inventoried within SHA ROW are single residential driveway culvert end structures (See below for more details), bridge inlets, under drains, roof drainage, or other private tie-ins with the exception of the first or last structure from a private storm drain system and curb opening. If an under-drain pipe has an end structure (such as an endwall), then the structure is inventoried. Curb openings are only inventoried when affecting the drainage area for a BMP or major outfalls. If it is deemed necessary to include a curb cut in the database, the curb cut is captured as an inlet feature with comments identifying the feature as a curb opening. A curb opening is not a COG or COS inlet with an open back, but simply a cut in the curb where sheet flow is exiting impervious. The following are brief discussions of the structures in the data. See Chapter 2 of the Maryland SHA Stormwater NPDES Program SOP for more information, figures, and descriptions of each field. End / Head StructuresAn end / head structure is any structure at the upstream or downstream end of a culvert or pipe. These can include headwalls, endwalls, end sections, and projection pipes. Often the end / head structure is designated on the contract sheets and field verified. When contract plans are not available for a roadway, the SHA Book of Standard for Highway & Incidental Structures should be referenced if structure types are unfamiliar with field teams. Outfall areas are not to be inventoried, but will be analyzed during the inspection process. Headwalls (HW) are structures that are placed at the upstream end of pipes and culverts to provide a stable or hydraulically desirable entrance to the conveyance. Headwalls are usually concrete but can be constructed of wood or masonry, such as brick or concrete block. Wall structures on the upstream side of a culvert or pipe are inventoried as headwalls. Plan sheets may designate the upstream end of a pipe or culvert as an endwall, but these structures should be inventoried as headwalls. All wall-end structures at the upstream end of a pipe or culvert should be inventoried as headwalls. Endwalls (EW) are structures that are placed at the downstream end of pipes and culverts to provide a stable or hydraulically desirable exit to the conveyance. Endwalls are usually concrete, but can be constructed of wood or masonry such as brick or concrete block. All wall structures on the downstream side of a culvert or pipe are inventoried as endwalls. Plan sheets may designate the downstream end of pipe or culvert as a headwall, but these structures should be inventoried as endwalls. All wall-end structures at the downstream end of a pipe or culvert should be inventoried as endwalls. End Sections (ES) are structures that transition the ends of pipes into slopes and provide stability to the pipe entrances and outflows. End sections do not affect the hydraulic capacity or efficiency of the pipes. End sections can be constructed of concrete, metal, or plastic (HDPE). End sections can either be inventoried at the upstream or downstream end of a pipe. Projection Pipes (PP) are not physical structures but represent the upstream and downstream end of a pipe if an end structure on a pipe does not exist. Projection pipes are captured spatially as a feature and represent the ends of pipes. Inlet StructuresInlets are structures that collect storm drain runoff. Inlets convey the runoff to closed storm drain systems, open conveyance, or outfalls. There are many different types of inlet structures, and all are discussed in the SHA Standard Design Manual and should be reviewed prior to conducting an inventory. Spring heads are also inventoried as inlets. Inlets (IN) are hydraulic structure chambers below surface grade that collect storm drain runoff. An inlet either has a grate or open sides / curb to allow runoff to enter the storm drain system. Inlets are often constructed of concrete, masonry brick, or concrete block. Spring Heads (SH) are inventoried as inlets. Spring heads are inventoried only where they emerge and are connected to a storm drain system. Spring heads are inventoried because they provide evidence for the presence of ground water for dry weather flows during illicit discharge field screening operation. Spring heads may be identified from contract drawings or identified during the field inventory. Spring heads are mostly found in rural areas. Connection StructuresA connection structure is a storm drain structure that connects conveyance (pipes and ditches) within a system and is not an inlet, riser, weir, or pumping station. These can include manholes, ditch intersections, junction boxes, pipe connections, wye connections, capped inlets, pipe bends, and pipe directions. Because field crews are not required to open manhole lids and enter closed storm drain structures, no designation type is necessary for connection structures. All of the attribute data for these structures will be collected from contract drawings, including connection material and top of manhole elevations. The existence of connection structures should be field verified for spatial accuracy, even though the attributed data will be collected from contract drawings. For structures that are buried or paved over, a GPS point is to be recorded at the best estimated location in the field based on contract plan sheets. The verification of attribute table data for structures that cannot be verified in the field will be completed based on plan sheet information. This also holds true for structures that are buried or cannot be accessed; the attribute data should be obtained from plan sheets. Manholes (MH) are hydraulic structures that connect pipes through a system. They are used as access points to a system, to change direction or invert elevations for pipes, as a junction to change pipe size and / or material, and as a junction of multiple pipes to a single pipe. Manholes are frequently paved over or buried, but are still inventoried. Unless it is certain that the manhole does not exist, the manhole is inventoried. Manholes with lids that have designed holes to allow runoff to enter are inventoried as manholes and not inlets. Ditch Intersections (ID) are geographic representations of where ditches meet, begin, or end a system and are captured as point features. These features are used to define the extents of ditches. Junction Boxes (JB) are underground hydraulic structures that connect pipes through a system. They are used to change direction or invert elevations for pipes, to change pipe size and / or material, and to connect multiple pipes to a single pipe. Identifying junction boxes in the field is difficult because these structures are usually buried with no part of the structure exposed to the surface. Junction boxes are only inventoried from contract drawings and should never be assumed in the field, unless the field crew is certain the structure is a junction box. If the field crew suspects that pipes are merging together and no contract plans are available to confirm this, the connection should be inventoried as a pipe connection and not a junction box. Pipe Connections (PC) are locations throughout the conveyance of a system where two or more pipes connect. A pipe connection is also captured at the location where a closed storm drain pipe connects to a culvert or stream crossing. Wye Connections (YC) are hydraulic structures that join two pipes together within a system’s conveyance. Wye connections will be identified from contract drawings and should not be assumed in the field. Instead of assuming a wye

The IPCD is as of July 03, 2018 and is a nationwide database of passenger transportation terminals, with data on the availability of connections among the various scheduled public transportation modes at each facility. The IPCD data covers the following types of passenger transportation terminals/stops: 1. Scheduled airline service airports. 2. Intercity bus stations (includes stations served by regular scheduled intercity bus service such as Greyhound, Trailways, code sharing buses such as Amtrak Thruway feeder buses, supplemental buses that provide additional frequencies along rail routes, and airport bus services from locations that are outside of the airport metropolitan area). 3. Intercity and transit ferry terminals. 4. Light-rail transit stations. 5. Heavy-rail transit stations. 6. Passenger-rail stations on the national rail network served by intercity rail and/or commuter rail services. 7. Bike-share stations belonging to bike-share systems that are open to the general public, IT-automated, and station based (contain hubs to which users can grab and return a bike) The data elements describe the location of the above types of terminals as well as the availability of intercity, commuter, and transit rail; scheduled air service; intercity and transit bus; intercity and transit ferry services; and bike-share availability. Transit bus service locations are not specifically included in the database. However, the status of transit bus as a connecting mode is included for each bike-share facility in the database.

The ZIP file consist of GIS files and an Access database with information about the excavations, findings and other metadata about the archaeological survey.

SSURGO consists of spatial data and a comprehensive relational database with tables that describe soil properties, interpretations and productivity values. The USDA Natural Resources Conservation Service (NRCS, formerly Soil Conservation Service) provides a download of the statewide SSURGO database that includes vector and raster spatial data, database tables and their relationship classes, and a user guide. To access SSURGO, go to the USDA NRCS Geospatial Data Gateway. To download the database, on the right side of the page, click on the Direct Data Download link under, I Want To... The Direct Data / NAIP Download page will then open. Click on the Soils Geographic Databases link. Then click on the folder named gSSURGO by State (date in folder name). Scroll through the list and select gSSURGO_NJ.zip. Then click on the Download button on the upper right. A message will open that Your Download is In Progress. You will then be prompted to select a file download location.

The IPCD is as of July 03, 2018 and is a nationwide database of passenger transportation terminals, with data on the availability of connections among the various scheduled public transportation modes at each facility. The IPCD data covers the following types of passenger transportation terminals/stops: 1. Scheduled airline service airports. 2. Intercity bus stations (includes stations served by regular scheduled intercity bus service such as Greyhound, Trailways, code sharing buses such as Amtrak Thruway feeder buses, supplemental buses that provide additional frequencies along rail routes, and airport bus services from locations that are outside of the airport metropolitan area). 3. Intercity and transit ferry terminals. 4. Light-rail transit stations. 5. Heavy-rail transit stations. 6. Passenger-rail stations on the national rail network served by intercity rail and/or commuter rail services. 7. Bike-share stations belonging to bike-share systems that are open to the general public, IT-automated, and station based (contain hubs to which users can grab and return a bike) The data elements describe the location of the above types of terminals as well as the availability of intercity, commuter, and transit rail; scheduled air service; intercity and transit bus; intercity and transit ferry services; and bike-share availability. Transit bus service locations are not specifically included in the database. However, the status of transit bus as a connecting mode is included for each bike-share facility in the database. Metadata

The Bikeshare dataset was compiled on June 30, 2025 and was updated September 17, 2025 from the Bureau of Transportation Statistics (BTS) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The bikeshare layer shows the location of all bikeshare docking stations, along with their address if known and the city and state it is located in. Prior to April 30, 2025, this bikeshare layer reflected the bikeshare stations available for the latest Intermodal Passenger Connectivity Database (IPCD) data collection along with intermodal passenger connectivity information. To provide this timelier snapshot of bikeshare stations, the Bureau of Transportation Statistics is no longer including connectivity information. To obtain the previously provided IPCD Bikeshare layer on NTAD for the latest only bikeshare year that included connectivity information, query the current IPCD layer on NTAD (https://doi.org/10.21949/1522239) using the query where the “BIKE_SHARE” field is equal to 1, signifying that bikeshare service is provided at that location. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529012

SWDC 3Waters Asset Data exported out of Master database weekly at Wellington Water Ltd (WWL). Height levels are in terms of NZVD2016 as of 1 July 2022.*This Federated Feature Service references our data in an Enterprise geodatabase (egdb) which is updated weekly via FME workbench from InfoAsset. It has limited symbology and includes Abandoned, removed & virtual assets. It's purpose is so that staff can access the raw data which is updated weekly. They can add it to their Ar Pro projects and it allows them to view the attribute tables & change symbols. It's other purpose is so that councils and the public can download the data form our Open Data Portal. It is only shared with our organisation in Enterprise because we dont want the public to use it as it is hosted on "our" server which is not as robust as the ESRI server. Also, if it's shared with the public, it may slow down the service for our staff. So every week it is copied to AGOL as a Hosted Feature Service which is shared with the public and our Open Data Portal.

Essential Facilities map service is published to GISPortal for various APPs such as WebEOC, Hurrtrak. Map service published on September 1, 2020.

FC was created and is maintained by BSO GIS Unit as a single source of facilities deemed essential by BSO. Used in apps & map services (i.e. POI). Useful for retrieving DLE Stations; Fire Stations; Jails; all BSO essential facilities. Useful in EOC, RTCC.Date Updated: 4/24/2020 Source: N/AMODIFICATIONS: removed HOSPITALrecs (EFCLASS=MEDICAL); added new BLDGTYPE "BSO DLE SUB STATION"; REFER TO Documentation.Coordinates: GCS_WGS_1984 Documentation: Update Essential Facilities Feature Class.docx .docx http://bsoteams.sheriff.bso/itd/gis/DOCS/ADMINISTRATION/Data%20Management/Data%20Source%20Updates/EssentialFacilities/

Mxd Location: \app2016share\MXD\AGENCYWIDE\Essential_Facilities.mxd

Data Type: SDE Feature Class Database Platform: SQL Server Server: GEODB Connection Properties: GEODB Authentication Type: Database authentication User name: gis Database: GIS Version: sde.DEFAULT Description: Instance default version. Feature Class: GIS.BSO.EssentialFacilitiesBSO Feature Type: Simple Geometry Type: Point Coordinates have Z values: No Coordinates have measures: No

Geographic Coordinate System: GCS_WGS_1984 Datum: D_WGS_1984 Prime Meridian: Greenwich Angular Unit: Degree

Computer sessions are counted using software. EnvisionWare Computer Access and Reservation System allows library patrons to schedule time to use library computers. In addition, the Envisionware Database tracks the number of print jobs by user and printer. This functionality allows DCPL to track the number of sessions, hours of usage at each DCPL computer workstation, and the number of print jobs and pages at each printer. The output of this EnvisionWare system is a dataset that tracks the number of unique computer sessions, total hours of computer usage, printer sessions, and printer usage at each DCPL workstation by user account. The dataset includes personally identifiable information (PII) of users.WiFi sessions are also counted using software. Cisco-Meraki Wi-Fi system allows library patrons to connect to DCPL Wi-Fi. This functionality allows DCPL to track the number of wireless devices connected to DCPL Wi-Fi. The output of this Cisco-Meraki Wi-Fi system is a dataset that tracks the number Wi-Fi connections at each DCPL Branch.Gate counts are tracked Vea Web is a database system that tracks the number of entries into each library facility using heat sensors on the door of each facility. This functionality allows DCPL to track the volume of library entries at each DCPL branch every hour. The output of this Vea Web database system is a dataset that is used to report branch visits.