Open kevinpapst opened 4 years ago
I have users using the app across the country, it would be handy to be able to automatically detect timezone and update accordingly.
Can you explain your use-case? You mean after detecting the geo position, detect the timezone and use it, instead of the configured users timezone?
That's exactly correct. I'm not sure how feasible that is, I may need to make a custom android app with wrappers around the API calls or something and implement the geo position.
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Kevin Papst @.> Sent: Tuesday, May 18, 2021 3:16:57 PM To: kevinpapst/MetaFieldsBundle @.> Cc: Dave Campbell @.>; Comment @.> Subject: Re: [kevinpapst/MetaFieldsBundle] Capture GEO position (#44)
Can you explain your use-case? You mean after detecting the geo position, detect the timezone and use it, instead of the configured users timezone?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/kevinpapst/kimai-plugins/issues/42, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALKJUX4TMEMV3FWGHHM5QJLTOK4KTANCNFSM4M6ZQCUQ.
Yeah, I don't think this will become part of Kimai. Too many possible problems and also required databases (or external APIs), which cannot be included in a default installation.
Besides theoretical problems with user privacy (in case an external API would be used for detecting the timezone), which is a very big thing here in Europe.
Well… If it's just the Geo-Position it can be achieved by just adding two custom fields for lat and lon (which is possible with the current version of Kimai and MetaFields and doesn't need any modification). The whole interpretation is not part of Kimai, but can be done by external scripts. One example… Technician arrives at the customer site. Uses a whatever type of app to start a timesheet. This app then adds the geo data into this timesheet entry. After stopping this timesheet (or every night) all the geo data is processed to calculate the driving distances for billing. We do something similar but without saving geo data in Kimai. We process everything external and create a timesheet for driving time and expense entries for driving distance.
Add new field type to capture the geo position.
Two flavors:
What do we do with this data? Simple longitude and latitude data is not human friendly.