Descendants of 85633129
-
Repo whosonfirst-data-admin-ma/126/020/176/9/1260201769.geojson
ID 1260201769
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
Repo whosonfirst-data-admin-fr/136/068/209/3/1360682093.geojson
ID 1360682093
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
-
Béhobie —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-fr/136/068/237/5/1360682375.geojson
ID 1360682375
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
-
Repo whosonfirst-data-admin-fr/136/068/376/3/1360683763.geojson
ID 1360683763
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
-
Esnazu —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-fr/136/068/580/3/1360685803.geojson
ID 1360685803
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
-
Hondarribia —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-fr/136/068/758/3/1360687583.geojson
ID 1360687583
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Endarlatsa —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-fr/136/068/448/1/1360684481.geojson
ID 1360684481
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
-
Iñarbil —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-fr/136/068/459/5/1360684595.geojson
ID 1360684595
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
-
La Kosta —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-fr/136/068/570/1/1360685701.geojson
ID 1360685701
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
-
Deskarga —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-fr/136/068/582/3/1360685823.geojson
ID 1360685823
Inception date unknown Cessation date unknown
It was last modified October 19, 2018.
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,545 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?