Editorial policy and accuracy principles

Every variable fact — slope length, lift count, elevation range — is tied to a source and shown with its verification date. Beyond that, all four metrics come from the SAME source: a comparison table with mixed sources is a wrong table.

We do not fill an unverifiable field with a guess. The source publishes no lift count for five catalogue entries; those cells show a dash. Estimating from comparable resorts would be an invention the reader could not detect, while a dash is honest — 'unknown' is not 'zero'.

Derived values are labelled as derived. Vertical drop is not a field in the source; it is computed as top minus base. Likewise 'slope length per lift' is not a quality measure but a ratio derived from two fields, and the page says so.

Where several sources give different numbers for the same value, we do not pick one and hide the rest. We publish both, with their sources and our note on why each source says what it does.

Then we state plainly which value this site uses. Our criterion: prefer the value that comes with a breakdown, can be recomputed, and is internally consistent. We use 21.2 km for total slope length because the difficulty breakdown (7.6 + 9.5 + 4.1) adds up to exactly that.

A disputed number is never written into structured data. Declaring a value to a search engine as settled would contradict the page saying it is disputed.

Snow depth is produced in two different ways: direct measurement on the piste, or the output of a weather model. The values on this site are the second, and they are labelled "model estimate" wherever they appear.

At low-elevation resorts the distinction matters more: the pack works close to the freezing line and snowmaking is the backbone of the season. That second factor, invisible to the model, can separate the piste sharply from the estimate.

Maintaining that distinction is one of this site's most fundamental rules. Where certainty is required, we send the reader to the resort's own announcements.

Snow and weather data refresh automatically every half hour, and the data time is shown on the page.

The cable car timetable and the resort figures are updated by hand as their sources change, and the verification date is refreshed with them. Our automated check warns when a verification is more than 180 days old, so information cannot go stale quietly.

At the start of each season all resort data is re-verified from scratch. That prevents something which changed mid-season from carrying over into the next one.

When we learn that we have published something wrong, we do not quietly delete it. We correct it and show the update date on the page.

If you notice an error, write to info@kayakmerkez.com. We especially want to hear about numerical errors; the value of this site rests on its numbers being right.

Articles on this site pass editorial review before publication. There is no content that is generated automatically and published without review.

The publishing schedule draws on a pre-written pool: one article goes live each day, but every text was written and reviewed before it entered the queue.