New Washington / Wabash Stops Missing From API

18 views
Skip to first unread message

TreKing

unread,
Oct 5, 2017, 10:33:14 PM10/5/17
to cta developers
I asked about this in response to the announcement of the addition of the new station here:
https://groups.google.com/d/msg/ctadevs/M3ZXXN4zjC8/pY0VMk8xDwAJ

No one responded to that post and I got no response to an email directed at feed...@transitchicago.com, or to the email form at http://www.transitchicago.com/feedback/

Is anyone from CTA still monitoring this group? If this is not the right place for reporting issues with the API, what is?

The API is current broken for the two newest stops and renders apps that try to show predictions via route / direction / stop useless.

Once again:

The train tracker api is returning an error for the two new stop IDs (30383 and 30384) which is currently making it impossible to add support for tracking trains specifically at these stops:

http://lapi.transitchicago.com/api/1.0/ttarrivals.aspx?key=nunyabizness&stpid=30384

<?xml version="1.0" encoding="utf-8"?>
<ctatt>
    <tmst>20170919 21:34:03</tmst>
    <TimeStamp>20170919 21:34:03</TimeStamp>
    <errCd>108</errCd>
    <errNm>Invalid stpid specified: '30384'</errNm>
</ctatt>

The station ID (41700) does work though:


<?xml version="1.0" encoding="utf-8"?>
<ctatt>
    <tmst>20170919 21:35:37</tmst>
    <errCd>0</errCd>
    <errNm />
    <eta>
        <staId>41700</staId>
        <stpId>30384</stpId>
        <staNm>Washington/Wabash</staNm>
        <stpDe>Service at Inner Loop platform</stpDe>
        <rn>720</rn>
        <rt>Org</rt>
        <destSt>30182</destSt>
        <destNm>Midway</destNm>
        <trDr>5</trDr>
        <prdt>20170919 21:35:08</prdt>
        <arrT>20170919 21:36:08</arrT>
        <isApp>1</isApp>
        <isSch>0</isSch>
        <isDly>0</isDly>
        <isFlt>0</isFlt>
        <flags />
        <lat>41.88443</lat>
        <lon>-87.62622</lon>
        <heading>178</heading>
    </eta>
...
</ctatt>

Randy Baxley

unread,
Oct 5, 2017, 10:41:25 PM10/5/17
to cta...@googlegroups.com
You might want to try the chihacknight slack.  CTA developers presented there Tuesday.

--
--
...
 
You received this message because you are subscribed to the Google
Groups "cta developers" group. Visit http://www.transitchicago.com/developers to see data available from CTA.
To post to this group, send email to cta...@googlegroups.com
To unsubscribe from this group, send email to
ctadevs+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/ctadevs?hl=en

---
You received this message because you are subscribed to the Google Groups "cta developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ctadevs+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

TreKing

unread,
Oct 20, 2017, 7:49:33 PM10/20/17
to cta...@googlegroups.com
Never heard back to any inquiry, but looks like it's finally working as it should.


For more options, visit this group at
http://groups.google.com/group/ctadevs?hl=en

---
You received this message because you are subscribed to the Google Groups "cta developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ctadevs+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
...
 
You received this message because you are subscribed to the Google
Groups "cta developers" group. Visit http://www.transitchicago.com/developers to see data available from CTA.
To post to this group, send email to cta...@googlegroups.com
To unsubscribe from this group, send email to

For more options, visit this group at
http://groups.google.com/group/ctadevs?hl=en

---
You received this message because you are subscribed to the Google Groups "cta developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ctadevs+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages