This is the latest iteration of the maps I've been making to help on our farm. Since we have a good amount of tree cover and therefore GPS measurements are rarely 5m or less and our trees are planted anywhere from 9m to 2m apart from each other, we currently aren't using GPS data points for anything and only use hole numbers that are put into google sheets in a way that they represent the orientation of holes in real space.
So let me explain the Table from A1-E7,. Row one has dropdowns for every single column of data collected from ODK forms as well as additional calculations I do in google sheets in a different sheet. These 5 column values control what is displayed in each cell, which are all concatenated with an underscore for each cell of the map based on a unique hole number that identifies each tree at its location.
Cells A2-E7 control the conditional formatting of the map and I can input info from a dropdown or type it in. The conditional formatting will only allow one color to be displayed per cell, so cells with a lower row number (on top) will display even if it has conditions met in rows below. Lets take row 2 and row 5. Row 2 is going to highlight cells that contain "Avocado" and "TRUE", which for this value means that only Avocados with a single tree of a any variety will be highlighted. Row 5 will highlight cells that contain Avocado. Column F shows the number of occurences that fulfill those conditions and the highlight color for that rows conditions. So in this case, for row 2 there are 17 Avocado trees that only have 1 tree of that variety that get highlighted dark green. For row 5, there are 51 Avocados total which get highlighted blue but that 51 INCLUDES Avocado trees that have only 1 unique variety, so there are actually only 51- 17 = 34 cells highlighted blue.
It seems like no matter how many times I think I don't need another piece of data displayed on the map, I inevitably would like another map that is slightly different, which is why I made the table all dynamic so that I can control what data is displayed and what is highlighted. @Aly_Blenkin ,@norlowski, @yanokwa, I don't know if this helps you fall down the slippery slope or gives you any ideas for how to filter/display different data on map view for the new things y'all are working on, but I figured I'd tag you so you can see the kinds of things I'm doing with spatial data even though its not GPS data.
This looks interesting and mind boggling! So much data to take in...
Not all directly ODK relevant but you could spot point all your trees once (if you had a high accuracy GNSS receiver you might manage sub-metre accuracy, so wouldn't have overlaps) or even go old skool and make a map on a vector basis (start in the corner of the plot, go x degrees for y metres, etc with the corner as your datum)
And then continue to use your (w)hole numbers in your forms but also be able to use select_one map appearance (entities?) or use @ahblake's Summit Fever 'select from SVG' (so you manually plot out those points in your idea of space on a diagram as clickable points, rather than GPS coordinates).
But even without that, you could plot these in QGIS using your own row / column projection to generate the map - then all those points can have attributes associated and you can colour-code / symbolise the dataset...
And you could link that dataset to ODK to keep it up to date... you can import entities or submissions (or both) and KEY those points, or use a calculate to generate the geometry in real space...
Might be a bit more visually pleasing than a spreadsheet, with all the power of spatial analysis at those green fingertips of yours!
Do the hole numbers ever change, as they aren't contiguous in your sheet? If they are fixed you could certainly create an SVG map of the plots as a representation of their layout plus the hole number, which would let you select a plot by tapping the hole as a fast method for form use (but scanning a barcode / entering a hole number is likely as fast with less effort).
What's the closest any hole is to another? 2m is plenty to allow you to plot holes out in a GIS platform, even if they're not exactly ground truthed (like @seewhy says, you could capture the corners as best you can, then use these to layout your holes manually in QGIS), and still zoom close enough in Collect (using Mapbox) to select the one you want, but the downside is that points can only have a single character inside the map pin , so you'd have to tap them to bring up the label with hole#.
If you did do that it would allow you to use @seewhy 's QuODK and pull your current hole entity data in and style it as needed, or in many different ways, according to all of your various rules.
I often wish I could select a form field(s) in Central to use as a filter, beyond the existing filters on status/submitter/date), as a quick view, but is this just replicating other products and not ODK's core...
, so you'd have to tap them to bring up the label with hole#.