Descendants of 1108826389
-
Repo whosonfirst-data-admin-ch/112/576/775/9/1125767759.geojson
Inception date unknown Cessation date unknown
It was last modified August 10, 2019. This record is deprecated.
-
Gy —
this is a locality marked as current
Repo whosonfirst-data-admin-ch/112/587/036/7/1125870367.geojson
ID 1125870367
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Gys —
this is a neighbourhood marked as current
Repo whosonfirst-data-admin-ch/139/440/984/7/1394409847.geojson
ID 1394409847
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ch/112/529/682/1/1125296821.geojson
ID 1125296821
Inception date unknown Cessation 2017-05-19
It was last modified August 10, 2019.
-
Repo whosonfirst-data-admin-ch/139/439/503/7/1394395037.geojson
ID 1394395037
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
01150 —
this is a postalcode
Repo whosonfirst-data-postalcode-fr/421/296/413/421296413.geojson
ID 421296413
Inception date unknown Cessation date unknown
It was last modified June 03, 2017.
-
01260 —
this is a postalcode
Repo whosonfirst-data-postalcode-fr/421/296/437/421296437.geojson
ID 421296437
Inception date unknown Cessation date unknown
It was last modified September 19, 2019.
-
01360 —
this is a postalcode
Repo whosonfirst-data-postalcode-fr/421/296/459/421296459.geojson
ID 421296459
Inception date unknown Cessation date unknown
It was last modified September 19, 2019.
-
01460 —
this is a postalcode
Repo whosonfirst-data-postalcode-fr/421/296/481/421296481.geojson
ID 421296481
Inception date unknown Cessation date unknown
It was last modified June 03, 2017.
-
01590 —
this is a postalcode
Repo whosonfirst-data-postalcode-fr/421/296/503/421296503.geojson
ID 421296503
Inception date unknown Cessation date unknown
It was last modified June 03, 2017.
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,547 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?