Facebook

From ropewiki.com
Jump to navigation Jump to search

Ropewiki Conditions is an automated processes that periodically scans a number of Facebook.com groups and user pages to automatically extract condition reports from Facebook post. Facebook condition reports are aggregated with conditions extracted from other Beta sites (such as candition.com, descente-canyon.com, etc.) and conditions reported by Ropewiki users.

  • You can check latest conditions for 11424 documented locations by opening their Ropewiki page (Eaton Canyon, Sorrosal, etc.).
  • You can search canyons by name using the search box in the upper right hand corner (direct search) or by Location (geographic search) or Region (region search)
  • You can check most recent conditions reported at the Beta page, where you can also filter by region
  • you can check what conditions you have reported through Facebook with Show reports

If you want Ropewiki Conditions to generate condition reports from more Facebook posts:

  • Invite it to Facebook groups where they post trip reports
  • Invite to be friends to have all your Facebook posts monitored

NOTE: By becoming friends you give Ropewiki permission to extract text and pictures from your messages. Some of your best pictures may be chosen to become 'Main picture' for canyon articles, these pictures will be re-posted to Ropewiki crediting your facebook user as author and providing a link to your Facebook page in the Credits section. If you do not agree with that, please unfriend 'Ropewiki Conditions'.

Reporting Conditions on Facebook[edit]

To report a condition in a Facebook message you should include at the beginning of your text:

  • Name: the Ropewiki page name is preferred to avoid name conflicts, but the robot will also do its best to match with any names in the AKA list. Mentioning the region where the canyon is located (Huesca, New Zealand, etc) will help avoid mistakes. If you include the Roperwiki page url (or any Beta sites url) in the text the match will be guaranteed.
  • Date: the full date is preferred to avoid misunderstandings (2016.08.10, 08/10/2016, 10 Aug 2016) but the robot will also try to understand partial dates (Aug 10, 10.08, 08/10) and relative dates (today, yesterday, last Sunday, ayer, sabado pasado, etc.) in multiple languages.

If a canyon name and date are properly recognized your message will receive a 'Like' from Ropewiki Conditions and a conditions report will be recorded on ropewiki.com crediting your Facebook user and providing a link to the original Facebook message.

If there are a few possible matches, the robot will pick the most popular location based on ratings. If there are too many possible matches or none at all, the message will be ignored.

Messages that refer to dates in the future (future trips) and messages that refer to dates that are not recent (>30 days) will be ignored.

Writing style[edit]

The recommended style for writing a post (or album title) is:

  • "Name Date"
  • "Name Date ...text..."
  • "Name Date ...text... flowing Q ...text..." (english)
  • "Name Date ...text... caudal Q ...text..." (spanish)

Alternatively you can also write:

  • "Date Name "
  • "Date Name : ...text..."
  • "Date Name flowing Q ...text..." (english)
  • "Date Name caudal Q ...text..." (spanish)

Q is a water flow qualification, multiple languages are allowed:

  • [dry | very low | low | moderate | high | very high | extreme]
  • [dry | very weak | weak | good | strong | very strong | monstrous]
  • [seco | muy bajo | bajo | correcto | alto | muy alto | excesivo]
  • [seco | muy flojo | flojo | normal | fuerte | muy fuerte | imposible]

Using a different writing style will make it less likely to be understood by the robot. If the robot detects ambiguity, the condition report may be flagged as 'questionable' (?).

It's not recommended, but you CAN report multiple canyons in a same post, by writing a line for each canyon and including a full date on each line and optional different conditions for each. The robot will like your post if it can understand at least one of your canyon names, but you won't know if he got all of them.


Examples : condition reports extracted from Facebook posts:

Facebook post Condition report
"Salamander Canyon (CA-OC) 3/25/2017..." Conditions:Salamander_Canyon-RadekSott@Facebook-2017-03-25
"Stafford Creek 18-Mar-2017 3C4III 5mm 4*: my first canyon of the season in PNW..." Conditions:Stafford Creek-LucaChiarabini@Facebook-2017-03-18
"25/03/2017 Barranco Fenollet este caudal bajo y mucha nieve aproximacion muy..." Conditions:Fenollet_I_(East)-DavidGrotesck@Facebook-2017-03-25

More information[edit]

You can include additional information' in your Facebook post to produce a detailed condition report. You can include:

  • ACA rating system: 3C, 4B, 3A, etc.
  • French rating system: v4a4, v6a3, v3a5, etc.
  • Wetsuit thickness: 0mm, 3mm, 5mm, etc.
  • Quality (1 to 5 stars): 2*, 3*, 4*, 5*, etc.
  • Time in hours: 4h, 6.5h, 12hr, etc.
  • Number of people: 3p, 7pp, etc.

Just write these bits of information somewhere in your post and the robot will use it to create a full condition report. You can also edit your Facebook post to include this extra information AFTER it has already posted on ropewiki.com (Conditions are refreshed daily).

Examples: (ACA rating)

TEXT Condition report
3C WaterflowC1.pngModerate flow
3B/C 3mm 4* WaterflowC½.pngLow flow, Wetsuit2.pngThin wetsuit, Smiley4.pngGood
4C2 R 7mm 5* WaterflowC2.pngHigh flow, Danger3.pngSpecial challenges, Wetsuit4.pngThick wetsuit, Smiley5.pngAwesome
3B X 1mm 4* 7.5hr 3pp WaterflowB.pngVery low flow, Danger4.pngAdvanced challenges, Wetsuit1.pngRain jacket, Smiley4.pngGreat, 7.5 hours, 3 people

Examples: (French rating)

TEXT Condition report
v3a4 WaterflowC1.pngModerate flow
v3a3 3mm 4* WaterflowC½.pngLow flow, Wetsuit2.pngThin wetsuit, Smiley4.pngGood
v5a5 7mm 5* WaterflowC2.pngHigh flow, Danger3.pngSpecial challenges, Wetsuit4.pngThick wetsuit, Smiley5.pngAwesome
v6a2 1mm 4* 7.5hr 3pp WaterflowB.pngVery low flow, Danger4.pngAdvanced challenges, Wetsuit1.pngRain jacket, Smiley4.pngGreat, 7.5 hours, 3 people

Conversions[edit]

Below is the logic used to convert between ACA / French rating systems and how to use these ratings to report conditions.

TECHNICAL Not Technical Very Easy Easy Moderate Difficult Very Difficult Extremely Difficult
ACA Technical rating: 1 or 2 3 (r<30ft) 3 (r>30ft) 3 PG or 4 R X XX
French Vertical rating: v1 v2 v3 v4 v5 v6 v7
Difficulty Condition: Danger0.png Nontechnical Danger1.png Easy Danger1.png Easy Danger2.png Normal Danger3.png Special challenges Danger4.png Advanced Danger5.png Extreme
WATER FLOW Dry Calm Weak Moderate Strong Very Strong Extremely Strong
ACA Water rating: A B B/C C1
C
C2
C R
C3
C X
C4
C XX
French Aquatic rating: a1 a2 a3 a4 a5 a6 a7
Water Condition: WaterflowA.pngDry WaterflowB.png Very Low
WaterflowB.png Deep pools
WaterflowC½.png Low WaterflowC1.png Moderate WaterflowC2.png High WaterflowC3.png Very High WaterflowC4.png Extreme
Caudal (Spanish) Seco Muy bajo
Muy flojo
Hilillo de agua
Pozas de agua
Bajo
Flojo
Escaso
Normal
Adecuado
Alto
Fuerte
Muy alto
Muy fuerte
Muy peligroso
Extremo
Excesivo
Imposible
TIME <2h 2h - 4h 4h - 8h 8h - 24h >1 day >2 days
ACA Time rating: I II III IV V VI
French Commitment/Duration rating: I II III IV V VI
NO CONVERSION FOR COMMITMENT
WETSUIT 0mm 1mm - 2mm 3mm - 4mm 5mm - 6mm 7mm - 10mm Xmm
Condition report: Wetsuit0.png Nothing Wetsuit1.png Rain Jacket Wetsuit2.png Thin wetsuit Wetsuit3.png Full wetsuit Wetsuit4.png Thick wetsuit Wetsuit5.png Drysuit
QUALITY 0* 1* 2* 3* 4* 5*
Condition report: Smiley0.png Unknown Smiley1.png Poor Smiley2.png Ok Smiley3.png Good Smiley4.png Great Smiley5.png Awesome

Errors and Fixes[edit]

The robot will try to understand your post properly, but sometimes things go wrong. If you don't get a 'Like' from 'Ropewiki Conditions' within a day of your post, try this:

  • Writing style: Make sure you mentioned the Ropewiki page title and the full date at the beginning of your text or in the album title. If not, please correct it within a week of original post.
  • Unknown location: If your canyon is not in Ropewiki database, please consider adding it. Any user can make additions or changes, just signup for a free Ropewiki account.
  • Alternate name: if you used an alternate name not recognized by Ropewiki, you can change your post to use the official Ropewiki name or edit the Ropewiki page to add the name to the AKA list.
  • Typographic error: if the name of the canyon was misspelled in your Facebook post, you can edit and fix it within a week of original post date. If it's a common mistake, add it to the AKA list.

You can fix your post anytime within a week of the original posting date, if all works correctly you should get a 'Like' from 'Ropewiki Conditions' within a day of the edit.

Condition reports extracted from Facebook posts may also be edited on ropewiki.com. Ropewiki users can:

  • Confirm: acknowledge a Facebook condition report was properly matched
  • Edit: correct a condition report that was misunderstood (permanent change)
  • Delete: delete Facebook condition reports created by mistake (permanent delete)

History[edit]

Ropewiki will keep a history of the conditions that you posted and the canyons you visited, allowing you to view it as a map or a a Journal and even share them with friends and family.

GuillaumePlisson@Facebook's History

  • Facebook TripReports.png
  • GuillaumePlisson@Facebook's Jurnal of Canada trip

  • Facebook Journal.png
  • Credits[edit]

    Ropewiki Conditions developed by LucaChiarabini@Facebook