Difference between revisions of "Sugar"
m |
Aaronantrim (talk | contribs) (Many updates - outputs, cost, access and SNE) |
||
| Line 16: | Line 16: | ||
'''Sugar Network Editor (SNE)''' is an add-on to ESRI's ArcGIS desktop. It allows one to create and maintain transportation networks directly in ArcGIS. These networks are directly compatible with ESRI’s Network Analyst extension and other ESRI extensions, and transportation software products such as Citilabs Cube and Trafficware® Synchro. | '''Sugar Network Editor (SNE)''' is an add-on to ESRI's ArcGIS desktop. It allows one to create and maintain transportation networks directly in ArcGIS. These networks are directly compatible with ESRI’s Network Analyst extension and other ESRI extensions, and transportation software products such as Citilabs Cube and Trafficware® Synchro. | ||
| + | ==Transit data== | ||
'''Transit data''' can be imported from [[GTFS]]: | '''Transit data''' can be imported from [[GTFS]]: | ||
* Route alignments | * Route alignments | ||
| Line 23: | Line 24: | ||
The SNE allows editing all of the above features. | The SNE allows editing all of the above features. | ||
| + | ==Street network== | ||
'''Street network''' information can also be edited in the SNE. The default roadway map comes from [https://here.com/en/products-services/data/here-map-data HERE]. | '''Street network''' information can also be edited in the SNE. The default roadway map comes from [https://here.com/en/products-services/data/here-map-data HERE]. | ||
| + | |||
| + | ==Points of interest (POI) / Destinations== | ||
| + | '''POI''' data is also imported from the [https://here.com/en/products-services/data/here-map-data HERE] dataset (this is the same dataset that is also used for mobile navigation systems). This is used for calculating access to destinations and categories of destinations. | ||
=Sugar Access= | =Sugar Access= | ||
| − | '''Sugar Access''' is used to score and understand accessibility to employment opportunities, various errands, public services, and other destinations. It | + | '''Sugar Access''' is used to score and understand accessibility to employment opportunities, various errands, public services, and other destinations. It provides multi-modal accessibility calculations. Because street and transit data is incorporated in the analysis, accessibility analysis takes into account physical barriers in the street network. The software comes pre-loaded with data for communities. |
| + | |||
| + | Sugar Access can provide the following indicators: | ||
| + | |||
| + | * Travel times from single origin to many destinations | ||
| + | * Destination summation for a particular location (number of destinations of a particular type), e.g. parks by walking, jobs by transit | ||
| + | * Comprehensive accessibility analysis: For an entire population, what % of {jobs, etc.} can be accessed in 10 min, 20 min, 30min, etc. | ||
| + | * "Access Score": A weighted score that represents the accessibility implications of a transit scenario (see further discussion below). | ||
| + | |||
| + | ==Access Score== | ||
| + | The software can generate an "Accessibility Score" that is calibrated according to travelers' willingness to to make commute trips of various time lengths according to mode. The below graph shows one comparison of travelers' willingness to accept travel times by mode.<ref>See slide 6, Eric Sundquist, TCS 2016, https://www.slideshare.net/otrec/eric-sundquist-tcs-2016/1</ref> | ||
| + | |||
| + | [[File:Calculating accessibility.png|100px|frame|none]] | ||
| + | |||
| + | Factoring travelers' willingness to travel to weight the usefulness or realistic availability of jobs helps to provide a more complete picture of accessibility and avoids the "cliff effect" where a job that is 31 minutes away is not factored into an indicator of "Jobs within 30min". | ||
| + | |||
| + | ==Data outputs== | ||
| + | All analysis outputs can be exported as an ArcGIS Geodatabase (.GDP) or Microsoft Access database file (.MDB). All outputs used for rendering maps is available in ArcGIS or in exported files. | ||
| + | |||
| + | =Requirements= | ||
| + | Sugar requires [http://arcgis.com ArcGIS]. | ||
| + | |||
| + | =Cost / Licensing= | ||
| + | This software is generally licensed on an annual basis, but shorter subscriptions are available with a premium fee. | ||
| − | + | =Case study= | |
| + | Sugar Access was used in [http://smartscale.org/ Virginia DOT's Smart Scale project]. | ||
| − | + | =References= | |
<references /> | <references /> | ||
Revision as of 21:42, 3 April 2017
 | |
| Vendor | Citilabs |
|---|---|
| License | Proprietary http://www.citilabs.com/ end-user-license-agreement/ |
| Documentation | None found online |
| Website | http://www.citilabs.com/ software/sugar/ |
Overview
Sugar offers tools for managing, analyzing, and visualizing transportation networks and accessibility in any community. Sugar has two main components:
- Sugar Access
- Sugar Network Editor
Sugar Network Editor
Sugar Network Editor (SNE) is an add-on to ESRI's ArcGIS desktop. It allows one to create and maintain transportation networks directly in ArcGIS. These networks are directly compatible with ESRI’s Network Analyst extension and other ESRI extensions, and transportation software products such as Citilabs Cube and Trafficware® Synchro.
Transit data
Transit data can be imported from GTFS:
- Route alignments
- Stop locations
- Schedules
The SNE allows editing all of the above features.
Street network
Street network information can also be edited in the SNE. The default roadway map comes from HERE.
Points of interest (POI) / Destinations
POI data is also imported from the HERE dataset (this is the same dataset that is also used for mobile navigation systems). This is used for calculating access to destinations and categories of destinations.
Sugar Access
Sugar Access is used to score and understand accessibility to employment opportunities, various errands, public services, and other destinations. It provides multi-modal accessibility calculations. Because street and transit data is incorporated in the analysis, accessibility analysis takes into account physical barriers in the street network. The software comes pre-loaded with data for communities.
Sugar Access can provide the following indicators:
- Travel times from single origin to many destinations
- Destination summation for a particular location (number of destinations of a particular type), e.g. parks by walking, jobs by transit
- Comprehensive accessibility analysis: For an entire population, what % of {jobs, etc.} can be accessed in 10 min, 20 min, 30min, etc.
- "Access Score": A weighted score that represents the accessibility implications of a transit scenario (see further discussion below).
Access Score
The software can generate an "Accessibility Score" that is calibrated according to travelers' willingness to to make commute trips of various time lengths according to mode. The below graph shows one comparison of travelers' willingness to accept travel times by mode.[1]
Factoring travelers' willingness to travel to weight the usefulness or realistic availability of jobs helps to provide a more complete picture of accessibility and avoids the "cliff effect" where a job that is 31 minutes away is not factored into an indicator of "Jobs within 30min".
Data outputs
All analysis outputs can be exported as an ArcGIS Geodatabase (.GDP) or Microsoft Access database file (.MDB). All outputs used for rendering maps is available in ArcGIS or in exported files.
Requirements
Sugar requires ArcGIS.
Cost / Licensing
This software is generally licensed on an annual basis, but shorter subscriptions are available with a premium fee.
Case study
Sugar Access was used in Virginia DOT's Smart Scale project.
References
- ↑ See slide 6, Eric Sundquist, TCS 2016, https://www.slideshare.net/otrec/eric-sundquist-tcs-2016/1