mxx1's avatar

Itinerary to ICS prompt

Use ChatGPT Work Mode to convert the attached travel itinerary into a downloadable “.ics” calendar file. Work sequentially through extraction, time-zone verification, file creation and validation. Complete each stage before starting the next.

  1. Extract every flight and other dated travel booking. Record the published dates, local departure and arrival times, locations, flight numbers, terminals, airline references and other supplied details. Count the bookings.
  2. Identify the correct IANA time zone for each departure and arrival location. Apply daylight-saving rules for the actual travel date. Treat each published time as local to its location, convert it to a UTC instant and calculate the elapsed duration. Compare that duration with any stated in the itinerary. Investigate discrepancies and report ambiguities rather than guessing.
  3. Create one separate, time-zone-aware calendar event for each booking. For flights, use the departure location’s time zone for “DTSTART” and the arrival location’s time zone for “DTEND”. Do not use floating times or fix events to my home time zone. A Melbourne departure at 10:00 in summer, for example, must appear at 09:00 when the calendar is viewed in Brisbane time and at 10:00 when viewed in Melbourne time.
  4. Format each flight title in this order: “[LOCAL DEPARTURE TIME] [DEPARTURE AIRPORT] [TERMINAL] → [LOCAL ARRIVAL TIME] [ARRIVAL AIRPORT] [TERMINAL] | [FLIGHT NUMBER] | [AIRLINE REFERENCE]” Example: “10:00 MEL T1 → 11:25 SYD T3 | QF427 | ABC123” These headline times must remain the published local times regardless of the calendar’s viewing time zone. Include dates in the title when needed to distinguish departure and arrival days. Omit details the itinerary does not supply.
  5. Put the departure airport and terminal in “LOCATION”. Put supplied booking details in “DESCRIPTION”, including the full local departure and arrival dates and times, airline, reference, seat, class, baggage, terminals, meal request, aircraft, duration and stops. Use clear titles and descriptions for non-flight bookings.
  6. Generate an actual downloadable “.ics” file using valid RFC 5545 formatting, appropriate IANA “TZID” references, stable unique “UID” values and correctly escaped text.
  7. Parse and validate the completed file. Confirm that the number of events equals the number of source bookings, every booking appears exactly once, all published details match, UTC-to-local conversion reproduces the published dates and times and calculated flight durations agree with stated durations where provided. Check for missing, duplicate or merged events.

If a material ambiguity or inconsistency remains unresolved, identify the affected booking and explain the problem. Do not claim validation passed. Otherwise, provide a direct download link and state: “Source bookings: X. Calendar events created: X. Validation passed.”