Problem with GEO property when importing into Google Calendar

[sgehrig]

It seems as if the Google Calendar does not support the GEO property that was added with commit 7a3751f (this is also addressed in pull request #66). Importing an event with a GEO property fails in Google Calendar.

There should be an option to disable the GEO property because setting the geo location works perfectly for iOS and Mac using the X-APPLE-STRUCTURED-LOCATION property.

[sgehrig]

[sgehrig]

The iCal used looks like:

BEGIN:VCALENDAR
VERSION:2.0
PRODID:xxxxxx
CALSCALE:GREGORIAN
X-MICROSOFT-CALSCALE:GREGORIAN
X-PUBLISHED-TTL:P1W
BEGIN:VEVENT
UID:7fb3594c3ba12f47106f4122c650e7e99ac99e00
DTSTART:20160603T170000Z
SEQUENCE:3085364
TRANSP:TRANSPARENT
DTEND:20160603T190000Z
URL:https://example.com/event
LOCATION:Sporthalle Horkesgath\, Horkesgath 33\, 47803 Krefeld\, Deutschland
 d
X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-ADDRESS="Sporthalle Horkesgath, Hor
 kesgath 33, 47803 Krefeld, Deutschland";X-APPLE-RADIUS=49;X-TITLE=Sporthal
 le Horkesgath / Krefeld:geo:51.33701\,6.52919
GEO:51.33701\,6.52919
SUMMARY:Summary
CLASS:PUBLIC
CATEGORIES:Cat
DTSTAMP:20160601T072711Z
CREATED:20160601T072711Z
END:VEVENT
END:VCALENDAR

[sgehrig]

Just dug around a little bit and the problem is that RFC 5545 says that the The value MUST be two SEMICOLON-separated FLOAT values. while the library uses an escaped comma to separate lo latitude and longitude - it just reuses the locationGeo property that's being put into the Apple X-property.

[sgehrig]

Fixed with pull request #74 - can be closed.

[markuspoerschke]

Thanks for your contribution!

[dualitysol]

Does not work like this