LoPoi category Seating
Gathering feedback
By highlighting LoPoi, it now makes sense to introduce a new category of seating.
I often look for a bench to take a break when hiking. highlighting seating would be very good here.
You could show all benches and picnics in this category.
Picnic already exists but often a bench would be enough.
Files:
Screenshot_2025...
I like this idea 
But please don't categorise picnic areas and benches as the same thing. There are millions of benches.
But please don't categorise picnic areas and benches as the same thing. There are millions of benches.
But that's exactly what I want. All the seating. This includes picnic areas and benches. Because you can sit on both.
If you don't want that, just use the picnic area.
But that's exactly what I want. All the seating. This includes picnic areas and benches. Because you can sit on both.
If you don't want that, just use the picnic area.
If there are two categories, you can activate both and have what you want.
If there are two categories, you can activate both and have what you want.
But there's only one. That's why I want a seat, and both should be displayed.
But there's only one. That's why I want a seat, and both should be displayed.
So you want a special (separate) category "seats", but the existing picnic area category remains?
I still think it would make more sense to add a "Benches" category so that you also have the option of highlighting only benches (without picnic areas). In my opinion, "summarising" different object types is the wrong approach. Everyone has different views and ideas about what should be grouped together.
You just have to activate two categories.
So you want a special (separate) category "seats", but the existing picnic area category remains?
I still think it would make more sense to add a "Benches" category so that you also have the option of highlighting only benches (without picnic areas). In my opinion, "summarising" different object types is the wrong approach. Everyone has different views and ideas about what should be grouped together.
You just have to activate two categories.
I think that also makes a lot of sense. When I search for a place to sit, Picnic should automatically be displayed.
Picnic: 2 benches and a table
Bench: 1 bench
There is already a picnic category. If you don't want a bench then simply activate Picnic.
Why should I activate 2 categories if I can do it with one? And there is no one who is looking for a seat but does not want a picnic displayed.
I think that also makes a lot of sense. When I search for a place to sit, Picnic should automatically be displayed.
Picnic: 2 benches and a table
Bench: 1 bench
There is already a picnic category. If you don't want a bench then simply activate Picnic.
Why should I activate 2 categories if I can do it with one? And there is no one who is looking for a seat but does not want a picnic displayed.
I would also really like to see benches added as a separate LoPoint category.
For hiking, benches can be very useful POIs. When planning a walk – or simply looking for a place to take a short break while hiking – it would be great to be able to display or highlight nearby benches in Locus Map.
A lot of this information is already available in OpenStreetMap as "amenity=bench". For example, OSM node 12836841019 is a correctly mapped bench that has been in OSM for quite some time. It is immediately visible in apps such as Every Door, but it does not appear as a LoPoint in Locus Map.
Since benches are already included in the underlying OSM data, it would be very useful if Locus could include "amenity=bench" in the LoPoints database as well.
Personally, I would prefer Benches as a separate LoPoint category, rather than combining them with picnic sites or other seating. That would make it possible to specifically highlight benches while hiking.
I think this could be a very useful addition for hikers and walkers.
I would also really like to see benches added as a separate LoPoint category.
For hiking, benches can be very useful POIs. When planning a walk – or simply looking for a place to take a short break while hiking – it would be great to be able to display or highlight nearby benches in Locus Map.
A lot of this information is already available in OpenStreetMap as "amenity=bench". For example, OSM node 12836841019 is a correctly mapped bench that has been in OSM for quite some time. It is immediately visible in apps such as Every Door, but it does not appear as a LoPoint in Locus Map.
Since benches are already included in the underlying OSM data, it would be very useful if Locus could include "amenity=bench" in the LoPoints database as well.
Personally, I would prefer Benches as a separate LoPoint category, rather than combining them with picnic sites or other seating. That would make it possible to specifically highlight benches while hiking.
I think this could be a very useful addition for hikers and walkers.
I understand your point about picnic areas, but for me they serve a different purpose.
What I would really like is the possibility to specifically show benches (amenity=bench) as LoPoints. When I am hiking uphill, for example, I am not looking for a picnic area – I am simply looking for a bench where I can sit down for a few minutes, catch my breath and then continue my hike.
In situations like that, knowing that there is a bench 200 or 500 metres further along the trail can actually be very useful.
So I would strongly prefer Benches as a separate category, even if picnic areas are also included in a broader “Seating” category. That way users can choose exactly what they want to display.
There are already huge numbers of amenity=bench objects mapped in OSM, so it would be great to actually be able to use that information in Locus Map while hiking.
I understand your point about picnic areas, but for me they serve a different purpose.
What I would really like is the possibility to specifically show benches (amenity=bench) as LoPoints. When I am hiking uphill, for example, I am not looking for a picnic area – I am simply looking for a bench where I can sit down for a few minutes, catch my breath and then continue my hike.
In situations like that, knowing that there is a bench 200 or 500 metres further along the trail can actually be very useful.
So I would strongly prefer Benches as a separate category, even if picnic areas are also included in a broader “Seating” category. That way users can choose exactly what they want to display.
There are already huge numbers of amenity=bench objects mapped in OSM, so it would be great to actually be able to use that information in Locus Map while hiking.
Of course I would! 🙂 I think we may be misunderstanding each other.
I have absolutely no problem with picnic areas being included as well. My point is that I would also really like to see all the individual amenity=bench objects.
Especially in hilly or mountainous areas, picnic areas can be few and far between, while individual benches are often placed along hiking trails, sometimes exactly at places where hikers may need a short break.
When walking uphill, it can be very useful just to know that there is a bench another 200 or 500 metres further along the trail. You might decide to keep going until that bench rather than stop somewhere along the path.
So yes: picnic areas and benches. 🙂 I just don't want the many individual benches that are already mapped in OSM to be left out. For hikers, their locations can be genuinely useful information.
Of course I would! 🙂 I think we may be misunderstanding each other.
I have absolutely no problem with picnic areas being included as well. My point is that I would also really like to see all the individual amenity=bench objects.
Especially in hilly or mountainous areas, picnic areas can be few and far between, while individual benches are often placed along hiking trails, sometimes exactly at places where hikers may need a short break.
When walking uphill, it can be very useful just to know that there is a bench another 200 or 500 metres further along the trail. You might decide to keep going until that bench rather than stop somewhere along the path.
So yes: picnic areas and benches. 🙂 I just don't want the many individual benches that are already mapped in OSM to be left out. For hikers, their locations can be genuinely useful information.
One more thought: there is probably a reason why OpenStreetMap treats amenity=bench as a POI in its own right and even gives benches their own map symbol. 🙂
A bench is not necessarily part of another facility such as a picnic area. It can be a useful destination or waypoint by itself – especially for hikers.
The data is already there in OSM. It would be great if Locus could make use of it as LoPoints as well.
One more thought: there is probably a reason why OpenStreetMap treats amenity=bench as a POI in its own right and even gives benches their own map symbol. 🙂
A bench is not necessarily part of another facility such as a picnic area. It can be a useful destination or waypoint by itself – especially for hikers.
The data is already there in OSM. It would be great if Locus could make use of it as LoPoints as well.
Yes, a picnic includes a bench and a table. And a bench is just a bench; if I'm looking for somewhere to rest, I'll look for a bench, so a picnic is automatically included.
Yes, a picnic includes a bench and a table. And a bench is just a bench; if I'm looking for somewhere to rest, I'll look for a bench, so a picnic is automatically included.
Exactly — and that's actually my point. 🙂
If I'm looking for somewhere to rest, I want to see all benches, including the many standalone benches that are not part of a picnic site.
Showing picnic sites does not solve that: it only shows a small subset of the places where I can sit down. Especially on mountain and hiking trails, standalone benches are much more common and useful than picnic sites.
OSM already distinguishes amenity=bench from tourism=picnic_site for exactly that reason. I would simply like Locus/LoPoints to expose that existing bench data as well.
Exactly — and that's actually my point. 🙂
If I'm looking for somewhere to rest, I want to see all benches, including the many standalone benches that are not part of a picnic site.
Showing picnic sites does not solve that: it only shows a small subset of the places where I can sit down. Especially on mountain and hiking trails, standalone benches are much more common and useful than picnic sites.
OSM already distinguishes amenity=bench from tourism=picnic_site for exactly that reason. I would simply like Locus/LoPoints to expose that existing bench data as well.
That's exactly what the suggestion above is. A “Picnic” category, which displays only picnic-related items, and a “Bench” category, which displays both bench- and picnic-related items.
That's exactly what the suggestion above is. A “Picnic” category, which displays only picnic-related items, and a “Bench” category, which displays both bench- and picnic-related items.
Ah, I think we finally discovered that we actually agree. 😄
To be honest, I don't really mind how Locus organizes the categories, or whether picnic sites are included under “Bench”, “Seating” or something else. I'll happily leave that puzzle to Locus. 😉
As long as I can see all those standalone OSM benches on the map — the ones I desperately need to catch my breath when I've once again underestimated the hill I'm walking up — I'll be very happy! 😅
Thanks for the clarification!
Ah, I think we finally discovered that we actually agree. 😄
To be honest, I don't really mind how Locus organizes the categories, or whether picnic sites are included under “Bench”, “Seating” or something else. I'll happily leave that puzzle to Locus. 😉
As long as I can see all those standalone OSM benches on the map — the ones I desperately need to catch my breath when I've once again underestimated the hill I'm walking up — I'll be very happy! 😅
Thanks for the clarification!
Hi all, we keep a list of features that should be at least considered as POIs - that means perhaps became first class citizens of the Locus Map. Benches (and more generic seating options) are of course there. The reason we hesitate to add them: there is 3 000 000 of them worldwide, and there is no reasonable logic to accept just "the important ones". (This kind of logic exists for e.g. "tree": It must have a name or be a "landmark"). Anyway I agree Locus should know them in some form.
Hi all, we keep a list of features that should be at least considered as POIs - that means perhaps became first class citizens of the Locus Map. Benches (and more generic seating options) are of course there. The reason we hesitate to add them: there is 3 000 000 of them worldwide, and there is no reasonable logic to accept just "the important ones". (This kind of logic exists for e.g. "tree": It must have a name or be a "landmark"). Anyway I agree Locus should know them in some form.
Replies have been locked on this page!