Can I add a map to the .ics file?
When setting the location of an event in Calendar on Mac, it offers suggestions that, when clicked, insert the map into the event. Is it possible to embed a map in a file .ics
so that the map is displayed after import? It seems that just setting LOCATION
when creating the calendar file is not enough.
I have looked at RFC 2445 but cannot find anything to help.
My guess is that in order to embed a map in an event, the user needs to specifically select a location from the suggestions offered when typing, and that this cannot be done when importing. Is my guess correct?
source to share
short answer: NO, you cannot embed the map in the .ics file, but your calendar render can do it by parsing the .ics file
long-answer:
RFC2445
was replaced by RFC5545
RFC5545
specifies in section 8.3.4 the following datatypes, none of which allows you to have a map in the .ics file
+-----------------+---------+--------------------------+
| Value Data Type | Status | Reference |
+-----------------+---------+--------------------------+
| BINARY | Current | RFC 5545, Section 3.3.1 |
| | | |
| BOOLEAN | Current | RFC 5545, Section 3.3.2 |
| | | |
| CAL-ADDRESS | Current | RFC 5545, Section 3.3.3 |
| | | |
| DATE | Current | RFC 5545, Section 3.3.4 |
| | | |
| DATE-TIME | Current | RFC 5545, Section 3.3.5 |
| | | |
| DURATION | Current | RFC 5545, Section 3.3.6 |
| | | |
| FLOAT | Current | RFC 5545, Section 3.3.7 |
| | | |
| INTEGER | Current | RFC 5545, Section 3.3.8 |
| | | |
| PERIOD | Current | RFC 5545, Section 3.3.9 |
| | | |
| RECUR | Current | RFC 5545, Section 3.3.10 |
| | | |
| TEXT | Current | RFC 5545, Section 3.3.11 |
| | | |
| TIME | Current | RFC 5545, Section 3.3.12 |
| | | |
| URI | Current | RFC 5545, Section 3.3.13 |
| | | |
| UTC-OFFSET | Current | RFC 5545, Section 3.3.14 |
+-----------------+---------+--------------------------+
To achieve what you want to do, your calendar render needs to parse the property of the calendar LOCATION
(see 3.8.1.7 ) which is a string, or better if you have that you can parse the property GEO
(see 3.8.1.6 ) which is consists of two floats giving longitude and latitude.
source to share