As well as what wrs said in a sibling comment, iCalendar does not have a way to specify the location of a meeting in a machine-readable way that can be turned into the timezone for that location.

Sadly, iCalendar is very much tied to using timezones for locations. I expect that if/when Europe finally gets round to abolishing DST, there will be some significant changes to the timezone boundaries, and as a consequence, much hilarious calendaring failure. Dunno if it will affect as many people as the 2007 DST changes in North America, which caused a lot of extra work for people running Microsoft Exchange, because it was designed assuming that timezones never change. And this design error carries over to iCalendar, tho (apart from tz boundary changes) it is better than it was.

Yup. Similarly with the time zone aware Rust crate “chrono” you also have datetime representations for local time called “naive” datetime to store date time without time zone.

And likewise in PostgreSQL you can store timestamp without time zone.

Combine that representation with lat/long gps coordinates and you have what you need for scheduling future events at specific locations regardless of changes in time zone names and offsets.

Not quite — that requires you to find the time zone locality out of band somehow. The request is to have a standard way to store the time zone (not the current offset of the time zone) in the same string as the date/time.

The ical format allows dates like DTSTART;TZID=Europe/London:20230901T201000

Whether your calendar software will let you choose how it expresses the timezone and whether the recipient's calendar software will store it that way is another question...

Google Calendar does, at least. It even supports representing events that being and end in different timezones (like a plane flight or a cross country trip)