Rules applicable to the Topoguide

Activités :
Catégories : info site
Type d'article : collaboratif (CC by-sa)

Waypoints

Major Summit and sub-summit

  • Summits can be associatesd/linked in order to create a hierarchy between them : major summit > sub-summit.
  • The associations of summits must be used only for the organisation of :
  • There's no constraint on the major summit's altitude : it can be lower, equal or greater to the altitude of sub-summits. The choice will depend on what is organized thanks to the major summit : big summits with numerous peaks or antecimes, or big cliffs separated into different climbing routes zones, or set of ice climbing zone...
  • The number of hierarchy levels must not exceed 3 : major summit > Sub-Summit > Sub-Sub-Summit
  • A sub-summit must be associated to only one major summit.
  • The different sub-summits of a major summit must not be associated one with the other. (Pyramid hierarchy only).

Go to the child waypoint (sub waypoint), open "Edit" (small pencil on the top right) and in the "Associations" section, add the waypoint (major waypoint).
After submission, in case of mistake, only moderators can correct and reassociate in the proper way.

In a hierarchical display, the name of the sub-summit is cut after the 1st dash surrounded by spaces in order to display only the part at the right of the dash. Thus :

  • To repeat the name of the major summit (A) into the name of the sub-summit (B) :
    • the name of the major summit must be placed first, separated from the name of the sub-summit by a dash surrounded by spaces : A - B
    • the name of the major summit must not contain a dash surrounded by spaces, but can contain a dash separating 2 words without space.
  • To NOT repeat the name of the major summit (A) into the name of the sub-summit (B) :
    • the name of the sub-summit must no contain a dash surrounded by space, but can contain a dash separating 2 words without space.

A hierarchy between summits has for consequences :

  • In the page of the major summit, will be displayed : all routes associated to the major summit, but also routes associated to the sub-summits and sub-sub-summits. The list of outings will contain all routings associated to all these routes.
  • It will be the same in the outings creation form : the list of routes displayed after having chosen the major summit will contain all routes associated to sub-summits and sub-sub-summits.
  • In the page of a sub-summit will be displayed the hierarchy with the major summit and all sub-summits, thus permitting to easily navigate from one summit to another.

Take-off and landing for paragliding

Rules to be described Meanwhile please refer to (in french) : https://forum.camptocamp.org/t/deco-et-attero-parapente-dans-le-topoguide/178405/3

Naming to be used when 2 orthographs coexist

For summits (or waypoints) for which 2 orthographs coexist, both names can be precised in the Title field, separating them by a "/" (name_1 / name_2). If one is much more used than the other, it is better to put the most used in the title, and the other as a remark in the waypoint document body.
NB : for summits with different names depending on the language, names have to be mentionned in the different languages versions. (refer for example to Matterhorn)

Routes

Contributor's convention

To contribute to camptocamp's topoguide, it is mandatory to respect the Contributor's convention.
Please note that the Rules concerning equipped climbing routes are more restrictive than for other routes.

Historical rules for routes & summits

Please refer to the article "Convention historique itinéraire & sommet"

Association of documents to routes

  • Waypoints
    • All passes crossed by a route must be associated to this route.
    • All huts on the route (or at the starting / ending points) must be associated to the route. This rule does not apply to lodges. (see hereunder).
    • When the route describes a traverse between 2 huts, please associate the route to other routes describing access to huts.
  • Routes
    • For a route consisting of an approach and difficulties (alpinism, climbing, steep skiing), when a part of the difficulties is common to another route (alternative), please associate both routes together.
    • For a route not consisting of difficulties, but with a major part (>70%) common to another route, please associate both routes together.
    • For a route not consisting of difficulties and describing a crossing of a summit or a pass, please associate the routes described as round-trips for both slopes.

Punctual georeferencing of a route

  • For the climbing routes (alpinism, ice climbing, one-pitch rock climbing), the georeferencing is placed at the starting point of the route.
  • For the non climbing routes, the point must be placed at the starting of the part not common to other routes. The aim is :
    • that routes of a summit are not displayed grouped together at 50m of the summit point.
    • that routes of a valley are not displayed grouped together at one only point of the valley.
  • For a route describing a crossing but with the descent not consisting of difficulties, the point is placed on the ascending route, in a discriminating place. When there is another route taking the same ascent, it is better to slightly separate both points.

Creation (or not) of a new route

  • When a pass is very close to a summit, and the cotations to reach the pass or the summit are similar, it is better NOT TO create a dedicated route for the pass, but to use the summit's route (mentioning the possibility of stopping at the pass as an alternate) The same rule will apply for an antecime/shoulder and a summit.
  • In the case of a multi-activities route (alpinism-snow & ski for example), it is better to have only one route for all activities when there are not so many differences from one activity to another in terms of route taken. If the route becomes too complicated and less readable, it can be divided by activity, but in this case, please think to associate all routes together.

Raids description

Most of the rules concerning raids are indicated in the help. Some rules are more precise can be indicated hereunder :

Bibliography et webography

The field "webography" enables to indicates the source of information availables on the web. The link must direct precisely to the page giving the information and not to the home page of the website.

This is particularly true for blogs. Just after the article creation of the blog, it is in the first position on the home page. A link to the home page seems to be enough. But a few weeks later the article is not any more on the home page, or after lot of scroll down. Please think to using the permalink of the article.
Moreover, the home page can be heavier and longer to load with low debit connexions. The article page is much lighter.

Regarding the links to a document (pdf, image), it is better to use as much as possible the following convention mentioning the direct link to the file (for low debit connexions) and the link to the closer context, in order to enable a navigation on the external site.

[Topo](www.link_to_the_PDF) on the site [Whatever](www.link_to_the_closer_context)

This is particularly true for Timetables of common transportation or other documents with non-persistent addresses : it is important to give the link to a persistent environment as a generic page of timetable search / route.

Outings

Organisation of outings

The title of an outing must contain the name of the summit or the route realized or aimed to be done.

Outings without information

Outings without figures, text nor image are tolerated on camptocamp. But, the completeness of the outing must be placed to "empty" in order not to be displayed on the homepae. When saving, completeness is pre-selected to an approximate value depending on the filling of both figures and text fields.
The fields "choice lists" and altitudes regarding conditions enable to give useful information without typing any text. In this case, completeness proposed is "draft". Nevertheless, a little phrase is most of the time useful to give precisions or complementary information.

Recent outings

A recent outing on a well known route is useful by the information it gives on recent conditions. Please fill in properly the conditions fields with figures and give a few additional information on the text fields, even if it seems redundant with other outings of the same day or former days. In fact, it is useful to be able to cross sources between several outings evenmore because some informations are complementary. (It's rare that an outing describes all conditions as much as it could be)

Old / passed outings

For outings registered years after their realization, it is much more difficult and less interesting to make a precize feedback on the conditions of the route. Nevertheless, it is useful to give its opinion on the route (even more for the routes with only few outings), or tell the progress of the day, what was seen (historical interest). It's also possible to improve the route's description in the topoguide, or add a few photos, ...
The philosophy is to contribute to the site by sharing useful information with other contributors.

Access

Major access and sub-access

  • It's possible to associate 2 accesses together to create a hierarchy : majors access > sub-access.
  • The association of access together must be reserved to following cases :
    • The accesses are not cleared from snow during winter : they are associated to the last access cleared from snow (which becomes the major access)
      Example : Bonnenuit
    • The accesses are close to a village with public transportation coverage
      Example : Villard-de-Lans
    • The accesses are the different stations of a ski lift
      Example : Argentière
  • There is no constraint on the major access' altitude : it can be lower, greater or equal to the altitude of sub-accesses
  • The number of levels of hierarchy must not exceed 2 : major access > sub-access
  • A sub-access must only be associated to one major access.
  • The sub-access of a same major access must not be associated between them (pyramidal hierarchy only)

Go to the child waypoint (sub waypoint), open "Edit" (small pencil on the top right) and in the "Associations" section, add the waypoint (major waypoint).
After submission, in case of mistake, only moderators can correct and reassociate in the proper way.

In a hierarchical display, the name of the sub-access is cut after the 1st dash surrounded by spaces in order to display only the part at the right of the dash. Thus :

  • To repeat the name of the major access (A) into the name of the sub-access (B) :
    • the name of the major access must be placed first, separated from the name of the sub-access by a dash surrounded by spaces : A - B
    • the name of the major access must not contain a dash surrounded by spaces, but can contain a dash separating 2 words without space.
  • To NOT repeat the name of the major access (A) into the name of the sub-access(B) :
    • the name of the sub-access must no contain a dash surrounded by space, but can contain a dash separating 2 words without space.

A hierarchy between accesses has for consequences :

  • In the page of the major access, all routes associated to the major access will be displayed, but also routes associated to the sub-accesses. The list of outings will contain all outings associated to all these routes.
  • It will be the same in the outings creation form : the list of routes displayed after having chosen the major access will contain all routes associated to sub-accesses.
  • In the page of a sub-access, the hierarchy with the major access and all sub-accesses will be displayed, thus permitting to easily navigate from one access to another.

Ski lifts

Refer to dedicated article

Huts, lodges, bivouacs

Association of documents to lodges

  • Lodges should not be associated to a route. They must only be associated to the closest access.

Association of access routes to the huts

  • either directly create a route, f.i from the hut's page
  • either use an existing route and associate the hut's page.

Climbing site

General rules

Refer to the dedicated article

Major site and sub-site

  • It's possible to associate sites together, to create a hierarchy : major site > sub-site (or sector)
  • The association of site together must be reserved to the organisation of a big climbing site.
    Example : Saint-Égrève
  • There's no constraint on the altitude of a sub-site : it can be lower, greated or equal to the one of sub-sites.
  • The number of levels of hierarchy must not exceed 3 : major site > Sub-site > sub-sub-site.
  • A sub-site must only be associated to 1 major site.
  • The sub-sites must not be associated together (pyramidal hierarchy only).

Go to the child waypoint (sub waypoint), open "Edit" (small pencil on the top right) and in the "Associations" section, add the waypoint (major waypoint).
After submission, in case of mistake, only moderators can correct and reassociate in the proper way.

Georeferencing

The major site must always be referenced.
But if sub-sites are close to the major site (<200m), it is not needed to reference the sub-sites in order not to overload the map.

In a hierarchical display, the name of the sub-site is cut after the 1st dash surrounded by spaces in order to display only the part at the right of the dash. Thus :

  • To repeat the name of the major site (A) into the name of the sub-site (B) :
    • the name of the major site must be placed first, separated from the name of the sub-site by a dash surrounded by spaces : A - B
    • the name of the major site must not contain a dash surrounded by spaces, but can contain a dash separating 2 words without space.
  • To NOT repeat the name of the major site (A) into the name of the sub-site(B) :
    • the name of the sub-site must no contain a dash surrounded by space, but can contain a dash separating 2 words without space.

A hierarchy between sites has for consequences :

  • In the page of the major sites, will be displayed : all routes associated to the major sites, but also routes associated to the sub-sites. The list of outings will contain all outings associated to all these routes.
  • It will be the same in the outings creation form : the list of routes displayed after having chosen the major sites will contain all routes associated to sub-sites.
  • In the page of a sub-sites, the hierarchy with the major sites and all sub-sites will be displayed, thus permitting to easily navigate from one site to another.

Local products

Books

Book cover

As a general manner, images used to illustrate a book (book cover) are not royalty free. Thus, an exception to licences is done in this partivular case and topoguide's moderators are made aware by mail when an image is associated to a book. Only moderators can choose to use a 'Copyright' licence for books covers. To be in conformance with the quote right, the image of the book cover must also be of a reasonnable size, for example 800x600 pixels.

Images / photos

Refused / not accepted images

An image registered on camptocamp by a member who is not the author, must be diffused under a licence compatible with the ones used on camptocamp.
Due to that, a map extract from Google Map or Geoportail (IGN) is not accepted.
But a map extract from Swisstopo will be accepted under certain conditions : less than 500000 pixels, registered as "individual image" (CC by-nc-nd) and with the mention of the data source ("Swisstopo"). More information.

Image deviated from another image on camptocamp

When a collaborative image is created from another collaborative image on camptocamp, it is necessary to associate both images together. In the association tool, copy the ID of the image (the high number of image makes the keyword search for images too long).

Commentaries on documents

Commentaries are not forums. The commentaires will be strictly mmoderated depending on the nature of the document. The moderation reserves the right to suppress (temporarily or definitely) without justification any commentary.

Individual documents

Outings

An outing is an individual document. The contributor who added the outing is the author (in term of law's of property) of this outing. Outing's comments can be seen as a discussion between friends about this outing.
One can also ask the outing's author precision about the content (weather, snow, rock quality...). Negative comments are not accepted.

Profile

Collaborative documents

Voir dans une autre langue
slovène•chinois•français
 Qualité du document : moyen
CC BY SA 3.0
Ce contenu est sous licence Creative Commons BY-SA 3.0

Commentaires