V3 · Sonnet

A region for rainy days · a sample day under cover (a model, not a trip)

How much rain will you put up with today?

20 min

Without JavaScript, the limit slider, visit swaps and day settings do not work. Below is a static example for a 20 min limit.

Move the slider (or use the arrow keys, Home, End) and see on which transfer the limit breaks. In the model, every transfer includes a few minutes outdoors.

The day works out

Start 10:00 · return 13:34 · 214 of 300 min (86 min spare) · 16 of 20 min in the rain

Start10:00
Return to start13:34
  • stay indoors (letter = point)
  • outdoors, within the limit
  • outdoors, over the limit
  • in transit, no rain (assumption)
  • break indoors
  • waiting for opening

Solid line at the end: the end of the time budget (15:00). The width of each segment is proportional to minutes; the order of blue and grey within a single transfer is conventional.

This is a schematic of the model with places A–F invented for the page, not a map and not a timetable. The same stages are described in the list below.

The model’s checks found no clashes: opening windows, time budget, rain limit and midnight are all fine. This does not confirm tickets or real opening hours.

Day schedule

Times follow from the minutes: every transfer, visit and break moves the clock. After midnight every stage is marked “+1 day”.

  1. 10:00until 10:18

    Start → Technology factory

    18 min · public transport · 7 min in the rain (7 of 20 min in total)

  2. 10:18until 11:33

    Technology factory

    75 min · model point A · technology · open 10:00–18:00 · 387 min until closing

    Booking required (the model does not check tickets)

  3. 11:33until 12:18

    Indoor break

    45 min · 0 min in the rain (model assumption)

  4. 12:18until 12:36

    Technology factory → Reading room and palm house

    18 min · public transport · 5 min in the rain (12 of 20 min in total)

  5. 12:36until 13:16

    Reading room and palm house

    40 min · model point D · quiet culture · open 09:00–20:00 · 404 min until closing

  6. 13:16until 13:34

    Reading room and palm house → Start

    18 min · public transport · 4 min in the rain (16 of 20 min in total)

“Show alternatives” next to a visit opens the comparison below.

Swapping one visit

Each row below is the whole day recalculated with one alternative, on the same minute scale as the “Now” row. The vertical line is the end of the budget. So you can see at once which later point stops fitting, how much spare time is lost and what the nearest clash is, before you change anything.

Instead of: Technology factory (visit 1 of 2)

Without JavaScript this section does not calculate alternatives. An example from the model: swapping the Technology factory for the Craft manufactory (opens 11:30) moves the end of the day from 13:34 to 14:41 and adds 72 min of waiting before entry, so the day does not work out.

No changes. Choose a visit in the schedule, then an alternative.

    Day assumptions

    Day settings (variant, departure, budget, mode of travel, break, custom point) work only with JavaScript. The example above has a 10:00 departure, a 300 min budget, public transport, a 45 min lunch and a 20 min rain limit.

    These settings change the clock, the length of transfers and the budget. You set the rain limit with the slider at the top of the page and read the result of the changes there, under the slider.

    Ready-made day variant

    Try 22:30 to see a plan run past midnight.

    From departure to return. Range 60–720 min. The result updates when the value is valid; an invalid one is rejected by the model when you leave the field (Tab).

    Model values, not measurements. The walk to the entrance of the particular point is added to the time outdoors.

    Inserted after the first visit (a day with 1–2 visits) or after the second (3–4 visits).

    Advanced mode: your own point for the pool of alternatives

    The point goes into the pool, not straight into the plan. Then choose a visit and compare. The data stay in this browser tab and are not saved.

    Model limits and sources

    What this model calculates

    • Everything is in minutes: the clock starts at the departure time, and the end is the return to the starting point.
    • A transfer lasts as long as the chosen mode of travel implies; if the walk to the entrance is longer, the transfer is extended.
    • Time outdoors is a model value per transfer plus the walk to the entrance of the point. Waiting for opening counts towards the length of the day but not towards rain: this is an assumption, not a measurement.
    • A visit is checked against opening hours on the day on which you arrive. Arrival after midnight falls on the next day and is marked “+1 day”.
    • “Booking required” is only a marker. The model does not know whether tickets are available or whether free slots fit the clock.

    What is not here

    • Real opening hours, prices, journeys, delays or a weather forecast.
    • A map: distances between points are not known, there are only the model’s transfer minutes.
    • Data saving, accounts or external services. The page works without a network.

    Model points A–F

    Invented for this page. They do not refer to real places.

    • A · Technology factory · technology · 75 min · 10:00–18:00 · outdoor walk to entrance 3 min · booking (marker)
    • B · Film underground · film and set design · 60 min · 10:00–17:30 · 4 min · booking
    • C · Illusion pavilion · illusion and experiment · 45 min · 11:00–19:00 · 2 min
    • D · Reading room and palm house · quiet culture · 40 min · 09:00–20:00 · 1 min
    • E · Craft manufactory · workshops · 70 min · 11:30–18:00 · 3 min · booking
    • F · Planetarium · science · 50 min · 10:30–18:30 · 2 min · booking

    Source fact versus assumption

    From earlier versions: an article by the Polish Tourist Organisation sets side by side three different indoor experiences: Fabryka Robotów in Łącznik, MovieGate in Wrocław and Be Happy! in Szczecin (technology, film, illusion). They are not points of a single route. This description was carried over from V2 and was not re-checked while building V3; it needs verifying at the source.

    Model assumption: the source does not give a coherent regional cluster, so the plan works on six schematic points.

    What changed compared with V2

    • The four-counter dashboard was removed: the same numbers are now on the tape and in the rows.
    • The “Swap point…” drop-down list at each row gave way to a comparison of all alternatives at once.
    • alert() dialogs were replaced with in-text messages, and emoji in markers with words.
    • Saving to localStorage was removed, because the sample day and reset are enough.
    • V2 described arriving before opening but did not move the clock. V3 adds the waiting to the length of the day.
    • The custom point is in advanced mode and goes into the pool, not straight into the route.

    Sources and links