DeepResearch Route Planner for / Routenplaner für Festival of Lights in Berlin
- eliaskouloures
- Oct 13
- 3 min read
# DeepResearch Prompt for „Festival of Lights“
## ROLE
You are an expert Berlin Festival of Lights 2025 route planner. Research live sources and produce 3–5 distinct routes for Tue, 14 Oct 2025 that fit the constraints below.
## OBJECTIVE
Create the best “City of Lights” tour for two people that:
Starts *18:30–19:00 CET** at Boxhagener Str. 74, 10245 Berlin.
Includes *“Piano Lake”** (exact location/coordinates required).
*Ends by 22:00 CET**, ideally near Luisenstr. 48, 10117 Berlin.
We are *mobile** and can cover longer stretches (walking + own bike/e-scooter). Do not analyze rental rules, costs, or availability.
Deliver a *mix of options**—each with different sights/clusters (minimal overlap).
*High signal-to-noise**: concise, scannable, decision-oriented.
## RESEARCH (MANDATORY)
Use the official *Festival of Lights 2025** program/map for installation names, addresses, and time windows (verify for 14 Oct 2025).
Confirm *sunset time** and weather/rain risk for Berlin on 14 Oct 2025.
* Estimate travel times (walk + fast transfers for long stretches).
Provide *citations/links** for non-obvious facts and each installation’s location.
## ROUTE DIVERSITY RULES
Produce *3–5 routes**, each with a distinct theme/area mix and ≤30% stop overlap across routes.
Example themes you may use:
1. Mitte Icons Blitz (Unter den Linden → Museum Island → B'gate/Potsdamer Platz)
2. East-to-Center Arc (Friedrichshain → Oberbaumbrücke → Alexanderplatz → Mitte)
3. City-West Classics (Tiergarten → Kulturforum → Ku'damm/Gedächtniskirche)
4. Spree Riverside Scenic (Spree embankments/bridges focus)
5. Photo-First, Low-Crowd Backstreets (alley cut-throughs, alternative façades)
“*Piano Lake**” appears in every route.
Optimize sequences for *maximum installations seen** within time, while ending near Luisenstr. 48 or with a clean early-exit to get there fast.
## ASSUMPTIONS
Walking pace ≈ *4.7–5.0 km/h**; fast transfers allowed for longer hops only.
Add *3–5 min buffers** at known pinch points (e.g., Brandenburg Gate, Museum Island).
If a listed installation is unconfirmed/changed on 14 Oct, *swap in the nearest verified alternative** and note it.
## OUTPUT FORMAT (STRICT)
1. Executive Summary (≤100 words) – pick a recommended route and why.
2. Route Options (3–5) – one section per route:
*Who it's for** (e.g., max-count, scenic, photo-centric).
*Start/End window** (absolute times on 14 Oct 2025).
*Totals**: installs seen (count), distance (km), time (mins), # long hops.
*Ordered stops** (concise, one line each):
* `# / Installation name / Address or GPS / ETA–ETD / segment mins & km / mode (walk or fast hop)`
*Why it works**: 3–4 bullets (coverage, density, crowd logic, end-near-home).
*Upsides / Downsides**: bullets, frank trade-offs.
*Early-exit plan**: where to cut and still end near Luisenstr. 48 quickly.
*Map links**: 1 Google/Apple Maps link per route (walking baseline), plus optional GPX/KML.
3. Comparison Table – rows = routes; cols = installs, km, est. mins, long hops (#), risk (low/med/high), weather sensitivity, end distance to Luisenstr. 48 (m).
4. Installation Index (Appendix) – table of all installations used: name, coords, effect type (projection/light sculpture), loop duration (if any), source link.
5. Citations – numbered, grouped by route and by installation.
## STYLE & CONSTRAINTS
*Concise** bullets, no filler. Metric units, CET timestamps.
*Do not** discuss scooter/bike brands, rentals, pricing, or legalities.
* If uncertain, state the assumption and provide the nearest verified backup.




