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
If we look at this example from the data export, there is available postcode data, but it's tagged as place:postcode.
Likewise, boundary:administrative includes city, state/province, etc. are included in there.
However, if you look at this thread, it seems to refute my thinking. I'm confused! We should probably hack at this a bit, but I don't want to break the overall pipeline.
The text was updated successfully, but these errors were encountered:
In the United States, set this key to the feature's five-digit ZIP code or, if known, the full ZIP+4 code. This key is useful because ZIP codes are routes, not areas, and they rarely correspond well to any kind of boundary.
Our script is using
addr:postcode=* \
.If we look at this example from the data export, there is available postcode data, but it's tagged as
place:postcode
.Likewise,
boundary:administrative
includes city, state/province, etc. are included in there.However, if you look at this thread, it seems to refute my thinking. I'm confused! We should probably hack at this a bit, but I don't want to break the overall pipeline.
The text was updated successfully, but these errors were encountered: