Questions and Answers
The mountain markers mean the same thing everywhere in the application:
- 🔵 Blue = default mountain (no user context)
- 🟢 Green = visited
- 🔴 Red = unvisited (only shown when the map represents a specific person)
- 🟡 Yellow = hovered or selected — always wins over the color underneath
Global rules
- When the map represents a specific person, mountains are green (visited) / red (unvisited)
- When there is no person involved, mountains are blue
- Yellow always overrides the color underneath while a mountain is hovered or selected
- Cluster circles use the same color as the individual mountain markers on that page
Per page
- Mountains / Activities / Users / Collections (list pages): all blue
- Mountain detail: all blue, the selected one yellow
- Activity detail: all blue + the mountains visited on that activity in green
- User detail: green visited / red unvisited
- Collection detail: only the collection's mountains, green visited / red unvisited
Visited mountains are always drawn on top, so a green mountain is never hidden behind a red one.
English
It can occasionally happen that an activity is not imported correctly. What you can do is:
- Go to the activity on Strava and click Edit Activity.
- Change visibility to Only me - this will cause the activity to be deleted in Fjelldatabasen.
- Change visibility back to Everyone or Followers only - this will cause the import to be triggered again in Fjelldatabasen.
When you sync an activity from Strava, it is automatically evaluated against all registered races. The evaluation uses four criteria — all of them must pass for a result to be registered.
1. Date and time (timed races only)
For races with a fixed date (e.g. an annual event), your activity must have started within 12 hours of the official race start. Permanent/unmarked courses (løyper uten fast dato) have no time restriction and are evaluated year-round.
2. Distance
Your recorded activity distance must be within ±20% of the official course distance. An activity of 8.5 km would for example match a course of 10 km, but not one of 5 km.
3. Start location
The first GPS point from your Strava activity must be within 200 meters of the official course start. If you started your watch a bit late or early, this is usually fine — but starting from a different location (e.g. a parking lot far from the start line) will cause the match to fail.
4. Route coverage
At least 70% of the official course route must be covered by your activity. The system samples a point along the course every 50 meters and checks whether you passed within 50 meters of it. This means short detours are tolerated, but cutting large sections of the course will prevent a match.
What if my result wasn't registered?
The most common reasons are:
- You forgot to start/stop Strava at the right place (start location check fails)
- Your watch recorded a significantly shorter or longer distance than the course (distance check fails)
- For timed events: your activity date doesn't match the event date
If you believe your activity should have matched, contact us and we can look into it manually.
