| [19:27:34] | * JustTB has quit (Ping timeout: 252 seconds) |
| [19:34:29] | * JustTB has joined #farmos |
| [23:08:52] | * FijiDave has quit (Remote host closed the connection) |
| [23:10:07] | * FijiDave has joined #farmos |
| [23:40:08] | * JustTB has quit (Quit: Leaving.) |
| [23:45:43] | * lupine has quit (Ping timeout: 245 seconds) |
| [00:06:34] | * lupine has joined #farmos |
| [04:05:08] | * JustTB has joined #farmos |
| [04:12:05] | <ludwa6> | jgaehring: yes - v-0.4.9 brings the MapBox functionality that was missing in previous version… And i guess i will need that to geolocate Observations in the field (using Movement function), until Observations and photos are automatically geolocated -which should be coming in the next version, yes? :-) |
| [04:15:58] | * JustTB has quit (Quit: Leaving.) |
| [04:54:06] | * JustTB has joined #farmos |
| [09:55:13] | <ludwa6> | Hello, room: if there is anyone here using mobile FieldKit app for posting Observations data to farmOS, i would like to know if it’s working for you, and if so how. I’m experiencing some issues with it, and would like to compare notes w/ another user, to know if it is just me or not. |
| [09:55:39] | <jgaehring[m]> | ludwa6: I don't think we'll be making geolocation automatic for all observations, but it should be pretty simple to manually add geolocation for any log, and with the next version the accuracy should be much improved |
| [09:56:06] | <ludwa6> | jgaehring: good to hear, thanks. |
| [09:56:37] | <ludwa6> | But i wonder: if one has location enabled on one’s iPhone or droid, and photos are geocoded by default... |
| [09:58:18] | <ludwa6> | … Wouldn’t it be nice if one could just hit the + button in FieldKit, then just shoot a photo, that is both geocoded and date/timestamped by default? Would be dead-easy from enduser perspective, but from dev perspective… whaddya think? |
| [09:58:56] | <mstenta[m]> | That would be pretty cool if Field Kit could read the EXIF data from the image and auto-fill the location based on it. |
| [09:59:14] | <ludwa6> | Yes -but can it not ready EXIF data? |
| [09:59:37] | <mstenta[m]> | I wonder if that's possible with JavaScript - I think that's basically what would be required though (of course, there are still then the considerations about what the best UX around that feature would be) |
| [10:00:17] | <mstenta[m]> | https://stackoverflow.com/questions/5784459/javascript-can-i-read-exif-d... |
| [10:00:33] | <mstenta[m]> | > Yes -but can it not ready EXIF data? |
| [10:00:33] | <mstenta[m]> | The real question is: can JavaScript read EXIF? |
| [10:00:44] | <ludwa6> | For me, the simpler the UI, the better; just a big + button, then another big button on the log entry form, asking if i want to add a photo -right at the top of form. |
| [10:00:53] | <mstenta[m]> | Field Kit is a bit different than other "native apps" |
| [10:01:50] | <mstenta[m]> | It isn't written using Android/iOS SDKs (software development kits) |
| [10:01:55] | <mstenta[m]> | Which have more capabilities with regard to reading filesystem etc |
| [10:02:02] | <mstenta[m]> | Field Kit is 100% JavaScript |
| [10:02:22] | <ludwa6> | Ah. maybe that is why it’s slow. I find it takes time for the form to fully load, and to scroll thru. |
| [10:02:29] | <mstenta[m]> | But based on that SO thread... it does sound like it's possible... just not in older browsers |
| [10:03:07] | <mstenta[m]> | Hmm really? I've always had a very fast/snappy experience with it |
| [10:03:37] | <mstenta[m]> | (not including the times when data is being sent/received from the server) |
| [10:04:00] | <mstenta[m]> | Do you experience different speeds in the iOS app vs https://farmOS.app? |
| [10:04:31] | <ludwa6> | Not me, not so much. Not on this iPhone 7, w/ latest iOS, out in the field. will have to check if it’s the network (test WiFi vs 3g) |
| [10:05:31] | <ludwa6> | farmos.app is… i gave that a little try out in the field, but didn’t see any advantage to it, vs using either FieldKit or my farmos.net site in browser. |
| [10:06:01] | <mstenta[m]> | but loading the log edit form should be instant... no network requests involved in that |
| [10:07:07] | <ludwa6> | just did it here at my desk, it was instant. but out in field, i have had to wait while trying to scroll down to location and photo features. |
| [10:07:39] | <ludwa6> | and the scrolling is not easy with cold and/or muddy fingers! |
| [10:08:19] | <mstenta[m]> | oh weird - yea i wonder if it's more of a touch screen issue than a code issue then |
| [10:08:37] | <ludwa6> | which reminds me of another issue i have with FieldKit: i would really prefer that the sort order of log be rev-chrono (like in farmOS) instead of forward chrono. |
| [10:09:07] | <ludwa6> | means i’m looking at ancient history by default, having to scroll as a rule to bottom of screen, before i can see the most current entries. |
| [10:14:45] | <mstenta[m]> | ah yea that's on my wishlist too :-) |
| [10:15:04] | <mstenta[m]> | i'll create an issue for it so we don't forget |
| [10:15:19] | <ludwa6> | great thanks |
| [10:18:22] | <mstenta[m]> | https://github.com/farmOS/farmOS-client/issues/246 |
| [10:21:07] | <ludwa6> | meanwhile, my FieldKit workflow for recording Observations (not editing; it is too slow, i wait until back at my desk to do that) is: click the plus button, enter a name if i can (else accept default date-timestamp name), scroll to bottom of form to hit the photo button, then geolocate using the movement tab, even tho it’s usually not an asset movement (which doesn’t tend to work anyway, because the lookup of assets doesn’t seem to |
| [10:21:08] | <ludwa6> | work). |
| [10:23:24] | <mstenta[m]> | > then geolocate using the movement tab |
| [10:23:47] | <mstenta[m]> | i'd recommend waiting for the geolocate feature on the main edit tab |
| [10:24:08] | <mstenta[m]> | the movement geodata should only be used if you are moving assets |
| [10:24:57] | <mstenta[m]> | they are two separate fields on logs... so if you use the movement tab, it won't go to the right place in farmOS |
| [10:26:02] | <ludwa6> | So you are saying: there’s no good way to geolocate now? i mean: no way to do it without screwing up one’s records? |
| [10:27:14] | <mstenta[m]> | This is the only way to do it: |
| [10:27:34] | <mstenta[m]> | ACTION uploaded an image: Screenshot from 2019-11-18 10-27-00.png (35KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/gnFxprNzTaNSPqSa... > |
| [10:27:43] | <ludwa6> | I’m not clear what is the nature of the forthcoming geolocation feature, and when to expect it… But absent geolocation feature, FieldKit is a non-starter for my field ops. |
| [10:28:01] | <mstenta[m]> | The "Add my GPS location to the log" is what is *supposed* to do it anyway... |
| [10:28:07] | <mstenta[m]> | And it does work sometimes |
| [10:28:17] | <mstenta[m]> | Ok I can explain: |
| [10:28:36] | <ludwa6> | I’ve tried using it in different sites on the farm, and it always adds the same precise point location. |
| [10:28:55] | <ludwa6> | or else i wind up watching a spinner that never stops. |
| [10:29:05] | <mstenta[m]> | We already have a button to add geolocation (pictured above)... but there were two issues we've experienced with it: |
| [10:29:32] | <mstenta[m]> | 1) sometimes it doesn't work at all |
| [10:29:33] | <mstenta[m]> | 2) other times the accuracy is bad |
| [10:29:55] | <mstenta[m]> | jgaehring: found that the code we are using for it has an optional setting to "enable high accuracy" - which was not enabled |
| [10:30:01] | <mstenta[m]> | so that's the change he made |
| [10:30:14] | <mstenta[m]> | which might help with 2... but i'm not sure if it will help with 1 |
| [10:30:29] | <mstenta[m]> | > I’ve tried using it in different sites on the farm, and it always adds the same precise point location. |
| [10:30:29] | <mstenta[m]> | Question: are you on wifi? |
| [10:30:35] | <ludwa6> | ATM, yes. |
| [10:31:01] | <mstenta[m]> | The location will be taken from the devices GPS -OR- from the IP address of your wifi connection |
| [10:31:23] | <mstenta[m]> | It could be that it's using the IP addess point... which would not change as you walk around |
| [10:31:48] | <ludwa6> | ohh! i wonder if it was remembering my IP; that could explain it. |
| [10:32:09] | <mstenta[m]> | I'm not familiar with all the code involved in geolocation in Field Kit... but i have a pretty good understanding of the basic capabilities of GPS/Wifi Geolocation in Javascript... so i'm just speaking from that knowledge |
| [10:33:07] | <mstenta[m]> | to test... you could try disabling the wifi on your phone, which would force it to use your GPS |
| [10:33:28] | <ludwa6> | ok, i will try that next time i go outside. |
| [10:33:31] | <mstenta[m]> | i think |
| [10:33:37] | <mstenta[m]> | that might tell you if that's the problem or not |
| [10:34:17] | <mstenta[m]> | also: i DON'T know if Field Kit specifically is set up to listen for changes in location while you're walking around or not... |
| [10:34:20] | <mstenta[m]> | I know the map can do that (separate code) |
| [10:34:42] | <mstenta[m]> | so it might lock in the location that it receives first, and then doesn't update |
| [10:35:06] | <ludwa6> | that’s what it seems like it’s doing to me. |
| [10:35:28] | <mstenta[m]> | we should create an issue for that |
| [10:36:26] | <ludwa6> | not sure i understand the issue well enough to write it up correctly -but i could try if you want :-) |
| [10:37:13] | <mstenta[m]> | https://github.com/farmOS/farmOS-client/issues/247 |
| [10:37:47] | <ludwa6> | perfect |
| [10:37:53] | <ludwa6> | One other thing i need to solve is: how can i enable easy “viewer” access in FarmOS for unregistered users? |
| [10:38:36] | <jgaehring[m]> | > which might help with 2... but i'm not sure if it will help with 1 |
| [10:38:36] | <jgaehring[m]> | for #1 (sometimes it doesn't work at all) I've added a timeout, so it should just fail gracefully, rather than keep spinning ad infinitum, so that you can try again |
| [10:38:37] | <mstenta[m]> | there isn't a way to open a farmOS instance up to the general public (yet) - but you can create a single user login with the "Farm Viewer" role if you want |
| [10:38:46] | <mstenta[m]> | eg: "Guest" |
| [10:39:02] | <mstenta[m]> | jgaehring: oh excellent! i remember you mentioning that now |
| [10:39:06] | <ludwa6> | right -got that- but then: how can i modify the default welcome screen to hold the codes? |
| [10:39:26] | <ludwa6> | in my vdl.farmos.net instance |
| [10:39:49] | <jgaehring[m]> | > It could be that it's using the IP addess point... which would not change as you walk around |
| [10:39:49] | <jgaehring[m]> | that's very possible... I'll have to look into it |
| [10:40:04] | <mstenta[m]> | ludwa6: no way to do that unfortunarely |
| [10:40:13] | <mstenta[m]> | not on farmier hosting anyway |
| [10:40:37] | <mstenta[m]> | if you have another website for the farm, you could post a link there, with the login credentials |
| [10:40:40] | <ludwa6> | so: i have to send guest access codes via side-channel. hm, this is awkward. |
| [10:42:20] | <ludwa6> | if i could point user to a page on our website, configured to look just like the default farmier login, only with the codes… I guess that’s what i must do. |
| [10:42:35] | <mstenta[m]> | yea sorry - unless you want to self-host and create a custom module that alters the login page |
| [10:43:21] | <ludwa6> | ACTION very happy w/ Farmier hosting :-) |
| [10:43:44] | <mstenta[m]> | i'm glad! :-) |
| [10:48:48] | <ludwa6> | mstenta: there’s another thing i must ask about, in order to. get this thing into production on our farm -that is the data import feature. |
| [10:49:46] | <ludwa6> | I see that most log types have an import affordance, described thusly: Import CSV files with one or more of these columns: Done, Date, Log name, Asset IDs, Asset names, Areas, Notes, Categories, Quantity measure, Quantity value, Quantity unit, Quantity label, Lot number. |
| [10:50:52] | <ludwa6> | So are these columens ALL optional? in other words, could be all optional, so long as each line of the CSV contains one of those items populated? |
| [10:51:58] | <ludwa6> | sorry: those fields are from the Log:Harvest import form. |
| [10:54:13] | <mstenta[m]> | The date field is required for logs |
| [10:54:20] | <mstenta[m]> | but yes everything else is optional (if i remember correctly) |
| [10:54:35] | <mstenta[m]> | seedings and transplantings also require a planting asset |
| [10:54:41] | <mstenta[m]> | https://farmos.org/guide/import/ |
| [10:55:31] | <mstenta[m]> | (we need to better document "required" fields... some specific log types have some extra required fields that others don't... but for the most part the general types (activities, harvests, inputs, observations) only require a date) |
| [10:56:07] | <ludwa6> | good -thanks |
| [14:25:47] | * FijiDave_ has joined #farmos |
| [14:25:56] | * FijiDave has quit (Ping timeout: 276 seconds) |