Methodology and editorial policy

How StarsWithMe scores sky conditions in Taiwan

For Taiwan: The scoring formula, hard gates, source policy, refresh limits, locale review status, and the separate rules for a planning option.

Saetbyeol Studio is responsible for this methodology and the evidence shown on destination pages. Forecasts are generated automatically; people review which sources qualify, which places are included, and what is published.

Locale review statusThis language version completed its pre-release editorial review.

Sky-condition score (0–100)

Every valid hour during astronomical darkness is scored from the same weighted inputs. The displayed night value is the best valid hour for that place. The score compares the sky only; it does not approve a journey.

Cloud cover: 45%
Rain probability: 15%
Moon interference: 20%
Relative humidity: 8%
Visibility: 8%
Wind speed: 4%

Hard gates and missing data

Cloud cover at or above 90% forces the hourly score to 0.
Precipitation probability at or above 70% forces the hourly score to 0.
If any required weather or lunar input is missing, invalid, or outside its accepted range, the hour is partial and receives no score. Missing data never becomes a favourable zero.

Sky comparison is separate from trip eligibility

A place can have a high sky score and still be ineligible for a planning option. Eligibility requires fresh scored conditions, a published open-access basis, and a mapped arrival point with accepted evidence. An actual warning, closure, blocking restriction, missing required booking, missing arrival point, or expired static access evidence removes eligibility. Unverified live warnings, roads, transport, smoke, or air quality are shown as cautions, never as a safety clearance. Recheck the linked official sources immediately before departure.

Forecast, astronomy, and official trip sources

Weather inputs come from the Open-Meteo forecast grid. They are model forecasts, not live instruments at the viewing point.
Sun, astronomical twilight, moon phase, moon altitude, moonrise, and moonset are calculated with Astronomy Engine from the place coordinates, IANA timezone, and local date.
Planning eligibility uses fresh sky data plus a published access basis and a mapped arrival point backed by accepted evidence. Live authority, warning, road, transport, smoke, and air-quality checks are recorded separately when available. Destination pages preserve each institution or source title, link, checked time, and expiry.
A DarkSky designation, tourism page, or community map can provide context, but never substitutes for current access, booking, closure, warning, road, or lawful-arrival evidence.

Refresh window and automation limits

Released international data is generated every six hours and remains valid for eight hours, leaving a two-hour scheduling buffer. Preview data may be generated manually. On page load the site checks once for a newer version. This is not a live sensor feed: warnings, closures, roads, transport, smoke, and air quality can change between updates and must be rechecked before travel.

Known limitations

Forecast grids can miss local cloud, fog, terrain, smoke, and fast weather changes; coordinates do not prove conditions at every nearby turnout.
Regional aerosol products are context, not local health sensors or a ranking signal between nearby places.
Opening hours, bookings, roads, transport, wildfire restrictions, and closures can change between refreshes.
The service does not replace emergency warnings, managing-authority instructions, local judgement, or professional travel advice.

Technical references

Open-Meteo Forecast API Open-Meteo data licence Astronomy Engine