Descendants of 85633341
-
6891 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/629/437261629.geojson
ID 437261629
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
6961 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/651/437261651.geojson
ID 437261651
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
6991 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/659/437261659.geojson
ID 437261659
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
7003 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/663/437261663.geojson
ID 437261663
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
7004 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/665/437261665.geojson
ID 437261665
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
7005 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/667/437261667.geojson
ID 437261667
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
7006 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/669/437261669.geojson
ID 437261669
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
7007 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/671/437261671.geojson
ID 437261671
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
7039 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/261/673/437261673.geojson
ID 437261673
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
7702 —
this is a postalcode
Repo whosonfirst-data-postalcode-no/437/262/005/437262005.geojson
ID 437262005
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,594 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?