Descendants of 85632729
-
00200 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/139/421527139.geojson
ID 421527139
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
03570 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/163/421527163.geojson
ID 421527163
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
04100 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/165/421527165.geojson
ID 421527165
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
04170 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/167/421527167.geojson
ID 421527167
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
04200 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/169/421527169.geojson
ID 421527169
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
05100 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/171/421527171.geojson
ID 421527171
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
05170 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/173/421527173.geojson
ID 421527173
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
06100 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/175/421527175.geojson
ID 421527175
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
06171 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/179/421527179.geojson
ID 421527179
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
06200 —
this is a postalcode
Repo whosonfirst-data-postalcode-mz/421/527/181/421527181.geojson
ID 421527181
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 2,316 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?