| [01:22:39] | * JustTB has quit (Quit: Leaving.) |
| [02:36:22] | * JustTB has joined #farmos |
| [10:33:26] | * ludwa6 has joined #farmos |
| [10:35:27] | * ludwa6 has left #farmos () |
| [10:35:57] | * ludwa6 has joined #farmos |
| [10:53:28] | <ludwa6> | G’day room. Am having a bit of trouble with FieldKit version 0.4.8; since installing latest upgrade, it won’t sync with my instance at Farmier. Can anyone suggest anything that might help? |
| [10:54:39] | <mstenta[m]> | ludwa6: do you know what version you were on before? was it really old? |
| [10:55:17] | <mstenta[m]> | a little while back (months now) we made a necessary change to the database that Field Kit uses, which requires you to fully uninstall and reinstall for the new version to work |
| [10:55:33] | <mstenta[m]> | you could try that |
| [10:55:52] | <mstenta[m]> | but if you have any "unsynced" logs on your device, they will be lost when you uninstall |
| [10:55:54] | <mstenta[m]> | so check that first |
| [10:56:11] | <ludwa6> | good question, mike; it’s been awhile, and i just did the upgrade without looking, so i don’t remember prevous version. |
| [10:56:18] | * sol5 has joined #farmos |
| [10:56:54] | <ludwa6> | so if i quit and reinstall, that should work? don’t care about loss of data at this point, so i will try. |
| [10:59:10] | <mstenta[m]> | yes, you'll need to completely uninstall the app and then reinstall it |
| [10:59:21] | <jgaehring[m]> | (that update got pushed out in mid-July, FYI, it was the version 0.4.2 update) |
| [11:00:06] | <ludwa6> | hey Jamie: yeah, i remember doing the upgrade back then. |
| [11:00:50] | <ludwa6> | So i just did a deinstall/ reinstall, and it did sync just the two late tasks i have on dashboard. is that how it should work? |
| [11:02:28] | <mstenta[m]> | Oh good! so it did successfully pull them from the server? |
| [11:02:50] | <ludwa6> | apparently so, yes |
| [11:02:51] | <mstenta[m]> | It will only pull logs that are assigned to you, and are marked as "not done" |
| [11:03:02] | <ludwa6> | ok, that makes sense. |
| [11:03:20] | <ludwa6> | but now i just logged an observation on mobile, tried to sync, and it doesn’t seem to want to. |
| [11:03:30] | <jgaehring[m]> | > hey Jamie: yeah, i remember doing the upgrade back then. |
| [11:03:30] | <jgaehring[m]> | huh, I hope this isn't migration issue we didn't anticipate |
| [11:03:59] | <mstenta[m]> | hmm does it give any error? what happens? |
| [11:04:06] | <jgaehring[m]> | is there any error message? or does it just keep spinning? |
| [11:04:34] | <mstenta[m]> | be sure to open up /farm/logs/observations on your farmOS and refresh to see if it appears |
| [11:04:49] | <ludwa6> | ah, i see: yes, they do in fact appear. |
| [11:05:11] | <mstenta[m]> | ah great! |
| [11:06:04] | <ludwa6> | got this little challenge, maybe Don Blair told you about. We installed his Quahog sensor this morning, and it’s now pushing readings into the sensor module. Nice! |
| [11:06:46] | <ludwa6> | But now: how to i geolocate that sensor? |
| [11:08:14] | <ludwa6> | I dont’ see a geolocatoni field in the sensor template. |
| [11:09:17] | <ludwa6> | the larger challenge is to correlate remote sensing data with observations in the field. |
| [11:10:12] | <ludwa6> | for this, we need to have sensors geolocated, and be able to reference geocoded sensors in observations logged using FieldKit |
| [11:15:34] | <ludwa6> | in the sensor’s edit form, i see a location field. i should enter co-ordinates there manually? or is there a way to log the location onsite, using FieldKit? |
| [11:16:48] | <jgaehring[m]> | oh, I think you could use Field Kit to create a movement log for each sensor |
| [11:18:55] | <skipper_is[m]> | The location field should relate to an area, you can create a point area, and use that |
| [11:20:14] | <ludwa6> | ah, a point area. will try to create one for the sensor. |
| [11:20:23] | <skipper_is[m]> | You might be able to use fieldkit, but I'd probably just create an area called 'Steve the Sensor' or whatever it is, just as a point. Can be related to the field it is in. Then set the location of the sensor to that |
| [11:21:32] | <jgaehring[m]> | you can also create a movement log in farmOS and select a location on the map |
| [11:21:46] | <ludwa6> | makes sense, skipper_is ; will try that. |
| [11:22:10] | <ludwa6> | jgaering: i see the movement log form in FieldKit, but the map is a zoomed-out view of whole farm. |
| [11:22:25] | <ludwa6> | and i can’t zoom in to place the point with precision. |
| [11:23:43] | <ludwa6> | oh, wait: i now see a zoom control… but it is *super* slow, even though i am on a fast internet connection. |
| [11:23:51] | <jgaehring[m]> | in farmOS you can do... Add Log > Assets > Add Items then select the sensor you want, then under the Movemement tab, expand the Geometry field, and it will open up a map for you, then you can create a point |
| [11:24:55] | <jgaehring[m]> | > and i can’t zoom in to place the point with precision. |
| [11:24:55] | <jgaehring[m]> | ah yes, we've got some upstream updates which should improve precision, but it might be a week or two before that update goes out (it's tied to some more complicated updates) |
| [11:25:35] | <ludwa6> | yes, i’m gonna do it in farmOS… But now i am in Movement form of FieldKit i am curious. Will this update made it a useful tool for geolocated observations in the field? |
| [11:26:26] | <jgaehring[m]> | I'm hoping so |
| [11:27:12] | <ludwa6> | That’s what will make it really useful for me, if entries in field can be coded with location of the phone. is that possible, or will it be soon? |
| [11:27:36] | <jgaehring[m]> | it was a quick and easy fix I made while I was making some other modifications to the code around the geolocation stuff, but I haven't had a chance to test it out "in the field" quite yet |
| [11:28:11] | <ludwa6> | ok, jgaehring, i look forward to news about this as it develops. |
| [11:28:11] | <jgaehring[m]> | yea, that's the goal |
| [11:29:31] | <jgaehring[m]> | we're also going to make a change in the next few weeks that should allow you to drop a point (or a vertex of a polygon) at your current location while you're mapping a movement, which should make the whole process a lot easier |
| [11:30:00] | <ludwa6> | as we discussed with Don: remote sensing is great, as is a FieldKit for “subjective” observations… But if we can put the two things together, that makes for some powerful magic. |
| [11:31:12] | <ludwa6> | i like where you are going with this, jgaehring. rock on, mate! :-) |
| [11:32:10] | <jgaehring[m]> | thanks Walt! |
| [11:33:17] | * farmBOT has joined #farmos |
| [11:33:38] | <ludwa6> | jgaehring: FYI: still no word on the open-sourcing of code related to those FlowerPower sensors we are using in GROW project -tho beta test program was to be announced Nov 1. soon as i get the link to repo, will send so you can have a look. |
| [11:33:59] | <ludwa6> | Don is enroute from Algarve to Lisbon, i believe, for his last night in country. |
| [11:34:50] | <ludwa6> | Was great to finally meet him (and wife & son) and have his help getting Quahog plugged into ground and into farmOS |
| [11:35:18] | <jgaehring[m]> | oh great, I look forward to taking a look at the repo! |
| [11:57:59] | * sol5 has joined #farmos |
| [12:28:50] | <mstenta[m]> | > ah, a point area. will try to create one for the sensor. |
| [12:28:51] | <mstenta[m]> | @ludwa6 and skipper_is |
| [12:28:59] | <mstenta[m]> | there's a better way to do this |
| [12:29:16] | <mstenta[m]> | creating an area for the sensor isn't necessary |
| [12:30:08] | <mstenta[m]> | you can define a precise coordinate for the sensor's location WITHIN an existing area (which can be the general farm property area at the very least) |
| [12:30:29] | <ludwa6> | ok mstenta: how’s that done? |
| [12:31:15] | <mstenta[m]> | to do that, you basically need to set the sensor's location to the existing area, and then edit that movement log and specify a more precise geometry in the Geometry field under the "Movement To" area reference field |
| [12:31:39] | <mstenta[m]> | then the log is basically saying: "this sensor is located in this area at this specific point" |
| [12:32:12] | <mstenta[m]> | ah! ludwa6 it says you just rejoined - did you miss all my messages? |
| [12:32:22] | <mstenta[m]> | hah |
| [12:32:50] | <ludwa6> | no, i see your msgs since 5:28: |
| [12:33:38] | <mstenta[m]> | oh good :-) |
| [12:33:43] | <ludwa6> | but i’ve already create an area, as a point… gave it parent of the correct landplot, named it quahog_1 (actually that name auto-populated, once i started to type it in). |
| [12:34:00] | <mstenta[m]> | yes! so first: open up the sensor asset in farmOS |
| [12:34:01] | <ludwa6> | but it’s got nothing to do with a “Movement To” |
| [12:34:26] | <ludwa6> | i am on the sensor object now |
| [12:35:01] | <mstenta[m]> | ah ok... so you don't need that point area |
| [12:35:07] | <mstenta[m]> | it just clutters up your areas list |
| [12:35:32] | <mstenta[m]> | in the sensor, scroll down to the bottom and click "Logs with special purpose" and look to see if you have movement logs for the sensor asset |
| [12:35:58] | <ludwa6> | hm. i have edited the area, giving it that quahog_1 location, and now sensor object shows it correctly mapped. |
| [12:36:04] | <mstenta[m]> | (these are just logs that "move" the asset to a location - that's how all locations are determined in farmOS: https://farmos.org/guide/location/) |
| [12:36:18] | <mstenta[m]> | if you have more than one, perhaps we can clean them up - you just need one |
| [12:36:33] | <mstenta[m]> | but assuming you just have one, do the following: |
| [12:37:43] | <ludwa6> | i don’t see any logs with special purpose… but i see two observations, corresponding to the first location i gave it (within a landplot) and then another where i gave it the point area i created subsequently. |
| [12:37:43] | <mstenta[m]> | that makes sense - adding an "area" specifically for the asset would work - but it's a bit "messy" in my opinion |
| [12:37:55] | <ludwa6> | yes, it was a bit clunky. |
| [12:38:17] | <mstenta[m]> | the better way is to use the "Movement Geometry" field, described at the bttom of this: https://farmos.org/guide/location/ |
| [12:38:29] | <mstenta[m]> | ok gotcha |
| [12:38:42] | <mstenta[m]> | so... delete the newer log (that references the new point area you created) |
| [12:38:53] | <mstenta[m]> | then delete the new point area (you don't need it) |
| [12:39:20] | <mstenta[m]> | then... open the first observation log (which references the landplot) |
| [12:41:12] | <ludwa6> | done |
| [12:41:16] | <ludwa6> | now? |
| [12:41:30] | <mstenta[m]> | Edit the observation log |
| [12:41:47] | <mstenta[m]> | Click on the "Assets" tab on the left, then open the "Movement" box |
| [12:42:01] | <mstenta[m]> | You should see the "Movement to" field which references the landplot |
| [12:42:08] | <ludwa6> | yes |
| [12:42:09] | <mstenta[m]> | And under that, is a Geometry box. Open that and you should see a map with the landplot's geometry. |
| [12:42:27] | <ludwa6> | yes |
| [12:42:29] | <mstenta[m]> | Click the "X" button in the bottom of the map to clear that shape, then click the Point button and drop a point where the sensor is |
| [12:42:39] | <mstenta[m]> | Then save the log and go back to view the sensor asset |
| [12:42:52] | <mstenta[m]> | It should show that it is located in the landplot at that point |
| [12:43:59] | <ludwa6> | funny: there is a point (little grey circle) there. drop another dot on top of that? |
| [12:44:10] | <ludwa6> | that is i guess the point area i defined. |
| [12:44:11] | <mstenta[m]> | ah yes, that is probably the new area you created |
| [12:44:18] | <mstenta[m]> | yup |
| [12:44:24] | <ludwa6> | do i need to get rid of that first? |
| [12:44:28] | <mstenta[m]> | the map will show all areas as grey, for reference |
| [12:44:37] | <mstenta[m]> | no, you can get rid of it after if you want |
| [12:44:45] | <mstenta[m]> | it's harmless |
| [12:44:50] | <mstenta[m]> | but you don't need it anymore |
| [12:45:20] | <ludwa6> | no… if every movement has a corresponding area, that will quickly get to be a bit much |
| [12:45:36] | <mstenta[m]> | so, the same process can now be done with Field Kit, as Jamie described... and it's a bit easier than in the farmOS UI (which is a bit clunky to go through all those steps... I know...) :-) |
| [12:45:56] | <mstenta[m]> | yea exactly |
| [12:46:21] | <mstenta[m]> | areas should just represent "permanent" places |
| [12:46:32] | <mstenta[m]> | ideally |
| [12:47:17] | <mstenta[m]> | in Field Kit, you can: create a new log, click the movement tab, select the sensor, and the landplot, then click the map and edit the shape to be just a point |
| [12:47:33] | <ludwa6> | But in FieldKit, the map is unusable as it stands. So i guess that’ll have to wait for the “promiseware” Jamie spoke of some hours ago :-) |
| [12:47:35] | <mstenta[m]> | fewer steps :-) (i'm really excited about that new feature) |
| [12:47:42] | <ludwa6> | you and me both! |
| [12:47:49] | <mstenta[m]> | ah |
| [12:48:08] | <mstenta[m]> | well... so what Jamie was talking about might be slightly different... if i understand correctly |
| [12:48:32] | <mstenta[m]> | he made a change to the GPS code, so that it would be faster and more accurate |
| [12:48:33] | <mstenta[m]> | but that's not the same thing as the map itself |
| [12:48:50] | <mstenta[m]> | you said your map was zooming slowly? is that the issue you had? |
| [12:49:22] | <ludwa6> | he spoke of two things -one of which was the map, and one of which was the ability to record an observation with current location automatically geocoded on that record. |
| [12:49:46] | <ludwa6> | yes, the map is horribly slow, even on fast internet connection. really not usable. |
| [12:51:11] | * sol5 has left #farmos () |
| [12:52:35] | <mstenta[m]> | are the background map tiles loading slowly? |
| [12:53:19] | <mstenta[m]> | i've experienced that too from time to time - those are provided by Open Street Map, and it seems that their servers sometimes get painfully slow |
| [12:54:01] | <mstenta[m]> | there is an alternative option: MapBox satellite tiles |
| [12:54:03] | <ludwa6> | yes, the basemap is zoomed-out view of whole farm… then if you try to zoom in, it goes to an even more zoomed-out view that is so fuzzy as to be indiscerible. then it never comes into focus again, even after some minutes. |
| [12:54:15] | <mstenta[m]> | do you have a few minutes to try that with me and see if it works better for you? |
| [12:54:35] | <ludwa6> | sure. right now there is just one option under base layers: openStreetMap |
| [12:55:06] | <mstenta[m]> | ok yea... it's probably the OSM tiles |
| [12:55:31] | <ludwa6> | sux |
| [12:55:36] | <mstenta[m]> | yea, i'll add MapBox... one moment... |
| [12:57:47] | <mstenta[m]> | ok can you try closing your app and reopening it? |
| [12:58:16] | <ludwa6> | done |
| [12:58:50] | <mstenta[m]> | does mapbox appear as another layer option now? |
| [12:59:05] | <ludwa6> | hm. map showed up real sharp… but then i clicked on it, and it went to fuzzy view of all europe and africa again. |
| [12:59:25] | <ludwa6> | and that icon with base layers shows just OpenStreetMap again. |
| [13:00:03] | <mstenta[m]> | ah ok... jgaehring when does FK load `/farm.json` to get the MapBox key? |
| [13:00:13] | <mstenta[m]> | oh... or is that not deployed to v0.4.8?? |
| [13:00:36] | <mstenta[m]> | ludwa6 this is a super beta feature we just added recently... ;-) |
| [13:00:54] | <ludwa6> | fine, if we can get it working |
| [13:01:26] | <mstenta[m]> | ludwa6: in the meantime, try this out... |
| [13:01:39] | <mstenta[m]> | go to https://farmos.github.io/farmOS-map |
| [13:01:48] | <mstenta[m]> | that is a demo of the farmOS mapping library, with both OSM and MapBox |
| [13:01:54] | <ludwa6> | i see |
| [13:02:04] | <mstenta[m]> | see if you notice the same delay in OSM on that... and if MapBox is any better for you |
| [13:02:53] | <ludwa6> | no, this works great on my desktop. |
| [13:03:01] | <ludwa6> | but not in FieldKit |
| [13:03:22] | <mstenta[m]> | i am experiencing noticeable slowness with OSM when i test that too, for what it's worth |
| [13:04:17] | <mstenta[m]> | oh? OSM too? |
| [13:04:47] | <mstenta[m]> | hmm... i'm not sure why that would be. and ultimately we might not have much control over it |
| [13:05:03] | <ludwa6> | OSM is the only option under BaseMaps in FieldKit… and it sux. |
| [13:05:14] | <jgaehring[m]> | > ah ok... jgaehring when does FK load `/farm.json` to get the MapBox key? |
| [13:05:15] | <jgaehring[m]> | When the My Logs screen first loads |
| [13:05:22] | <mstenta[m]> | field kit is using the same code - and making the same requests for those tiles |
| [13:05:46] | <mstenta[m]> | jgaehring: ok thanks - if Walt closed and opened the app, should that refresh it? |
| [13:06:34] | <jgaehring[m]> | As long as he's logged in yes |
| [13:06:58] | <ludwa6> | ACTION reboots FieldKit again |
| [13:07:17] | <mstenta[m]> | ludwa6: can you confirm your farmOS URL for me? (feel free to direct message me if you don't want to broadcast it here) i added the MapBox key to what I assume is your farmOS... but hopefully i made the right assumption :-) |
| [13:07:48] | <ludwa6> | vdl.farmos.net |
| [13:08:12] | <mstenta[m]> | ok that's what i thought :-) |
| [13:08:42] | <ludwa6> | ok, so still: when i try to log a movement, i get a nice sharp map displayed under asset to move/ move to boxes... |
| [13:08:54] | <mstenta[m]> | the mapbox key is in place, so it's just a matter of Field Kit finding it and adding it to the map |
| [13:09:22] | <ludwa6> | … but when i click on that good map of my farm, it zooms out to a view of half the world, with an icon at top right that reveals just one BaseMap option: OpenStreetMap |
| [13:09:47] | <ludwa6> | and trying to zoom in on that map is brutal. |
| [13:10:08] | <ludwa6> | so lo-rez, it is useless |
| [13:10:36] | <mstenta[m]> | ok so that sounds like two issues |
| [13:10:54] | <ludwa6> | when i get anywhere near S of Portugal, it is so fuzzy, you can’t even make out the coastline any more |
| [13:10:58] | <mstenta[m]> | 1) mapbox layer isn't being added |
| [13:11:27] | <mstenta[m]> | 2. the "static" map and the "editable" map are starting you in different places |
| [13:11:49] | <mstenta[m]> | jgaehring: can you point me to the place in the code that controls these two scenarios? |
| [13:11:57] | <mstenta[m]> | i may be able to see what's going on |
| [13:12:22] | <mstenta[m]> | (and by two scenarios i mean where the map zooms to) |
| [13:12:31] | <mstenta[m]> | (for the "static" and "editable" maps) |
| [13:14:06] | <jgaehring[m]> | is the mapbox layer being added for the first screen, under the Movement tab? |
| [13:15:03] | <mstenta[m]> | the first screen doesn't have a layer switcher |
| [13:15:04] | <jgaehring[m]> | what assets or areas are you referencing before you go to the second screen? |
| [13:16:37] | <jgaehring[m]> | https://github.com/farmOS/farmOS-client/blob/master/src/client/component... |
| [13:17:10] | <mstenta[m]> | is that included in v0.4.8 |
| [13:17:20] | <mstenta[m]> | really need to start tagging commits... ;-) |
| [13:17:54] | <mstenta[m]> | release commits* |
| [13:20:09] | <jgaehring[m]> | that's the master branch, so it's 0.4.8 |
| [13:21:21] | <mstenta[m]> | ok cool |
| [13:21:52] | <jgaehring[m]> | I wonder if this could be an issue with Mapbox's tiles for Portugal |
| [13:22:08] | <mstenta[m]> | hmm i wonder why it's not getting pulled in for Walt |
| [13:22:11] | <mstenta[m]> | it's in farm.json |
| [13:22:30] | <ludwa6> | the map that i’m using for everything these days is this: https://www.geoportal.org/?f:selectedAreaCoordinates=37.1394782701073,-8... |
| [13:22:35] | <mstenta[m]> | he said it works in https://farmos.github.io/farmOS-map |
| [13:23:29] | <ludwa6> | mstenta: that one is not bad, but several years out of date |
| [13:23:41] | <ludwa6> | pretty good resolution tho. |
| [13:23:49] | <mstenta[m]> | nice! |
| [13:23:54] | <mstenta[m]> | i wonder if they offer a tile server |
| [13:24:02] | <mstenta[m]> | if so, we could add it as a layer in OpenLayers maps |
| [13:24:27] | <ludwa6> | that would rock. it’s so good, i can almost see the sensor in the ground :-) |
| [13:24:37] | <jgaehring[m]> | also wondering if this could be related: https://github.com/farmOS/farmOS-client/issues/236 |
| [13:24:49] | <jgaehring[m]> | ...reading into it again now |
| [13:25:18] | <mstenta[m]> | that could be related to the second issue he's experiencing |
| [13:25:47] | <mstenta[m]> | ludwa6: when you first click the "Movement" tab, are you selecting an area that has a geometry? |
| [13:26:10] | <mstenta[m]> | (in the "Movement to" field) |
| [13:26:23] | <mstenta[m]> | it should auto-populate the map with the selected area's shape |
| [13:26:41] | <mstenta[m]> | and it will use that same shape (and auto-zoom) when you then click on the map to go into "edit mode" |
| [13:26:52] | <ludwa6> | it did show the area’s shape. but click on it, and then… back out to the view from nowhere |
| [13:27:02] | <jgaehring[m]> | > is the mapbox layer being added for the first screen, under the Movement tab? |
| [13:27:03] | <jgaehring[m]> | there's no layer switcher, but it should automatically load the Mapbox layers if the API key is present |
| [13:27:43] | <mstenta[m]> | oh ok, i forgot about that... thought it needed to be saved in the layer memory (localstorage)... but that wasn't available then |
| [13:28:57] | <mstenta[m]> | > it did show the area’s shape. but click on it, and then… back out to the view from nowhere |
| [13:28:58] | <mstenta[m]> | huh that's weird |
| [13:32:03] | <jgaehring[m]> | I'm trying to figure out the steps to reproduce... |
| [13:32:06] | <mstenta[m]> | ludwa6: can you try https://farmos.app |
| [13:32:09] | <ludwa6> | Q: should upcoming tasks that are assigned to me show up in my FieldKit? cuz i just created one on desktop, and it doesn’t show up, tho i pressed sync now and even rebooted the FieldKit |
| [13:32:12] | <mstenta[m]> | that is the same app - just in the browser instead of a native app |
| [13:32:25] | <ludwa6> | i am there. |
| [13:32:30] | <mstenta[m]> | curious if you have the same issue there |
| [13:32:52] | <jgaehring[m]> | ludwa6: do you experience these issues when you create a brand new log without adding any assets or areas to it? |
| [13:32:52] | <ludwa6> | but it says i have no logs at all to display -not even the 3 in FieldKit. let alone the one i' |
| [13:33:16] | <ludwa6> | jgaehring: dunno, will try |
| [13:34:50] | <jgaehring[m]> | > Q: should upcoming tasks that are assigned to me show up in my FieldKit? cuz i just created one on desktop, and it doesn’t show up, tho i pressed sync now and even rebooted the FieldKit |
| [13:34:50] | <jgaehring[m]> | as long as you marked it as _not_ done... but logs default to being marked as done, so you would have needed to uncheck that manually |
| [13:35:26] | <jgaehring[m]> | it's possible if we have a log with corrupted data, like in the movement field, that could be messing up the syncing process |
| [13:36:43] | <ludwa6> | i dunno, but it’s a mess, with things on both sides of desktop / mobile fence that don’t match, and the browser version of FieldKit shows nothing. |
| [13:37:32] | <ludwa6> | maybe i should uninstall and reinstall again -dya think? |
| [13:37:44] | <ludwa6> | what’s in FieldKit right now doesn’t matter |
| [13:40:05] | <ludwa6> | the browser version of FieldKit does in fact show two overdue tasks, when i click the “upload” arrow at top RH corner of screen |
| [13:40:13] | <ludwa6> | but it doesn' |
| [13:40:32] | <ludwa6> | doesn’t show the task i assigned myself, to be done on next Friday |
| [13:41:09] | <mstenta[m]> | did you log in on farmos.app? |
| [13:41:10] | <mstenta[m]> | with the same username? |
| [13:41:19] | <ludwa6> | mstenta: yes |
| [13:41:32] | <mstenta[m]> | ah ok |
| [13:41:34] | <mstenta[m]> | (sorry riot is moving slow) |
| [13:42:21] | <mstenta[m]> | ludwa6: can you post a screenshot of farmOS vs Field Kit? |
| [13:43:13] | <mstenta[m]> | also: i wonder if you have any filters applied in field kit (the little funnel button in the top right) - those will show/hide certain logs in field kit (doesn't affect what gets pulled from farmOS - just affects what's visible in FK) |
| [13:43:56] | <ludwa6> | ACTION tries to remember how to upload file in IRC |
| [13:44:41] | <mstenta[m]> | ah yea... maybe use imgur.com - free upload |
| [13:44:42] | <mstenta[m]> | then you can just paste a link |
| [13:47:43] | <ludwa6> | https://imgur.com/a/MBnu4t8 |
| [13:48:59] | <mstenta[m]> | Ahhhhhh |
| [13:49:04] | <mstenta[m]> | Field Kit doesn't support soil tests :-( |
| [13:49:48] | <mstenta[m]> | although it may support all log types soon! |
| [13:49:58] | <ludwa6> | so: lemme try something else. an observation, perhaps. |
| [13:50:34] | <mstenta[m]> | When we started it was just for observations, then we added activities, seedings, inputs, harvests - but it's a hard-coded list still |
| [13:50:41] | <mstenta[m]> | https://github.com/farmOS/farmOS-client/issues/240 |
| [13:51:36] | <ludwa6> | ok, so that observation showed up in web version of FieldKit |
| [13:52:03] | <ludwa6> | and in mobile! ok, so that’s one problem solved. |
| [13:52:20] | <ludwa6> | anything more to do on the map problem? |
| [13:53:41] | <mstenta[m]> | ok! great! |
| [13:53:53] | <mstenta[m]> | did you try farmOS.app for the map issue? did it have the same issue as the app? |
| [13:54:03] | <ludwa6> | ACTION goes to check |
| [13:55:26] | <ludwa6> | web version: when i try to add a log item, shift to movements view… i just get the two text fields, no map at all |
| [14:04:21] | <mstenta[m]> | oh..... jgaehring is farmOS.app broken? |
| [14:04:54] | <mstenta[m]> | does it have field module code deployed for testing? |
| [14:05:09] | <mstenta[m]> | i'm seeing an error in console: `Error installing Test module` |
| [14:06:53] | <jgaehring[m]> | what's the version in farmOS.app? |
| [14:07:09] | <jgaehring[m]> | you may need to close that tab and reload it for the newest version to install |
| [14:07:30] | <jgaehring[m]> | > i'm seeing an error in console: `Error installing Test module` |
| [14:07:31] | <jgaehring[m]> | yea I made a mistake when building the last version for the web |
| [14:07:40] | <jgaehring[m]> | forgot to switch git branches |
| [14:07:54] | <jgaehring[m]> | that shouldn't cause any problems though |
| [14:08:40] | <mstenta[m]> | oh ok - yea it's v0.4.8 |
| [14:13:23] | <jgaehring[m]> | right, but Walt might not have that version |
| [14:13:35] | <jgaehring[m]> | (service workers might have something older cached) |
| [14:13:35] | <mstenta[m]> | ah right |
| [14:13:58] | <ludwa6> | i am running 0,4.8, says my iPhone |
| [14:14:34] | <mstenta[m]> | i wonder: could we make the service worker perform a request to a file (eg: `/VERSION.txt`) and auto update if it's out of sync? |
| [14:14:40] | <jgaehring[m]> | ah, that's strange then |
| [14:14:42] | <mstenta[m]> | ludwa6: is it 0.4.8 on farmOS.app as well? |
| [14:15:12] | <ludwa6> | no -there it says 0.4.4 |
| [14:16:03] | <mstenta[m]> | ah ok! |
| [14:16:07] | <ludwa6> | are we not all looking at the same thing at https://farmos.app ? |
| [14:16:32] | <mstenta[m]> | yes that's what we're looking at too... |
| [14:16:41] | <mstenta[m]> | but it has some caching involved which means you're looking at an older version |
| [14:16:45] | <jgaehring[m]> | > i wonder: could we make the service worker perform a request to a file (eg: `/VERSION.txt`\) and auto update if it's out of sync? |
| [14:16:46] | <jgaehring[m]> | um, that probably wouldn't be the most effective way... we could just fine-tune the service worker to flush the cache if we want, but that may not necessarily present the best UX (eg, screen atutomatically refreshing w/o the user wanting it to)... we can consider it though |
| [14:16:58] | <mstenta[m]> | (service worker caching... a bit different than normal browser caching) |
| [14:17:05] | <mstenta[m]> | (so that it can work offline) |
| [14:17:25] | <ludwa6> | i haven’t visited this app for many moons -since it was first announced in the discourse group, i think |
| [14:17:47] | <mstenta[m]> | ludwa6: what browser are you using? |
| [14:18:17] | <ludwa6> | Google Chrome Version 78.0.3904.97 (Official Build) (64-bit) |
| [14:18:18] | <jgaehring[m]> | if you close the tab and reopen it, it should flush the cacheeeeeeeeeeee |
| [14:18:31] | <jgaehring[m]> | oops, sticky keyboard ;-) |
| [14:19:02] | <ludwa6> | right -now i see the map in web version |
| [14:19:21] | <jgaehring[m]> | great! |
| [14:19:34] | <ludwa6> | and here, the layers work as they should |
| [14:19:48] | <mstenta[m]> | great! and satellite layer? |
| [14:19:49] | <jgaehring[m]> | and is it just OSM, or do you see the MapBox sattelite view? |
| [14:19:57] | <jgaehring[m]> | great! |
| [14:19:58] | <ludwa6> | i’m on the MapBox view now |
| [14:20:21] | <ludwa6> | works fine in web app. |
| [14:20:25] | <mstenta[m]> | hooray! |
| [14:20:25] | <jgaehring[m]> | I'd still like to go through the steps to reproduce on the iOS app if we can |
| [14:20:46] | <mstenta[m]> | getting closer... :-) |
| [14:20:48] | <ludwa6> | you need me for this? i gotta go for supper momentarily |
| [14:20:51] | <jgaehring[m]> | wondering again if this relates to issue #236 |
| [14:21:44] | <ludwa6> | if there’s something i can do to help now, let me know… else it must wait an hour or so |
| [14:21:47] | <jgaehring[m]> | oh no worries |
| [14:22:39] | <jgaehring[m]> | when you get a chance, I'd like to know if the issue with the maps persists when you open up a brand new log, without entering any data |
| [14:23:21] | <ludwa6> | yes, it persists. |
| [14:23:27] | <ludwa6> | ACTION breaks for dinner |
| [14:23:32] | <jgaehring[m]> | if it is related to issue 236, it may work fine with a fresh log (assuming there's some corruption of the data that Field Kit can't handle, thereby messing up the maps) |
| [14:23:33] | <jgaehring[m]> | ah, darn |
| [14:23:35] | <mstenta[m]> | jgaehring: i wonder... |
| [14:23:58] | <jgaehring[m]> | thanks Walt, all good feedback, enjoy your supper!!! |
| [14:24:02] | <mstenta[m]> | the map is loading all farm areas... (displayed in gray) |
| [14:24:18] | <mstenta[m]> | yea thanks Walt! super helpful - we can finish later |
| [14:24:35] | <jgaehring[m]> | right |
| [14:25:01] | <mstenta[m]> | ... if it took longer than normal to load those areas (if there were a lot of them), could it be that the map is being displayed before they are available, and so it's not zooming in? |
| [14:25:46] | <mstenta[m]> | how are those being added to the map currently? can you point me to the relevant code? |
| [14:26:12] | <jgaehring[m]> | hmm, I don't think so... |
| [14:26:43] | <mstenta[m]> | because it sounds like the map is not zooming in. and iirc the map is set to zoom to that layer |
| [14:27:21] | <mstenta[m]> | so if that layer wasn't available, for whatever reason, then the zoomToLayer() would fail |
| [14:27:34] | <mstenta[m]> | (is that the function you're using in FK?) |
| [14:29:21] | <jgaehring[m]> | https://github.com/farmOS/farmOS-client/blob/master/src/client/component... |
| [14:30:04] | <jgaehring[m]> | `this.geoJSON` is the areas' GeoJSON |
| [14:30:18] | <mstenta[m]> | ah ok |
| [14:30:33] | <mstenta[m]> | hmm so... this is probably not the same issue but... |
| [14:30:33] | <jgaehring[m]> | `this.wkt` is the Movement Geometry |
| [14:31:06] | <mstenta[m]> | i see that there are two `if` conditions that run `zoomToLayer` and `zoomToVectors` |
| [14:31:24] | <mstenta[m]> | will those both run under certain conditions? |
| [14:31:36] | <jgaehring[m]> | and bear in mind, this is the general Map.vue component that's used in both EditLog.vue (the static map) and EditMap.vue (the editable map) |
| [14:31:40] | <mstenta[m]> | if so, that might cause weird behavior |
| [14:32:30] | <mstenta[m]> | the `zoomToVectors` and `zoomToLayer` functions are a bit tricky... |
| [14:32:39] | <mstenta[m]> | https://github.com/farmOS/farmOS-map/blob/master/src/instance/methods/zo... |
| [14:33:17] | <mstenta[m]> | ah... soo.... |
| [14:34:00] | <mstenta[m]> | do we need to wrap the `zoomToLayer()` in an `on('change'` listener? |
| [14:34:48] | <mstenta[m]> | `zoomToLayer()` will only zoom `if (source.getState() === 'ready' && source.getFeatures().length > 0)` |
| [14:35:02] | <mstenta[m]> | so i wonder if, in Walt's case, that's not true when it is being run |
| [14:35:49] | <mstenta[m]> | but... i dunno... i mean... it's loading WKT, which I would think would be instanct |
| [14:35:50] | <mstenta[m]> | instant* |
| [14:36:52] | <jgaehring[m]> | hm yea, it was pretty hairy getting all those conditionals to work in the right way... but make sure to note, it's `once('change')`, not `on('change')` |
| [14:37:05] | <mstenta[m]> | right right `once` |
| [14:37:07] | <mstenta[m]> | that's what i meant |
| [14:37:54] | <mstenta[m]> | it's important to have that listener, especially with a source that is requested via HTTP request, because it won't have a geometry until that request finishes... at which point `change` will be fired |
| [14:38:23] | <mstenta[m]> | i'm not sure if it's necessary for non-HTTP request layers though |
| [14:38:34] | <mstenta[m]> | i would think that would be available immediately, but maybe it's not |
| [14:41:52] | <mstenta[m]> | this is just a guess... might be a red herring |
| [14:42:32] | <jgaehring[m]> | > it's important to have that listener, especially with a source that is requested via HTTP request, because it won't have a geometry until that request finishes... at which point `change` will be fired |
| [14:42:32] | <jgaehring[m]> | right, that's why I needed to do that specifically for the geoJSON layer |
| [14:43:03] | <mstenta[m]> | oh hmm... you know... `once` might actually be an issue in some cases... |
| [14:43:16] | <jgaehring[m]> | > i would think that would be available immediately, but maybe it's not |
| [14:43:16] | <jgaehring[m]> | correct, the WKT is available immediately, so if the WKT is present, we zoom on that layer immediately |
| [14:43:19] | <mstenta[m]> | well.. not in this case actually i guess |
| [14:43:49] | <mstenta[m]> | (sorry , out of order riot messages) |
| [14:44:54] | <mstenta[m]> | hmm well - might be easier to debug with Walt present... |
| [14:45:28] | <mstenta[m]> | we can ask him if the WKT features are showing up or not (he'll have to manually zoom to them |
| [14:45:31] | <jgaehring[m]> | yea |
| [14:46:48] | <mstenta[m]> | the fact that it's working in farmOS.app, and not FK, is strange |
| [14:47:16] | <mstenta[m]> | iOS i mean |
| [14:49:51] | <jgaehring[m]> | yea |
| [14:50:01] | <jgaehring[m]> | Greg hasn't reported any issues with it has he? |
| [14:51:08] | <mstenta[m]> | I vaguely remember something similar with him |
| [14:51:28] | <mstenta[m]> | But I think it got resolved? |
| [14:51:54] | <mstenta[m]> | I'm not sure if they are actively using it yet |
| [14:55:58] | <mstenta[m]> | in the meantime... i'm getting back into the line/polygon measurement stuff :-) |
| [14:56:52] | <mstenta[m]> | i just need to figure out the best way to tie the measurement tooltips to specific features (rather than just specific coordinates), so that i can update them when shapes change |
| [14:57:11] | <mstenta[m]> | this feels like something that would be a lot easier in Vue/React :-) |
| [14:58:39] | <jgaehring[m]> | haha, yea, probably |
| [15:22:05] | <ludwa6> | ACTION back. Dunno what you mean about WKT features… but any attempt to zoom on map is essentially useless. |
| [15:27:35] | <mstenta[m]> | when you say "essentially useless" does that mean broken? or just annoyingly slow? |
| [15:28:16] | <ludwa6> | soon as i touch the map that appears on movement screen by default, it changes to a global view of OpenStreetMap that loses resolution as you zoom in on it, such that a 10k square km selection is essentially inscrutable. |
| [15:28:16] | <mstenta[m]> | "WKT features" refers to the shapes that should show up on your map in gray (representing all the areas from your farmOS) |
| [15:28:32] | <mstenta[m]> | if you open the map in farmOS.app, you should see the grey area outlines (double check that...) |
| [15:28:41] | <ludwa6> | and it never resolves into a usable image, no matter how long i wait |
| [15:29:12] | * FijiDave has joined #farmos |
| [15:29:14] | <ludwa6> | yes, correct: farmos.app shows the grey boundary areas |
| [15:29:16] | <mstenta[m]> | hmm yea that's really annoying... makes it hard to debug |
| [15:29:20] | <ludwa6> | on a hi-rez map |
| [15:29:27] | <mstenta[m]> | so i guess we need to debug the mapbox layer first... so that we can debug the zoom issue |
| [15:30:35] | <mstenta[m]> | ludwa6: what version of iOS are you using, do you know? (@jg |
| [15:30:39] | <mstenta[m]> | (jgaehring are you able to see this in the Apple Test Flight system?) |
| [15:31:02] | <ludwa6> | no way to see grey farm plot boundaries on the iOS view; can barely distinguish white of continental landmass from blue of ocean when zoomed in to size of southern portugal. |
| [15:31:18] | <mstenta[m]> | ludwa6: oh... how about we try this: can you open the browser on your phone and go to farmOS.app there? let's see if that is any different than on your desktop |
| [15:31:39] | <mstenta[m]> | just looking for any difference we can find at this point so we have something to dig into |
| [15:32:01] | <jgaehring[m]> | > "WKT features" refers to the shapes that should show up on your map in gray (representing all the areas from your farmOS) |
| [15:32:02] | <jgaehring[m]> | other way around, wkt is the orange shapes, geojson is the gray |
| [15:32:15] | <ludwa6> | in fact i have farmOS open in iPhone’s safari brower. am looking to find the version… |
| [15:33:29] | <ludwa6> | anyway: just went to “add area” in safari on iPhone… and it gives me a good map of farm context, with grey boudaries of all my areas, and i can zoom in on it no problem. |
| [15:33:57] | <ludwa6> | iOS version is 13.1.3 |
| [15:33:58] | <jgaehring[m]> | > ([jgaehring](https://matrix.to/#/@jgaehring:matrix.org) are you able to see this in the Apple Test Flight system?) |
| [15:33:59] | <jgaehring[m]> | hmm, don't think so, but I can check |
| [15:34:06] | <mstenta[m]> | oh right - thanks for the clarification jgaehring |
| [15:34:35] | <mstenta[m]> | oh you mean you opened vdl.farmos.net? |
| [15:34:51] | <mstenta[m]> | try opening https://farmOS.app instead |
| [15:35:35] | <mstenta[m]> | i want to see if, on your phone, https://farmOS.app (in Safari), has the same issues as the iOS FK app |
| [15:35:57] | <ludwa6> | mstenta: ok, will try |
| [15:36:06] | <mstenta[m]> | namely: |
| [15:36:07] | <mstenta[m]> | 1. map does not automatically zoom to gray areas |
| [15:36:07] | <mstenta[m]> | 2. MapBox layer is not available as an option |
| [15:38:45] | <ludwa6> | mstenta: farmos.app map works fine in Safari on iPhone |
| [15:39:10] | <ludwa6> | with grey boundary areas on hi-rez map, speedy update on zoom, etc. |
| [15:39:22] | <mstenta[m]> | ah ok interesting |
| [15:39:46] | <mstenta[m]> | wellll... worth noting: you can "install" farmOS.app and use it just like a standard iOS app |
| [15:40:02] | <ludwa6> | ? |
| [15:40:30] | <mstenta[m]> | oh crap i may have spoken too soon ... I don't know if Apple supports that yet |
| [15:40:56] | <ludwa6> | there is no installing a web app on iOS, AFAIK |
| [15:41:01] | <mstenta[m]> | on Android, farmOS.app will automatically popup a window that says "Install on home screen" and it will show an icon just like normal apps, without the need to install anything |
| [15:41:09] | <jgaehring[m]> | it's supported for the features we have, except the camera |
| [15:41:18] | <mstenta[m]> | "progressive web app" |
| [15:41:29] | <jgaehring[m]> | "install" is a bit of a misnomer |
| [15:41:31] | <mstenta[m]> | right... that's the only issue: camera isn't working yet |
| [15:41:55] | <jgaehring[m]> | basically, it's added to your home screen and cached for offline use |
| [15:42:21] | <mstenta[m]> | jgaehring: is it correct that iOS does not support that yet? |
| [15:43:00] | <jgaehring[m]> | iOS does not prompt you to add a PWA to your home sreen the way Android does |
| [15:43:12] | <jgaehring[m]> | but you can add it to your homescreen manually |
| [15:43:27] | <jgaehring[m]> | and all the other guts of the PWA are supported |
| [15:43:35] | <jgaehring[m]> | at least the pwa features we use |
| [15:43:40] | <ludwa6> | jgaehring: do you know how to add to iOS home screen? |
| [15:44:12] | <jgaehring[m]> | it gets a little weird for stuff like push notifications, and background tasks |
| [15:44:50] | <mstenta[m]> | oh cool! |
| [15:45:02] | <mstenta[m]> | so in that case, you might be able to do that ludwa6 , and uninstall the app itself |
| [15:45:16] | <mstenta[m]> | we're hoping to get the camera stuff worked out in the near future... but everything else should work |
| [15:45:42] | <ludwa6> | i don’t know about this, adding to home screen. Closest thing i can conceive is bookmarking the app in Safari. |
| [15:46:26] | <jgaehring[m]> | you use the share button in iOS safari |
| [15:46:50] | <jgaehring[m]> | and then one of the options it gives you is "Add to Home Screen" |
| [15:46:50] | <mstenta[m]> | yea it kinda like a special bookmark :-) |
| [15:47:02] | <mstenta[m]> | but better, and works offline |
| [15:47:03] | <jgaehring[m]> | right |
| [15:48:17] | <ludwa6> | ah, i see how to do it. OK, it’s on my home screen. will test offline use. if that works… Cool! |
| [15:48:50] | <mstenta[m]> | cool! |
| [15:55:37] | <ludwa6> | interesting: i just turned my iPhone’s wifi off, created an observation in iOS FieldKit, synced, and it showed up in desktop immediately. I’m at home with 3g access… But i will try this in the field tomorrow, where i have spottty connectivity, to see if it will hold the entry in memory until i get internet connected again. If that works, this PWA tech may serve the need. |
| [15:56:35] | <jgaehring[m]> | awesome! |
| [15:56:51] | <ludwa6> | only: did i understand you right, that camera doesn’t work in this PWA app on mobile? |
| [15:57:27] | <jgaehring[m]> | correct, however, you can upload images that you've already taken |
| [15:57:51] | <jgaehring[m]> | we're working to fix the feature for opening the camera directly from the app |
| [16:00:50] | <ludwa6> | one PITA with this PWA version on iPhone is: i have to submit credentials every time i launch it. |
| [16:00:51] | <mstenta[m]> | yea - so you can take a photo with your camera, so that it saves to the phone, then open field kit and "select from file" |
| [16:01:08] | <mstenta[m]> | (workaround) |
| [16:07:04] | <ludwa6> | ACTION gotta go; g’nite guys |
| [16:07:29] | * ludwa6 has quit (Quit: ludwa6) |
| [16:08:09] | <mstenta[m]> | night ludwa6 ! great talking! |
| [16:12:16] | <jgaehring[m]> | night Walt, thanks for everything! |
| [17:36:00] | * JustTB has quit (Ping timeout: 246 seconds) |
| [17:51:30] | * JustTB has joined #farmos |
| [18:13:15] | * sol5 has joined #farmos |