13:31 <abyrd> thanks for posting the link demory , I was just looking for it
13:31 <demory> oh, you are on. hi!
13:32 <mattwigway> thanks!
13:32 <abyrd> yep, I am around, I just might not be able to stay for the whole duration
13:32 <demory> sure
13:33 <demory> so, hi everyone. long time no chat!
13:33 <demory> should we do a quick check in?
13:33 <demory> FrankP grant_h, as I mentioned over email I'm doing work on the TriMet modules again
13:34 <abyrd> and I'm setting aside the time to work on the routing problems
13:34 <demory> one thing I'm working on now is enabling geocoding in the new UI modules
13:34 <FrankP> hey David...hi guys...working on a text version of the planner. Mele got another job. Grant and I were testing latest version of the code, and have a few bugs we think, including the 985 one that's still pending.
13:35 <mattwigway> I pushed a bunch of fixes for car routing.
13:36 <demory> FrankP, you mean 945?
13:36 <FrankP> right...945
13:36 <demory> yeah, that's one abyrd is looking at
13:36 <mattwigway> also, have there been any academic papers written about OTP?
13:36 <FrankP> Grant's going to file some more soon...
13:36 <abyrd> mattwigway, yes there have
13:37 <abyrd> but the references I have are getting a bit old, there might be more recent ones
13:39 <demory> FrankP grant_h, Bibiana sent me a couple emails w/ several other weird routing issues, which I forwarded to Andrew. I'll also fwd to you two so you know what we're looking at
13:39 <demory> we should get all those in the issue tracker for ease of reference
13:40 <abyrd> mattwigway, try McGurrin and Greczner - Performance Metrics: Calculating Accessibility Using Open Source Software and Open Data
13:41 <FrankP> agreed...easier to use an issue number (even if I add 40 to that number)
13:41 <abyrd> yes, I've got the full list of strange routes
13:41 <abyrd> who is going to add the issues, should I just do it as I reproduce them?
13:42 <mattwigway> thanks,
13:43 <demory> abyrd, sure (re you adding issues as you reproduce them)
13:44 <abyrd> ok noted
13:45 <demory> On the UI side, one thing I'm working on now is geocoder integration w/ the new modules. FrankP, I assume http://maps.trimet.org/geocoder/geocode is the correct service to use?
13:46 <demory> Ok. I'm running into cross-domain request issues given that I'm not developing/testing within trimet.org. I gather it is not set up for jsonp requests?
13:47 <FrankP> No probably not.
13:49 <demory> Well, that won't be an issue one you deploy this on your end. But it makes dev/testing a little tricky. I may just use a public service like geocoder.us for testing the UI, and you can switch that out once you deploy it internally
13:50 <demory> It's just one property in a config file you'd need to change
13:50 <FrankP> I'll look to adding a callback method. You have a certain name you'd like for the method? Or should I take in a parameter for the name of the callback (anyone know if that causes a XSS vulnerability?
13:54 -!- mattwigway [~[email protected]] has joined #opentripplanner
13:54 <demory> FrankP, I'm using JQuery for the ajax calls, which defaults to a callback paramater
13:55 <FrankP> okay...I'll do the param (jQuery can't be wrong :0), and let you know...searching for the geocoder code as we speak...
13:56 <demory> great, thanks
13:57 <demory> ok, anything else we should discuss today?
13:58 <mattwigway> FrankP, you could also add Access-Control-Allow-Origin: * to allow cross-domain access (we did this on the classic trip planner)
13:59 <FrankP> and with that Matt, you don't need to wrap the response?
13:59 <demory> that's true. maybe just do that for the test instance if you don't want to expose the public one
13:59 <FrankP> Yeah, I'll change maps5 later today, and send you an email David.
14:00 <demory> ok, great
14:03 <grant_h> hey guys, sorry, had a phone call I had to take, abyrd I can ticket the issues if you'd rather not, but may not have chance to till early next week if that's alright