Descendants of 85633135
-
78241 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/181/437272181.geojson
ID 437272181
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78243 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/183/437272183.geojson
ID 437272183
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78244 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/185/437272185.geojson
ID 437272185
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78245 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/187/437272187.geojson
ID 437272187
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78246 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/189/437272189.geojson
ID 437272189
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78247 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/193/437272193.geojson
ID 437272193
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78248 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/195/437272195.geojson
ID 437272195
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78250 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/197/437272197.geojson
ID 437272197
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78251 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/199/437272199.geojson
ID 437272199
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
78253 —
this is a postalcode
Repo whosonfirst-data-postalcode-ee/437/272/201/437272201.geojson
ID 437272201
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
There are so many results for this query that the Spelunker database can't do page1, page2, page3... style pagination without getting sad. There are actually 1,258 pages worth of results for this query but as of this writing there is only the "next page" of results. We all have our limits, right? Speaking of limits, these query results have a pretty short shelf life. As long as you are paging through the results everything will be okay but if left idle for too long (about 5 minutes) they will expire and you'll need to perform a new query. It's good to have constraints to work against, right?