Places that have a concordance with ro-ancpi:id= (Romanian National Agency for Cadastre and Land Registration (ANCPI))
-
Joldeşti —
this is a locality marked as current
Repo whosonfirst-data-admin-ro/101/782/617/101782617.geojson
ID 101782617
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ro/101/782/625/101782625.geojson
ID 101782625
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ro/129/385/962/1/1293859621.geojson
ID 1293859621
Inception date unknown Cessation date unknown
It was last modified June 26, 2020.
-
Humoreni —
this is a locality marked as current
Repo whosonfirst-data-admin-ro/101/782/649/101782649.geojson
ID 101782649
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Costâna —
this is a locality marked as current
Repo whosonfirst-data-admin-ro/101/782/663/101782663.geojson
ID 101782663
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ro/129/386/497/7/1293864977.geojson
ID 1293864977
Inception date unknown Cessation date unknown
It was last modified June 26, 2020.
-
Repo whosonfirst-data-admin-ro/129/387/008/3/1293870083.geojson
ID 1293870083
Inception date unknown Cessation date unknown
It was last modified June 26, 2020.
-
Corni —
this is a locality marked as current
Repo whosonfirst-data-admin-ro/101/782/699/101782699.geojson
ID 101782699
Inception date unknown Cessation date unknown
It was last modified August 01, 2023.
-
Repo whosonfirst-data-admin-ro/129/388/389/9/1293883899.geojson
ID 1293883899
Inception date unknown Cessation date unknown
It was last modified June 26, 2020.
-
Clit —
this is a locality marked as current
Repo whosonfirst-data-admin-ro/129/388/686/5/1293886865.geojson
ID 1293886865
Inception date unknown Cessation date unknown
It was last modified June 26, 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,376 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?