linuzer

Yes, here's the content: ``` ~/libpostal/data/libpostal/address_parser$ ls -lah insgesamt 759M drwxr-xr-x 2 2002 1001 4,0K Dez 13 15:41 . drwxr-xr-x 8 root root 4,0K Nov 29 16:43 .. -rw-r--r-- 1...

...sorry, wrong button :-((

I did it completely: a config, providing the full path, make clean, make, make install. But unfortunately with the same result.

to make sure that we talk about the same string: I use this address string: `центральная улица 24 заводоуковскии городскои округ тюменская область уральскии федеральныи округ` and am pasting it...

OK, but the result is almost the same: ``` Result: { "road": "центральная улица", "house_number": "24", "house": "заводоуковский городской", "city": "округ", "state_district": "тюменская область", "city": "уральский", "state_district": "федеральный", "state": "округ"...

Thanks a lot for your great help! I will try this special parser tomorrow. My Problem is that I have to geocode regularly several 100 thousand customer addresses in different...

Thank you very much for your support! I'll try it when it is online.

There's still a detail which I don't quite understand. You wrote: > For normalization, the preferred way to do it is to first parse the user input into components, which...

Thanks a lot for that detailed explanation an this outline, that cleared up a lot! I implemented this logic now in PostgreSQL, being able to parse and normalize into different...

Yes, I parse both, the OSM-addresses and my query-addresses and then normalize each component separately, storing the variations in separate tables that stay linked to the original address. And yes,...