Commuter Rail data

[Adam Travis]

Thanks for all of the info at the meeting tonight. I have a question
about the Commuter Rail Station Line Ordering document. Is there a
reason the Newburyport/Rockport line is represented in a linear way,
as opposed to having two branches? I can see how you might now want
to apply the labels Primary or Secondary, but it is still not as
linear as the Lowell line, for example. So I'm wondering what the
thinking was behind that.

I also found one little mistake in the Developer Guide PDF. First
though, I want to say that I think that document is really great! I
like that it contains good conceptual notes and an overview, as well
as the detailed feed definition. I really appreciate that type of
information being available, and hope you can keep publishing guides
like this for all data feeds. The little mistake is in the Data Feed
section. It says the Destination field is an integer, but clearly the
example is a string.

The Data Feed info is really great. The one thing I can think of that
would help is to define the field lengths for the strings. I can
always guess or look up the current longest values, but I'd love to
build my database to match the max field lengths you could deliver.

Thanks again for all of the hard work to make this available. I'm
really looking forward to digging into it.

Thanks,
Adam Travis

[Jeff Kaufman]

Adam Travis wrote:
> Thanks for all of the info at the meeting tonight. I have a
> question about the Commuter Rail Station Line Ordering document.

> ... I also found one little mistake in the Developer Guide PDF. ...

Is this information available online somewhere for people who couldn't
make the meeting last night?

Jeff