Splitting the KLADR database

Question

Database

Hello, dear habrazhitel!

I would like to know if anyone has ever used the KLADR database in their projects (for the web, in particular) ?
And if used, then whether it was broken into tables or not?

If you expand it according to their description, then you get the following entity structure: Region-

> District-> City-> Settlement

be it a city, a village or something else.

Is it worth while splitting to combine the last two tables into one (city and locality)? And what to do with cities that themselves can include other settlements without being tied to a district (for example, Krasnodar in the Krasnodar Territory or Maykop in Adygea)?

I will be glad to any answer)

ZY . Questions have already arisen, so I’ll say right away - the MySQL database, and the service will be quite heavily loaded, therefore, query speed is a priority)

Answer 1

And also, if suddenly someone knows how, for example, the VKontakte or My Circle database is organized? Judging by the presence of cities, the contact definitely (although perhaps only partially) uses the KLADR base, but how did they organize it?

Answer 2

There is ONE table in the cladre for all regions, territories, cities and settlements, the difference is only in the value of the code column. Streets are another table. And, more importantly, abbreviations. Why cut it into a bunch of separate tables, if you can work perfectly with such an architecture? If you have any questions about cladding, please ask.

Answer 3

Used but not cut.
Just a problem with cities without regions and sub-cities near cities, they were not allowed to “beautifully” break up. You never know what level we belong to. paragraph.
But in practice, it turned out that it is quite easy to work with such a one-table structure.
The main thing is to enter a link to the "level above", otherwise it is quite problematic to operate with area codes in the code.

Answer 4

What does "for a trading site" mean? How is the address used in your system?