You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there. This may be a broader issue than stated here, but I have noticed that certain West London postcodes are not recognised by the API and a 400 error is returned along with a 'no postcode match can be found' message. A few examples are W1, W2, W3 and W7.
Example request: curl -X GET https://api.carbonintensity.org.uk/regional/postcode/w7
Response:
"error": {
"code": "400 Bad Request",
"message": "No postcode match can be found."
}
}
The text was updated successfully, but these errors were encountered:
From my testing so far it seems like results granularity is at the region level, but some postcodes in London are in region 12 ("South England") and some are in 13 ("London") . The same is true for Glasgow for example (it is usually in South Scotland, but has one postcode in North Scotland). If anyone else is looking at this or you still are, you may be better off just using region-wide endpoints and selecting the regions from https://carbon-intensity.github.io/api-definitions/?python#region-list after some experimentation with the return values of postcode-specific endpoints.
Hi there. This may be a broader issue than stated here, but I have noticed that certain West London postcodes are not recognised by the API and a 400 error is returned along with a 'no postcode match can be found' message. A few examples are W1, W2, W3 and W7.
Example request:
curl -X GET https://api.carbonintensity.org.uk/regional/postcode/w7
Response:
The text was updated successfully, but these errors were encountered: