-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding LSOA21 data #1181
Comments
Actually, it looks like you already added the August 2023 data - which I think uses LSOA21 by default, although I'm not sure - if you're able to clarify, that would be great, thanks! 👍 https://github.com/ideal-postcodes/postcodes.io/releases/tag/15.3.0 |
Hey @cblanc 👋 Sorry for the direct ping, but I wondered if this might be something you could advise on please? |
The apologies owed are from me @jamgregory Sorry for the late reply I'm fairly certain LSOA is 2011: https://github.com/ideal-postcodes/postcodes.io/blob/master/data/scripts/lsoa.js Am looking to do a significant release for most recent ONSPD which will include all data returned by ONSPD, including 2021 LSOAs. Will be a backwards breaking change at DB schema level but API will be ok. |
No worries at all @cblanc, thanks for the reply 👍 That sounds great, thank you. I wrote a quick script last week to compare the LSOA11 and LSOA21 values, and they appear to be the same in the most recent ONSPD data (August 2023) so there's no rush now from my perspective to include that, but I think it would be useful in future if they do change 🙌 |
Would be great to add OA as well. |
Hello 👋
Not sure if this is on your roadmap already, but will you be updating the data to use the Census 2021 data (for example, LSOA21) in the near future? We have a requirement to collect that data in the near future, and it'd be great if we could use your API to do that.
Thanks!
The text was updated successfully, but these errors were encountered: