[OSM-dev] Namefinder - what to do

Robert (Jamie) Munro rjmunro at arjam.net
Tue Jan 22 16:46:24 GMT 2008


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

Tom Hughes wrote:
| In message <223020e60801220443h78d1575gd1ecec230167831c at mail.gmail.com>
|         Nick Black <nickblack1 at gmail.com> wrote:
|
|> If we create an index on the way_tags k & v column we can directly
|> search live data and retain the vast majority of the functionality of
|> the namefinder search.  This obviously leaves the nodes being
|> unsearchable.  So I'm going to look at moving node tags into a
|> node_tags table.
|
| Splitting out the node tags is good. I suspect they are quite
| inefficient at the moment as they make the node records variable
| length. Plus splitting them out lets us have full text indexes
| on the tags although that does force us to use MyISAM for the
| tags table.

And we would fix the ; problem.

|> TomH: what do you think about creating a full text index on  way_tags
k & v?
|
| We already have one on v, but not k.
|
| I've no objection to putting one on k - it will allow some more
| restrictions on the search API to be lifted.

Surely k only needs a normal index, not a full text one. For the
purposes of a name finder like thing we just need to search the values
for k=name - I don't know if you can do a conditional index in MySQL. I
have a feeling you can't, which means that it would have to be a
separate table of name tag values.

Something that would be good is an HTML page for each node or way that
had an openlayers with the thing highlighted, and a list of things
associated with it (either with relations, with connecting ways, or just
nearby) with links. It could also "transclude" wikipedia content about
the object if there is any. The idea would be that search engines would
spider it and when someone searches for something we would be in the
results.

Robert (Jamie) Munro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHlh3ez+aYVHdncI0RAtv/AJ4xXbKIc6O07sOWCbqgdWRMi4KGKACeN1lU
XM0VBgOwN6UICUfhw2w68e4=
=OPXb
-----END PGP SIGNATURE-----




More information about the dev mailing list