The 3 nearest cities should be featured in the city selection. This means they are listed first, before the alphabetical listing of all sites/regions. Nearest cities are based on the location of the device and its distance to all sites/regions
The app has to calculate the distance to all cities and select the closest ones. A cut off distance of 50 km is useful. That means, if no site/region is closer than 50km, no region is shown.
It could make sense to implement this using an IP-based location lookup as this requires no GPS.
The problem with this issue is that most devices (desktop) which use the webapp do no offer a location. Also scrolling down to your home city is not as much of a problem as on mobile.
Therefore this issue is not important right now.
Max Ammann - 16.11.2018, 13:54:30
The 3 nearest cities should be featured in the city selection. This means they are listed first, before the alphabetical listing of all sites/regions. Nearest cities are based on the location of the device and its distance to all sites/regions
The longitude and latitude for sites/regions (and also for its aliases) is available in the sites endpoint of the APIv3: https://github.com/Integreat/cms/wiki/REST-APIv3-Documentation#response
The app has to calculate the distance to all cities and select the closest ones. A cut off distance of 50 km is useful. That means, if no site/region is closer than 50km, no region is shown.
It could make sense to implement this using an IP-based location lookup as this requires no GPS. The problem with this issue is that most devices (desktop) which use the webapp do no offer a location. Also scrolling down to your home city is not as much of a problem as on mobile. Therefore this issue is not important right now.
Environment: - Linked issues: