-
|
I've read the docs so far: https://github.com/tess1o/geopulse but am still wondering if someone could share more info about the “best” combination. I'm the sole user of my geopulse instance, I rarely travel so most of the time its just work, shopping and walking the dog. I don't need geopulse to reflect my location and travels in real-time, so I have no issue with rate limited providers. What exactly is the difference between the 4 providers? Is it a quality issue? If so, can you rate them in order? I'm not worried about privacy at the moment so that is not the most important criteria. Also, I saw you can easily self-host a local photon instance, I had it up and running when I was testing dawarich, and I am wondering if there is any point in doing so except for privacy reasons? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Hello, Just use default Nomatim, no extra configuration is needed from your side. It's enabled by default and for me works fine. GeoPulse will fetch reverse geocoding information first time (if you Import data from other source) and then when you go to a new place which is not yet available in our DB. If you visit the same places it won't send any requests to the provider and will use the data we already have. So it's quite good from performance perspective. Or you can actually try Nomatim and Photon (public or selfhosted instance) and compare results:
Probably this is the only way to figure out the best option for you. If you don't like particular results you can update the display name for them individually on the same "Reverse Geocoding Management" page. Google Maps and Mapbox are other options but they require API Keys (free tier is available). I'd consider them only if you're not satisfied with free options. Regarding public or selfhosted options (like for Nomatim and Photon) - probably it's a question or privacy and preference. You own your provider, you can maintain it, you don't care if public one dies some day. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I've done a handful of tests with reconciling between nominatim and photon and it's hit-and-miss. Each recognizes about 50% of the visited places and if they don't, they just display the street address. If I were to manually fix this, I'd select all street addresses and reconcile them, and I'd probably get 50% of them to actually display a business name instead of a street address. I wanted to give mapbox a quick test and manually tried reconciling a handful of points but am getting this error. Any ideas or shall I open a separate issue? |
Beta Was this translation helpful? Give feedback.
Hello,
Just use default Nomatim, no extra configuration is needed from your side. It's enabled by default and for me works fine.
GeoPulse will fetch reverse geocoding information first time (if you Import data from other source) and then when you go to a new place which is not yet available in our DB. If you visit the same places it won't send any requests to the provider and will use the data we already have. So it's quite good from performance perspective.
Or you can actually try Nomatim and Photon (public or selfhosted instance) and compare results: