Skip to content

Better geo support #895

@gaellalire

Description

@gaellalire

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.

Feature description

ICS is providing a GEO field, however it seems there is no such field in android calendar (only https://developer.android.com/reference/android/provider/CalendarContract.EventsColumns#EVENT_LOCATION).
I did not look at what ICSx5 is doing for unknown fields, it would be great if ICSx5 can put it somewhere Fossify could fetch.
If this is not possible, putting GEO in directly in location is an alternative that Fossify already support. However Fossify demands that the GEO is the full location value, preventing a human readable location.
I propose that Fossify should be looking for a GEO anywhere in the location screen.
So we can have something like
'Gymnase Municipal 45.35350769999999, 5.6093441'

Why do you want this feature?

Having a location easy to read for a human, and without ambiguity for a program

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestIssue is about a new feature or improving existing feature/behavior.needs triageIssue is not yet ready for PR authors to take up

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions