Implement context fusion #60
Conversation
| this.overlays = biigle.$require('annotations.overlays'); | ||
| // console.log('geoOverlays: ', this.overlays); | ||
| // console.log('activeId: ', this.settings); | ||
|
|
There was a problem hiding this comment.
@mzur,
I am a bit confused by all the imports between the biigle modules, which is why I pose this question:
In the geo-module I created a ContextLayerMixin for the annotationCanvas.vue of biigle/core.
In this mixin, I want to access a couple of variables from the annotation settings tab (i.e. the activeId or opacity of the geo-overlay settings, which are part of yet another plugin that is published from the geo-module to the settingsTab.vue in core).
In order to access these variables, do I have to make them available as properties in the annotationCanvas component (here) in biigle/core, or can I directly import them, for example the whole settings-variable from the settings-store?
The first option should work because the variables would be made accessible within the ContextLayerMixin, but it would require changes to the code in biigle/core, which doesn't seem right. Regarding the second option, I'm not sure how to make the settings-store variable available.
There was a problem hiding this comment.
I see your point, there is no direct way to access the settings in an annotation canvas mixin. Maybe you can do it like the reports module. It does everything in the settings tab plugin by using the annotations.map.init and images.change events to hook up OpenLayers objects and update image data.
…on settings-store.
| return tileLayer; | ||
| }, | ||
| updateCurrentImage(id, image) { | ||
| this.currentImage = image; |
There was a problem hiding this comment.
@mzur,
when metadata is provided for the volume, what is the currently implemented way to access the metadata for each image (i.e. the point geo-coordinate)?
There was a problem hiding this comment.
The image model has the attributes lat and lng. Other metadata must be accessed via $image->metadata.
…-layer extent (pixel).
…t corner of an image as reference)
|
@mzur, I'll forward you the example dataset + computed metadata-file for testing purposes. |
Refers to #45
The following data and metadata should be present in a suitable dataset for the context-fusion feature:
ToDo-list:
opacity,currentImage,activeOverlay) without having to delete the context-layer, but rather setting the visibility true/false.tileLayer.on('prerender',...). For instance, when the layer is rotated by 180°, and dragging the image downwards, tiles in the upper viewport disappear (so it seems the tile-loading function is not mirrored with the rotation).Improvement list:
implement "automatic" scaling, given suitable data exists (i.e. pixel-to-unit-ratio's of both mosaic and image)
change the manual scaling method to reflect the scaling of the context-layer in the viewport. The current solution functions as follows: In the image annotation-view...
Currently, the
mousewheelzoominteraction gets deactivated when in Edit-mode (to not zoom in/out when adjusting scale). But this also hinders the scaling itself to be reflected on the OL-viewport.possibly generalize the
calculateExtent()method, as it is currently assumed that the reference point of the single image is the center of the imageFor further details on the ToDo's, see also comments in settingsTabPlugin.vue