[Photon] Next steps

[Yohan Boniface]

On 06/20/2014 10:09 AM, Christoph Lingg wrote:
> hi guys!
> btw, have you tested the json dump of photon or were you using the python script?

json from the java exporter (certainly not up to date because we still 
have many street duplicates).

> I would ask felix for a nominatim export to json, so we will finally have an up to date and bug free global data set we can publish on photon.komoot.de and people can use for an photon setup without installing nominatim.
>

That would be great!

> My plans: I’m working on releasing a new version of photon on komoot at the beginning of next week.


> i am using the fork i created that does not use fuzzy search but is very solid in return.

You should test positivescoring branch also :)

> It is also uncertain to me how fuzzy is increasing the load of the system. has anybody made experience with that? felix told me that fuzzy comes with the price of high cpu consumption …?

This is certainly the case, but we *do* want fuzzy at the end, right?

> Nevertheless this release will resolve a lot of bugs in the current komoot setup and is already a big step as i have to change the infrastructure from solr to es. And i am learning about how to deploy elasticsearch, things i can contribute to photon then.
>

Are you able (or can I?) to set up a worldwide version using 
positivescorting branch on photon.komoot.de? Like in another port, to 
keep the master as main access point.


>> Then I would like to test the "split at search time + match prefix" scenario suggested by Peter. I wonder if this can solve the noise we have when mixing fuzzi + edgengrams for small words.
> cool!
>
>> Also, I'm thinking about spitting the search test module in a separate repository: as we are working now with many branches, and switching a lot, and adding tests here and there, merging becomes more and more tricky.
>> Also it's better to have all search test cases available in any branches.
> I understand your point, it wasn’t a gread pain for me though.

Are you only working on master, man? :)
I've seen some .pyc coming around, and I'm not sure positivescoring or 
custom-similarity can be painlessly merged into master at this point (we 
also have some other branches not pushed) ;)

 > For me both solutions are fine.

OK, so let's split :)

>
>> Plus I would like to start working on adapter for Nominatim, Photon Solr, and also Pelias soon, to be able to compare results.
>> What are your thoughts on this?
> Why are you interested in it?

Monitor the progress and how much things are going better or worse than 
other option around. Search logic isn't something we can totally 
control, so it's good to have some point that help decide "this scenario 
is better than this one" or "doing this change make things better or worse".
Also, I'm not sure how they are doing metrics in Pelias, but this is 
typically a module we should factorise between the two projects imho. :)


BTW, any news from Pelias people?