zipcode doesn't have city.id, causing parsing failures #2
Description
More or less enough said, the normal q endpoint continues to provide the id, but it's a bit of a problem when the zipcode endpoint isn't usable due to it missing a field (heaven knows why, since population and timezone are still listed, so it knows where I'm asking)