We have updated the boundary data for the ULEZ and Congestion Charge schemes. The new files are available at http://roads.data.tfl.gov.uk under boundaries/
CC_Boundary_v8_20190526_tab_shape.zip
ULEZ_Boundary_20190526.json
ULEZ_Boundary_20190526_tab_shape.zip
ccz.json
Are there updates to the new boundaries for Oct 2021 that come into play in a couple of days.
Searching the http://roads.data.tfl.gov.uk/ is a needle in the haystack exercise
thanks
Hi Mark,
I agree roads data bucket is not very user-friendly. Please find direct links to the data you are looking for:
LEZ boundaries:
ULEZ - LINK TO BE UPDATED
https://s3-eu-west-1.amazonaws.com/roads.data.tfl.gov.uk/boundaries/ULEZ_Boundary_20190526_tab_shape.zip
We are also going to update the links on our Open Data page here:
Kind regards,
Jakub
Would it be fair to use the word unusable in fact?
I think the intention for S3 bucket is to be used with a key rather than from a browser, but I agree, it’s not useable at all in the current form!
The biggest problem in our roads.data bucket is one feed that generates files every 15 minutes…We are currently reviewing our datasets (including this S3 bucket) to remove data that is not used and clean things up.
Sorry, I usually try to keep away from criticism.
Perhaps if there was a way of having “folders” at the top level of the https interface that applied filters to the output so that humans and Google could have a better shot at finding things?
Hi Brian, your criticism is actually very helpful. We release our data for others, so it’s good to see how/if it’s used!
From what I remember, AWS S3 doesn’t have an option to create folders, but I will double check.
Cheers!
Jakub
Folders are a thing!
Also you can have lots of versions of files. I’m storing the NRE Darwin Pushport output in this bucket and you can send multiple versions (as they output adds up/changes)
Using this you could index each days data into a single S3 filename but still have it updated every X minutes.
Hope this helps.
Thanks Jakub, but the 2nd link doesn’t work:
Error>
NoSuchKey
The specified key does not exist.
boundaries/ULEZ_Boundary_20190526_tab_shape.zip
P8PE9RET4PH579XM
jGea1k/1Gg/ijYBrOI/3asDGmcD2LXuzPDSWjh3R+pCkej+XPrOjlU2s1jbIQQWfuj6O8Z4zOtQ=
Hi Mark,
Please have a look at the links from the post above. These links work fine.
Kind regards,
Jakub
I struggled for a while to find any relevant data for this topic; after a while of searching for APIs and GeoJson boundaries I found the London Data Store to hold the most relevant, easy to access data.
Definitely worth a look for anyone trying to access the correct data for ULEZ and other relevant topics.
