Importing your logbook

Liberate your logbook ascent data, whether you want to use it for other purposes or swap logbook providers. To that end we have put work into importing and exporting logbook capabilities on the site.

Importing to thecrag.com means:

  • Your logbook gets linked to a registered community index of routes worldwide.
  • Your logbook can use the local grade of the route you climbed.
  • Your logbook is integrated into iPhone and Andriod apps.
  • Cool stats in your profile page (eg look at Lee's profile page).
In beta test phase! Please note that the importing logbook service is in beta test phase, but is relatively stable. We have had at least two climbers import three logbooks from different sources totalling over 3000 ascents. See the section on beta test testamonials below for initial impressions. If you are interested then please contact us so we can work with you to get your import completed.

thecrag.com has been around since 1999, so we are committed to provide an enduring service. From the beginning we have had a unique approach to our logbook service in that your logbook must be linked to registered routes in our community database. This means you cannot put any old rubbish in your logbook.

You should also note that there are no restrictions on users exporting their logbook from thecrag.com. This feature is available for both CSV and Excel formats.

thecrag.com also has an API, meaning logbook data can be accessed programatically for third party applications. If you are a climbing business and you want to provide value add logbook services then please contact us.

We have got the worlds biggest community routes database with over 250k routes registered. However we are the first to admit we have not yet completed the journey of registering a comprehensive list of routes from around the world. This means you should be able to easily import a large portion of your logbook, but you may have to create routes for the ones that don't exist in our database. Don't worry even if the routes are not in our database then the imported ascent is kept in a separate record so that it can me matched later.

To be honest, importing is quiet complex. Firstly you have to work out how to get your logbook from your current provider - not every provider has such open policies. You then have to know how to create a CSV file format saved using UTF8 encoding. This needs to be uploaded to your account and you need to confirm the matches to routes in the system.

Don't let this complexity scare you off, contact us and we will do our best to help you through the process.

If you are interested in importing your logbook then please contact us first because everybody seems to have unique issues which we want to understand to improve the import process.

How to import your logbook

We would encourage you to trial the import process on our develompent system first - dev.thecrag.com - to make sure the process works as you expect. It is difficult to 'undo' an import.

Note that you can have a break from this process at any point and come back to it later - even months later if you wanted to.

If you cannot get your logbook from your current provider then review the section below on hints to exporting from other providers.

  1. Prepare your logbook on your computer in an CSV file format using UTF8 character encoding. At a bare minimum you need crag and route columns, but also country is highly recommended. We can help with this if you want.
  2. Log into thecrag.com and from the dashboard click the "Action -> Import Logbook" link.
  3. Click the 'Upload CSV File' button.
  4. Select your file and click 'Next'. If successful you will be taken to a screen displaying the first 10 lines of your logbook.
  5. You have to configure the import to tell the system how to interpret the CSV file. Assign data fields to various columns, indicate whether there is a header row or not, tell the system which grading system context you want to use for interpretting grades you import and set up the date format. If this is too much we can log into your account and do this for you. When done select 'Confirm Configuration' radio button and click 'Next'.
  6. You will be taken back to the import control panel. Here you need to decide whether you want to do one line at a time (very slow, not recommended) or do some bulk assessment (highly recommended). In fact the one-line-at-a-time mode should only be really used after you have done as much as you can with the bulk assessment.
  7. To start the bulk assessment click the 'Start Bulk Assessment' button. The sytem has to do a lot of number crunching so this will take some time (maybe an hour or more depending on the size of the input file). You should just go away and do something else. When the system has finished it's number crunching it will email you - click the link provided in the email or the 'Report Bulk Assessment' button from the control page.
  8. You should get a page with a filter near the top with import route assessments below that. The idea is that you need to confirm what the system thinks is the best match for each of your ascents you are importing. The system does a reasonable job at pre-selecting the most likely match so this is actually quite quick. Before you go on you might want to read the section on understanding assessment filters before you go on.
  9. Decide whether you want to save your ascent grades from the assigned route or you want them to be the same as the import file - set the 'Local grade' checkbox accordingly then scroll down the bottom and click the 'Refresh with filter' button to update the screen layout.
  10. Make a filter selection, click 'Refresh with filter', review system assignments, and once you are happy click the 'Confirm update' checkbox and then the 'Save and continue' button. This will iterate you through the remaining routes of the filter selection.
  11. Note that if you 'Skip assignment' for a particular ascent line then no changes are made to the database for that record and subsequent filter settings will find it again.
  12. Repeat with different filter selections if necessarily working down to the harder cases.
  13. Once you have confirmed everything you can you should be left with ascents that could not be matched to a route. See the section below on what to do about unmatched routes. Basically you wait until the index has been updated rerun the "Start Bulk Assessment" process and see what new routes have been matched.
  14. Your done for now.

Please note there are some additional tricks to import individual lines using the one-at-a-time form.

  • To access the one-at-a-time form click the 'Next Pending Line' from the import dashboard.
  • If you cannot find a match in the list of system candidates then you can do a manual search by clicking on 'none' radio button and a manual search box should appear. If you select a result from this search it will be added to the list of candidates.
  • If you know the route is in the system but the search is still not matching using the manual search then you can put the route id into the search box to be added to the list of candidates.
  • You may revert a 'skipped' or 'deferred' line back to pending status by clicking on the 'report' link in the table of the main import dashboard screen, then find the line and click on the 'revert' link.
  • You may jump to a particular pending or deferred line by clicking on the line status in the import report, as above.

System number crunching

When you start a bulk assessment, the system processes candidate matches for all unassigned import ascents. If you have already assigned a route to an ascent then this is not included in the number crunching.

When the system finishes it's number crunching it sends the user an email saying that bulk assessment is ready.

To find candidate matches the system progressively tries to match countries, crags, sectors, cliffs and routes using system search functionality. In otherwords if you are importing an ascent of 'Bart' in the United States then the system will not match other Bart routes in Australia and New Zealand.

Matching is done based on a fuzzy search logic, the same as index search. This means mispellings are usually matched. The search also takes into account alternate names, so if areas are know by different names then make sure the system knows this.

Finally the system compares grades to see if the grade of the candidate route matches the grade of the ascent. This system uses the standard grading conversion rules. If it does match then a is displayed next to the candidate route grade, otherwise a is displayed.

Understanding assessment filters

The idea of the assessment filters is to make your assessment confirmation easier and quicker.

Whenever you change your assessment filter then scroll to the bottom of the page and click 'Refresh with filter' to get an updated screen.

  • Number lines left: Reports the number of ascent log lines yet to be assigned to a route. Filtering is only ever done on these unassigned ascents.
  • Filter: You can set this to group by similar matching patterns. It much faster to assess cases if they have the same patterns. Generally speaking you would start with the first filter 'Single candidate match with grade, country and crag matching', and work your way down.
  • Number lines shown: Number of ascent log lines to report on the assessment screen. For some filters, above, you may want to set this to 100 or more so you can quickly get through lots of matches.
  • Number lines skipped: This will allow you to start anywhere in a filter list. It is automatically updated when you 'Save and continue' so that you will get the next set of records by default.
  • Tooltips: This checkbox determines whether or not the matched index path is shown directly in the table or in tooltips that popup when you hover your mouse over the candidate route. Leave this unchecked until you get to the difficult cases.
  • Show stats: This shows area/route counts from unassigned ascent lines. Useful to know the concentration of routes not in the index.
  • Order by area: This orders the list by area, which can make assessment confirmation much quicker dealing with things crag by crag.
  • Local grade: Sets the import to use the grade of the assigned route for the imported ascent. If not set then the imported ascent will use the grade from the import file with an opportunity for you to manually override this.

What to do about unmatched routes

Basically you wait until the index has been updated, then re-run "Start Bulk Assessment" which will re-do all the number crunching for unassigned ascents.

Your choices are whether you wait for somebody else to do the work, or you create the missing routes yourself. In case you did not know there are benefits for contributing to the index - see Crag Karma.

Let us know if you are choosing to update the index yourself and we will do everything we can to support your efforts.

You might be able to make some low hanging fruit corrections to the index by providing some alternate names to areas in the index, if thecrag search simply missed the route because the area is known as something different in the index.

Ultimately if you are left with unassigned rubbish in your logbook which you have no hope of ever working out what route it really was then this will just stay in your unassigned pile.

Hints to exporting from other providers

We want to use this section to share other users experience when importing.

You should not be scared about emailing your current provider and asking them what their process is for exporting your logbook.

Paper copy

One of our users had a paper copy of their logbook from an excel spreadsheet which had been lost. He scanned it in with Optical Character Recogition (OCR) technology, created an CSV which was then easliy imported.

If you don't have OCR technology at your fingertips try your local printers/office shop.

8a

Our users report that exporting from 8a is quite difficult.... until now. An independent climber has built a service to export his scorecard from 8a.nu. He has made it freely available for everybody in the google chrome webstore:

https://chrome.google.com/webstore/detail/8a-exporter/hekkfoilcpojpemdamefenfhielmbcen

Beta test testamonials

Testamonial 1: Climber who wanted logbook backup using thecrag export.

I used to write every climb I did down in a little notepad. Being able to looks back over what I've climbed my notes for the climbs helps job my shocking memory. I like to look back and reminisce over past ascents.

I spilt a drink of this little notepad one day and nearly lost everything so I decided to convert this little notepad into the digital age.

Rather than just using a spreadsheet I decided that manually inputing my whole log book to the 8a database would be better so that friends and family could look at while I'm climbing while I'm away on trips.

I used 8a for a few years but inputting new ascents was a tedious process and there was no backup facility I could use to export my logbook out of 8a (I was worried about the 8a site disappearing) I decided to seek out something new. That's when I found thecrag.

It looked like thecrag had been around for year but I quickly noticed that it was under heavy development, new features being added on a monthly basic (compared to 8a where nothing changed in te 2 years I used it)

My main objects where

  1. being able to export my logbook (which thecrag had already implemented)
  2. being more easily able to log my accents into my logbook (which thecrag already did by simply being able to click on multiple climbs in a crag and clicking Log Ascents)
  3. being able to import my 8a logbook into thecrag.

This last objective wasn't available but thecrag was willing to add this feature for me.

In the process of 2 weeks they added the feature, I helped them beta test it and iron out the bugs and now I'm happy to say I have ditched my 8a account and happily using thecrag.