Descendants of 85669797
-
Repo whosonfirst-data-admin-cn/119/325/700/5/1193257005.geojson
ID 1193257005
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Tunli —
this is a locality
Repo whosonfirst-data-admin-cn/119/325/701/3/1193257013.geojson
ID 1193257013
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Xilu —
this is a locality
Repo whosonfirst-data-admin-cn/119/325/702/3/1193257023.geojson
ID 1193257023
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-cn/119/325/703/3/1193257033.geojson
ID 1193257033
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-cn/119/325/705/5/1193257055.geojson
ID 1193257055
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-cn/119/325/706/3/1193257063.geojson
ID 1193257063
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-cn/119/325/710/5/1193257105.geojson
ID 1193257105
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-cn/119/325/712/7/1193257127.geojson
ID 1193257127
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-cn/119/326/701/1/1193267011.geojson
ID 1193267011
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
-
Repo whosonfirst-data-admin-cn/119/326/703/1/1193267031.geojson
ID 1193267031
Inception date unknown Cessation date unknown
It was last modified August 24, 2019.
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,983 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?