Accessibility dashboard for the University of Exeter showing the following features:Campus buildingsAcademic buildingsUniversity accommodationLibrariesStudent's Guild buildingsSports facilitiesOther buildingsAccessibility features (SDG 10)Wheelchair accessible buildingsDisabled parking spacesDisabled toiletsLiftsAccessibility spaces (e.g. AccessAbility rooms, disability support services)Disabled refuge system call pointsWheelchair access rampsGender neutral toiletsHealth and wellbeing features (SDG 3)First aid locationsOutdoor wellbeing spacesDefibrillatorsFire assembly pointsSafer walking routesThe dashboard can be customised to suit an individual user's needs, by toggling the features listed above on and off. This is to allow the map to hold a lot of information and functionality, without being too cluttered upon initial loading. Whilst the map has the potential to become quite busy if all of the feature layers are turned on, the map is not intended to be used in this way, hence why the default is for the map to load with only buildings and safer walking routes visible.By clicking on an individual building or feature, a pop-up containing further information and photographs will appear. For buildings, there will be an option for the user to open Google Maps in a new tab, to allow them to easily navigate to any building from their current location. This was chosen as there is currently not a function within ArcGIS Online Dashboards to allow the user to input their own location for directions, but the dashboard could be updated appropriately if this function became available at a later date. For accessibility and wellbeing features, the pop-ups contain useful information such as the floor the feature is located on, whether there are any booking requirements to use the feature, whether the feature is fully functional, etc. This is to allow users with disabilities to be able to determine which buildings on campus are suitable for them - for example, a user in a wheelchair can click on accessible parking spaces to see whether they are able to get into the building without assistance from the parking space, allowing them to make any necessary arrangements prior to their arrival.Through the use of ArcGIS Web Experience Builder, the dashboard has been customised to automatically change between two layout formats, depending on the user's screen size. This allows for the dashboard to be fully functional for users wanting to navigate the campuses on-the-go, without the need for a large screen size.

This data set should not be considered official. it has not be verified, cleaned, etc. It's sole purpose is to test functionality of Operations Dashboard.

Links to recordings of the Integrated Services Program and 9-1-1 & Geospatial Services Bureau webinar series, including NG9-1-1 GIS topics such as: data preparation; data provisioning and maintenance; boundary best practices; and extract, transform, and load (ETL). Offerings include:Topic: Virginia Next Generation 9-1-1 Dashboard and Resources Update Description: Virginia recently updated the NG9-1-1 Dashboard with some new tabs and information sources and continues to develop new resources to assist the GIS data work. This webinar provides an overview of changes, a demonstration of new functionality, and a guide to finding and using new resources that will benefit Virginia public safety and GIS personnel with roles in their NG9-1-1 projects. Wednesday 16 June 2021. Recording available at: https://vimeo.com/566133775Topic: Emergency Service Boundary GIS Data Layers and Functions in your NG9-1-1 PSAP Description: Law, Fire, and Emergency Medical Service (EMS) Emergency Service Boundary (ESB) polygons are required elements of the NENA NG9-1-1 GIS data model stack that indicate which agency is responsible for primary response. While this requirement must be met in your Virginia NG9-1-1 deployment with AT&T and Intrado, there are quite a few ways you could choose to implement these polygons. PSAPs and their GIS support must work together to understand how this information will come into a NG9-1-1 i3 PSAP and how it will replace traditional ESN information in order to make good choices while implementing these layers. This webinar discusses:the function of ESNs in your legacy 9-1-1 environment, the role of ESBs in NG9-1-1, and how ESB information appears in your NG9-1-1 PSAP. Wednesday, 22 July 2020. Recording available at: https://vimeo.com/441073056#t=360sTopic: "The GIS Folks Handle That": What PSAP Professionals Need to Know about the GIS Project Phase of Next Generation 9-1-1 DeploymentDescription: Next Generation 9-1-1 (NG9-1-1) brings together the worlds of emergency communication and spatial data and mapping. While it may be tempting for PSAPs to outsource cares and concerns about road centerlines and GIS data provisioning to 'the GIS folks', GIS staff are crucial to the future of emergency call routing and location validation. Data required by NG9-1-1 usually builds on data that GIS staff already know and use for other purposes, so the transition requires them to learn more about PSAP operations and uses of core data. The goal of this webinar is to help the PSAP and GIS worlds come together by explaining the role of the GIS Project in the Virginia NG9-1-1 Deployment Steps, exploring how GIS professionals view NG9-1-1 deployment as a project, and fostering a mutual understanding of how GIS will drive NG9-1-1. 29 January 2020. Recording available at: https://vimeo.com/showcase/9791882/video/761225474Topic: Getting Your GIS Data from Here to There: Processes and Best Practices for Extract, Transform and Load (ETL) Description: During the fall of 2019, VITA-ISP staff delivered workshops on "Tools and Techniques for Managing the Growing Role of GIS in Enterprise Software." This session presents information from the workshops related to the process of extracting, transforming, and loading data (ETL), best practices for ETL, and methods for data schema comparison and field mapping as a webinar. These techniques and skills assist GIS staff with their growing role in Next Generation 9-1-1 but also apply to many other projects involving the integration and maintenance of GIS data. 19 February 2020. Recording available at: https://vimeo.com/showcase/9791882/video/761225007Topic: NG9-1-1 GIS Data Provisioning and MaintenanceDescription: VITA ISP pleased to announce an upcoming webinar about the NG9-1-1 GIS Data Provisioning and Maintenance document provided by Judy Doldorf, GISP with the Fairfax County Department of Information Technology and RAC member. This document was developed by members of the NG9-1-1 GIS workgroup within the VITA Regional Advisory Council (RAC) and is intended to provide guidance to local GIS and PSAP authorities on the GIS datasets and associated GIS to MSAG/ALI validation and synchronization required for NG9-1-1 services. The document also provides guidance on geospatial call routing readiness and the short- and long-term GIS data maintenance workflow procedures. In addition, some perspective and insight from the Fairfax County experience in GIS data preparation for the AT&T and West solution will be discussed in this webinar. 31 July 2019. Recording available at: https://vimeo.com/showcase/9791882/video/761224774Topic: NG9-1-1 Deployment DashboardDescription: I invite you to join us for a webinar that will provide an overview of our NG9-1-1 Deployment Dashboard and information about other online ISP resources. The ISP website has been long criticized for being difficult to use and find information. The addition of the Dashboard and other changes to the website are our attempt to address some of these concerns and provide an easier way to find information especially as we undertake NG9-1-1 deployment. The Dashboard includes a status map of all Virginia PSAPs as it relates to the deployment of NG9-1-1, including the total amount of funding requested by the localities and awards approved by the 9-1-1 Services Board. During this webinar, Lyle Hornbaker, Regional Coordinator for Region 5, will navigate through the dashboard and provide tips on how to more effectively utilize the ISP website. 12 June 2019. Recording not currently available. Please see the Virginia Next Generation 9-1-1 Dashboard and Resources Update webinar recording from 16 June 2021. Topic: PSAP Boundary Development Tools and Process RecommendationDescription: This webinar will be presented by Geospatial Program Manager Matt Gerike and VGIN Coordinator Joe Sewash. With the release of the PSAP boundary development tools and PSAP boundary segment compilation guidelines on the VGIN Clearinghouse in March, this webinar demonstrates the development tools, explains the process model, and discusses methods, tools, and resources available for you as you work to complete PSAP boundary segments with your neighbors. 15 May 2019. Recording available at: https://www.youtube.com/watch?v=kI-1DkUQF9Q&feature=youtu.beTopic: NG9-1-1 Data Preparation - Utilizing VITA's GIS Data Report Card ToolDescription: This webinar, presented by VGIN Coordinator Joe Sewash, Geospatial Program Manager Matt Gerike, and Geospatial Analyst Kenny Brevard will provide an overview of the first version of the tools that were released on March 25, 2019. These tools will allow localities to validate their GIS data against the report card rules, the MSAG and ALI checks used in previous report cards, and the analysis listed in the NG9-1-1 migration proposal document. We will also discuss the purpose of the tools, input requirements, initial configuration, how to run them, and how to make sense of your results. 10 April 2019. Recording available at: https://vimeo.com/showcase/9791882/video/761224495Topic: NG9-1-1 PSAP Boundary Best Practice WebinarDescription: During the months of November and December, VITA ISP staff hosted regional training sessions about best practices for PSAP boundaries as they relate to NG9-1-1. These sessions were well attended and very interactive, therefore we feel the need to do a recap and allow those that may have missed the training to attend a makeup session. 30 January 2019. Recording not currently available. Please see the PSAP Boundary Development Tools and Process Recommendation webinar recording from 15 May 2019.Topic: NG9-1-1 GIS Overview for ContractorsDescription: The Commonwealth of Virginia has started its migration to next generation 9-1-1 (NG9-1-1). This migration means that there will be a much greater reliance on geographic information (GIS) to locate and route 9-1-1 calls. VITA ISP has conducted an assessment of current local GIS data and provided each locality with a report. Some of the data from this report has also been included in the localities migration proposal, which identifies what data issues need to be resolved before the locality can migrate to NG9-1-1. Several localities in Virginia utilize a contractor to maintain their GIS data. This webinar is intended for those contractors to review the data in the report, what is included in the migration proposal and how they may be called on to assist the localities they serve. It will still ultimately be up to each locality to determine whether they engage a contractor for assistance, but it is important for the contractor community to understand what is happening and have an opportunity to ask questions about the intent and goals. This webinar will provide such an opportunity. 22 August 2018. Recording not currently available. Please contact us at NG911GIS@vdem.virginia.gov if you are interested in this content.

Clip art of a dashboard. Provided by ESRI Professional services to be used as a button image. This image is a vector illustration of a dashboard icon designed in a thin-line, outline style. Created by A. Shaparenko (2022) and sourced from iStock, the icon represents a simplified and stylized depiction of a dashboard interface. It features a balanced arrangement of gauges, dials, and panel elements, evoking a sense of data visualization and monitoring. The clean, modern aesthetic of the icon makes it well-suited for technology, analytics, and data-driven applications, such as business intelligence, performance tracking, and public health monitoring tools. The minimalist line art style ensures clarity and adaptability across different digital platforms, allowing for easy recognition and integration into various interfaces. This specific image has been provided by ESRI Professional Services and is used as a button image within the opioid dashboard to enhance the visual appeal and functionality of the interface. By incorporating this symbol, the dashboard conveys its purpose of providing users with data-driven insights, real-time analytics, and interactive visualization capabilities to support informed decision-making. For reference, the original artwork is available on iStock: Shaparenko, A. (2022). Dashboard icon outline style. Thin line creative dashboard icon for logo, graphic design and more [Vector illustration]. iStock. Link to image.

Road segments representing centerlines of all roadways or carriageways in a local government. Typically, this information is compiled from orthoimagery or other aerial photography sources. This representation of the road centerlines support address geocoding and mapping. It also serves as a source for public works and other agencies that are responsible for the active management of the road network. (From ESRI Local Government Model "RoadCenterline" Feature)**This dataset was significantly revised in August of 2014 to correct for street segments that were not properly split at intersections. There may be issues with using data based off of the original centerline file. ** The column Speed Limit was updated in November 2014 by the Transportation Intern and is believed to be accurate** The column One Way was updated in November of 2014 by core GIS and is believed to be accurate.[MAXIMOID] A unique id field used in a work order management software called Maximo by IBM. Maximo uses GIS CL data to assign locations to work orders using this field. This field is maintained by the Transportation GIS specialists and is auto incremented when new streets are digitized. For example, if the latest digitized street segment MAXIMOID = 999, the next digitized line will receive MAXIMOID = 1000, and so on. STREET NAMING IS BROKEN INTO THREE FIELDS FOR GEOCODING:PREFIX This field is attributed if a street name has a prefix such as W, N, E, or S.NAME Domain with all street names. The name of the street without prefix or suffix.ROAD_TYPE (Text,4) Describes the type of road aka suffix, if applicable. CAPCOG Addressing Guidelines Sec 504 U. states, “Every road shall have corresponding standard street suffix…” standard street suffix abbreviations comply with USPS Pub 28 Appendix C Street Abbreviations. Examples include, but are not limited to, Rd, Dr, St, Trl, Ln, Gln, Lp, CT. LEFT_LOW The minimum numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 101.LEFT_HIGH The largest numeric address on the left side of the CL segment. Left side of CL is defined as the left side of the line segment in the From-To direction. For example, if a line has addresses starting at 101 and ending at 201 on its left side, this column will be attributed 201.LOW The minimum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 100.HIGHThe maximum numeric address on the RIGHT side of the CL segment. Right side of CL is defined as the right side of the line segment in the From-To direction. For example, if a line has addresses starting at 100 and ending at 200 on its right side, this column will be attributed 200.ALIAS Alternative names for roads if known. This field is useful for geocode re-matching. CLASSThe functional classification of the centerline. For example, Minor (Minor Arterial), Major (Major Arterial). THIS FIELD IS NOT CONSISTENTLY FILLED OUT, NEEDS AN AUDIT. FULLSTREET The full name of the street concatenating the [PREFIX], [NAME], and [SUFFIX] fields. For example, "W San Antonio St."ROWWIDTH Width of right-of-way along the CL segment. Data entry from Plat by Planning GIS Or from Engineering PICPs/ CIPs.NUMLANES Number of striped vehicular driving lanes, including turn lanes if present along majority of segment. Does not inlcude bicycle lanes. LANEMILES Describes the total length of lanes for that segment in miles. It is manually field calculated as follows (( [ShapeLength] / 5280) * [NUMLANES]) and maintained by Transportation GIS.SPEEDLIMIT Speed limit of CL segment if known. If not, assume 30 mph for local and minor arterial streets. If speed limit changes are enacted by city council they will be recorded in the Traffic Register dataset, and this field will be updating accordingly. Initial data entry made by CIP/Planning GIS and maintained by Transportation GIS.[YRBUILT] replaced by [DateBuilt] See below. Will be deleted. 4/21/2017LASTYRRECON (Text,10) Is the last four-digit year a major reconstruction occurred. Most streets have not been reconstructed since orignal construction, and will have values. The Transportation GIS Specialist will update this field. OWNER Describes the governing body or private entity that owns/maintains the CL. It is possible that some streets are owned by other entities but maintained by CoSM. Possible attributes include, CoSM, Hays Owned/City Maintained, TxDOT Owned/City Maintained, TxDOT, one of four counties (Hays, Caldwell, Guadalupe, and Comal), TxState, and Private.ST_FROM Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the From- direction. Should be edited when new CL segments that cause splits are added. ST_TO Centerline segments are split at their intersections with other CL segments. This field names the nearest cross-street in the To- direction. Should be edited when new CL segments that cause splits are added. PAV_WID Pavement width of street in feet from back-of-curb to back-of-curb. This data is entered from as-built by CIP GIS. In January 2017 Transportation Dept. field staff surveyed all streets and measured width from face-of-curb to face-of-curb where curb was present, and edge of pavement to edge of pavement where it was not. This data was used to field calculate pavement width where we had values. A value of 1 foot was added to the field calculation if curb and gutter or stand up curb were present (the face-of-curb to back-of-curb is 6 in, multiple that by 2 to find 1 foot). If no curb was present, the value enter in by the field staff was directly copied over. If values were already present, and entered from asbuilt, they were left alone. ONEWAY Field describes direction of travel along CL in relation to digitized direction. If a street allows bi-directional travel it is attributed "B", a street that is one-way in the From_To direction is attributed "F", a street that is one-way in the To_From direction is attributed "T", and a street that does not allow travel in any direction is attibuted "N". ROADLEVEL Field will be aliased to [MINUTES] and be used to calculate travel time along CL segments in minutes using shape length and [SPEEDLIMIT]. Field calculate using the following expression: [MINUTES] = ( ([SHAPE_LENGTH] / 5280) / ( [SPEEDLIMIT] / 60 ))ROWSTATUS Values include "Open" or "Closed". Describes whether a right-of-way is open or closed. If a street is constructed within ROW it is "Open". If a street has not yet been constructed, and there is ROW, it is "Cosed". UPDATE: This feature class only has CL geometries for "Open" rights-of-way. This field should be deleted or re-purposed. ASBUILT field used to hyper link as-built documents detailing construction of the CL. Field was added in Dec. 2016. DateBuilt Date field used to record month and year a road was constructed from Asbuilt. Data was collected previously without month information. Data without a known month is entered as "1/1/YYYY". When month and year are known enter as "M/1/YYYY". Month and Year from asbuilt. Added by Engineering/CIP. ACCEPTED Date field used to record the month, day, and year that a roadway was officially accepted by the City of San Marcos. Engineering signs off on acceptance letters and stores these documents. This field was added in May of 2018. Due to a lack of data, the date built field was copied into this field for older roadways. Going forward, all new roadways will have this date. . This field will typically be populated well after a road has been drawn into GIS. Entered by Engineering/CIP. ****In an effort to make summarizing the data more efficient in Operations Dashboard, a generic date of "1/1/1900" was assigned to all COSM owned or maintained roads that had NULL values. These were roads that either have not been accepted yet, or roads that were expcepted a long time ago and their accepted date is not known. WARRANTY_EXP Date field used to record the expiration date of a newly accepted roadway. Typically this is one year from acceptance date, but can be greater. This field was added in May of 2018, so only roadways that have been excepted since and older roadways with valid warranty dates within this time frame have been populated.

Feature layer generated from running the Join Features solution

Feature layer generated from running the Join Features solution

The Sidewalk Success Story Dashboard provides an overview of the Ithaca Sidewalk Program, which began in January 2014. This initiative aims to upgrade the city's sidewalks to meet federal accessibility standards while minimizing the costs for individual property owners. The dashboard features an interactive map that allows users to view the progress by SIDs (sidewalk improvement districts) and/or by year, offering a clear picture of the program's impact and ongoing efforts to enhance accessibility throughout Ithaca.

Feature layer generated from running the Join Features solution

Explore and interact with different layers to better understand the green and healthy movement in Wisconsin K-12 schools. This dashboard features Green & Healthy Schools data, partner information, WI school information and climate change related layers that help decision-makers better understand school's needs. This dashboard is featured on the Green & Healthy Schools website and allows the public to interact with data collected. The dashboard was last updated on March 18th, 2025. Zoom in on the map or use the search bar to find your own school and what we know about your school. Explore the map to get inspired by other schools are partnering with providers.

Impact Summary is a configurable app template which highlights an area and shows a summary of data related to its location. Use CasesPresents the impact of an event or a proposal on the local population.The data presented in the boxes, at the bottom of the map, can be any integer data allowing you to answer new questions about locations that you cannot answer with maps alone. For instance, in the web map you could enrich your polygon with demographics, landscape, infrastructure, and other variables using Enrich Layer or analyze your own data with Aggregate Points. Then you can use this template to show your analysis with a simple web mapping application.Configurable OptionsThe template can be configured using the following options:Map: Choose the web map used in your application.Mobile/Embed: A responsive side drawer is shown depending on the size available and can be toggled by the user.Navigation: Home and Geo-locate buttons add ease of map navigation.Content: Summarize integer data by choosing a Feature layer containing the fields. A layer containing multiple features and has a renderer defined allows for selecting the features by the renderer values. An interactive dashboard provides ability to categorize fields in up to 4 group panels and page through the fields.Summary: Briefly describe your application in the Area panel.Search: Enable Search for addresses and places.Share: Enable sharing using Twitter or FacebookData RequirementsThis application requires a feature layer with at least one numeric field. For more information, see the Layers help topic for more details.This app also includes the ability to geoenrich data as an alternative to providing your own numeric data. This option requires an ArcGIS Organization or ArcGIS developers Subscription and consumes credits.Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

Feature layer generated from running the Join Features solution for the Council Districts Infographic's Dashboard.

Feature layer generated from running the Join Features solution

Includes point locations that provide support services for water, stormwater, sewer, medical care, transportation, law enforcement and emergency operations, and other critical functions.

Feature layer generated from running the Join Features solution

Feature layer generated from running the Join Features solution was configured and published as part of the Yosemite Observer Physical Science Dashboard project. Funded by a grant from the Yosemite Conservancy, the Yosemite Observer Dashboard was published in 2023 with the goal of connecting the public with the important work of physical scientists and landscape ecologists at Yosemite National Park. The dashboard is maintained by the Yosemite Physical Sciences and Landscape Ecology Branch of Resource Management and Science.IRMA Data Store Reference

Feature layer generated from running the Join Features solution City limits with a CSV that contains Infographics and PDF URL's.This item feeds the first tab in the Dallas Council Districts Dashboard

This feature layer provides access to OpenStreetMap (OSM) point of interest (POI) data for Europe, which is updated periodically with the latest edits. This hosted feature layer view is referencing a hosted feature layer of OSM point (node) data in ArcGIS Online that is updated with minutely diffs from the OSM planet file. This feature layer view includes POI features defined as a query against the hosted feature layer for amenity, shop, and tourism, features (e.g. amenity is not blank or shop is not blank or tourism is not blank).Note: due to the size of data and volume of edits, the OSM layers for Europe currently reflect edits made within the last 30 days.In OSM, an amenity is a useful and important facility for visitors and residents, such as places of worship or school, and a shop is a place selling retail products or services, such as a supermarket or florist. Tourism features are places and things of specific interest to tourists including places to see, places to stay, things and places providing information and support to tourists. These features are identified with an amenity tag, shop tag, or tourism tag.Zoom in to large scales (e.g. Cities level or 1:160k scale) to see the POI features display. You can click on the feature to get the name of the POI. The name of the POI will display by default at very large scales (e.g. Building level of 1:2k scale). Labels can be turned off in your map if you prefer.Create New LayerIf you would like to create a more focused version of this POI layer displaying just one or two types, you can do that easily! Just add the layer to a map, copy the layer in the content window, add a filter to the new layer (e.g. amenity is bar or shop is alcohol), rename the layer as appropriate, and save layer. You can also change the layer symbols or popup if you like. Esri may publish a few such layers that are ready to use, but not for every type of POI.Important Note: if you do create a new layer, it should be provided under the same Terms of Use and include the same Credits as this layer. You can copy and paste the Terms of Use and Credits info below in the new Item page as needed.