|
|
|
|
|
by jaymzcampbell
549 days ago
|
|
Did something change with how the locations are managed? I tried to add myself and used the lookup for London, which then gave a lat/long as part of the address, like your examples. But then I noticed that I was all alone and the "rest" of london in a 30+ group have their location without lat/lng. This is what it gave me when entering London, UK: meet.hn/city/51.5074456,-0.1277653/London But compare with, e.g, https://news.ycombinator.com/user?id=jones58 - meet.hn/city/gb-London. It looks like that's affecting other cities like Paris too - a large "original" group, and then a solitary one with lat/lng. |
|
To do so, I implemented a search using OpenStreetMap. The thing is, OpenStreetMap can give several results for a given location (and rightfully so). Example with Paris: https://www.openstreetmap.org/search?query=Paris%2C%20France.
When I updated the way meet.hn handles location, I migrated all city ids like the one you mention "gb-London" to a new one using lat/long.
The problem is: when users select a location, they can end up at another (close) location suggested by OpenStreetMap. To mitigate this pb, if locations have the same full name or OpenStreetMap id, I don't display them in the location selector.
Also, I put locations of type "city" first to nudge users into selecting cities more and hopefully end up with less problems of this kind.
Code about this is here: https://github.com/borisghidaglia/meet-hn/blob/808143d36841b...
There is something to be done, but I only had overly complicated ideas to fix this.
Very open to suggestions. Don't hesitate to open an issue/PR for this on GitHub.