Transport Analyst - Revision history

Leeor: redirect to Conveyal Analysis

2017-08-31T21:07:30Z

redirect to Conveyal Analysis

← Older revision		Revision as of 21:07, 31 August 2017
Line 1:		Line 1:
			#REDIRECT [[Conveyal Analysis]]
	~~{{infobox~~
	~~\|title=Transport Analyst~~
	~~\|image=~~
	~~\|vendor=[[Conveyal]]~~
	~~\|license=[[The MIT License]]~~
	~~\|documentation= http://analysis-ui.readthedocs.io/en/latest/~~
	~~\|data_in= [[GTFS]], [[OpenStreetMap]], ACS/Census, LODES, custom shapefiles~~
	~~\|data_out= GIS shapefiles, maps, accessibility graphs, GeoTIFF,~~
	~~\|website= [http://conveyal.com/projects/analyst/ http://conveyal.com/projects/analyst/]~~
	}}

	Transport Analyst integrates transit and land use data to compare current system performance and accessibility with various scenarios. It is an open source tool developed by [[Conveyal]], and can be hosted and run independently or hosted by Conveyal for a fee along with consulting services.

	~~==Accessibility Assessment==~~
	[[~~File:~~Conveyal~~-jobs-access.png\|thumb\|Identifying places that see increased access to jobs due to a new transit line. <br>Source: http://conveyal.com/projects/analyst/]]~~
	~~[[File:~~Analysis-spectrogram.png\|thumb\|Accessibility spectrogram from Conveyal Analyst. Shows the increase in accessible opportunities (in this case jobs) as travel time increases. The wider portions reveal system uncertainty or unreliability caused by low service frequency.<ref>Conveyal analysis-ui documentation. Accessed 20 April 2017. http://analysis-ui.readthedocs.io/en/latest/analysis/#spectrogram</ref> ]]

	Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes offer new opportunities for collaboration between land use and transportation planning. The software can intake multiple alternatives and return graphical prototypes such as spectrograms and histograms that compare accessibility outcomes for the different scenarios.

	The accessibility outcomes offered by Analyst display the total number of a given amenity that can be reached within a given amount of time from a given point, or for a full system analysis, the number of origin destination combinations available within a given amount of time. For example, it can show how many jobs can be reached from a household, or how many household-job combinations exist withing a time cutoff. The information is displayed as a spectrogram that demonstrates the change in access to the given amenity as the travel time cutoff increases, and as a histogram that shows the variability of accessibility for a given time cutoff with in a time range, highlighting the effects of schedules and headways.

	A single point analysis, showing accessibility from that point to all other points, can be calculated quickly, usually taking 5-15 second. An analysis of an entire region, looking at accessibility from every point to every other point, takes longer. The factors that most affect computation time are the size of the region, the number of points in the region, and the size and density of the transit and transportation network. Furthermore, a scenario analysis is able to use results from the base case and only run the analysis where results will differ. Therefore, more changes in a scenario will lead to longer computational time. An analysis run on a single server can take anywhere from a few hours to a few days depending on the complexity of the system. If the analysis is run on multiple servers, either using [[Conveyal\|Conveyal's]] hosting service or through other access to cluster computing, the runtime can be reduced to a few minutes to a few hours.

	~~==Scenario Creation==~~
	~~[[File:Analyst-scenario-editor.png\|thumb\|Modeling a new transit line using the scenario editor. <br>Source: http://conveyal.com/projects/analyst/]]~~
	Different scenarios can be generated a number of different ways. Future scenarios can be generated by importing foretasted demographic and jobs data as custom shapefiles. These are usually derived from regional or state forecast models. Scenarios can also be generated by importing custom demographic, jobs, or point destination data that represent the predicted result of a land use change or of a new development. Furthermore, scenarios can represent changes or additions to the transit system, generated through edited [[GTFS]] files or by using [[conveyal\|Conveyal's]] scenario editing tool. If a new potential transit line only has a route planned, the scenario editor can add stops according to a set spacing. These can be moved to represent more likely stop location, say at large intersections or transit centers. Multiple scenarios can be generated and run simultaneously to offer an accessibility and performance comparison analysis.

	~~==Other Features==~~
	~~===Public Outreach===~~
	Analyst can be run on a web interface that allows for public outreach and consultation. The map allows users to see the impact alternative scenarios would have on them and to make recommendations as a result. It can output maps in [[GIS]] format for integration into publications and reports.

	~~===Walk time===~~
	Travel time calculations incorporate pedestrian travel time, using the street network to account for how long it takes to walk to and from the bus station. [[Conveyal]] is currently developing other multimodal access calculations, such and biking and driving, so that bikes on transit, bikeshare, and park-and-ride can be better accounted for. Walk time is calculated using the pedestrian street network available through [[OpenStreetMap]], however a direct street network editor is in development.

	~~===Title VI and Equity===~~
	Using demographic data from census inputs, Analyst can preform equity analyses and reveal disparate impacts that a given scenario might create. This analysis aides transit agencies to ensure projects comply with [[Transit and Civil Rights\| Title VI]] in the US, and supports agencies in determining how projects align with their own internal equity goals.

	~~==Open-source==~~
	[[Conveyal\| Conveyal's]] commitment to open data and open-source has led them to use open data for all of Transport Analyst's inputs, such as publicly available [[GTFS]] feeds, map data from [[OpenStreetMap]], and census data. The components for Analyst are themselves open source, licensed under the [[Apache 2]] license.

	~~==References==~~
	~~<references />~~

	~~[[Category:GTFS-consuming applications]]~~
	~~[[Category: Scenario planning tools~~]]

Leeor: explaining the accessibility dispaly

2017-05-05T20:59:31Z

explaining the accessibility dispaly

← Older revision		Revision as of 20:59, 5 May 2017
Line 15:		Line 15:
	==Accessibility Assessment==		==Accessibility Assessment==
	[[File:Conveyal-jobs-access.png\|thumb\|Identifying places that see increased access to jobs due to a new transit line. <br>Source: http://conveyal.com/projects/analyst/]]		[[File:Conveyal-jobs-access.png\|thumb\|Identifying places that see increased access to jobs due to a new transit line. <br>Source: http://conveyal.com/projects/analyst/]]
	Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes offer new opportunities for collaboration between land use and transportation planning. . The software can intake multiple alternatives and return graphical prototypes such as spectrograms and histograms that compare accessibility outcomes for the different scenarios.		[[File:Analysis-spectrogram.png\|thumb\|Accessibility spectrogram from Conveyal Analyst. Shows the increase in accessible opportunities (in this case jobs) as travel time increases. The wider portions reveal system uncertainty or unreliability caused by low service frequency.<ref>Conveyal analysis-ui documentation. Accessed 20 April 2017. http://analysis-ui.readthedocs.io/en/latest/analysis/#spectrogram</ref> ]]

			Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes offer new opportunities for collaboration between land use and transportation planning. The software can intake multiple alternatives and return graphical prototypes such as spectrograms and histograms that compare accessibility outcomes for the different scenarios.

			The accessibility outcomes offered by Analyst display the total number of a given amenity that can be reached within a given amount of time from a given point, or for a full system analysis, the number of origin destination combinations available within a given amount of time. For example, it can show how many jobs can be reached from a household, or how many household-job combinations exist withing a time cutoff. The information is displayed as a spectrogram that demonstrates the change in access to the given amenity as the travel time cutoff increases, and as a histogram that shows the variability of accessibility for a given time cutoff with in a time range, highlighting the effects of schedules and headways.

	A single point analysis, showing accessibility from that point to all other points, can be calculated quickly, usually taking 5-15 second. An analysis of an entire region, looking at accessibility from every point to every other point, takes longer. The factors that most affect computation time are the size of the region, the number of points in the region, and the size and density of the transit and transportation network. Furthermore, a scenario analysis is able to use results from the base case and only run the analysis where results will differ. Therefore, more changes in a scenario will lead to longer computational time. An analysis run on a single server can take anywhere from a few hours to a few days depending on the complexity of the system. If the analysis is run on multiple servers, either using [[Conveyal\|Conveyal's]] hosting service or through other access to cluster computing, the runtime can be reduced to a few minutes to a few hours.		A single point analysis, showing accessibility from that point to all other points, can be calculated quickly, usually taking 5-15 second. An analysis of an entire region, looking at accessibility from every point to every other point, takes longer. The factors that most affect computation time are the size of the region, the number of points in the region, and the size and density of the transit and transportation network. Furthermore, a scenario analysis is able to use results from the base case and only run the analysis where results will differ. Therefore, more changes in a scenario will lead to longer computational time. An analysis run on a single server can take anywhere from a few hours to a few days depending on the complexity of the system. If the analysis is run on multiple servers, either using [[Conveyal\|Conveyal's]] hosting service or through other access to cluster computing, the runtime can be reduced to a few minutes to a few hours.

Leeor: add street network info

2017-05-05T20:43:01Z

add street network info

← Older revision		Revision as of 20:43, 5 May 2017
Line 28:		Line 28:

	===Walk time===		===Walk time===
	Travel time calculations incorporate pedestrian travel time, using the street network to account for how long it takes to walk to and from the bus station. [[Conveyal]] is currently developing other multimodal access calculations, such and biking and driving, so that bikes on transit, bikeshare, and park-and-ride can be better accounted for.		Travel time calculations incorporate pedestrian travel time, using the street network to account for how long it takes to walk to and from the bus station. [[Conveyal]] is currently developing other multimodal access calculations, such and biking and driving, so that bikes on transit, bikeshare, and park-and-ride can be better accounted for. Walk time is calculated using the pedestrian street network available through [[OpenStreetMap]], however a direct street network editor is in development.

	===Title VI and Equity===		===Title VI and Equity===

Leeor: correct multimodal info

2017-05-05T20:39:56Z

correct multimodal info

← Older revision		Revision as of 20:39, 5 May 2017
Line 27:		Line 27:
	Analyst can be run on a web interface that allows for public outreach and consultation. The map allows users to see the impact alternative scenarios would have on them and to make recommendations as a result. It can output maps in [[GIS]] format for integration into publications and reports.		Analyst can be run on a web interface that allows for public outreach and consultation. The map allows users to see the impact alternative scenarios would have on them and to make recommendations as a result. It can output maps in [[GIS]] format for integration into publications and reports.

	===~~Multimodal Analysis~~===		===Walk time===
	~~Analyst allows~~ for multimodal ~~analysis~~, ~~incorporating walking, cycling, transit~~ and driving~~. Multimodal analysis allows planners to account for park-and-rides~~, bikes on transit, ~~and~~ bikeshare ~~systems. It also allows planners to consider walking time to~~ and ~~from stops when considering accessibility on the system. As a result, first~~ and ~~last mile questions~~ can be ~~addressed directly in the planning process~~.		Travel time calculations incorporate pedestrian travel time, using the street network to account for how long it takes to walk to and from the bus station. [[Conveyal]] is currently developing other multimodal access calculations, such and biking and driving, so that bikes on transit, bikeshare, and park-and-ride can be better accounted for.

	===Title VI and Equity===		===Title VI and Equity===

Leeor: added auto stop genration

2017-05-05T20:34:34Z

added auto stop genration

← Older revision		Revision as of 20:34, 5 May 2017
Line 21:		Line 21:
	==Scenario Creation==		==Scenario Creation==
	[[File:Analyst-scenario-editor.png\|thumb\|Modeling a new transit line using the scenario editor. <br>Source: http://conveyal.com/projects/analyst/]]		[[File:Analyst-scenario-editor.png\|thumb\|Modeling a new transit line using the scenario editor. <br>Source: http://conveyal.com/projects/analyst/]]
	Different scenarios can be generated a number of different ways. Future scenarios can be generated by importing foretasted demographic and jobs data as custom shapefiles. These are usually derived from regional or state forecast models. Scenarios can also be generated by importing custom demographic, jobs, or point destination data that ~~would be~~ the predicted result of a land use change or of a new development. Furthermore, scenarios can represent changes or additions to the transit system, generated through edited [[GTFS]] files or by using Conveyal's scenario editing tool. ~~multiple~~ scenarios can be generated and run simultaneously to offer accessibility and performance analysis.		Different scenarios can be generated a number of different ways. Future scenarios can be generated by importing foretasted demographic and jobs data as custom shapefiles. These are usually derived from regional or state forecast models. Scenarios can also be generated by importing custom demographic, jobs, or point destination data that represent the predicted result of a land use change or of a new development. Furthermore, scenarios can represent changes or additions to the transit system, generated through edited [[GTFS]] files or by using [[conveyal\|Conveyal's]] scenario editing tool. If a new potential transit line only has a route planned, the scenario editor can add stops according to a set spacing. These can be moved to represent more likely stop location, say at large intersections or transit centers. Multiple scenarios can be generated and run simultaneously to offer an accessibility and performance comparison analysis.

	==Other Features==		==Other Features==

Leeor at 20:29, 5 May 2017

2017-05-05T20:29:28Z

← Older revision		Revision as of 20:29, 5 May 2017
Line 17:		Line 17:
	Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes offer new opportunities for collaboration between land use and transportation planning. . The software can intake multiple alternatives and return graphical prototypes such as spectrograms and histograms that compare accessibility outcomes for the different scenarios.		Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes offer new opportunities for collaboration between land use and transportation planning. . The software can intake multiple alternatives and return graphical prototypes such as spectrograms and histograms that compare accessibility outcomes for the different scenarios.

	A single point analysis, showing accessibility from that point to all other points, can be calculated quickly, usually taking 5-15 second. An analysis of an entire region, looking at accessibility from every point to every other point, takes longer. The factors that most affect computation time are the size of the region, the number of points in the region, and the size and density of the transit and transportation network. Furthermore, a scenario analysis is able to use results from the base case and only run the analysis where results will differ. Therefore, more changes in a scenario will lead to longer computational time. An analysis run on a single server can take anywhere from a few hours to a few days depending on the complexity of the system. If the analysis is run on multiple servers, either using [[Conveyal\|Conveyal's]] hosting service or through other access to cluster computing, the runtime can be reduced to a few ~~minute~~ to a few hours.		A single point analysis, showing accessibility from that point to all other points, can be calculated quickly, usually taking 5-15 second. An analysis of an entire region, looking at accessibility from every point to every other point, takes longer. The factors that most affect computation time are the size of the region, the number of points in the region, and the size and density of the transit and transportation network. Furthermore, a scenario analysis is able to use results from the base case and only run the analysis where results will differ. Therefore, more changes in a scenario will lead to longer computational time. An analysis run on a single server can take anywhere from a few hours to a few days depending on the complexity of the system. If the analysis is run on multiple servers, either using [[Conveyal\|Conveyal's]] hosting service or through other access to cluster computing, the runtime can be reduced to a few minutes to a few hours.

	==Scenario Creation==		==Scenario Creation==

Leeor: added runtime info

2017-05-05T20:28:59Z

added runtime info

← Older revision		Revision as of 20:28, 5 May 2017
Line 15:		Line 15:
	==Accessibility Assessment==		==Accessibility Assessment==
	[[File:Conveyal-jobs-access.png\|thumb\|Identifying places that see increased access to jobs due to a new transit line. <br>Source: http://conveyal.com/projects/analyst/]]		[[File:Conveyal-jobs-access.png\|thumb\|Identifying places that see increased access to jobs due to a new transit line. <br>Source: http://conveyal.com/projects/analyst/]]
	Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. ~~For example,~~ Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes ~~allow~~ land use ~~planner~~ and transportation ~~planners to collaborate toward shared goals~~. The software can intake multiple alternatives and ~~quickly display~~ graphical prototypes that compare accessibility outcomes for the different scenarios.		Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes offer new opportunities for collaboration between land use and transportation planning. . The software can intake multiple alternatives and return graphical prototypes such as spectrograms and histograms that compare accessibility outcomes for the different scenarios.

			A single point analysis, showing accessibility from that point to all other points, can be calculated quickly, usually taking 5-15 second. An analysis of an entire region, looking at accessibility from every point to every other point, takes longer. The factors that most affect computation time are the size of the region, the number of points in the region, and the size and density of the transit and transportation network. Furthermore, a scenario analysis is able to use results from the base case and only run the analysis where results will differ. Therefore, more changes in a scenario will lead to longer computational time. An analysis run on a single server can take anywhere from a few hours to a few days depending on the complexity of the system. If the analysis is run on multiple servers, either using [[Conveyal\|Conveyal's]] hosting service or through other access to cluster computing, the runtime can be reduced to a few minute to a few hours.

	==Scenario Creation==		==Scenario Creation==

Leeor: /* Out Features */

2017-05-05T20:14:08Z

Out Features

← Older revision		Revision as of 20:14, 5 May 2017
Line 21:		Line 21:
	Different scenarios can be generated a number of different ways. Future scenarios can be generated by importing foretasted demographic and jobs data as custom shapefiles. These are usually derived from regional or state forecast models. Scenarios can also be generated by importing custom demographic, jobs, or point destination data that would be the predicted result of a land use change or of a new development. Furthermore, scenarios can represent changes or additions to the transit system, generated through edited [[GTFS]] files or by using Conveyal's scenario editing tool. multiple scenarios can be generated and run simultaneously to offer accessibility and performance analysis.		Different scenarios can be generated a number of different ways. Future scenarios can be generated by importing foretasted demographic and jobs data as custom shapefiles. These are usually derived from regional or state forecast models. Scenarios can also be generated by importing custom demographic, jobs, or point destination data that would be the predicted result of a land use change or of a new development. Furthermore, scenarios can represent changes or additions to the transit system, generated through edited [[GTFS]] files or by using Conveyal's scenario editing tool. multiple scenarios can be generated and run simultaneously to offer accessibility and performance analysis.

	==~~Out~~ Features==		==Other Features==
	===Public Outreach===		===Public Outreach===
	Analyst can be run on a web interface that allows for public outreach and consultation. The map allows users to see the impact alternative scenarios would have on them and to make recommendations as a result. It can output maps in [[GIS]] format for integration into publications and reports.		Analyst can be run on a web interface that allows for public outreach and consultation. The map allows users to see the impact alternative scenarios would have on them and to make recommendations as a result. It can output maps in [[GIS]] format for integration into publications and reports.

Leeor at 20:23, 6 April 2017

2017-04-06T20:23:19Z

← Older revision		Revision as of 20:23, 6 April 2017
Line 1:		Line 1:
	~~{{edit queue~~
	~~\|editor=Leeor~~
	}}

	{{infobox		{{infobox
Line 9:		Line 6:
	\|license=[[The MIT License]]		\|license=[[The MIT License]]
	\|documentation= http://analysis-ui.readthedocs.io/en/latest/		\|documentation= http://analysis-ui.readthedocs.io/en/latest/
	\|data_in= [[GTFS]], [[OpenStreetMap]], ~~National census data~~		\|data_in= [[GTFS]], [[OpenStreetMap]], ACS/Census, LODES, custom shapefiles
	\|data_out= [[GIS]]		\|data_out= GIS shapefiles, maps, accessibility graphs, GeoTIFF,
	\|website= [http://conveyal.com/projects/analyst/ http://conveyal.com/projects/analyst/]		\|website= [http://conveyal.com/projects/analyst/ http://conveyal.com/projects/analyst/]
	}}		}}

	Transport Analyst ~~accounts for~~ transit and land use data to ~~evaluate the~~ performance ~~of impact of current transport systems~~ and ~~assess how~~ various ~~system changes would alter performance~~. It's an open source tool developed by [[Conveyal]] and is the ~~primary~~ tool ~~they use when preforming consulting services~~.		Transport Analyst integrates transit and land use data to compare current system performance and accessibility with various scenarios. It is an open source tool developed by [[Conveyal]], and can be hosted and run independently or hosted by Conveyal for a fee along with consulting services.

			==Accessibility Assessment==
			[[File:Conveyal-jobs-access.png\|thumb\|Identifying places that see increased access to jobs due to a new transit line. <br>Source: http://conveyal.com/projects/analyst/]]
			Analyst offers basic statistics of how far or fast a system can carry people but also, by layering information from [[OpenStreetMap]] and census data, it allows planners to view accessibility. For example, Analyst can display job opportunities, businesses, and various amenities that become more accessible to people living near a new planned transit line. Accessibility outcomes allow land use planner and transportation planners to collaborate toward shared goals. The software can intake multiple alternatives and quickly display graphical prototypes that compare accessibility outcomes for the different scenarios.

			==Scenario Creation==
			[[File:Analyst-scenario-editor.png\|thumb\|Modeling a new transit line using the scenario editor. <br>Source: http://conveyal.com/projects/analyst/]]
			Different scenarios can be generated a number of different ways. Future scenarios can be generated by importing foretasted demographic and jobs data as custom shapefiles. These are usually derived from regional or state forecast models. Scenarios can also be generated by importing custom demographic, jobs, or point destination data that would be the predicted result of a land use change or of a new development. Furthermore, scenarios can represent changes or additions to the transit system, generated through edited [[GTFS]] files or by using Conveyal's scenario editing tool. multiple scenarios can be generated and run simultaneously to offer accessibility and performance analysis.

	Analyst ~~goes beyond basic statistics of how far or fast~~ a ~~system can carry people~~. ~~By layering information from [[OpenStreetMap]] and census data, it~~ allows ~~planners~~ to ~~view accessibility. For example, Analyst can display job opportunities, businesses,~~ and ~~various amenities that become more accessible~~ to ~~people living~~ a ~~new planned transit line~~. ~~In this way it ties~~ in ~~land use planning. It is geared to intake multiple alternatives~~ and ~~quickly display graphical prototypes that compare accessibility outcomes for the different scenarios~~.		==Out Features==
			===Public Outreach===
			Analyst can be run on a web interface that allows for public outreach and consultation. The map allows users to see the impact alternative scenarios would have on them and to make recommendations as a result. It can output maps in [[GIS]] format for integration into publications and reports.

	Analyst ~~can be run on a web interface that~~ allows for ~~public outreach~~ and ~~consultation~~. ~~The map~~ allows ~~users~~ to ~~see the impact alternative scenarios would have~~ on ~~them~~ and to ~~make recommendations as~~ a result~~. It~~ can ~~output maps~~ in ~~[[GIS]] format to easily integrate results into publications and reports~~.		===Multimodal Analysis===
			Analyst allows for multimodal analysis, incorporating walking, cycling, transit and driving. Multimodal analysis allows planners to account for park-and-rides, bikes on transit, and bikeshare systems. It also allows planners to consider walking time to and from stops when considering accessibility on the system. As a result, first and last mile questions can be addressed directly in the planning process.

	~~Analyst allows for multimodal analysis, incorporating walking, cycling, transit~~ and ~~driving. this simplifies planning when accounting for park-and-rides, bikes on transit, and bikeshare systems.~~ Using demographic data from census inputs, Analyst can do equity analyses and reveal disparate impacts that ~~any~~ scenario might create. ~~Not only is it important~~ to ensure ~~transposition development is equitable, but this step is crucial in the US where agencies are required to~~ comply with [[Transit and Civil Rights\| Title VI]].		===Title VI and Equity===
			Using demographic data from census inputs, Analyst can preform equity analyses and reveal disparate impacts that a given scenario might create. This analysis aides transit agencies to ensure projects comply with [[Transit and Civil Rights\| Title VI]] in the US, and supports agencies in determining how projects align with their own internal equity goals.

	[[Conveyal\| Conveyal's]] commitment to open data and open source has led them to use open data for all of Transport Analyst's inputs, such as publicly available [[GTFS]] feeds, map data from [[OpenStreetMap]], and census data. The components for Analyst are themselves open source, licensed under the [[Apache 2]] license.		==Open-source==
			[[Conveyal\| Conveyal's]] commitment to open data and open-source has led them to use open data for all of Transport Analyst's inputs, such as publicly available [[GTFS]] feeds, map data from [[OpenStreetMap]], and census data. The components for Analyst are themselves open source, licensed under the [[Apache 2]] license.

	==References==		==References==

Leeor at 23:35, 1 April 2017

2017-04-01T23:35:49Z

← Older revision		Revision as of 23:35, 1 April 2017
Line 8:		Line 8:
	\|vendor=[[Conveyal]]		\|vendor=[[Conveyal]]
	\|license=[[The MIT License]]		\|license=[[The MIT License]]
	\|documentation= ~~Check [https~~://~~github~~.~~com/conveyal Conveyal GitHub], [https://github~~.~~com~~/~~conveyal/analyst https://github.com~~/~~conveyal~~/~~analyst]~~		\|documentation= http://analysis-ui.readthedocs.io/en/latest/
	\|data_in= [[GTFS]], [[OpenStreetMap]], National census data		\|data_in= [[GTFS]], [[OpenStreetMap]], National census data
	\|data_out= [[GIS]]		\|data_out= [[GIS]]