http://tmtest.teresco.org/user/mapview.php?units=miles&u=yakra&rg=CT,RI is good.
http://tmtest.teresco.org/user/mapview.php?units=miles&u=yakra&cr=oh.i080 is broken. West edge of my screen is slightly into UT. East edge a little into IL. The route appears at first glance to be off-center a bit too far north, but checks out when we account for the southern extent of I-80 nationwide.
I'm thinking it's centered, just not zoomed out enough. I'm not sure why the
fitBounds function doesn't zoom out beyond a certain level. I don't think I put any restrictions on it, intentionally. You might have noticed that when you set the zoom level though the popup, it's limited as to how far out you can go. That is done intentionally to avoid an initial load with a massive amount of data. As far as I can tell, there's no way
fitBounds should get it's hands on that limit.
Normally when viewing a ConnectedRoute, chopped routes are in CSV order in the route table. I-80, I-05 & US1 all check out.
Not http://tmtest.teresco.org/user/mapview.php?units=miles&u=yakra&cr=chnjl.g25 for whatever reason.
Right now, the _con.csv line is:
chng;G25;;Tianjin;chnnm.g25,chnjl.g25,chnln.g25,chnhe.g25,chntj.g25,chnhe.g25hua,chnsd.g25bin
but the first 3 chopped routes in the table are JL, LN, NM respectively.
Aside: isn't the CSV order incorrect?
mapview.php is putting things in the array in the
chng_con.csv order;
mapviewParams.roots.push('chnnm.g25');
mapviewParams.roots.push('chnjl.g25');
mapviewParams.roots.push('chnln.g25');
mapviewParams.roots.push('chnhe.g25');
mapviewParams.roots.push('chntj.g25');
mapviewParams.roots.push('chnhe.g25hua');
mapviewParams.roots.push('chnsd.g25bin');
But.. it's the order of the routes in
chng.csv that matters on the query, as that's the order used to gather segments, then from those segments, the routes they comprise to be added to the table. I think a reorder of the G25 entries in
chng.csv would fix this.
Maybe we need to clarify that the order routes show up in
abcx.csv should match their order with an entry of
abcx_con.csv? It's possible this is the first time we've depended on that, but unless there's a reason we might want to allow different orderings in those files, I'd rather fix the data than complicate the code.
