Editorial policy and accuracy principles
Presenting a number as more certain than it is does more harm than not showing it at all.
Sourcing principle
Every variable fact — piste count, lift length, elevation, season dates — is tied to a source and shown with the date it was verified. Variable information without a source is not published.
We do not fill an unverifiable field with a guess. For example, the distance from each gate to the city centre is not published gate by gate in the official source, so that field is left empty on this site. Writing an approximate number would be selling the reader false precision.
Model estimate versus measurement
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.
Maintaining that distinction is this site's most fundamental editorial rule. Where certainty is required, we send the reader to the official source.
Update cadence
Snow and weather data refresh automatically every half hour, and the data time is shown on the page.
Resort data — piste counts, line lengths, elevations — is updated by hand as the official source changes, and the verification date is refreshed with it. We do not publish perishable information such as prices or dates without a verification date.
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 an error is found
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@erciyescanli.com. We especially want to hear about numerical errors; the value of this site rests on its numbers being right.
Use of AI
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.