3 votesdikkeknodel shared this idea ·
I haven't used this functionality yet, but seen it. Since I am just registered on Komoot today I don't have friends yet, so didn't think about using.
I really had to laugh out loud that this is actually how the "Invitation option" is implemented. What if everybody would not give a date and time for a birthday party?
A little thought experiment just crossed my mind:
Considering that you never added your birthdate to any social network, but most of your friends have a reasonable idea of your approximate date of birth (weren't you born in April?), I assume the data would be normally distributed.
One early outlier might show up a week early. From then onwards each day there will be more people. Your actual day of birth there will most likely be the most people and then their number decreases again until nine days later the late outlier shows up.
If you'd be lucky (or unlucky when you value your beer and wine collection) all of them will come early and stay late just to make sure that they have been at your special day...
Anyway, I give it three votes!
that is a useful and good idea. However, to add it to our system. there are a few things we need to mind: There are hikers and bikers who wish to avoid using ferries, while others specifically wish to add them to their Tours. On the other hand – and the problem also includes using lifts for instance – they might not be usable at all times of the day and year.
So we can realize this idea to your best contentment we therefore need to consider quite a few things. We are however planning to look into this in more detail, and will keep you posted here when we are ready.
A certain level of planning skill should be assumed of the person doing the tour. Looking into the ferry schedule is part of that in my opinion. Komoot reports in the tour description that there is a ferry crossing, so it should not be a surprise.
Komoot knows from the OpenStreetMap dataset that it relies on that there is a ferry. Often this dataset also includes information about the name of the operator, and there website. This information could be supplied to the Komoot user.
When you are on the komoot website in the 'Plan' part, there is a box in the left column 'Search for Place or Address'. When you put the cursor in there immediately a list is shown to enable layers for camping, restaurants etc. So the data is already there (in the OpenStreetMap dataset on which Komoot relies).
If you mean places to camp in the wild, which are off course not marked, then the highlights initiative below enables that. I suggest you put maximum votes on that :-).
Additionally, the general map would look a lot cleaner if the highlights would only be visible for the specific tour their made in.
Komoot is using OpenStreetMap (OSM) data. I see a lot of highlights in my region that are actually duplicates of what was already shown on the map from Point of Interest in the OSM dataset. Like for example there are many restaurant at the top of mountains, which have been marked in OSM since long before Komoot was even thought of, but it is also added as a highlight for cycling and, sepately, for hiking. This is just wasting the overview on the map.
I think however for a specific planned tour that it may be valuable to highlight such spot that you will pass (closely enought to make a detour). But for the general map it is just making a mess. You can enable the layer with restaurant and see it.
At another place in this help site somebody actually requested the option to classify the highlights. That person probably had no clue that most of these PoIs are already in OSM and that such info should be contributed back to OSM (see http://help.komoot.de/forums/213895-ideas/suggestions/18819544-add-highlights-categories).
Komoot is using OpenStreetMap (OSM) data. All the information Giuseppe is asking for is already in that OSM dataset as Points of Interest. Apparently Komoot made the decision to not show that information.
It would be a waste to have people enter this information yet another time, while it is mostly already in the dataset. If it is not in OSM, then it should be contributed to the OpenStreetMap dataset instead. Otherwise I would consider it parasitic behaviour, when you're only taking from OSM but not giving back to the community. OSM is used much more broadly than Komoot alone.
I see a lot of highlights in my region that are actually duplicates of what was already shown on the map from OSM data. Like for example there is a restaurant at a top of the mountain, which has been marked in OSM since long before Komoot was even thought of, but it is also added as a highlight for cycling and, sepately, for hiking. This is just wasting the overview.