Eric Abrahamsen <e...@ericabrahamsen.net> writes: > Eric S Fraga <e.fr...@ucl.ac.uk> writes: > >> On Friday, 17 Apr 2015 at 13:43, Eric Abrahamsen wrote: >> >> [...] >> >>> Nevermind, I'm an idiot! It looks like it's supposed to be >>> "geo:<latitude>,<longitude>", which matches up nicely with Org link >>> formats. >>> >>> I'll go experiment for a bit. >> >> Keep us posted. I would love to have this functionality as well. The >> LOCATION property does make it through org -> MobileOrg -> Google >> Calendar so an easy to create geo: aware property would be quite useful. > > Preliminary experiments are positive! In fact, it was enough just to use > a string like "geo:XXXX,YYYY" as the LOCATION property. That survived > the ical export, and the caldav transfer, and when I "clicked" the > resulting location line in the Android calendar app, it offered to open > the link with OSMand, and showed me the correct coordinates. > > The nature of OSMand's response made me suspect that it might also > accept arbitrary strings to search on (ie POI names or something), but > further messing about will have to wait until tomorrow. > > Next up is finding out how to mark up the links so we can have a > human-readable link text, with the link address hidden. Perhaps it will > honor HTML, I don't know.
No, it ignores HTML. I've asked a question on StackOverflow, though, so who knows... http://stackoverflow.com/questions/29713943/formatting-text-of-ics-calendar-feed-to-make-clickable-intents-in-android
