Descendants of 85633723
-
Nepli —
this is a locality
Repo whosonfirst-data-admin-by/134/377/233/9/1343772339.geojson
ID 1343772339
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-de/125/985/725/9/1259857259.geojson
Inception date unknown Cessation date unknown
It was last modified May 20, 2019. This record is deprecated.
-
Repo whosonfirst-data-admin-de/129/347/590/3/1293475903.geojson
Inception date unknown Cessation date unknown
It was last modified May 20, 2019. This record is deprecated.
-
Repo whosonfirst-data-postalcode-pl/421/387/935/421387935.geojson
ID 421387935
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
Repo whosonfirst-data-postalcode-pl/421/388/257/421388257.geojson
ID 421388257
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
Repo whosonfirst-data-postalcode-pl/421/389/201/421389201.geojson
ID 421389201
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
Repo whosonfirst-data-postalcode-pl/421/389/203/421389203.geojson
ID 421389203
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
Repo whosonfirst-data-postalcode-pl/421/389/205/421389205.geojson
ID 421389205
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
Repo whosonfirst-data-postalcode-pl/421/389/209/421389209.geojson
ID 421389209
Inception date unknown Cessation date unknown
It was last modified September 22, 2016.
-
Repo whosonfirst-data-postalcode-pl/421/389/215/421389215.geojson
ID 421389215
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 6,882 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?