Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
General Transit Feed Spec Changes
Home
About this group
Apply for group membership
Message from discussion proposal: trip_type to allow client applications to exclude unusual trips from certain displays
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mike Gilligan  
View profile  
 More options Nov 21 2008, 2:25 pm
From: Mike Gilligan <mgilli...@gmail.com>
Date: Fri, 21 Nov 2008 11:25:51 -0800 (PST)
Local: Fri, Nov 21 2008 2:25 pm
Subject: Re: proposal: trip_type to allow client applications to exclude unusual trips from certain displays
Print | View thread | Show original | Report this message | Find messages by this author
If you look at the latest TriMet feeds, there is a field named
trip_type in trips.txt. I currently have a text description but an
enumeration would work better. The value is either blank, to indicate
typical service, Express, or Limited. These values are currently being
used by TimeTablePublisher for footnotes. Express is service that
skips a significant segment of the typical route path, Limited is
service that only serves limited/major stops during a segment of the
typical route path. I think it would be nice to have a more
comprehensive list of trip_types such as Typical (0,blank), Limited
(1), Express(2), Short Line(3), Branching(4), etc.

In house, we also maintain a field to indicate that a pattern will not
be displayed to the public for our system map & other GIS files. We
could supply a patterns.txt file which includes the shape_id and a
public field (0,blank = include, 1 = exclude)

Thanks,
Mike Gilligan
TriMet

On Nov 20, 6:41 pm, Joe Hughes <joe.hughes.c...@gmail.com> wrote:

> Summary:
> Add a way to distinguish between typical and atypical trip patterns.

> Motivation:
> Many agencies have a few trips per day that follow unusual paths for
> that route.  For instance, most trips on the BART rail system in the
> San Francisco bay area stop at either SFO Airport or Millbrae, but not
> both.  However, a few trips per day (usually in the late night/early
> morning) stop at both.  When displaying summary views of the route,
> some clients might want to exclude the uncharacteristic trips.

> Proposal:
> The following field would be added to trips.txt:
> --------------------------------
> trip_type (optional):
> The trip_type field characterizes the path (sequence of stops) that
> this trip visits.  The allowable values are:

> "0" - the trip follows a typical path
> "1" - the trip follows an unusual path, something that the route does
> only a few times a day or on special occasions.  A trip should be
> given this value if riders wouldn't expect the route to follow this
> path.

> If the field is omitted, all trips are treated as though they have
> trip_type "0".
> --------------------------------

> Discussion:
> While this meets the basic need, one could argue that the format would
> be better served by a more explicit notion of "trip patterns"; that
> is, giving each trip a pattern ID that groups it with similar trips.
> We could then mark certain patterns as atypical, rather than marking
> the individual trips.

> Your thoughts?

> Joe Hughes
> Google


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google