Descendants of 85632509
-
1101 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/797/504775797.geojson
ID 504775797
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1124 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/819/504775819.geojson
ID 504775819
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1125 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/821/504775821.geojson
ID 504775821
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1130 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/823/504775823.geojson
ID 504775823
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1131 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/825/504775825.geojson
ID 504775825
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1134 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/829/504775829.geojson
ID 504775829
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1135 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/831/504775831.geojson
ID 504775831
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1140 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/833/504775833.geojson
ID 504775833
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1141 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/835/504775835.geojson
ID 504775835
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
1144 —
this is a postalcode
Repo whosonfirst-data-postalcode-py/504/775/837/504775837.geojson
ID 504775837
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 4,683 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?