[OSM-dev] Need advise for localization of Mapnik/Osmarender/Data search

Arne Goetje arne at linux.org.tw
Thu Jul 10 14:18:23 BST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Milo van der Linden wrote:

>> Nice! I assume that the main data is stored on the central OSM server,
>> that you get a reoccuring update and use that for your database? Or is
>> localization done entirely on your server?

Yes, it's on the central server and we get a regular excerpt.

> Is your local database postgres/postGIS?

yes.

>> In that case I would strongly advice to upgrade to the latest
>> postgresql: 8.3. It comes with full text search out of the box.
> 
>> <http://www.postgresql.org/docs/current/static/textsearch.html>
> 
>> Full text search makes transliteration a piece of cake and makes it case
>> insensitive. You would need to write your own "sounds-like" script on
>> the database for cases like: Zhong-Zheng Rd., Jhongjheng Rd., Jungjeng
>> Rd. Chung-cheng Rd, where I would advice you to maintain a seperate data
>> table.
> 
>> regarding the lack of spaces in addresses; A minumum amount of spaces is
>> needed for full text search to work. So I would sugest writing a script
>> that will strip house-numbers,citynames, and streetnames and store them
>> in separate tables. Or you can put spaces in front of and behind every
>> single character...
> 
>> read the documentation on textsearch with postgresql, it will probably
>> be a good help and starting point!

ok, thanks for the info.

> 
> It would be great if we could feed those improvements back into the main
> OSM project, so that the search on the main OSM website also delivers
> the correct results. So the question is: where is the code we need to
> enhance and how to coordinate it? I could provide a list of aliases for
> road names and Chinese characters to classify address patterns (County,
> City, Village, etc.) and explain the possible address patterns.

any comments on this?

Cheers
Arne
- --
Arne Götje (高盛華) <arne at linux.org.tw>
PGP/GnuPG key: 1024D/685D1E8C
Fingerprint: 2056 F6B7 DEA8 B478 311F  1C34 6E9F D06E 685D 1E8C
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIdgwfbp/QbmhdHowRAq1aAJ9TdeT7TCKIP98qo6po67GJlimY0gCeKK5X
7RG5FmOxSzlk/ytC9felM9s=
=VC5C
-----END PGP SIGNATURE-----




More information about the dev mailing list