There are a lot of data on cities, and cities are also very much. To keep everything in one collection and make an index, I think this will not be enough. Since it will be necessary to use more than one index. Are there any other features? breakdown into partitions, etc. Since there will be many genera to create a collection for each city, I think this is bad. Thank!
- According to the results of the 2010 census, 1,100 localities have the status of a city. Do you think this much? - avp
|
1 answer
- Each geographic item has its own type. Store everything in the same table with the link of each item to its parent.
Indices do by specific type and by parent.
For example:
In Belarus, there is a village like "Paris". She has her own type. In France, there is the city of Paris. The type "city" is of higher priority than the type "Village".
Sorry, maybe I didn’t understand the question well, but told me how it is done. PS The size of the database with cartographic coordinates is 32GB. Direct / reverse geocoding is done in thousandths of a second.
|