Descendants of 101735515
-
Repo whosonfirst-data-admin-ca/112/607/277/7/1126072777.geojson
ID 1126072777
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
Ancaster —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/112/608/883/9/1126088839.geojson
ID 1126088839
Inception date unknown Cessation date unknown
It was last modified August 23, 2019.
-
Mountview —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/858/749/03/85874903.geojson
ID 85874903
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Mohawk —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/858/749/15/85874915.geojson
ID 85874915
Inception date unknown Cessation date unknown
It was last modified November 08, 2021.
-
Beasley —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/858/748/19/85874819.geojson
ID 85874819
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Delta West —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/858/748/31/85874831.geojson
ID 85874831
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Gershome —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/858/748/43/85874843.geojson
ID 85874843
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Repo whosonfirst-data-admin-ca/858/748/53/85874853.geojson
ID 85874853
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Sherwood —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/858/748/75/85874875.geojson
ID 85874875
Inception date unknown Cessation date unknown
It was last modified February 21, 2020.
-
Southam —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ca/858/748/87/85874887.geojson
ID 85874887
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,454 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?