Imagery asset - any interest?

[walt]

@paul121

…By “mapS” I’m referring to the maps that are rendered on different pages in farmOS, eg: dashboard, asset list, asset view/edit, log view/edit, etc. You’ll notice that these all have subtle differences. It could be possible to select which (or all) maps to render an imagery asset on. For example, only render on the dashboard, or only render in log maps (if imagery is only used to identify fences for animal movement logs).

OK, i see what you mean. I was confused, because in my instance, the basemap is always the same, only the focus will change to a different range of co-ordinates, depending on what’s been selected for viewing… But i can see how this “Imagery Asset” class would enable delivery of whatever “map imagery” is most appropriate as a basemap for the context in focus.

For example: the default basemap imagery is fine for most of our purposes in the system -except when it comes to our Market Garden operation, which has 2 important new elements (a summer shade tunnel, AND an annex to our greenhouse that has doubled its size) not shown on the default satellite imagery, it is so old! If i could replace it with more current GeoTIFF map imagery, as proposed in another thread, that would be great -and this sounds like a good way to enable it.

@walt

As a non-dev user of farmOS, but a bit more savvy in realm. of GIS, i would observe that “layers” can be either bitmap or vector, while “imagery” refers to bitmaps specifically, so… Dunno if this distinction is quite obvious to the “naive” user, but seems to me important for the Developer to be aware.

@paul121

Good observation… maybe “map layers” is too general. I think “map imagery” better captures the goal here. And it less technical than something like “bitmap layers”

Yes -“map imagery” is a simple and unambiguous term that is friendly to both Users and Devs, seems to me.