mheadd · October 8, 2011 14:10
diff --git a/next-septa.txt b/next-septa.txt
 The NEXT-Septa project is here:
 https://github.com/reedlauber/Next-Septa

 Specifically, the import code is here:
 https://github.com/reedlauber/Next-Septa/blob/master/lib/tasks/import_gtfs.rake

 It's a ruby rake task, so if someone wanted to use it in their own Rails project, then can run it with a few optional arguments. e.g....
 rake import_gtfs // imports everything (currently default to buses only)
 rake import_gtfs[routes] // imports just routes
 rake import_gtfs[routes, rail] // imports routes for rail lines, not buses
 rake import_gtfs[routes, all] // imports routes for both buses and rail

 One thing to watch out for is how long some of this can take. Most of the datasets aren't too bad, but if I remember correctly, "trips" took almost an hour and "stop_times" took several hours. Funneling it all through rails might not be the best idea. A direct import into postgres (or whatever db) would probably be a lot faster.
	The NEXT-Septa project is here:
	https://github.com/reedlauber/Next-Septa

	Specifically, the import code is here:
	https://github.com/reedlauber/Next-Septa/blob/master/lib/tasks/import_gtfs.rake

	It's a ruby rake task, so if someone wanted to use it in their own Rails project, then can run it with a few optional arguments. e.g....
	rake import_gtfs // imports everything (currently default to buses only)
	rake import_gtfs[routes] // imports just routes
	rake import_gtfs[routes, rail] // imports routes for rail lines, not buses
	rake import_gtfs[routes, all] // imports routes for both buses and rail

	One thing to watch out for is how long some of this can take. Most of the datasets aren't too bad, but if I remember correctly, "trips" took almost an hour and "stop_times" took several hours. Funneling it all through rails might not be the best idea. A direct import into postgres (or whatever db) would probably be a lot faster.
No results found