Descendants of 101734959
-
Southdale —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/737/9/1108937379.geojson
ID 1108937379
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Crestview —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/739/1/1108937391.geojson
ID 1108937391
Inception date unknown Cessation date unknown
It was last modified November 08, 2021.
-
Weston —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/742/7/1108937427.geojson
ID 1108937427
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ca/110/893/743/7/1108937437.geojson
ID 1108937437
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Repo whosonfirst-data-admin-ca/110/893/744/9/1108937449.geojson
ID 1108937449
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Repo whosonfirst-data-admin-ca/110/893/752/1/1108937521.geojson
ID 1108937521
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Repo whosonfirst-data-admin-ca/110/893/755/1/1108937551.geojson
ID 1108937551
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Regent —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/759/9/1108937599.geojson
ID 1108937599
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Grassie —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/760/9/1108937609.geojson
ID 1108937609
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Seven Oaks —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/110/893/762/1/1108937621.geojson
ID 1108937621
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
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,649 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?