Best way to store object addresses?

Question

Database

Hello!

I would like to discuss a little.

Most likely, many have come across a solution to a similar problem - "catalog of organizations", "list of addresses", etc.
I understand that “it’s right as I need it,” but I’m wondering who used what approach, by what means and in what form organized the storage of such information?
Let's say the object is "building". Its characteristics:
- region (this is a region, region, territory);
- district of the region;
- street (this is an avenue, passage, street);
- house (building, structure);
- coordinates.

After all, streets with the same name can be in different regions, districts, cities.
Making a general list of streets is, of course, not an option.
It turns out that it is necessary to connect the streets with the city, the city with the district, then with the region.
And already the ID of the street_concrete_city to associate with some building.

I'm thinking: is it necessary to bind the object itself to a specific city or is it not necessary? If not, then it turns out like this:
- object identifier;
— street identifier of a particular city;
— object number (house number);
- other information.

Or maybe it's easier to make a list of available streets for a specific city and use it in the "hints" in the form of a "tag" when adding / searching for an address (as, for example, here on Habré)?

What difficulties, difficulties were in the approaches you tried?
What software solutions are best suited for such tasks (DBMS). Sphinx can help here too?

Thanks

Answer 1

Google the word "KLADR". No matter how much they tried to make simplified formats for storing addresses, they still came to KLADR. A very specific format, but there are still more pluses than minuses.