| [00:00:17] | * farmBOT has joined #farmos |
| [10:56:14] | <Greg[m]> | Hey folks... I'm curious can I sum all the acres in a farmos instance easily? I know those are calculated values, but wondering if it's possible to get them out in any way |
| [11:03:08] | <symbioquine[m]> | Do you mean of all the location asset's intrinsic geometry? |
| [11:05:26] | <Greg[m]> | no, the actual acre estimate for any polygons related to fields |
| [11:05:46] | <Greg[m]> | I believe it's just calcualted in the js itself on the front end... so I'm guessing it's not there which is a bummer, but curious if anyone has done this |
| [11:08:40] | <symbioquine[m]> | Greg[m]: Do you mean land assets with the type "field"? |
| [11:09:43] | <Greg[m]> | yes, land assets with type "field" in which the acres are displayed in the map. Is it possible / easy to both view the acreage value in farmOS tables and/or through the api. I guess that's the question hopefuly more clear |
| [11:12:14] | <symbioquine[m]> | Ah, cool |
| [11:12:36] | <symbioquine[m]> | No I don't think that's surfaced anywhere because I'm pretty sure it's computed using OpenLayers... |
| [11:12:51] | <symbioquine[m]> | but it shouldn't be very hard to compute via the api... |
| [11:13:56] | <Greg[m]> | yeah, true. I know conversations have happened, but I really wish that value was computed and stored in farmOS. IMO ideally in the geometry bucket as an additional field like lat or lon, with options for alternative calculations. |
| [11:14:18] | <Greg[m]> | (complaining of course... I know the answer is to engage it and work on it!) |
| [12:35:55] | <symbioquine[m]> | https://gist.github.com/symbioquine/160d435a951523c52c86f9327f8ba2c4 |
| [12:36:04] | <symbioquine[m]> | ACTION uploaded an image: (242KiB) < https://matrix.org/oftc/media/v1/media/download/ATZjqxDKdjlYc8szGgZ-aBYq... > |
| [12:36:47] | <symbioquine[m]> | https://farmos.discourse.group/t/share-your-jupyterlite-examples/1134/44... |
| [12:46:29] | <Greg[m]> | Cool thank you. If we can't get it from our partner directly, maybe we'll give it a shot. |
| [12:48:29] | <symbioquine[m]> | Some bits of that example are specific to Jupyterlite of course, but it should be pretty easy to adapt that code to run in another Python environment. |
| [12:50:30] | <symbioquine[m]> | The most obvious issue with that implementation is that it doesn't account for overlapping geometries... |
| [12:52:17] | <symbioquine[m]> | To fix that you'd need to create a union off all the geometries then take the area of the resulting area. |
| [12:52:31] | <symbioquine[m]> | s/take/compute/ |
| [12:52:46] | <symbioquine[m]> | s/take/compute/, s/area/geometry/ |
| [15:17:47] | <symbioquine[m]> | s/off/of/, s/take/compute/, s/area/geometry/ |
| [17:03:02] | * aislinnpearson[m] has joined #farmos |
| [17:03:03] | <aislinnpearson[m]> | Greg: I was thinking about calculating acreages as well this week. At Rothamsted our fields have multiple boundaries: what we measured with a gps, what the government (DEFRA) measured (I think maybe with a satellite?) which is again different to our cropped area (which is more a function on the drilled and managed and harvested area - which may all be different things). Some of this you can get from John Deere and in reality you |
| [17:03:03] | <aislinnpearson[m]> | might want to compare the values to improve efficiencies. In the end I switched them off in the mapping software we use so people have to think about exactly what area they want. |
| [17:03:59] | <aislinnpearson[m]> | Never ask a scientist when you want a simple answer. ‘It depends’ followed by overly detailed explanations is all we know how to do 😂 |
| [17:04:26] | <aislinnpearson[m]> | But I do think it would be great to store the actual calculated areas in assets and logs! |
| [17:23:14] | <Greg[m]> | Yeah, like I said, looking at other standards like Adapt and others, it makes sense to me most to be in the existing geometry field where there are other derived fields from the wkt already. That way, other custom geometries (which as you said can be calcualted a million ways...) can be included there as well. |
| [17:23:17] | <Greg[m]> | ACTION uploaded an image: (104KiB) < https://matrix.org/oftc/media/v1/media/download/AeTNobvFO7cjvmIoLgCX9xPb... > |
| [17:23:41] | <Greg[m]> | if FarmOS were more used with tractor automation or integrated with other systems, this would have been a much earlier absolute requirement IMO. |