Avego (Future Fleet) offers GTFS import/export capability. Are you interested?

[Andrew Merry]

Hi everyone,

We here at Avego have seen the capability and potential GTFS
has to offer and have as a gateway to our system implemented a GTFS
import/export facility that allows a user to import and edit GTFS data
easily. Once imported the user will be able to manage their data and
advertise to their customers in a quick and effective manner. For
those interested in what FutureFleet has to offer check out the
following: http://www.avego.com/ui/futurefleet.action.

What I'm looking for is for some of you guys to give us
feedback, comments and thoughts on our system. Any one whose
interested if you send us a GTFS file (validated of course) we will
import your data into system and allow you to interact with your GTFS
data using our functionality and experience the capability available.
What we gain is knowledge on how to make our system even better, what
you gain is the opportunity open your business to a wider market very
quickly.

We're proud of what we've achieved with GTFS import/export and
we'd love to get some feedback from the developer community. Those
interested please send your GTFS zip file to sup...@avego.com.

We are fully compatible with the GTFS apart from the following
exceptions:

agency.txt:
-agency_lang (optional).

stops.txt:
-stop_url (optional)
-location_type (optional)
-parent_station (optional)

routes.txt:
-route_url (optional)
-route_color (optional)
-route_text_color (optional)

trips.txt:
-trip_short_name (optional)
-direction_id (optional)
-block_id (optional)
-shape_id (optional)

stop_times.txt:
-stop_sequence is now correctly re-calculated
-stop_headsign (optional)
-pickup_type (optional)
-drop_off_type (optional)
-shape_dist_traveled (optional)

calendar.txt:
-fully supported

calendar_dates.txt:
-now fully supported

fare_attributes.txt:
-currency_type (required) - we dont use it, we take the currency from
the service providers country
-payment_method (required)
-transfers (required)
-transfer_duration (optional)

fare_rules.txt:
-contains_id (optional)

shapes.txt:
-we dont support shapes.txt yet

frequencies.txt:
-fully supported

transfers.txt:
-we dont support this file yet

There are still some caveats with the system. We don't support a file
that contains a trip with duplicate stops.

Over the next few months we will include these options as we stabilise
and improve the system.

Hope to here from you!

Andy Merry