SUGAR ACCESS USER GUIDE

Transcription

1 SUGAR ACCESS USER GUIDE

2 Contents WHAT WOULD YOU LIKE TO DO?... 3 WHAT IS SUGAR ACCESS?... 4 Sugar Launch Pad... 4 Sugar Network Editor... 4 INSTALLATION AND SETUP... 5 RUNNING YOUR FIRST ACCESSIBILITY ANALYSIS... 9 UNDERSTANDING SUGAR ACCESS DATA Analysis Location Data (Demographic Zones) Roadway and Pedestrian Network Public Transport Network Points of Interest Data WHAT S AN ACCESS SCORE? Special Considerations of Analyzing Specific Travel Modes Pedestrian Level of Service Bicycle Level of Service CALCULATING NON-WORK ACCESSBILITY Access Score Non-Work Tutorial UNDERSTANDING YOUR RESULTS Viewing Results in ArcGIS Online Viewing Results in ArcGIS Desktop Access Score Work/ Open Access Score Destination Summation Access Score Non-Work Open Access Score Travel Time Scenario Analyzer Creating an Accessibility Map Summary Table Input Summary LEVERAGING OPEN ACCESS SCORE Open Access Score Tutorial EDITING YOUR MULTIMODAL NETWORK Editing/updating roadway links Adding new roadway links Editing/updating public transport lines/routes SUGAR ACCESS CAPABILITIES ACCESS SCORE WORK ACCESS SCORE NON-WORK OPEN ACCESS SCORE POI SUMMARY... 46

3 POI SUMMARY TUTORIAL SCENARIO ANALYZER SCENARIO ANALYZER TUTORIAL GLOSSARY Here GTFS Lookup Tables for Updating Roadway Links Turn Penalty/Prohibition File Sugar Access Time Periods Destination Scoresheet Travel Time Decay Curves Appendix Pedestrian Level of Service Lookup... 0 Bicycle Level of Service Lookup... 1

4 WHAT WOULD YOU LIKE TO DO? The Basics Install Sugar Access What is Sugar Access? Learn more about the methodology behind Sugar Access (PDF Download) Learn the specifics about Sugar Access Applications Learn about the data included with Sugar Access Learn to edit your multimodal transportation network Run an Accessibility Analysis Follow along with the introduction to Sugar Access Video (Video Link) Measure access to jobs in your area (Access Score Work) Measure Access to non-work destinations in your area (Access Score Non-Work) Calculate the minimum travel time to a destination of interest How do I interpret my results? How do I compare the accessibility of two scenarios?

5 WHAT IS SUGAR ACCESS? Sugar Access is an ArcGIS add-in used to score and understand a community s accessibility to employment opportunities, daily errands, public services, and other points of interest. Sugar Access should be used to not only measure today s accessibility, but also for scenario planning, to quickly test and compare proposed changes to your city s transportation and land-use. A license to Sugar Access gives users access to the following tools within their ArcGIS desktop platform: Sugar Launch Pad The Sugar Launch Pad is an accessibility scenario builder for a user. Here, the user can ask their question about local accessibility; How many jobs are accessible by transit? What s the minimum travel time to walk to a school? The Launch Pad features five different applications to help a user succeed in answering their local accessibility questions: Access Score Work Access Score Non-Work Open Access Score POI Summary Scenario Analyzer Within the Launch Pad, the user can run the different accessibility applications and monitor the run status as they are uploaded to Sugar Access cloud processor, processed, and ready for download to the user s local desktop. For more details about the Launch Pad and its different applications, please see the following section. Sugar Network Editor The Sugar Network Editor is a tool to help users edit their roadway and public transportation networks. Sugar Access network data is formatted in Citilabs proprietary geodatabase format. This allows for a true multi-modal network to be conveyed when bringing together both the roadway and public transportation networks. To edit this network, the Sugar Network Editor tool must be used. The tool has the following capabilities for editing networks: Editing/updating roadway links Adding new roadway links Splitting roadway links Editing/updating public transport lines/routes Adding new public transport lines/routes

6 INSTALLATION AND SETUP Sugar Access is available for download from the Citilabs server: Download Sugar Installation Instructions 1. Once the software has been downloaded, run the.exe setup application 2. The license for Sugar may also be installed at this time by running the.exe setup application in the license folder 3. After the installation is complete you will see the following: Setup Instructions Once Sugar and your license are installed: 1. Run ArcMap 2. Enable the "Sugar" extension (from ArcMap), click "Customize" > "Extensions":

7 3. Select "Sugar" (if not already selected) 4. You should now see a "Sugar" menu item, select "Sugar" > "Sugar Launch Pad" 5. Log in with your Launch Pad account. An account is required in order to run Sugar Access apps on the Cloud. Please contact Citilabs if you need account information. 6. You should now have a docking window for Sugar Launch Pad (undock / resize as required):

8 7. Before running any Sugar Access apps, you will need to enter your username and password for ArcGIS Online. A user account is required to publish result map feature services to ArcGIS Online. Follow the steps shown below to enter this information.

9 If you do not have an account, please contact your ArcGIS Online Organization administrator. ESRI can assist with establishing an ArcGIS Online Organization if necessary. 8. Within the Sugar Launch Pad Settings window, you can also select your download folder. This will be your local folder in which all scenarios that are ran will be downloaded to.

10 RUNNING YOUR FIRST ACCESSIBILITY ANALYSIS Sugar Access is an out-of-the-box accessibility analysis tool. In doing so, you should be able to run your first accessibility analysis within minutes of getting set up within the Sugar Access platform. This tutorial can also be followed through the Introduction to Sugar Access Video. Let s get started! For this analysis, we will be looking at accessibility to jobs using public transport during the morning. 1. Within the Sugar Launch Pad, there are five applications to choose from for running our accessibility analysis. The easiest way to analyze access to jobs is through the Access Score Work application. Let s select that application from the Launch Pad: 2. Select an analysis location feature class The analysis location field is where you select the land-use data which will be used for your access to jobs analysis. You may browse to the specific feature class within your local geodatabase, provided to you with your license to Sugar Access. Once the geodatabase is highlighted, select the feature class which contains employment/job information and click open. What s a valid analysis location feature class? 3. Select the destination to measure access to You will notice that once a valid feature class is selected that a dropdown menu will be available to choose from. The menu is generated from the field names of the feature class that you had selected for the analysis location. Select Jobs from the dropdown menu:

11 4. Select a time period Select Morning-Peak to analyze accessibility during the AM peak period. This will affect the public transport schedule that is being used for the accessibility analysis. What times are used for these different time periods? 5. Select a mode of travel Select Transit to analyze accessibility using only walking and public transport. Your Launchpad window should look show the following selections thus far: 6. Select a roadway network The roadway network parameter is a reference to the local roadway network feature class for your analysis location. This network is contained within your local geodatabase from Sugar Access. Highlight the HWNetwork and click Open. Where does the local hwnetwork come from?

12 7. Select a transit network The transit network parameter is a reference to the local transit feature class for your analysis location. This network is also contained within your local geodatabase from Sugar Access. Highlight ptlines and click open. Where does the local transit network come from? 8. Select a turn penalty file The turn penalty file is an automatically generated for the local roadway network from Here. The turn penalty file should be located within the same zip file as your local geodatabase. Browse for the turn penalty file and click open. What is a turn penalty file? 9. Select an average walk speed The default walk speed within Sugar Access is set to 3.1 mph. This may be changed by the user, as they desire. We will leave it as 3.1 mph for this accessibility analysis. Remember, with a transit accessibility analysis, we are not only analyzing the transit network but also the walk network to the transit stops, so this field is important. 10. Select an average cycling speed This does not affect our transit analysis, so we will leave it as the default.

13 11. Upload to ArcGIS Online Sugar Access gives the user ability to automatically upload their accessibility analysis and maps to the user s ArcGIS Online account for sharing. To do so, the user must enter valid ArcGIS Online credentials within the Launch Pad settings, as well as having publishing privileges within their ArcGIS Online organization. Questions about publishing to ArcGIS Online? 12. Custom lookup table for value of time Sugar Access Access Scores do not treat every minute of travel time equally. To do so, we use decay curves to penalize longer trips, i.e. a job 15 minutes away will be more valuable than a job 30 minutes away. In this case, we will leave the parameter blank, and use the default decay curve for access to jobs. Questions about decay curves? 13. Lookup table for updated link speeds Lookup tables can be used to depict simple changes in the roadway network. This could be a change of speed, or the removal of a link. Since we are analyzing the baseline accessibility for transit, we will leave this parameter blank, thus not changing the roadway network. Questions about lookup tables? 14. Run your accessibility scenario Once all of the parameters have been specified, you can run your scenario. To do so, click the play button at the top left of the Launch Pad. 15. The data and scenario information will be uploaded to the cloud for processing. The scenario run can be monitored from the status window within the Launch Pad. The status window will open as soon as a scenario starts running. Congratulations! You have run your first Sugar Access accessibility analysis. Once the analysis has been completed, you may download your results and understand the accessibility of jobs by public transport in your local community. For help in understanding your results.

14 UNDERSTANDING SUGAR ACCESS DATA Sugar Access is a ready-to-use software package for accessibility analysis. All data necessary for accessibility analysis purposes is stored within an Esri formatted geodatabase. There are four major components for running accessibility analysis, these feature layers include the Analysis Location Data, Roadway and Pedestrian Network, Transit Network, and Points of Interest (POI) data. They can be described as the following: Analysis Location Data (Demographic Zones) The analysis location data within Sugar Access is a reference to a polygon or zonal dataset that is representative of the demographic and socio-demographic information contained within those zones. As a default, Sugar Access comes with data from both the 2010 Census and LODES datasets. This is represented both as Census Blocks and Census Block Groups within your local Sugar Access geodatabase. Analysis location data only works within Sugar as a feature class within a geodatabase, and will not work as a separate.shp file. Based on the time when have received your local Sugar Access geodatabase, your analysis location datasets may be the following: Zones_Jobs A collection of both Census Blocks and Block Groups with Census and LODE s population and employment information specifically developed for your local area. Zones_POI Similar to the Zones_Jobs dataset, but also contains summarized points of interest information. This may include the number of schools, restaurants in each zone. BlockGroups Census Block Groups with Census and LODE s population and employment information for your local area. CensusBlocks - Census Blocks with Census and LODE s population and employment information for your local area. When selecting the appropriate analysis location file, it is important to note that there is a limit of 32,000 polygon features (zones) for your analysis. For more information about what demographic and employment data is contained within your local geodatabase please see the metadata section.

15 One of the biggest benefits of Sugar Access is that it does depend on a particular dataset for its analysis location data. A user may use local parcel, census block, TAZ, block group data or more. Depending on the travel mode of the analysis, a user may want to select the following type of analysis location levels: Parcels Local walk or bike analysis Census Blocks regional bike, regional transit, or local auto analysis Census Block Groups Statewide auto or mega region transit analysis Roadway and Pedestrian Network Sugar Access roadway and pedestrian networks are all-street networks, developed by Here, a navigation company. An all-street network means that every highway, arterial, neighborhood road and every paved bike/pedestrian path is contained within the network. Networks are used from Here not only because of their coverage and geometric detail, but also the information contained for the network. This pertains to things such as the speed limit, travel mode allowance, and even the real travel speeds throughout the day. The roadway and pedestrian network is typically called the hwnetwork within your local geodatabase. The network may be added to the table of contents as a typical feature dataset would: Once the network is loaded within your ArcGIS Desktop, you will notice that it has loaded as two separate feature classes: HWNetwork Node HWNetwork Link This is a function of Citilabs proprietary geodatabases. Although there are two feature classes, they are both referencing each other to create one cohesive transportation network. This referencing is coded through the A and B attributes within the HWNetwork link feature class. These node references within the link is a reference to the N node number attribute within the HWNetwork Node feature class. These attributes are automatically updated based on the editing that is done to the network. More information about editing the roadway and pedestrian network? Roadway and pedestrian network metadata. Public Transport Network Sugar Access public transport network is typically developed from locally available GTFS (General Transit Feed Specification) files from the public transport authority. The files are used in the following fashion to build out the network within Sugar: Calendar.txt/Calendar_Dates.txt Used to identify the specific services that should be included in the network. Only one calendar date is specified per Sugar network.

16 Stops.txt Used to identify the specific location of the transit stops within the network. The stops from the GTFS file are aligned and joined to the closest HWNetwork Node of the closest HWNetwork Link. Routes.txt Used to identify the names of the different routes within the trips.txt file. Trips.txt Used to identify the different trips that a route makes throughout the day. Only trips identified within valid service IDs from the chosen date and Calendar files will be used. Stop_Times.txt/Frequency.txt Used to do the following: o Identify a list of unique transit lines (unique stop sequence) o Identify average headways for transit line, for each time-period o Identify run times between each stop, for each transit line, for each time-period The local GTFS files are converted to create the local Sugar public transport network, typically called ptlines within your local geodatabase. The network may be added to the table of contents as a typical feature dataset would, and should always be added with the HWNetwork at the same time. Once the network is loaded within your ArcGIS Desktop, you notice that it has loaded as three separate feature classes: Ptlines PTNode Ptlines PTLine Ptlines PTLink This is again a function of Citilabs proprietary geodatabase, that not only brings together the above feature classes to form a transit network, but to also be aligned with the roadway network. Both the Node and Link feature classes reference their overarching transit line they belong to within the PTLine feature class. The Node and Link feature classes also both reference and share the same node numbers as the corresponding HWNetwork. These attributes are automatically updated based on the editing that is done to the network. More information about editing the public transport network? Public transport network metadata. Points of Interest Data Sugar Access Points of Interest (POI) dataset are also developed by Here. This data contains information around the location of local destinations such as restaurants, schools, parks, and many more. This information is provided to the user within their local geodatabase in two different formats and feature classes: POI Point feature class representing the individual locations of every local point of interest Zones_POI Polygon feature class representing the locations of every local point of interest, aggregated to the local zone system. The polygon feature class is broken down by the name of type of Here POI. However, the point feature class represents the raw point location from Here.

17 Points of interest within the point feature class are broken down into categories from both Here (HERE_FACIL) and Citilabs (POINTCLASS). These categories represent different types of shops, services and facilities. The motivation for creating Citilabs own POI classification scheme as opposed to simply using HERE facility types is twofold. First, it permits the aggregation of facility type codes into destination types that are more relevant to accessibility analysis. Second, it permits the extension of this classification scheme for future analyses involving destination types not currently conceived of within the HERE classification. For example, if you wished to differentiate elementary schools from middle and high, you could add/change the code 300, 301 and 302 respectively for those different types of schools. In addition, if a user wished to analyze an entirely new destination type based upon their own POI data, they could use any of the POINTCLASS values in the range reserved for local customization. Citilabs has also set aside the range of POINTCLASS values for potential future expansion of Sugar Access, which may include consideration of other POI data sources in addition to those provided by HERE. The Pointclass attribute is used when conducting a non-work accessibility analysis, specifically. For more information about the Points of Interest data within your local geodatabase please see the metadata section. WHAT S AN ACCESS SCORE? After running your first accessibility analysis within Sugar Access, you may be wondering to yourself, what exactly did I just measure?. There are two types of access scores within Sugar Access: Access Score - Work Describes an individual s ability to reach employment opportunities. These could be jobs of all types, or specific jobs based on industry or wages. The metric is jobs equivalent accessible. Access Score - Non-work Describes an individual s ability to reach non-work destinations, often as part of their daily routine. These destinations could include grocery stores, schools, restaurants, parks, pharmacies, and other common destinations. The metric is non-dimensioned and from 1 to 100. So how is this different than measuring the amount of jobs or grocery stores reachable within 30 minutes? Access Scores utilize propensity to travel curves (or decay curves) to value shorter trips more than longer trips (in travel time), as well as to eliminate the need for an arbitrary travel time cutoff (such as 30 minutes). Decay curves are represented through multiple curves, one for each travel mode, and one for each trip purpose. Figure 1 represents the propensity to travel to work destinations on a national level, utilizing National Household Travel Survey (NHTS) data, produced by SSTI. The decay factor on the y- axis represents the percent of people willing to travel, such that the individual lines represent the change in the propensity to travel for different travel times, and different modes. For your first accessibility analysis, the curves in Figure 1 were utilized to calculate the work access scores that were computed within the analysis. For instance, when calculating the overall accessibility of one zone, you utilize the associated decay curves for each travel time. If 1,000 jobs were accessible by auto at a 15 minute travel time, this would equate to 550 equivalent jobs, while if the same jobs were accessible by auto at a 30 minute travel time, it would equate to 210 equivalent jobs, based on the extracted decay factors in Figure 1. The same process is done for jobs accessible by 1 minute, 2 minutes, 3 minutes 180 minutes, to come up with an Access Score Work for each zone.

18 Decay Factor 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Travel Time (minutes) Auto - Work Transit - Work Walk - Work Bike - Work Figure 1: Default National Work Trip Decay Curves from NHTS Data (SSTI) Travel Time Decay Factor 15 minutes 55% 30 minutes 21% Table 1: Extracted Auto Decay Factors for Work Trips The overall purpose of the Access Scores is not to create something that different than typical accessibility metrics, but rather to start to simplify and standardize accessibility metrics. This has been the goal of Citilabs, working with industry leaders Renaissance Planning Group and The State Smart Transportation Initiative. The goal within Sugar Access is to have an easy-to-understand interface and workflow for a user to start to calculate standardized accessibility metrics for their community. Special Considerations of Analyzing Specific Travel Modes Individuals often choose their mode of travel from aspects other than travel time, this could be the individual s conceived safety, enjoyment, or time spent in or outside of a vehicle. The implementation of travel time decay curves starts to disseminate the value of each potential trip by mode, but we need to add in other considerations when analyzing walk, bike, and transit modes. Again, these further applications of travel time utility is only used when decay factors are applied in the accessibility analysis (Access Score or Open Access Score with decay curves). Pedestrian Level of Service The pedestrian level of service along a roadway is defined by the environment surrounding it, taking into consideration physical aspects such as sidewalk availability, roadway speed, roadway volume, etc To operationalize this utilizing the available Here roadway data, the following attributes are used to define the pedestrian level of service: Roadway Number of Lanes Roadway Speed Limit Roadway Functional Class

19 Presence of Sidewalk (where data is available) The combination of the above attributes formulate a pedestrian level of service from 1 (low) to 5 (high). Each level of service level equates to a utility value for that roadway section. The utility value is a sense of the enjoyment that an individual would achieve by traversing that roadway section. A lookup table for the pedestrian level of service values is available in the appendix. In order to operationalize these level of service values, and ensure that the highest utility route is calculated, the walking speeds are recalculated per each roadway or pedestrian segment. For instance, in Table 2 below the mile equivalent were calculated based on an example walk speed of 3.0 mph. This means, that a 2-mile trip on a LOS 1 roadway is equivalent to a 1-mile trip on a LOS 4 roadway for an individual. LOS Level Utility Factor Mile Equivalent (minutes) 1 50% % % % % 18 Table 2: Pedestrian Level of Service Utility Factors Another way to think of the operationalizing of the pedestrian level of service is that the individual s decay of their trip is changing based on the level of service of the roadway segment that the individual is traversing on their trip. In the below picture, if an individual s trip improved 50% based on the LOS along the roadway segments they are traversing, the travel time decay for that trip reduces from 24% to 53%, based on the mode-specific decay curve that is used. Bicycle Level of Service The bicycle level of service along a roadway is similar to the Bicycle Level of Traffic Stress (LTS), formalized by the Mineta Transportation Institute. The Bicycle LTS from Mineta takes a weakest link approach, allowing for links with a particular LTS or lower to be traversable, based on the particular type of cyclist that is assumed. In-order to realize improvements or losses to accessibility due to an array of potential transportation projects, it is better to implement a utility-based approach, such as the one implemented for pedestrian level of service. The bicycle level of service along a roadway is similarly defined by the environment surrounding it, taking into consideration physical aspects such as bike facility type, roadway speed, roadway volume, etc To operationalize this utilizing the available Here roadway data, the following attributes are used to define the pedestrian level of service: Roadway Number of Lanes Roadway Speed Limit Roadway Functional Class Presence of bicycle facilities (where data is available) The combination of the above attributes formulate a bicycle level of service from 1 (low) to 10 (high). Each level of service level equates to a utility value for that roadway section. The utility value is a sense

20 of the enjoyment that an individual would achieve by traversing that roadway section. A lookup table for the bicycle level of service values is available in the appendix. In order to operationalize these level of service values, and ensure that the highest utility route is calculated, the bicycle speeds are recalculated per each roadway segment. For instance, in Table 3Table 2 below the mile equivalent were calculated based on an example bike speed of 9.0 mph. This means, that a 3-mile trip on a LOS 8 roadway is equivalent to a 1-mile trip on a LOS 3 roadway for an individual. LOS Level Utility Factor Mile Equivalent (minutes) 1 150% % % % % % % % % % 65.9 Table 3:Bicyclist Level of Service Utility Factors Another way to think of the operationalizing of the bicyclist level of service is that the individual s decay of their trip is changing based on the level of service of the roadway segment that the individual is traversing on their trip. In the below picture, if an individual s trip improved 50% if a trip is made along a LOS 1 roadway instead of a LOS 5 roadway, the travel time decay for that trip reduces from 24% to 53%, based on the mode-specific decay curve that is used.

21 Decay Factor CALCULATING NON-WORK ACCESSBILITY Non-work accessibility allows us to analyze an individual s ability to access non-work destinations, such as parks, schools, hospitals, and other daily destinations. While the other accessibility metrics allow an user to calculate access to one destination type, the Non-Work Access Score allows users to calculate access to multiple type of destinations, especially non-work destinations. Non-Work Access Scores are calculated from 0 to 100 and are typically normalized on a maximum Non-Work Access Score in a state or throughout the country. There are two aspects of calculating non-work accessibility that differentiate the analysis from a typical work accessibility analysis, decay curves specific to non-work destinations, and the utilization of a destination scoresheet. Figure 2 below shows both work and non-work decay curves by travel mode, again, using national NHTS data. The majority of the curves for the travel modes show a lower desire to travel times to reach nonwork destinations, however, for walking trips, there is a higher desire to make a non-work trip than a work trip. As a default, these non-work decay curves are used within the Non-Work Access Score application. 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Travel Time (minutes) Auto - Work Transit - Work Walk - Work Bike - Work Auto - Non-Work Transit - Non-Work Walk - Non-Work Bike - Non-Work Figure 2: Default National Non-Work Trip Decay Curves from NHTS Data (SSTI) The destination scoresheet allows a user to choose the types of destinations that they want to be included in their non-work accessibility analysis. Figure 3 below shows the default destination scoresheet for the non-work accessibility analysis, which was developed for Virginia s Smart Scale prioritization process. There are four different fields that make up the destination scoresheet: Description Type of non-work destination. May be more than one specific type of point of interest. Category Weight the relative weight that should be applied to the specific non-work destination category. The combined category weights of all the rows should add up to 100. POI Target The target number of points of interest which must be accessible nearby in order to assign the full category weight to the score for a given origin.

22 Pointclass A comma separated list of point of interest type codes. These code values can be found in the POI metadata. Figure 3: Default Access Score Non-Work Destination Scoresheet (SSTI) The non-work destination scoresheet is configurable by a user as a dbf and an example scoresheet is provided to the user with their original Sugar dataset. Access Score Non-Work Tutorial Non-work accessibility can be calculated similarly to the Access Score Work tutorial. This tutorial will show how a user can calculate non-work accessibility through the Access Score Non-Work application. This tutorial can also be followed through the Introduction to Sugar Access Video. Let s get started! For this analysis, we will be looking at accessibility to non-work destinations by walking. 1. Within the Sugar Launch Pad, there are five applications to choose from for running our accessibility analysis. The easiest way to analyze access to jobs is through the Access Score Non-Work application. Let s select that application from the Launch Pad: 2. Select an analysis location feature class The analysis location field is where you select the zonal system that you will for your analysis. You may browse to the specific feature class within your local geodatabase, provided to you with your license to Sugar Access. Once the geodatabase is highlighted, select the feature class which the non-work analysis should be calculated at, this could be parcels, census blocks, etc... and click open. What s a valid analysis location feature class? No non-work destination information need be already summarized within the feature class.

23 3. Select a time period - For this analysis, since we are choosing walking as the travel mode. This will not be affected by the time period. You may choose whichever time period you prefer. What times are used for these different time periods? 4. Select a mode of travel Select Walk to analyze accessibility using only walking. Your Launchpad window should look show the following selections thus far: 5. Select a points of interest point feature class The points of interest parameter is a reference to the local points of interest point feature class. The feature class is contained within your local geodatabase from Sugar Access. Highlight POI and click Open. Where does the local POI dataset come from?

24 6. Select a roadway network The roadway network parameter is a reference to the local roadway network feature class for your analysis location. This network is contained within your local geodatabase from Sugar Access. Highlight the HWNetwork and click Open. Where does the local hwnetwork come from? 7. Select a transit network The transit network parameter is a reference to the local transit feature class for your analysis location. This network is also contained within your local geodatabase from Sugar Access. Highlight ptlines and click open. Where does the local transit network come from? 8. Select a turn penalty file The turn penalty file is an automatically generated for the local roadway network from Here. The turn penalty file should be located within the same zip file as your local geodatabase. Browse for the turn penalty file and click open. What is a turn penalty file? 9. Select an average walk speed The default walk speed within Sugar Access is set to 3.1 mph. This may be changed by the user, as they desire. We will leave it as 3.1 mph for this accessibility analysis.

25 10. Select an average cycling speed This does not affect our transit analysis, so we will leave it as the default. 11. Upload to ArcGIS Online Sugar Access gives the user ability to automatically upload their accessibility analysis and maps to the user s ArcGIS Online account for sharing. To do so, the user must enter valid ArcGIS Online credentials within the Launch Pad settings, as well as having publishing privileges within their ArcGIS Online organization. Questions about publishing to ArcGIS Online? 12. Custom lookup table for value of time Sugar Access Access Scores do not treat every minute of travel time equally. To do so, we use decay curves to penalize longer trips, i.e. a job 15 minutes away will be more valuable than a job 30 minutes away. In this case, we will leave the parameter blank, and use the default decay curve for non-work access (Figure 2). Questions about decay curves? 13. Lookup table for updated link speeds Lookup tables can be used to depict simple changes in the roadway network. This could be a change of speed, or the removal of a link. Since we are analyzing the baseline accessibility for transit, we will leave this parameter blank, thus not changing the roadway network. Questions about lookup tables? 14. Custom access score destination weights Scoresheet for setting different weights to different point of interest category types. If we leave this parameter blank, the default non-work destination scoresheet (Figure 3) will be used. Questions about the destination scoresheet? 15. Run your accessibility scenario Once all of the parameters have been specified, you can run your scenario. To do so, click the play button at the top left of the Launch Pad. 16. The data and scenario information will be uploaded to the cloud for processing. The scenario run can be monitored from the status window within the Launch Pad. The status window will open as soon as a scenario starts running.

26 Congratulations! You have run a non-work accessibility analysis in Sugar Access. Once the analysis has been completed, you may download your results and understand the accessibility of non-work destinations in your local community. For help in understanding your results. UNDERSTANDING YOUR RESULTS Now that you have run several scenarios through the Access Score applications, there are many ways to visualize and analyze your data. To start the process, make sure you have downloaded the analysis database after your scenario has completed. The accessibility data can be viewed in both ArcGIS Desktop and ArcGIS Online. By default, the accessibility results that are published to your ArcGIS Online account are a simplified version of the raw accessibility results, rounded to reduce the size of the feature layer that is hosted on your ArcGIS Online account. Viewing Results in ArcGIS Online 1. To view the accessibility results in ArcGIS Online and build your first accessibility map, proceed to your ArcGIS Online content page. 2. You should find your accessibility results published to your ArcGIS Online content page. There may be multiple feature layers and service definitions based on the analyses that you ran. To create your first accessibility map, click the Add layer to new map with full editing control option under the feature layer.

27 3. Once your feature layer has been added to your map, you can utilize the Change Style tool to customize your accessibility map and publish it to a web application or website. Need more help creating maps within ArcGIS Online? Viewing Results in ArcGIS Desktop You may have also downloaded your accessibility results in order to view the results within ArcGIS Desktop. Once you have downloaded the results, you will find your zipped results file in your local download folder. Unzip the results in order to start viewing your accessibility results and building your accessibility maps within ArcGIS. 1. To view the database in ArcGIS, open ArcMap and add new data to your map.

28 As you may notice, there are several tables in both geographic and tabular format. They can be described as the following: Access: This is your main results geo-layer. It contains your original zonal layer with its attributes along with the newly calculated accessibility metrics. Summary Table: This table is generated to summarize your results with respect to the sociodemographic information in your zonal layer. You will find the weighted averages for your selected accessibility metrics for every zonal attribute. Input Summary: This table is used to keep track of the analysis inputs that are used for the specific scenario. Mode Access: This geo-layer feature your access score for a specific mode summarized (dissolved) into several bins for easy interpreting and publishing to ArcGIS Online. These are the feature layers that are automatically published to ArcGIS Online. Score: This is your main results geo-layer when using the Scenario Analyzer application. Add the Access geo-layer to your current map and double-click on the access table in your table of contents. Here you may visualize and view your accessibility metrics. You will notice that your access feature class is an appended version of your analysis location polygon feature class that had been used as input for the accessibility analysis. Based on the type of accessibility analysis that was completed, the following metrics will be generated within your access table. Access Score Work/ Open Access Score Destination Summation Mode Dests: This metric represents the accessibility of the respective zone (rows) to the particular type of destination that you have analyzed. For example, if your analysis was accessibility to jobs via transit, the TranDests metric would tell you the number of jobs reachable via transit for each zone.

29 Mode : This metric represents the Mode Dests category rounded down to either the closest 100 (walk) or 1,000. This is the metric that is dissolved in order to create the Mode Access feature layers. Scale: This metric represents the relative accessibility of the particular zone, or rather is the percentile of accessibility relative to all other zones. If the Scale for a particular zone is 47, this means that this zone has a higher accessibility than 47 percent of the other zones. This will not be calculated if multiple modes are analyzed. Mode Share: This metric represents the percent of a specific destination type throughout the region of your analysis that are accessible from the particular zone. This metric is generated when not using value of time within the Open Access Score application. Sumdests: If you have chosen to analyze multiple modes of travel, the Sumdests metric represents the sum of accessibility across all modes analyzed. Access Score Non-Work Score Mode : This metric represents the Non-Work Access Score that was calculated using the chosen destination scoresheet, values range from 0 to 100. Mode : This metric represents the corresponding Non-Work Access Score rounded down to the closest whole number. This is the metric that is dissolved in order to create the Mode Access feature layer. Open Access Score Travel Time Mode Time: This metric represents the minimum travel time from a particular zone to a destination type that was chosen in the analysis for a specific mode. Mintime: This metric represents the minimum travel time from a particular zone to a destination type for all modes that were chosen in the analysis. This metric is only calculated if multiple travel modes are analyzed. Scenario Analyzer Score1, Score2: These are the respective accessibility metrics (Access Score, Travel Time, etc...) from the two scenarios that you are comparing. These are automatically generated for the type of analysis that you have performed which can be viewed in the Input Summary table. Change: The change in accessibility from scenario 1 (baseline) to scenario 2 (alternative). This is computed by subtracting scenario 1 from scenario 2. Creating an Accessibility Map You may also choose to create an accessibility layer or map within ArcMap to display the accessibility results visually across your region. This can be done using the Access feature class, after it has been added as a layer in ArcMap. Maps can be easily created through the Symbology tab within the layer properties. For more information about creating beautiful accessibility maps within ArcMap, check out Esri s website.

30 Summary Table 2. After viewing the accessibility metrics spatially across each zone, you may also choose to look at a summary of these statistics. To do so, add the Summary Table from your database to your map: Right click on the on the Summary Table within the table of contents to open and view the results.

31 The Summary Table contains the following important information: Col_Name: This column contains the name of the socio-demographic group or variable in the zonal layer. Col_Sum: This column contains the sum of the socio-demographic group s population. For instance, in the above figure, there are 100,211 households in the dataset. Prod_Sum: This column is an intermediary step in getting the weighted accessibility and represents the product sum of accessibility for that socio-demographic group. Avg_TTime, AVG_Sumdestn, Avg_Score: This column contains the weighted average for the metric of the analysis that you have chosen (Travel Time, Access Score Work/ Destination Summation, and Access Score Non-Work). This average is weighted on the population of each category for every zone in the analysis. There is also a summary table that is produced when running the Scenario Analyzer application The Summary Table for the Scenario Analyzer contains the following information: Category: This column contains the name of the socio-demographic group or variable in the zonal layer. Scenario1/Scenario2: The average accessibility for a particular socio-demographic group for each scenario that you are comparing.

32 Difference: Average accessibility of scenario 2 minus average accessibility of scenario 1. PerChange: Percent change from average accessibility of scenario 1 to scenario 2. Input Summary The last output that we will view is the Input Summary, which summarizes the accessibility analysis that was ran for that scenario. 3. Add the Input Summary from your database to your map in a similar fashion as the Summary Table Right click on the Input Summary within the table of contents to view the analysis input summary. The Input Summary table shows the user which input was chosen for each parameter in the accessibility analysis. LEVERAGING OPEN ACCESS SCORE While Access Scores for Work and Non-Work destinations can certainly tell an overarching story about accessibility in our community, there might be a specific question around accessibility that you are wanting to ask. The Open Access Score application allows users to complete two straightforward accessibility analyses: Travel Time Analysis Minimum travel time to a select destination type. Destination Summation Analysis Number of destinations of a particular type accessible. Some questions that might be potentially answered with these types of analyses, would be: What is the minimum walking travel time to a grocery store?

33 What is the minimum transit travel time to a hospital? How many fast food restaurants are accessible within a 15-minute walk? Open Access Score Tutorial This tutorial will show how a user can calculate the accessibility for one of the questions asked above through the Open Access Score application. This tutorial can also be followed through the Introduction to Sugar Access Video. Let s get started! For this analysis, we will be looking at the minimum walking time to grocery stores. 1. Within the Sugar Launch Pad, there are five applications to choose from for running our accessibility analysis. Let s select that Open Access Score application from the Launch Pad to start our analysis: 2. Select a type of analysis As described above, there are two types of analysis that can be completed within the Open Access application, Travel Time and Destination Summation. Select the Travel Time analysis in order to measure the minimum travel time. 3. Select an analysis location feature class The analysis location field is where you select the zonal system that you will for your analysis. You may browse to the specific feature class within your local geodatabase, provided to you with your license to Sugar Access. Once the geodatabase is highlighted, select the feature class which the local points of interest data is already summarized, in this case it s Zones_POI... and click open. What s a valid analysis location feature class? 4. Select a Destination You will notice in the Zones_POI feature class, that all of the points of interest categories are already summarized along with the socio-demographic categories. Scroll down the list and select Grocery from the list. Want to measure access to a destination no on the list? 5. Select a time period For this analysis, since we are choosing walking as the travel mode. This will not be affected by the time period. You may choose whichever time period you prefer. What times are used for these different time periods? 6. Select a mode of travel Select Walk to analyze accessibility using only walking.

34 7. Select a maximum travel time In this case, we are measuring the minimum travel time to a particular destination, so that setting a maximum travel will not allow for any trips longer than a specific travel time to be measured. Let s set this to 30 minutes. Your Launchpad window should look show the following selections thus far: 8. Select a roadway network The roadway network parameter is a reference to the local roadway network feature class for your analysis location. This network is contained within your local geodatabase from Sugar Access. Highlight the HWNetwork and click Open. Where does the local hwnetwork come from? 9. Select a transit network The transit network parameter is a reference to the local transit feature class for your analysis location. This network is also contained within your local geodatabase from Sugar Access. Highlight ptlines and click open. Where does the local transit network come from? 10. Select a turn penalty file The turn penalty file is an automatically generated for the local roadway network from Here. The turn penalty file should be located within the same zip file as your local geodatabase. Browse for the turn penalty file and click open. What is a turn penalty file? 11. Select an average walk speed The default walk speed within Sugar Access is set to 3.1 mph. This may be changed by the user, as they desire. We will leave it as 3.1 mph for this accessibility analysis.

35 12. Select an average cycling speed This does not affect our transit analysis, so we will leave it as the default. 13. Upload to ArcGIS Online Sugar Access gives the user ability to automatically upload their accessibility analysis and maps to the user s ArcGIS Online account for sharing. To do so, the user must enter valid ArcGIS Online credentials within the Launch Pad settings, as well as having publishing privileges within their ArcGIS Online organization. Questions about publishing to ArcGIS Online? 14. Custom lookup table for value of time Sugar Access Access Scores do not treat every minute of travel time equally. Since we are conducting a travel time analysis, there are no value of time effects for the analysis, everything is measured as straight travel time. 15. Lookup table for updated link speeds Lookup tables can be used to depict simple changes in the roadway network. This could be a change of speed, or the removal of a link. Since we are analyzing the baseline accessibility for transit, we will leave this parameter blank, thus not changing the roadway network. Questions about lookup tables? 16. Run your accessibility scenario Once all of the parameters have been specified, you can run your scenario. To do so, click the play button at the top left of the Launch Pad. 17. The data and scenario information will be uploaded to the cloud for processing. The scenario run can be monitored from the status window within the Launch Pad. The status window will open as soon as a scenario starts running. Congratulations! You have run a accessibility analysis to grocery stores in Sugar Access. Once the analysis has been completed, you may download your results and understand the accessibility of grocery stores in your local community. For help in understanding your results.

36 EDITING YOUR MULTIMODAL NETWORK Sugar Access includes tools to help you edit the highway and public transportation networks. This section includes step-by-step instructions for working with Sugar input networks for typical examples such as updating walk access links, coding bikeways, and adding new transit service. Editing/updating roadway links The default networks that are provided with Sugar Access for your community include a basic representation of which links may be used by pedestrians. You may wish to update this based upon your local knowledge; for example to exclude certain streets from the walking network due to lack of sidewalks, or excessive vehicle traffic volume or speed. 1. Load the roadway and pedestrian network feature dataset in ArcMap. This is included in the local geodatabase provided to you with Sugar Access by Citilabs. a. From the Standard toolbar: click the Add Data button, browse to your local geodatabase, and double-click to add the highway network feature dataset 2. Zoom into the area which you would like to edit. 3. Make sure the Sugar Editor Toolbar is enabled. Go to Customize > Toolbars > Sugar Editor Toolbar. You can let the toolbar float and move it to the desired position on-screen, or dock it into place on the menu next to the ArcMap toolbars. 4. To begin an editing session, click the Start Editing button. This will automatically place ArcMap in edit mode and select the Edit Tool button. 5. Click on the link you would like to edit. The Sugar Feature Explorer will display the properties of the link you have chosen. 6. The AR_PEDEST attribute is Y for links included in the pedestrian network; N otherwise. To remove or add a link to the pedestrian network, edit this attribute. Your changes will be automatically applied unless you click on the Reset button. The same can be said for the

37 AR_BUS, AR_AUTO and Bike (1 or 0) attributes, these are the attributes that determine whether transit, driving and biking are possible on the link when doing an accessibility analysis. 7. Click on the Save Edits button to commit any changes to the geodatabase. To finish your session, click on the Stop Editing button, which will also prompt you to save any pending changes. 8. To visualize the changes to accessibility caused by your link updates, you can go to Sugar Launch Pad and re-run a walkability score analysis. Adding new roadway links You might also wish to add links to the network, such as bicycle trails, either existing or proposed. 1. Load the roadway and pedestrian network feature dataset in ArcMap. This is included in the local geodatabase provided to you with Sugar Access by Citilabs. a. From the Standard toolbar: click the Add Data button, browse to your local geodatabase, and double-click to add the highway network feature dataset 2. Zoom into the area which you would like to edit. a. Tip: You can add a basemap to overlay the network on imagery or a topographic view of existing development. This may help you when designing new features. 3. Make sure the Sugar Editor Toolbar is enabled. Go to Customize > Toolbars > Sugar Editor Toolbar. You can let the toolbar float and move it to the desired position on-screen, or dock it into place on the menu next to the ArcMap toolbars. 4. To begin an editing session, click the Start Editing button. This will automatically place ArcMap in edit mode and select the Edit Tool button. 5. Click on the Add Link button to enable adding new features to the network. Then, left-click where you would like to start adding the link, and continue left-clicking for each segment of the new bikeway, to sketch a curve, as shown below. a. Note: You can abandon your edits by right-clicking and selecting Delete Sketch, then using the Esc key on your keyboard.

38 b. Note: To finish your sketch, either right-click and select Finish Sketch from the context menu, or double-click. c. Note: If you click (or double-click) on an existing link, the feature will snap to that link by default. A new node will be automatically created at the point where the new and old features intersect upon finishing your edits. Select Automatic in the New Node ID window, shown below, to avoid being prompted to set node numbers manually in the future. You can change this setting by clicking the Automatic Node Numbering button on the Sugar Editor Toolbar. d. Note: New links are two-way by default. In the Sugar data model, this means a separate feature exists for each direction of travel, with potentially different properties for each direction. You can change this setting by clicking the Two-Way Editing button on the Sugar Editor Toolbar. 6. Using the Properties section of the Sugar Feature Explorer, set attributes for the new link you created as appropriate. For pedestrian and bicycle paths, all access restrictions (i.e. fields with the prefix AR at the beginning of their name) should be set to N, except for AR_PEDEST while the BIKE attribute should be set to 1, and the BIKE_FACIL= 1 (representing an exclusive right-

39 of-way bike path). More information about the roadway and pedestrian network fields? a. Note: If you are creating a series of similar links with the same essential properties (other than distance), you can click on the Copy Attributes button to set the current feature as a template to be used for subsequent added links. This step can save time and reduce error associated with manual data entry. 7. Click on the Save Edits button to commit any changes to the geodatabase. To finish your session, click on the Stop Editing button, which will also prompt you to save any pending changes. 8. To visualize the changes to accessibility caused by your new link additions, you can go to Sugar Launch Pad and re-run any bicycle-based analysis. Editing/updating public transport lines/routes During implementation of Sugar Access, Citilabs can import transit schedule information into your local Sugar geodatabase from a variety of formats, including GTFS. Public transport lines may also be coded in directly, for example to add services provided by operators who do not publish data in this format, or to encode proposed services and evaluate their accessibility. 1. Load the roadway and pedestrian network feature dataset in ArcMap. This is included in the local geodatabase provided to you with Sugar Access by Citilabs. Note that the public transit (PT) system relates to the roadway and pedestrian network, so both must be loaded in order to edit PT. 2. Load the public transit (PT) network feature dataset in ArcMap. This is also included in the local geodatabase provided to you with Sugar Access by Citilabs. Note: If the PT network you are creating represents an alternative scenario, you may wish to make a copy of the PT feature dataset before editing it. This can be accomplished in the Sugar Data Manager by right-clicking on the PT feature dataset, selecting Copy, then right-clicking on the geodatabase, and selecting Paste. The new PT data set will automatically be renamed; you can change this name to by right-clicking and selecting Rename. a. From the menu: select File > Add Data > Add data..., browse to your local geodatabase, and double-click to add the PT feature dataset b. From the Standard toolbar: click the Add Data button, browse to your local geodatabase, and double-click to add the PT feature dataset

40 c. From the Sugar Data Manager: if the local geodatabase is not already loaded, click the Add data button, browse to your local geodatabase, and double-click to add the workspace. Once your local geodatabase is loaded, click the + next to the geodatabase icon to expand the view of included data. Right-click on the highway network feature dataset and select add to TOC. 3. Zoom into the area which you would like to edit. 4. Make sure the Sugar Editor Toolbar is enabled. Go to Customize > Toolbars > Sugar Editor Toolbar. You can let the toolbar float and move it to the desired position on-screen, or dock it into place on the menu next to the ArcMap toolbars. 5. To begin an editing session, click the Start Editing button. This will automatically place ArcMap in edit mode and select the Edit Tool button. 6. Click on the Add PT Lines button on the Sugar Editor Toolbar. Then, left-click on any highway network node to add the first stop in your new line. a. Left-click again on another highway network node to add a new stop, allowing Sugar to automatically choose the shortest route between the two stops along the street network, as shown below. b. You can hold down the Alt key on your keyboard and left-click to add a non-stop node to the line, allowing Sugar to automatically choose the shortest route. This method allows more control over the PT line alignment than simply left-clicking. c. You can also hold down the Shift key and left-click to add a stop node via direct link, rather than allowing Sugar to automatically choose the shortest route. This technique can be used to exercise full control over the PT route and/or to code in services that do not use roads, such as subway rail. Please note that each PT link needs an underlying speed, if the link is not aligned with the roadway network, then the XYSPEED attribute needs to be completed. 7. Double-click to add a stop and end the PT line sketch. Then, set the line properties using the Sugar Feature Explorer. At minimum, you must set a NAME, MODE, and HEADWAY for at least one period (e.g. HEADWAY_1). a. Note: The modes available in Sugar Access are closely aligned with the set of route types included in the GTFS format specification, with the exception that the code for Tram, Streetcar or Light Rail is changed to 8 from 0, as shown in the table below. Mode Name Description 1 Subway or Metro Any underground rail system within a metropolitan area.

41 2 Intercity Rail Used for intercity or long-distance travel. 3 Bus or BRT Used for short- and long-distance bus routes. 4 Ferry Used for short- and long-distance boat service 5 Cable car Used for street-level cable cars where the cable runs beneath the car. 6 Gondola Typically used for aerial cable cars where the car is suspended from the cable. 7 Funicular Any rail system designed for steep inclines. 8 Tram, Streetcar, or Light Rail Any light rail or street level system within a metropolitan area. b. Headway is related to service frequency, and is defined as the average time (in minutes) between successive runs of a service during a specified time period. This information is automatically obtained from GTFS schedule data when available, but needs to be entered by the user when coding new lines for scenario testing purposes. There are five HEADWAY periods (HEADWAY_1 through HEADWAY_5) available; only four are used by Sugar Access; HEADWAY_1, HEADWAY_2, HEADWAY_3, HEADWAY_4. They correspond to the time periods: HEADWAY_1 AM Peak HEADWAY_2 PM Peak HEADWAY_3 Midday Peak HEADWAY_4 Off Peak HEADWAY_5 Daily Average Questions about what Public Transport fields are essential in Sugar? c. By default, new lines are one-way, even though it may appear that the ONEWAY attribute is 0. To ensure a line is two-way, you must re-enter the ONEWAY attribute as 0. You may also change the ONEWAY attribute to 1 to ensure that the line to be one-way. Note that lines which traverse one-way roadway links must have ONEWAY set equal to 1, or an error will occur during analysis. d. If you are coding multiple PT lines that have similar attributes, you can save time by clicking on the Copy Attributes button in the Feature Explorer. This will set the current line s properties as a template to be used for subsequent lines. e. Double-Click outside your transit line on the map to apply the line properties settings. 8. Click on the Save Edits button to commit any changes to the geodatabase. To finish your session, click on the Stop Editing button, which will also prompt you to save any pending changes. To visualize the changes to accessibility caused by your new PT line additions, you can go to Sugar Launch Pad and re-run any transit-based analysis. You can use the Scenario Analyzer to visualize a before-after comparison of the results.

42 Decay Factor SUGAR ACCESS CAPABILITIES ACCESS SCORE WORK Access Score - Work Describes an individual s ability to reach employment opportunities. These could be jobs of all types, or specific jobs based on industry or wages. The metric is jobs equivalent accessible. So how is this different than measuring the amount of jobs or grocery stores reachable within 30 minutes? Access Scores utilize propensity to travel curves (or decay curves) to value shorter trips more than longer trips (in travel time), as well as to eliminate the need for an arbitrary travel time cutoff (such as 30 minutes). Decay curves are represented through multiple curves, one for each travel mode, and one for each trip purpose. Figure 4Figure 1 represents the propensity to travel to work destinations on a national level, utilizing National Household Travel Survey (NHTS) data, produced by SSTI. The decay factor on the y-axis represents the percent of people willing to travel, such that the individual lines represent the change in the propensity to travel for different travel times, and different modes. For your first accessibility analysis, the curves in Figure 1 were utilized to calculate the work access scores that were computed within the analysis. For instance, when calculating the overall accessibility of one zone, you utilize the associated decay curves for each travel time. If 1,000 jobs were accessible by auto at a 15 minute travel time, this would equate to 550 equivalent jobs, while if the same jobs were accessible by auto at a 30 minute travel time, it would equate to 210 equivalent jobs, based on the extracted decay factors in Figure 5. The same process is done for jobs accessible by 1 minute, 2 minutes, 3 minutes 180 minutes, to come up with an Access Score Work for each zone. 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Travel Time (minutes) Auto - Non-Work Transit - Work Walk - Work Bike - Work Figure 4: Default National Work Trip Decay Curves from NHTS Data (SSTI)

43 Travel Time Decay Factor 15 minutes 55% 30 minutes 21% Table 4: Extracted Auto Decay Factors for Work Trips Access Score Work consists of the following parameters: Analysis Location - Locational information, such as Census Blocks, Census Block Groups, Parcels, or user customized zones used to summarize and visualize scores. Must be a polygon feature class within geodatabase. Destination Field within the analysis polygon feature class corresponding to the employment or points of interest type representing the destinations for your accessibility analysis (i.e. what are you analyzing access to?) Time Period Time of day for the accessibility analysis; Morning-Peak, Afternoon, Evening-Peak, Nighttime. Please contact your local Sugar Access administrator if you are interested in knowing the exact times for the time periods. Changing the time period will affect the transit schedule and the auto speeds that are being used for your accessibility analysis. Mode of Travel Travel mode to be used in the accessibility analysis; Walk, Auto, Bike, Transit, All, Non- Auto (All Modes but Auto), and Non-Transit (All Modes but Transit). The transit analysis consists of a combined walk and transit analysis. Roadway Network Citilabs formatted Roadway and Pedestrian network from local geodatabase. Turn Penalties Turn Prohibition and/or penalty text file received as part of local Sugar data. Public Transport Network Citilabs formatted Public Transport network from local geodatabase. Average Walking Speed (mph) Average walking speed used when completing a Walk or Transit accessibility analysis. Average Cycling Speed (mph) Average cycling speed used when completing a Bike accessibility analysis. Upload to ArcGIS Online Option for user to upload accessibility analysis results to ArcGIS Online. User must have an ArcGIS Online account with publishing rights. Custom Lookup Table for Value of Time (Optional) DBF table consisting of decay values per mode with the associated travel times. The table should contain the following columns: time, walk, bike, transit, auto. If no custom lookup tables are used for the accessibility analysis, then the national average curves will be used, as shown in Figure 4. An Example DBF table should have been delivered with your Sugar Access dataset. Lookup Table for Updated Link Speeds (Optional) DBF table consisting of updated speed or level of service values to particular roadway links. The DBF table should contain the following columns: LINK, SPEEDFROM, SPEEDTO, WALKLOS_FR, WALKLOS_BIKELOS_FR, BIKELOS_TO. LINK Corresponds to Here link attribute. WALKLOS and BIKELOS correspond to Walk and Bike level of stress, respectively. How do I run a work accessibility analysis?

44 Decay Factor ACCESS SCORE NON-WORK Access Score - Non-work Describes an individual s ability to reach non-work destinations, often as part of their daily routine. These destinations could include grocery stores, schools, restaurants, parks, pharmacies, and other common destinations. The metric is non-dimensioned and from 1 to 100. Non-work accessibility allows us to analyze an individual s ability to access non-work destinations, such as parks, schools, hospitals, and other daily destinations. While the other accessibility metrics allow an user to calculate access to one destination type, the Non-Work Access Score allows users to calculate access to multiple type of destinations, especially non-work destinations. Non-Work Access Scores are calculated from 0 to 100 and are typically normalized on a maximum Non-Work Access Score in a state or throughout the country. There are two aspects of calculating non-work accessibility that differentiate the analysis from a typical work accessibility analysis, decay curves specific to non-work destinations, and the utilization of a destination scoresheet. Figure 2 below shows both work and non-work decay curves by travel mode, again, using national NHTS data. The majority of the curves for the travel modes show a lower desire to travel times to reach nonwork destinations, however, for walking trips, there is a higher desire to make a non-work trip than a work trip. As a default, these non-work decay curves are used within the Non-Work Access Score application. 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Travel Time (minutes) Auto - Work Transit - Work Walk - Work Bike - Work Auto - Non-Work Transit - Non-Work Walk - Non-Work Bike - Non-Work Figure 5: Default National Non-Work Trip Decay Curves from NHTS Data (SSTI) The destination scoresheet allows a user to choose the types of destinations that they want to be included in their non-work accessibility analysis. Figure 3 below shows the default destination scoresheet for the non-work accessibility analysis, which was developed for Virginia s Smart Scale prioritization process. There are four different fields that make up the destination scoresheet: Description Type of non-work destination. May be more than one specific type of point of interest.

45 Category Weight the relative weight that should be applied to the specific non-work destination category. The combined category weights of all the rows should add up to 100. POI Target The target number of points of interest which must be accessible nearby in order to assign the full category weight to the score for a given origin. Pointclass A comma separated list of point of interest type codes. These code values can be found in the POI metadata. Figure 6: Default Access Score Non-Work Destination Scoresheet (SSTI) The non-work destination scoresheet is configurable by a user as a.dbf and an example scoresheet is provided to the user with their original Sugar dataset. Access Score Non-Work consists of the following parameters: Analysis Location - Locational information, such as Census Blocks, Census Block Groups, Parcels, or user customized zones used to summarize and visualize scores. Must be a polygon feature class within geodatabase. Time Period Time of day for the accessibility analysis; Morning-Peak, Afternoon, Evening-Peak, Nighttime. Please contact your local Sugar Access administrator if you are interested in knowing the exact times for the time periods. Changing the time period will affect the transit schedule and the auto speeds that are being used for your accessibility analysis. Mode of Travel Travel mode to be used in the accessibility analysis; Walk, Auto, Bike, Transit, All, Non- Auto (All Modes but Auto), and Non-Transit (All Modes but Transit. The transit analysis consists of a combined walk and transit analysis. Points of Interest Point feature class containing points of interest to be used from local geodatabase. Roadway Network Citilabs formatted Roadway and Pedestrian network from local geodatabase. Turn Penalties Turn Prohibition and/or penalty text file received as part of local Sugar data. Public Transport Network Citilabs formatted Public Transport network from local geodatabase. Average Walking Speed (mph) Average walking speed used when completing a Walk or Transit accessibility analysis. Average Cycling Speed (mph) Average cycling speed used when completing a Bike accessibility analysis. Upload to ArcGIS Online Option for user to upload accessibility analysis results to ArcGIS Online. User must have an ArcGIS Online account with publishing rights.

46 Custom Lookup Table for Value of Time (Optional) DBF table consisting of decay values per mode with the associated travel times. The table should contain the following columns: time, walk, bike, transit, auto. If no custom lookup tables are used for the accessibility analysis, then the national average curves will be used, as shown in Figure 4. An Example DBF table should have been delivered with your Sugar Access dataset. Lookup Table for Updated Link Speeds (Optional) DBF table consisting of updated speed or level of service values to particular roadway links. The DBF table should contain the following columns: LINK, SPEEDFROM, SPEEDTO, WALKLOS_FR, WALKLOS_BIKELOS_FR, BIKELOS_TO. LINK Corresponds to Here link attribute. WALKLOS and BIKELOS correspond to Walk and Bike level of stress, respectively. Custom Access Score Destination Weights (Optional) DBF table consisting of priority weights and targets for particular types of points of interests, demonstrating the importance of each destination type for that Access Score definition. The DBF table should contain the following columns: DESCRIPTION, CAT_WEIGHT, POI_TARGET, POINTCLASS as demonstrated in Figure 6. As example DBF table should have been delivered with your Sugar Access dataset. How do I run a Non-Work accessibility analysis? OPEN ACCESS SCORE While Access Scores for Work and Non-Work destinations can certainly tell an overarching story about accessibility in our community, there might be a specific question around accessibility that you are wanting to ask. The Open Access Score application allows users to complete two straightforward accessibility analyses: Travel Time Analysis Minimum travel time to a select destination type. Destination Summation Analysis Number of destinations of a particular type accessible. Some questions that might be potentially answered with these types of analyses, would be: What is the minimum walking travel time to a grocery store? What is the minimum transit travel time to a hospital? How many fast food restaurants are accessible within a 15-minute walk? Open Access Score consists of the following parameters: Analysis Type There are two types of accessibility analyses that can be conducted as mentioned above: Travel Time calculates the minimum travel to one of your destinations. Dest Summation calculates the amount of destinations that are accessible within the chosen travel time cutoff. Analysis Location - Locational information, such as Census Blocks, Census Block Groups, Parcels, or user customized zones used to summarize and visualize scores. Must be a polygon feature class within geodatabase. Destination Field within the analysis polygon feature class corresponding to the employment or points of interest type representing the destinations for your accessibility analysis (i.e. what are you analyzing access to?)

47 Time Period Time of day for the accessibility analysis; Morning-Peak, Afternoon, Evening-Peak, Nighttime. Please contact your local Sugar Access administrator if you are interested in knowing the exact times for the time periods. Changing the time period will affect the transit schedule and the auto speeds that are being used for your accessibility analysis. Mode of Travel Travel mode to be used in the accessibility analysis; Walk, Auto, Bike, Transit, All, Non- Auto (All Modes but Auto), and Non-Transit (All Modes but Transit. The transit analysis consists of a combined walk and transit analysis. Maximum Travel Time (minutes) Only destinations within this maximum travel time will be analyzed when running the destination summation analysis. This will reduce the run time of the accessibility scenario being ran. Roadway Network Citilabs formatted Roadway and Pedestrian network from local geodatabase. Turn Penalties Turn Prohibition and/or penalty text file received as part of local Sugar data. Public Transport Network Citilabs formatted Public Transport network from local geodatabase. Average Walking Speed (mph) Average walking speed used when completing a Walk or Transit accessibility analysis. Average Cycling Speed (mph) Average cycling speed used when completing a Bike accessibility analysis. Upload to ArcGIS Online Option for user to upload accessibility analysis results to ArcGIS Online. User must have an ArcGIS Online account with publishing rights. Use Decay Curves for Value of Time Specifies whether to use decay functions for weighting destinations by travel time incurred. If decay curves are not used, all destinations accessible within the specified travel time will be weighted equally. Custom Lookup Table for Value of Time (Optional) DBF table consisting of decay values per mode with the associated travel times. The table should contain the following columns: time, walk, bike, transit, auto. If no custom lookup tables are used for the accessibility analysis, then the national average curves will be used, as shown in Figure 4. An Example DBF table should have been delivered with your Sugar Access dataset. Lookup Table for Updated Link Speeds (Optional) DBF table consisting of updated speed or level of service values to particular roadway links. The DBF table should contain the following columns: LINK, SPEEDFROM, SPEEDTO, WALKLOS_FR, WALKLOS_BIKELOS_FR, BIKELOS_TO. LINK Corresponds to Here link attribute. WALKLOS and BIKELOS correspond to Walk and Bike level of stress, respectively. POI SUMMARY There are two main components of accessibility, those are the origin and destination of a person s trip. These could include someone s home, their place of work, or the neighborhood grocery store. For methodological efficiency purposes, zones are used in lieu of singular points. Therefore, origin and destination point data such as stores and office buildings must be summarized within zones in order to analyze their accessibility. To accomplish this, the POI Summary application allows users to summarize desired destination types within their zonal system. The POI Summary Application is very similar to a simple Spatial Join Geoprocessing type of analysis, in that it will join the specified attributes of a point to the closest polygon (zone). This may be a number of different things, based on the additional local data that you have for your community:

48 Number of elementary schools Number of hospital beds Floor space of grocery store Acres of public parks The POI Summary Application consists of the following parameters: Points of Interest Summary Polygons Locational information, such as Census Blocks, Census Block Groups, Parcels, or user customized zones used to summarize and visualize scores. Must be a polygon feature class within geodatabase. Your desired destination type will be summarized into this zone system, appending your existing data. Points of Interest Layer Point feature class containing points of interest to be used in summary. The feature class should contain a field summarizing the particular point of interest of concern. For instance, if elementary schools were to be summarized from a local school s point feature class, there should be a field called elementary, specifying whether each school is an elementary school (0 or 1). Points of Interest (POI) Category The specific field in the points of interest feature class to be summarized into your zones. Field must be of a numeric field type. This field will be summed among the points of interest within the same zone. For instance, if the category is restaurants, then the number of restaurants will be represented for each input zone. Upload to AGOL Produces an ArcGIS Online map consisting of the POI summary results. POI SUMMARY TUTORIAL The majority of the points of interest types are most likely already summarized in your local geodatabase, within the Zones_POI polygon feature class (or Census_Blocks_POI). In the case that they are not, or if you would like to summarize a local points of interest layer in your community, the following tutorial will enable you to do just that. Let s summarize restaurants into our zone system, using the provided points of interest feature layer. 1. Load the POI feature class in ArcMap. These are included in the local geodatabase provided to you with Sugar Access by Citilabs. a. From the Standard toolbar: click the Add Data button, browse to your local geodatabase, and double-click to add the POI feature class 2. Right-click on the POI layer in the Table of Contents (TOC) and select Open Attribute Table. Check to see whether there is already a field named with the desired name in the table (i.e. restaurants, etc ) a. If there is no field, click on the Table Options button and select Add Field..., then add a new field with type Double, as shown below.

49 3. Select the points you wish to include in this POI category. a. You can select points based upon a query using Selection > Select By Attributes... as shown below. 4. Calculate weights for the selected points of interest, reflecting in this instance whether it is a restaurant or not. a. Use the Show selected records button in the attribute table. Right-click on the Restaurants field and select Field Calculator..., then enter the value of 1 to the selected points for this particular instance. Repeat this step with different selections to attach different weights to different sets of points (perhaps apply a value of 0.5 to fast food restaurants). Or, if you simply want to count the points, assigning equal weight to each, enter a 1 as shown below.

50 b. Or, start an Edit session in ArcMap and adjust the weights for individual points using your local knowledge of the importance and/or capacity of specific facilities. Save your edits and end the session when you are finished. c. Locally-gathered points of interest, such as establishment data, may already contain fields with values that suggest natural weights (such as jobs, parking spaces, or hospital beds). In this case you may not need to calculate a new weight field, or you may be able to copy the weights from an existing field. 5. In Sugar Launch Pad, select POI Summary from the Application drop-down field and edit the key parameters required for your analysis, as shown below. When done, click the Save Keys button and then the Run Scenario button to begin launching the scenario on the cloud. Once the run has been completed, you will download the polygon feature class within the geodatabase. You may the new polygon feature class within the Open Access Score application to measure access, in this case to measure access to restaurants. SCENARIO ANALYZER After you have run a couple of scenarios in Sugar Access, you may wish to make comparisons between the accessibility of each scenario. The Scenario Analyzer application is provided to allow you to accomplish this task. This may be compare different transportation projects, or land-use allocations. The

51 Scenario Analyzer application is a simple application that takes in two accessibility analysis runs (using the same zones or analysis polygons) and calculates the difference, or change in accessibility between the two scenarios. The application assumes that the same type of analysis and application were used for the two scenarios, i.e. Open Access Score Travel Time analysis to hospitals with automobiles, or Access Score Work with transit. The POI Summary Application consists of the following parameters: Base Scenario A one-word description for the base accessibility scenario input. Travel Mode to Analyze Select the mode of which the input accessibility scenarios were conducted. If all modes were conducted in the analyses, please choose the mode that you would like to compare accessibility fore. Base Result Select the geodatabase file from your base scenario. You should reference the entire geodatabase, not just the Access feature class. Comparison Scenario A one-word description for the comparison accessibility scenario input. Comparison Result Select the geodatabase file from your comparison scenario. You should reference the entire geodatabase, not just the Access feature class. Upload to AGOL Produces an ArcGIS Online map consisting of the Scenario Analyzer results. SCENARIO ANALYZER TUTORIAL 1. Select the Scenario Analyzer from the Application drop-down. 2. Enter the key parameters as shown below. Usage notes follow: a. Provide one-word names for both your base and comparison scenario. b. Select the mode at which the accessibility analysis was conducted. If multiple modes were analyzed during the accessibility analysis, select the mode which you would like to compare. Only one mode may be compared at a time.

52 c. Browse to both your base result geodatabase as well as your comparison result geodatabase, referencing just the geodatabase itself. These should be your two selections for the base and comparison result parameters, respectively. Once your Scenario Analyzer run is complete. You may download the results to view and analyze further. The completed result output will be the base scenario feature class appended with the calculated difference between the two scenarios. To learn more about the results from the Scenario Analyzer Application.

53 GLOSSARY Here Here is a worldwide leader in navigation, mapping, and location experiences. Here supplies accurate information for roadway and pedestrian link attributes, necessary in analyzing the transportation network. Here does not only contain physical information about the network, such as the number of lanes or speed limit of the roadway, Here also supplies traffic pattern information for 82 countries worldwide. This traffic speed information is available throughout the day, allowing for differentiating between time-periods when analyzing the transportation network. For more information about Here, click here. GTFS The General Transit Feed Specification (GTFS) supplies a standardized transit schedule for the industry worldwide. The GTFS feeds are the same schedules that are being used for route planning through popular online trip planning websites and platforms. The feed contains a series of.txt files that define the physical location of the transit stops, the specific routes and services that are ran through those stops, and at what time of day, and what specific dates they are ran. GTFS files are produced by local transit agencies and the majority are made public through websites such as transitfeeds.com. For more information about GTFS information, click here. Lookup Tables for Updating Roadway Links There are a few ways to measure the change in accessibility due to changes in roadway travel time or bike and pedestrian level of service. If there are many updates and new links to be analyzed, then the most efficient manner may be to copy and paste an entire new roadway and pedestrian network to edit. However, if there are only a few changes to make to roadway links, then it is usually more efficient to build a table depicting the changes to roadway or pedestrian network. The new speed or level of services attributes will be updated during the accessibility analysis for the specified Here link IDs. In the below example of a link lookup table, you will notice that there are two values for each attribute per link ID. In most cases, Here links are bi-directional (two-way streets). The DIR_TRAVEL attribute within the Here network corresponds with whether a link is To or From it s A and B nodes. This allows the user to update the link in either direction, or both directions. As mentioned above, there are three attributes that you may change to the roadway or pedestrian link: Speed Roadway speed to replace existing speed for specified time-period for accessibility analysis. WalkLOS Roadway walk level of service, corresponding to values 1 through 5. Value will replace current level of service for roadway as calculated by a combination of roadway attributes (Speed Limit, Number of Lanes, Functional Class). For more information about walk level of service in accessibility analysis, click here. BikeLOS Roadway bike level of service, corresponding values 1 through 10. Value will replace current level of service for roadway as calculated by a combination of roadway attributes (Speed Limit, Number of Lanes, Functional Class, Bike ROW). For more information about bike level of service in accessibility analysis, click here. It should also be mentioned that there are additional functionalities that can be served through the link update table.

54 Do Not Change Attribute for Link If a zero is used for a specific attribute for the link, then that value for the link will remain unchanged. For instance, the above table would not change the walk level of service for link 1 in the To direction. Remove link If negative one is used for a specific attribute for the link, then that link will be nontraversable for that specific mode (Speed for auto, WalkLOS for walk, BikeLOS for bike). For an example link update table to download, please click here. Turn Penalty/Prohibition File The turn prohibition file is created from the Here navigation data. The purpose of the file is to depict nonallowable vehicle turning movements based on the navigation data. The data is contained in a.pen file which is a part of your Sugar Access data package. The file can edited with a.txt file editor, and consists of rows depicting a set of sequential links that are not traversable in that particular sequence. In the below figure, turning movements from link to link is prohibited, given the -1 in the right column. A user may edit a local turn penalty/prohibition file to add additional prohibitions or penalties. Sugar Access Time Periods Sugar Access allows for the accessibility analysis of different times of day: AM Peak Midday PM Peak Off Peak Each time-period is specific to the roadway and transit network for which it was defined for. These timeperiods were chosen for specific networks at the time the data was created and delivered. Changing the time-period of your accessibility analysis, has two effects: Auto Speeds The auto speeds within the Here network are calculated by averaging the hourly speeds across the defined time-period. In the accessibility analysis, Sugar will use the speed attribute associated with the specific time-period. The speed attributes are defined within the Roadway and Pedestrian metadata. Transit Schedule The transit network may differ by time-period in terms of the headway of the specific service and the run time of that service. In the accessibility analysis, Sugar will use the headway and average run time attributes associated with the specific time-period. The transit attributes are defined within the transit metadata. Destination Scoresheet The destination scoresheet allows a user to choose the types of destinations that they want to be included in their non-work accessibility analysis. The figure below shows the default destination

55 scoresheet for the non-work accessibility analysis, which was developed for Virginia s Smart Scale prioritization process. There are four different fields that make up the destination scoresheet: Description Type of non-work destination. May be more than one specific type of point of interest. Category Weight the relative weight that should be applied to the specific non-work destination category. The combined category weights of all the rows should add up to 100. POI Target The target number of points of interest which must be accessible nearby in order to assign the full category weight to the score for a given origin. Pointclass A comma separated list of point of interest type codes. These code values can be found in the POI metadata. The non-work destination scoresheet is configurable by a user as a.dbf and an example scoresheet is provided to the user with their original Sugar dataset. For more information about the manner in which the destination scoresheet is applied methodologically, please view the Sugar Access White Paper. Travel Time Decay Curves Propensity to travel curves (or decay curves) are used to value shorter trips more than longer trips (in travel time), as well as to eliminate the need for an arbitrary travel time cutoff (such as 30 minutes). Decay curves are represented through multiple curves, one for each travel mode, and one for each trip purpose. The figure below represents the propensity to travel to work destinations on a national level, utilizing National Household Travel Survey (NHTS) data, produced by SSTI. The decay factor on the y- axis represents the percent of people willing to travel, such that the individual lines represent the change in the propensity to travel for different travel times, and different modes. For instance, when calculating the overall accessibility of one zone, you utilize the associated decay curves for each travel time. If 1,000 jobs were accessible by auto at a 15 minute travel time, this would equate to 550 equivalent jobs, while if the same jobs were accessible by auto at a 30 minute travel time, it would equate to 210 equivalent jobs, based on the extracted decay factors in the figure below. The same process is done for jobs accessible by 1 minute, 2 minutes, 3 minutes 180 minutes, to come up with an Access Score Work for each zone.

56 Decay Factor 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Travel Time (minutes) Auto - Work Transit - Work Walk - Work Bike - Work Travel Time Decay Factor 15 minutes 55% 30 minutes 21% For more information on how decay curves are applied in the methodology of Sugar Access, please view the Sugar Access White Paper.

57 Appendix

58 Pedestrian Level of Service Lookup 6+ Lanes 4+ Lanes 2 Lanes Speed Speed Speed Functional Class >= <=30 >= <=30 >= <=30 Freeway/Major 1,2 Highway Major Arterial Minor Arterial/Collector Local Lanes Ped Only NA NA NA 5

59 Bicycle Level of Service Lookup