Difference between revisions of "Sugar"

From TransitWiki
Jump to navigation Jump to search
(Many updates - outputs, cost, access and SNE)
(Reorganized, added information on run time, clarified transit network needs)
 
(One intermediate revision by the same user not shown)
Line 5: Line 5:
 
|license= Proprietary [http://www.citilabs.com/end-user-license-agreement/ http://www.citilabs.com/ end-user-license-agreement/]
 
|license= Proprietary [http://www.citilabs.com/end-user-license-agreement/ http://www.citilabs.com/ end-user-license-agreement/]
 
|documentation= None found online
 
|documentation= None found online
 +
|data_in= ACS/Census, HERE, LODES, [[GTFS]], GIS shapefiles
 +
|data_out= GIS database, Microsoft Access Database, maps, Access Score
 
|website= [http://www.citilabs.com/software/sugar/ http://www.citilabs.com/ software/sugar/]
 
|website= [http://www.citilabs.com/software/sugar/ 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 offers tools for managing, analyzing, and visualizing transportation networks and accessibility in any community. Sugar has two main components:
 
* Sugar Access
 
* Sugar Access
 
* Sugar Network Editor
 
* Sugar Network Editor
 +
 +
=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. This allows for accessibility measures by different modes and also means that when calculating travel time for transit, Sugar calculates the entire trip length, including walking to and from the station and wait time. Because street and transit data is incorporated in the analysis, accessibility analysis takes into account physical barriers in the street network that may hinder walking to a station. The software comes pre-loaded with data for many communities, but data can also be edited using Sugar's network editor. This allows a user to analyze the impact of non-transit projects on the transit network if it affects accessibility to stations. In order give accurate access scores for transit, Sugar calculates exact travel times, and so requires complete transit network information, include station locations and stop to stop travel times.
 +
 +
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, 30 min, 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 30 min".
 +
 +
===Run time===
 +
The accessibility measurements are very computationally intensive, and so can take a long time, depending on a number of factors such as mode choice, network size, number of zones, and computing power. An estimates average run time is 2-4 hours<ref>Personal email contact with Matthew Pettit, Product Applications Engineer at Citilabs</ref>. Measuring transit accessibility tends to take longer than walking or driving.
 +
 +
===Case study===
 +
Sugar Access was used in [http://smartscale.org/ Virginia DOT's Smart Scale project].
  
 
=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.
+
'''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 with transportation software products such as Citilabs Cube and Trafficware® Synchro.
  
−
==Transit data==
+
===Transit data===
 
'''Transit data''' can be imported from [[GTFS]]:
 
'''Transit data''' can be imported from [[GTFS]]:
 
* Route alignments
 
* Route alignments
Line 22: Line 45:
 
* Schedules
 
* Schedules
  
−
The SNE allows editing all of the above features.
+
The SNE allows editing of all of the above features.
  
−
==Street network==
+
===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==
+
===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.
 
'''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=
+
=Technical Specifications=
−
'''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===
−
 
 
−
==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.
 
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=
+
===Requirements===
 
Sugar requires [http://arcgis.com ArcGIS].
 
Sugar requires [http://arcgis.com ArcGIS].
  
−
=Cost / Licensing=
+
===Cost / Licensing===
−
This software is generally licensed on an annual basis, but shorter subscriptions are available with a premium fee.
+
This software is generally licensed on an annual basis, but shorter subscriptions are available with a premium fee. Costs are negotiated on a case by case basis, depending on clients needs.
−
 
 
−
=Case study=
 
−
Sugar Access was used in [http://smartscale.org/ Virginia DOT's Smart Scale project].
 
  
 
=References=
 
=References=

Latest revision as of 00:29, 13 May 2017

Sugar
Sugar-logo.png
Vendor Citilabs
License Proprietary http://www.citilabs.com/ end-user-license-agreement/
Documentation None found online
Data Input ACS/Census, HERE, LODES, GTFS, GIS shapefiles
Data Output GIS database, Microsoft Access Database, maps, Access Score
Website http://www.citilabs.com/ software/sugar/



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 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. This allows for accessibility measures by different modes and also means that when calculating travel time for transit, Sugar calculates the entire trip length, including walking to and from the station and wait time. Because street and transit data is incorporated in the analysis, accessibility analysis takes into account physical barriers in the street network that may hinder walking to a station. The software comes pre-loaded with data for many communities, but data can also be edited using Sugar's network editor. This allows a user to analyze the impact of non-transit projects on the transit network if it affects accessibility to stations. In order give accurate access scores for transit, Sugar calculates exact travel times, and so requires complete transit network information, include station locations and stop to stop travel times.

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, 30 min, 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]

Calculating accessibility.png

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 30 min".

Run time

The accessibility measurements are very computationally intensive, and so can take a long time, depending on a number of factors such as mode choice, network size, number of zones, and computing power. An estimates average run time is 2-4 hours[2]. Measuring transit accessibility tends to take longer than walking or driving.

Case study

Sugar Access was used in Virginia DOT's Smart Scale project.

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 with 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 of 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.

Technical Specifications

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. Costs are negotiated on a case by case basis, depending on clients needs.

References

  1. ↑ See slide 6, Eric Sundquist, TCS 2016, https://www.slideshare.net/otrec/eric-sundquist-tcs-2016/1
  2. ↑ Personal email contact with Matthew Pettit, Product Applications Engineer at Citilabs
Retrieved from "https://www.transitwiki.org/TransitWiki/index.php?title=Sugar&oldid=4223"