Describe the improvement you would like to see
Currently the map service is dependant on loading png images from an azure blob service. Rewrite this to be more flexible for non-Equinorian users. The service then approxes position from pixels in image.
These separate issues will make MapService not dependant on BlobService:
[ ] Write a storage interface for MapService, where in-memory storage is an option. In-mem storage needs metadata for position/boundraries for all images to be fetchable from mapservice.
[ ] Consider having a dummy map uploaded to flotilla memory interface
[ ] Make MapService dependant on storage interface, and not BlobService directly
[ ] Write Map class to replace BlobItem reference in MapService
How will this change existing functionality?
Easier to run for external companies, less coupling in program
How will this improvement affect the current Threat Model?
Describe the improvement you would like to see Currently the map service is dependant on loading png images from an azure blob service. Rewrite this to be more flexible for non-Equinorian users. The service then approxes position from pixels in image. These separate issues will make MapService not dependant on BlobService:
How will this change existing functionality? Easier to run for external companies, less coupling in program
How will this improvement affect the current Threat Model?