King County Trip Planner
This is the argument setup for the King County Trip Planner (http://tripplanner.kingcounty.gov/cgi-bin/itin_page.pl?resptype=U).
Similar systems can be seen in use with:
- Pierce Transit (http://tripplanner.piercetransit.org/cgi-bin/itin_page.pl?resptype=U) (probably the same system with a different point of entry)
- Phoenix (http://tripplan.phoenix.gov/cgi-bin/itin_page.pl?resptype=U)
- Capital Metro (Austin, Texas) (http://atps.capmetro.org/cgi-bin/itin_page.pl?resptype=U)
- NFTA Metro (Buffalo, NY and Niagara) (http://metrotrip.nfta.com/cgi-bin/itin_page.pl?resptype=U)
- TriMet (the Portland, Oregon Metropolitan Area) (http://trimet.org/go/cgi-bin/plantrip.cgi)
- Although http://ride.trimet.org (the "new" Trip Planner suggested on that page) looks closer, judging by query parameters used in the URL Bing has it at
- Minneapolis/St. Paul (http://metrotransit.org/tripPlanner/Default.aspx) (found by bouncing around from http://tips.metc.state.mn.us/cgi-bin/serv_page.pl?resptype=U)
- and, to a lesser extent, New Jersey (formerly http://atisweb.njtransit.com/cgi-bin/itin_page.pl?resptype=U, now http://www.njtransit.com/sf/sf_servlet.srv?hdnPageAction=TripPlannerTo).
This system may be based on Ontira TripFinder.
My guess, based on the patterns I see, is that the developer offers a base package with a Perl interface that does server-side address resolution, and can do special cases on other systems (such as New Jersey's JSP and Minneapolis's ASP) with a map (like the one seen on TriMet), hence the latitude/longitude coordinate-based hidden inputs on the form seen here (and the client-side data entry on New Jersey).
The page submits this as a POST to itin.pl (in the standard way for HTML forms, a URL-encoded body).
Example Query Arguments
Miscellaneous header data
- I don't know what this is about.
- No idea- judging by the search results, this system appears to be the only software that uses the identifier "resptype" (excluding some undocumented code in some obscure system in OpenBSD, some recurring documentation that had no actual explanatory text or signifier as to what it was documenting, and a field in NTLM's client challenge code).
- My guess is this signifies UTF-8 encoding for the response.
- Interestingly, nothing happens if you leave it off or change it (in the itin_page URL).
These were all specified but blank (or 0 in a couple cases). They're hidden inputs at the top of the form. No idea why these are still on the page, but some enlightenment as to their original/future usage can be found on the New Jersey and TriMet pages.
1. Where does your trip start?
2. Where does your trip end?
3. When is your trip?
(MM/DD/YY) (Note that ironically the server sends this defaulted to M/D/YY)
I want to
- D = Leave my starting point (Depart)
- A = Arrive at my destination (Arrive)
At (These default to the nearest (not next) 5-minute interval)
4. What is the farthest you want to walk?
- .25 = "1/4 of a Mile"
- .50 = "1/2 of a Mile" (the default)
- .75 = "3/4 of a Mile"
- 1.0 = "One Mile"
5. Which is the most important?
- T = Fastest Way
- X = Fewest Transfers
- W = Minimal Walking
6. Do you require an accessible trip?
- Only defined if checked (which it isn't be default)
- stupid http forms always submit data for the submit element which you have to make to submit