zbycz / osmapp

Lets make a universal app for OpenStreetMap
https://osmapp.org
GNU General Public License v3.0
218 stars 19 forks source link

Climbing: Grouping #729

Open alensiljak opened 1 week ago

alensiljak commented 1 week ago

I noticed that areas can be nested, which is convenient for grouping of crags into sectors, then into sub-areas, and areas. So far I've only added two levels for area (crag -> sector (area) -> area). It would be great if this scheme could be used for sectors as it offers a recursive, hence infinite, nesting. Not saying that it is necessary but it would be good to have support for a few levels.

Following that, the top-level area would be displayed before child areas/sectors. The top level is the one without a parent relationship.

Any thoughts?

Some areas can pretty full of individual crags and there are actually multiple sectors, as per info guide on site. It would be really useful to support this grouping in multiple levels.

For example, see the Wachau area:

https://openclimbing.org/48.39828,15.52434

The navigation in the panel works well. It is just rendering of the overlay on the map that simply shows an area with most elements, which is wrong in the case of grouping. The top-level area only has 3 sub-areas and one multi-pitch route in it but it represents the whole site and has the appropriate name.

The photos/topos should also propagate?

jvaclavik commented 1 week ago

Logically it totally make sense to me. There are many big areas that should be definitely divided into smaller areas.

I'm just not sure how to show it on the map yet. If it has the same type as area it's tricky to know what area should be visible according to zoom.

For example let's say we have: Labske údolí - area Levy břeh - area Hranol - crag

I don't know how to decide on what zoom we should show Labské údolí and when levý břeh.

I will discuss it with @zbycz how we could do it.