gTraffic: Version 2.2

I have fixed the problem with the map. The latest version of the map control 2.77 isn’t compatible with the GWT wrapper I use for the Google Map. As soon as I saw the javascript errors in the Firebug console pane I knew right away what it was. I pinned the map version at 2.76 and it all burst back into life again.

I have taken this point to remove the roadworks and VMS data options from the application. Sorry, but I can’t get the Python scripts to login to the XML feed for these anymore and I’ve no time to put into fixing it. This is better than looking at data that was from last year.

Comments

2 Responses to “gTraffic: Version 2.2”

  1. Victor Delta on April 23rd, 2007 6:01 pm

    Hi

    I don’t want to complain but i think i ought to point out some missing info on your excellent gtraffic system. I’m not sure if this is the place to post such comments but i cannot find anywhere else…

    As you will see on the highways agency website, for some months you cannot access the A52 eastbound (the main access route to Nottingham) from the M1 (jn 25). I think they are working on the sliproad. There are big signs up rerouting the traffic via jns 24 or 26.

    However, this is not relected on your wesbite at all. Why not?

    TIA

    V

  2. Administrator on April 24th, 2007 11:36 pm

    Interesting. The feed is taken from the BBC and this is taken (as far as I know) from TrafficLink here

    http://www.trafficlink.co.uk/

    who supply data to the BBC. If it is not mentioned then it must be an oversight on their part.

    I have removed the specific ‘Roadworks’ feed from the map which might have mentioned it. This was because of the inability of the Python scripts, which collect the data, to login to the feed. I suspect that it would show up on that as it is an HA specific one. Looks like I should take some time to address this issue.

Leave a Reply