Dear All
Since after the online meeting a while ago I tried to formulate a draft based on the discussions on the mailing list / the meeting. Due to lack of time and energy, this took unfortunately a lot longer than I initially thought.
The current draft can be found here https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFh...
Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives.
If you like, please create comments directly in the document or reply to this email when you have feedback. The idea would be to collect all discussion points at the bottom of the document and mark the discussed parts of the document with comments.
When writing the draft, I had the following thoughts:
- It would be could to include some background information about the Swiss hiking network as this could give some context for the rest of the document and might facilitate discussions about the topic. - There are different opinions on what level of detail the hiking network should be mapped. It is thus important to clearly state a minimal goal but also allow some flexibility. - Changes to the wiki page should not contradict existing mapped relations, except there are good reasons for it (such as e.g. the issue with using name tags for relations that clash with nominatim) - Figures are sometimes better to explain things than text. - For some regions, open datasets exist that contain the hiking network but no information about guideposts. These datasets should be usable.
lg rene
*English text below (Google translate)*
Bonjour,
Merci pour cette proposition ! Je carthographie le réseau pédestre depuis plusieurs années et je suis convaicu de l'intérêt d'avoir ces données dans OpenStreetMap !
Dans ma région j'ai carthographié les chemins pédestres d'une autre façon encore. Comme je sais que les chemins sont entretenus par les communes, j'ai créé une relation par commune. Cette relation regroupe tous les chemins de cette commune, ceci afin de ne pas avoir trop de relations, ou des chemins qui sont dans plusieurs relations.
Par exemple pour la commune d'Orsières : https://www.openstreetmap.org/relation/1067491
Ou celle de Sembrancher : https://www.openstreetmap.org/relation/1589286
J'espère que ce commentaire pourra vous être utile !
Meilleures salutations Raphaël Terrettaz
-----------
Hello,
Thank you for this proposal! I have been mapping the hiking network for several years and I am convinced of the interest of having this data in OpenStreetMap!
In my region I have mapped the hiking trails in another way. As I know that the paths are maintained by the municipalities, I created a relationship per municipality. This relation regroups all the paths of this municipality, in order to have a reduced number of relations, or paths in several relations.
For example for Orsières: https://www.openstreetmap.org/relation/1067491
Or for Sembrancher: https://www.openstreetmap.org/relation/1589286
Hope this comment can be useful to you!
Best regards Raphaël Terrettaz
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Garanti sans virus. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Le dim. 19 sept. 2021 à 15:02, René Buffat buffat@gmail.com a écrit :
Dear All
Since after the online meeting a while ago I tried to formulate a draft based on the discussions on the mailing list / the meeting. Due to lack of time and energy, this took unfortunately a lot longer than I initially thought.
The current draft can be found here https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFh...
Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives.
If you like, please create comments directly in the document or reply to this email when you have feedback. The idea would be to collect all discussion points at the bottom of the document and mark the discussed parts of the document with comments.
When writing the draft, I had the following thoughts:
- It would be could to include some background information about the
Swiss hiking network as this could give some context for the rest of the document and might facilitate discussions about the topic.
- There are different opinions on what level of detail the hiking
network should be mapped. It is thus important to clearly state a minimal goal but also allow some flexibility.
- Changes to the wiki page should not contradict existing mapped
relations, except there are good reasons for it (such as e.g. the issue with using name tags for relations that clash with nominatim)
- Figures are sometimes better to explain things than text.
- For some regions, open datasets exist that contain the hiking
network but no information about guideposts. These datasets should be usable.
lg rene
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
Une relation de 160 membres pour collectionner les chemins d'une même commune ? Cela ne va pas faire que des heureux.... Pourquoi pas un tag operator= ou maintained_by= ou autre ?
A 160 members relation collecting de trails on a same village ? Some may disagree... Why not an operator= or maintened_by= tag or else?
Yves
Le 19 septembre 2021 21:59:24 GMT+02:00, "Raphaël Terrettaz" r.terrettaz@gmail.com a écrit :
*English text below (Google translate)*
Bonjour,
Merci pour cette proposition ! Je carthographie le réseau pédestre depuis plusieurs années et je suis convaicu de l'intérêt d'avoir ces données dans OpenStreetMap !
Dans ma région j'ai carthographié les chemins pédestres d'une autre façon encore. Comme je sais que les chemins sont entretenus par les communes, j'ai créé une relation par commune. Cette relation regroupe tous les chemins de cette commune, ceci afin de ne pas avoir trop de relations, ou des chemins qui sont dans plusieurs relations.
Par exemple pour la commune d'Orsières : https://www.openstreetmap.org/relation/1067491
Ou celle de Sembrancher : https://www.openstreetmap.org/relation/1589286
J'espère que ce commentaire pourra vous être utile !
Meilleures salutations Raphaël Terrettaz
Hello,
Thank you for this proposal! I have been mapping the hiking network for several years and I am convinced of the interest of having this data in OpenStreetMap!
In my region I have mapped the hiking trails in another way. As I know that the paths are maintained by the municipalities, I created a relationship per municipality. This relation regroups all the paths of this municipality, in order to have a reduced number of relations, or paths in several relations.
For example for Orsières: https://www.openstreetmap.org/relation/1067491
Or for Sembrancher: https://www.openstreetmap.org/relation/1589286
Hope this comment can be useful to you!
Best regards Raphaël Terrettaz
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Garanti sans virus. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Le dim. 19 sept. 2021 à 15:02, René Buffat buffat@gmail.com a écrit :
Dear All
Since after the online meeting a while ago I tried to formulate a draft based on the discussions on the mailing list / the meeting. Due to lack of time and energy, this took unfortunately a lot longer than I initially thought.
The current draft can be found here https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFh...
Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives.
If you like, please create comments directly in the document or reply to this email when you have feedback. The idea would be to collect all discussion points at the bottom of the document and mark the discussed parts of the document with comments.
When writing the draft, I had the following thoughts:
- It would be could to include some background information about the
Swiss hiking network as this could give some context for the rest of the document and might facilitate discussions about the topic.
- There are different opinions on what level of detail the hiking
network should be mapped. It is thus important to clearly state a minimal goal but also allow some flexibility.
- Changes to the wiki page should not contradict existing mapped
relations, except there are good reasons for it (such as e.g. the issue with using name tags for relations that clash with nominatim)
- Figures are sometimes better to explain things than text.
- For some regions, open datasets exist that contain the hiking
network but no information about guideposts. These datasets should be usable.
lg rene
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
Oui je suis d'accord avec Yves, une relation de plus de 150 membres n'est pas gérable. Par contre ça m'a permis de répertorier rapidement tous les chemins pédestre que j'empruntais, sans que je sache forcément leur origine ou destination ! De plus je ne voyais pas d'utilisation de ces données précises dans OSM.
S'il y a une nouvelle façon standard de carthographier ces chemins, avec ce que j'ai déjà reconnu ce sera simple de créer de nouvelles relations !
Et, je me demande, est-ce que des contacts ont déjà été pris avec http://www.yway.ch/ ? C'est une base impressionnante de poteau indicateurs, cela permettrait d'ajouter rapidement tous ceux qu'il manque encore.
Raphaël Terrettaz
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Garanti sans virus. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Le dim. 19 sept. 2021 à 22:23, Yves ycai@mailbox.org a écrit :
Une relation de 160 membres pour collectionner les chemins d'une même commune ? Cela ne va pas faire que des heureux.... Pourquoi pas un tag operator= ou maintained_by= ou autre ?
A 160 members relation collecting de trails on a same village ? Some may disagree... Why not an operator= or maintened_by= tag or else?
Yves
Le 19 septembre 2021 21:59:24 GMT+02:00, "Raphaël Terrettaz" < r.terrettaz@gmail.com> a écrit :
*English text below (Google translate)*
Bonjour,
Merci pour cette proposition ! Je carthographie le réseau pédestre depuis plusieurs années et je suis convaicu de l'intérêt d'avoir ces données dans OpenStreetMap !
Dans ma région j'ai carthographié les chemins pédestres d'une autre façon encore. Comme je sais que les chemins sont entretenus par les communes, j'ai créé une relation par commune. Cette relation regroupe tous les chemins de cette commune, ceci afin de ne pas avoir trop de relations, ou des chemins qui sont dans plusieurs relations.
Par exemple pour la commune d'Orsières : https://www.openstreetmap.org/relation/1067491
Ou celle de Sembrancher : https://www.openstreetmap.org/relation/1589286
J'espère que ce commentaire pourra vous être utile !
Meilleures salutations Raphaël Terrettaz
Hello,
Thank you for this proposal! I have been mapping the hiking network for several years and I am convinced of the interest of having this data in OpenStreetMap!
In my region I have mapped the hiking trails in another way. As I know that the paths are maintained by the municipalities, I created a relationship per municipality. This relation regroups all the paths of this municipality, in order to have a reduced number of relations, or paths in several relations.
For example for Orsières: https://www.openstreetmap.org/relation/1067491
Or for Sembrancher: https://www.openstreetmap.org/relation/1589286
Hope this comment can be useful to you!
Best regards Raphaël Terrettaz
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Garanti sans virus. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#m_5791829846175558290_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Le dim. 19 sept. 2021 à 15:02, René Buffat buffat@gmail.com a écrit :
Dear All
Since after the online meeting a while ago I tried to formulate a draft based on the discussions on the mailing list / the meeting. Due to lack of time and energy, this took unfortunately a lot longer than I initially thought.
The current draft can be found here https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFh...
Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives.
If you like, please create comments directly in the document or reply to this email when you have feedback. The idea would be to collect all discussion points at the bottom of the document and mark the discussed parts of the document with comments.
When writing the draft, I had the following thoughts:
- It would be could to include some background information about
the Swiss hiking network as this could give some context for the rest of the document and might facilitate discussions about the topic.
- There are different opinions on what level of detail the hiking
network should be mapped. It is thus important to clearly state a minimal goal but also allow some flexibility.
- Changes to the wiki page should not contradict existing mapped
relations, except there are good reasons for it (such as e.g. the issue with using name tags for relations that clash with nominatim)
- Figures are sometimes better to explain things than text.
- For some regions, open datasets exist that contain the hiking
network but no information about guideposts. These datasets should be usable.
lg rene
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
Hi Raphael
I agree that we should not put all marked ways of one operator into a single relation. I think keeping them linear is easier for mappers and for data consumers. And as Yves said, you can still use the operator tag on all those relations. If you don't know the whole trail, you can still make a relation with parts. You can leave from/to empty.
Michael
On 22.09.21 21:29, Raphaël Terrettaz wrote:
Oui je suis d'accord avec Yves, une relation de plus de 150 membres n'est pas gérable. Par contre ça m'a permis de répertorier rapidement tous les chemins pédestre que j'empruntais, sans que je sache forcément leur origine ou destination ! De plus je ne voyais pas d'utilisation de ces données précises dans OSM.
S'il y a une nouvelle façon standard de carthographier ces chemins, avec ce que j'ai déjà reconnu ce sera simple de créer de nouvelles relations !
Et, je me demande, est-ce que des contacts ont déjà été pris avec http://www.yway.ch/ http://www.yway.ch/ ? C'est une base impressionnante de poteau indicateurs, cela permettrait d'ajouter rapidement tous ceux qu'il manque encore.
Raphaël Terrettaz
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Garanti sans virus. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Le dim. 19 sept. 2021 à 22:23, Yves <ycai@mailbox.org mailto:ycai@mailbox.org> a écrit :
Une relation de 160 membres pour collectionner les chemins d'une même commune ? Cela ne va pas faire que des heureux.... Pourquoi pas un tag operator= ou maintained_by= ou autre ? A 160 members relation collecting de trails on a same village ? Some may disagree... Why not an operator= or maintened_by= tag or else? Yves Le 19 septembre 2021 21:59:24 GMT+02:00, "Raphaël Terrettaz" <r.terrettaz@gmail.com <mailto:r.terrettaz@gmail.com>> a écrit : /English text below (Google translate)/ Bonjour, Merci pour cette proposition ! Je carthographie le réseau pédestre depuis plusieurs années et je suis convaicu de l'intérêt d'avoir ces données dans OpenStreetMap ! Dans ma région j'ai carthographié les chemins pédestres d'une autre façon encore. Comme je sais que les chemins sont entretenus par les communes, j'ai créé une relation par commune. Cette relation regroupe tous les chemins de cette commune, ceci afin de ne pas avoir trop de relations, ou des chemins qui sont dans plusieurs relations. Par exemple pour la commune d'Orsières : https://www.openstreetmap.org/relation/1067491 <https://www.openstreetmap.org/relation/1067491> Ou celle de Sembrancher : https://www.openstreetmap.org/relation/1589286 <https://www.openstreetmap.org/relation/1589286> J'espère que ce commentaire pourra vous être utile ! Meilleures salutations Raphaël Terrettaz ----------- Hello, Thank you for this proposal! I have been mapping the hiking network for several years and I am convinced of the interest of having this data in OpenStreetMap! In my region I have mapped the hiking trails in another way. As I know that the paths are maintained by the municipalities, I created a relationship per municipality. This relation regroups all the paths of this municipality, in order to have a reduced number of relations, or paths in several relations. For example for Orsières: https://www.openstreetmap.org/relation/1067491 <https://www.openstreetmap.org/relation/1067491> Or for Sembrancher: https://www.openstreetmap.org/relation/1589286 <https://www.openstreetmap.org/relation/1589286> Hope this comment can be useful to you! Best regards Raphaël Terrettaz <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Garanti sans virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#m_5791829846175558290_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> Le dim. 19 sept. 2021 à 15:02, René Buffat <buffat@gmail.com <mailto:buffat@gmail.com>> a écrit : Dear All Since after the online meeting a while ago I tried to formulate a draft based on the discussions on the mailing list / the meeting. Due to lack of time and energy, this took unfortunately a lot longer than I initially thought. The current draft can be found here https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFhUaE/edit?usp=sharing <https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFhUaE/edit?usp=sharing> Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives. If you like, please create comments directly in the document or reply to this email when you have feedback. The idea would be to collect all discussion points at the bottom of the document and mark the discussed parts of the document with comments. When writing the draft, I had the following thoughts: * It would be could to include some background information about the Swiss hiking network as this could give some context for the rest of the document and might facilitate discussions about the topic. * There are different opinions on what level of detail the hiking network should be mapped. It is thus important to clearly state a minimal goal but also allow some flexibility. * Changes to the wiki page should not contradict existing mapped relations, except there are good reasons for it (such as e.g. the issue with using name tags for relations that clash with nominatim) * Figures are sometimes better to explain things than text. * For some regions, open datasets exist that contain the hiking network but no information about guideposts. These datasets should be usable. lg rene _______________________________________________ talk-ch mailing list talk-ch@openstreetmap.ch <mailto:talk-ch@openstreetmap.ch> http://lists.openstreetmap.ch/mailman/listinfo/talk-ch <http://lists.openstreetmap.ch/mailman/listinfo/talk-ch>
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
Hi there
Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives.
Maybe swisstransfer.com? It's something that springs to my mind, but is more 1 to 1.
Hello,
I've tried to create a hiking route using the information in the document. I have 3 questions:
- Should I create 2 relationships between each signpost? One in one direction, and a second by reversing the from and the to?
- Is it possible to add to the relation the time indicated on the guidpost? It would be very useful data to show on a hiking map. But the "duration" tag should not be used for this (ref. https://wiki.openstreetmap.org/wiki/Relation:route). Did you know of another tag that might be suitable (assuming that the times will not be the same depending on the direction of the path).
- Do you Knowles if it’s possible to use data of the « www.yway.ch » website? Has anyone already contacted the administrator?
Thank you !
Raphael Terrettaz
Le dim. 19 sept. 2021 à 15:02, René Buffat buffat@gmail.com a écrit :
Dear All
Since after the online meeting a while ago I tried to formulate a draft based on the discussions on the mailing list / the meeting. Due to lack of time and energy, this took unfortunately a lot longer than I initially thought.
The current draft can be found here https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFh...
Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives.
If you like, please create comments directly in the document or reply to this email when you have feedback. The idea would be to collect all discussion points at the bottom of the document and mark the discussed parts of the document with comments.
When writing the draft, I had the following thoughts:
- It would be could to include some background information about the
Swiss hiking network as this could give some context for the rest of the document and might facilitate discussions about the topic.
- There are different opinions on what level of detail the hiking
network should be mapped. It is thus important to clearly state a minimal goal but also allow some flexibility.
- Changes to the wiki page should not contradict existing mapped
relations, except there are good reasons for it (such as e.g. the issue with using name tags for relations that clash with nominatim)
- Figures are sometimes better to explain things than text.
- For some regions, open datasets exist that contain the hiking
network but no information about guideposts. These datasets should be usable.
lg rene
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
Salut Raphael
This is indeed not clear from the draft description. I will try to update it to make it more clear. In general with most of the existing relations there is only one relation between two signposts. In rare cases there are hiking routes that are signed in only one direction. In these cases, based on Michael Spreng`s advice, I put a signed_direction=yes (e.g. [1]).
Mapping hiking times was also already previously mentioned. I'm not sure what the best way would be to map them. Typically, hiking times on guideposts are shown to a selection of "hiking destinations". The closest destination is not necessarily the next guidepost with a white label. In Ticino I saw that somebody mapped hiking times [2], but to be honest I do not yet fully understand how this works.
Personally, I'm not sure if I would map hiking times. From my experience, I prefer using apps such as the "Berner Wanderplaner" or the new swisstopo app that estimates the hiking time using the route and elevation data and allows to adjust the hiking speed according to my fitness.
I was not aware of yway.ch. I assume nobody was in contact with them before. A tool to collect guidepost photos would be quite nice. I assume I'm not the only one with a lot of guidepost photos on his phone.
lg rene
[1] https://www.openstreetmap.org/relation/1437462 [2] https://www.openstreetmap.org/node/4593590352
On Wed, 29 Sept 2021 at 13:59, Raphaël Terrettaz r.terrettaz@gmail.com wrote:
Hello,
I've tried to create a hiking route using the information in the document. I have 3 questions:
- Should I create 2 relationships between each signpost? One in one
direction, and a second by reversing the from and the to?
- Is it possible to add to the relation the time indicated on the
guidpost? It would be very useful data to show on a hiking map. But the "duration" tag should not be used for this (ref. https://wiki.openstreetmap.org/wiki/Relation:route). Did you know of another tag that might be suitable (assuming that the times will not be the same depending on the direction of the path).
- Do you Knowles if it’s possible to use data of the « www.yway.ch »
website? Has anyone already contacted the administrator?
Thank you !
Raphael Terrettaz
Le dim. 19 sept. 2021 à 15:02, René Buffat buffat@gmail.com a écrit :
Dear All
Since after the online meeting a while ago I tried to formulate a draft based on the discussions on the mailing list / the meeting. Due to lack of time and energy, this took unfortunately a lot longer than I initially thought.
The current draft can be found here https://docs.google.com/document/d/1RIn4vOpPggEzJOv9AMl1egxzeMLpkgxF0q8nWuFh...
Unfortunately, I can't send the PDF version (for people that do not want to access a google server) to the mailing list, as it is too big. But I'm open to suggestions for alternatives.
If you like, please create comments directly in the document or reply to this email when you have feedback. The idea would be to collect all discussion points at the bottom of the document and mark the discussed parts of the document with comments.
When writing the draft, I had the following thoughts:
- It would be could to include some background information about the
Swiss hiking network as this could give some context for the rest of the document and might facilitate discussions about the topic.
- There are different opinions on what level of detail the hiking
network should be mapped. It is thus important to clearly state a minimal goal but also allow some flexibility.
- Changes to the wiki page should not contradict existing mapped
relations, except there are good reasons for it (such as e.g. the issue with using name tags for relations that clash with nominatim)
- Figures are sometimes better to explain things than text.
- For some regions, open datasets exist that contain the hiking
network but no information about guideposts. These datasets should be usable.
lg rene
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
On Wed, Sep 29, 2021 at 09:01:13PM +0200, René Buffat wrote:
Salut Raphael
This is indeed not clear from the draft description. I will try to update it to make it more clear. In general with most of the existing relations there is only one relation between two signposts. In rare cases there are hiking routes that are signed in only one direction. In these cases, based on Michael Spreng`s advice, I put a signed_direction=yes (e.g. [1]).
Mapping hiking times was also already previously mentioned. I'm not sure what the best way would be to map them. Typically, hiking times on guideposts are shown to a selection of "hiking destinations". The closest destination is not necessarily the next guidepost with a white label. In Ticino I saw that somebody mapped hiking times [2], but to be honest I do not yet fully understand how this works.
For hiking times you should use the destination_sign relation https://wiki.openstreetmap.org/wiki/Relation:destination_sign
or, much more simple, the direction_* tags https://wiki.openstreetmap.org/wiki/Key:direction_north
The documentation for the direction tags is somewhat lacking but basically you add the destination + time separated with semicolon. Best to look at an example here: https://osm.mueschelsoft.de/destinationsign/example/index.htm#node=379405862...
The same information is also shown on waymarkedtrails, when you click on a guidepost with direction information: https://hiking.waymarkedtrails.org/#guidepost?id=3794058627 You just can't see if direction information is available until you open the guidepost information.
Sarah
Thank you for all the advice and information you gave to me! I started to map my region with a more "standard" method. I'm using "destination_sign" type relationships to represent guidepost information.
Example of guidepost (new):
https://hiking.waymarkedtrails.org/#guidepost?id=290083923
I also add a picture of each of these guideposts in Wikimedia Commons :-)
Example relationship (new):
https://hiking.waymarkedtrails.org/#route?id=13291245
Happy mapping !
Raphaël Terrettaz
Le mer. 29 sept. 2021 à 21:37, Sarah Hoffmann lonvia@denofr.de a écrit :
On Wed, Sep 29, 2021 at 09:01:13PM +0200, René Buffat wrote:
Salut Raphael
This is indeed not clear from the draft description. I will try to update it to make it more clear. In general with most of the existing relations there is only one relation between two signposts. In rare cases there are hiking routes that are signed in only one direction. In these cases,
based
on Michael Spreng`s advice, I put a signed_direction=yes (e.g. [1]).
Mapping hiking times was also already previously mentioned. I'm not sure what the best way would be to map them. Typically, hiking times on guideposts are shown to a selection of "hiking destinations". The closest destination is not necessarily the next guidepost with a white label. In Ticino I saw that somebody mapped hiking times [2], but to be honest I do not yet fully understand how this works.
For hiking times you should use the destination_sign relation https://wiki.openstreetmap.org/wiki/Relation:destination_sign
or, much more simple, the direction_* tags https://wiki.openstreetmap.org/wiki/Key:direction_north
The documentation for the direction tags is somewhat lacking but basically you add the destination + time separated with semicolon. Best to look at an example here:
https://osm.mueschelsoft.de/destinationsign/example/index.htm#node=379405862...
The same information is also shown on waymarkedtrails, when you click on a guidepost with direction information: https://hiking.waymarkedtrails.org/#guidepost?id=3794058627 You just can't see if direction information is available until you open the guidepost information.
Sarah
talk-ch mailing list talk-ch@openstreetmap.ch http://lists.openstreetmap.ch/mailman/listinfo/talk-ch
Am Mittwoch, 29. September 2021 21:01 schrieb René Buffat
A tool to collect guidepost photos would be quite nice.
I assume I'm not the only one with a lot of guidepost photos on his phone.
I use KartaView for the photos. I always take 2 photos: one from a distance for localisation in the terrain and one close up to be able to read the text:
https://kartaview.org/details/3843913/0
https://kartaview.org/details/3843913/1
The guidepost gets a image tag with the link and direction_* tags. Waymarked trails show direction arrows, destinations and the link to the image:
https://hiking.waymarkedtrails.org/#guidepost?id=9123101038
LG Robert
Hi zusammen Simple Frage: Warum ist natural=valley so unpopulär? Auf Topokarten empfinde ich die Talnamen als ziemlich essentiell zur schnellen Orientierung. Ist es, weil sie quer über alles drüberlaufen? Sollte man in Editoren mit layers ausbelnden können etc. Sie bräuchten wohl auch sowas wie eine "Grössenordnung", damit nicht das kleinste Couloir mit demselben riesigen Font auf die Karte käme wie das Wallis...
Cheers, Philippe
Hi
On 29.09.21 13:59, Raphaël Terrettaz wrote:
- Is it possible to add to the relation the time indicated on the
guidpost? It would be very useful data to show on a hiking map. But the "duration" tag should not be used for this (ref. https://wiki.openstreetmap.org/wiki/Relation:route https://wiki.openstreetmap.org/wiki/Relation:route). Did you know of another tag that might be suitable (assuming that the times will not be the same depending on the direction of the path).
Another possibility is with https://wiki.openstreetmap.org/wiki/Relation:destination_sign
Michael