Descendants of 890458485
-
Burnewood —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/629/1/1108936291.geojson
ID 1108936291
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ca/110/897/056/7/1108970567.geojson
ID 1108970567
Inception date unknown Cessation date unknown
It was last modified January 02, 2020.
-
Horse Hill —
this is a macrohood marked as current
Repo whosonfirst-data-admin-ca/110/897/058/1/1108970581.geojson
ID 1108970581
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ca/110/897/110/9/1108971109.geojson
ID 1108971109
Inception date unknown Cessation date unknown
It was last modified January 02, 2020.
-
Repo whosonfirst-data-admin-ca/110/897/122/3/1108971223.geojson
ID 1108971223
Inception date unknown Cessation date unknown
It was last modified January 02, 2020.
-
Decoteau —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/628/1/1108936281.geojson
ID 1108936281
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Knottwood —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/629/3/1108936293.geojson
ID 1108936293
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ca/110/897/056/5/1108970565.geojson
ID 1108970565
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
Repo whosonfirst-data-admin-ca/110/897/057/9/1108970579.geojson
ID 1108970579
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ca/110/897/058/9/1108970589.geojson
ID 1108970589
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
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,255 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?