Skip to content

Improve search results for US market #2509

@HarelM

Description

@HarelM

What happened?

It's hard to find things in the US

What I expect to happen

I should be able to find things in the US according to what I searched for

What steps will reproduce the bug?

Will be added later.

Product

  • Mapeak
  • Israel Hiking

Platform

  • The mobile appplication
  • The website in a browser

OS Name and Version

Any

Browser Name and Version

Any

Additional information

Here's a breakdown of the original reasoning for creating planet-search and its capabilities.
When looking at a global solution for Mapeak I have considered the following options:

  1. Nominatim (OSM's search)
  2. Photon (Komoot's search)
  3. Pelias (I don't know where it is used)

Photon is basically a nominatom port from a PostGIS database to elasticseach. I found the process cumbersome and complicated for no good reason. Moreover, it doesn't support relations, which is important for our use case - long hiking routes and bike routes.
I believe Photon supports fuziness since it uses elasticseach, but I'm not sure.
So the above two were rejected due to missing information and complexity.
When I looked at Pelias I saw that it can take a few days to build and I wasn't sure what is its memory and CPU footprint. I also remember that it was hard to setup, but that might not be the case anymore.
I ended up building planet-search to support the following use cases:

  1. There's a need to run planetiler for the POIs pmtiles so this needs to stay anyway.
  2. There's a lot of similar logic between POIs creation and search items creation since we want to achieve similar things, for example:
    2.1. Icons for both search and POIs
    2.2. Single results for things like waterways and mtb ways (i.e. merge them when possible)
    2.3. Solve some OSM quirkiness for places - node & polygon stuff
  3. Support Hebrew in regards to Niqqud (was recently solved to be honest)

Nevertheless, finding the right place in a global perspective might be more important than the above solutions that were made to match the previous search algorithm that was used in IHM and was fully in-memory.

The next step would be to define a list of search terms and the expected results foreach of them to better define the success criteria of this issue.
Once we define those we can test them and see what gives the best results and if there's a need to update the current planet-search code or switch to using a different search provider.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions