Note there is some type of bug in the note editor that prevents making format changes. Everytime a change is made the entire post is wiped clean from the display.

Oof, sorry about that bug, @MaggPi. Possibly legacy mode can help. Reading this now - very interesting!!!! Thank you!!!

OK, first I really like your overall summary -- Increasing Image sequencer applications... especially! Making satellite data accessible is also a great goal for the project.

large file size: Satellite file sizes are typically greater than 100 MBs and this often results in data storage problems. The proposed solution is to develop an Image Sequencer module that restrict file size (10MB) and is centered on a region of interest identified by the user.

To consider here -- a lot of satellite data is stored as (giant) GeoTiffs by default, and a number of systems have been developed to serve sub-sections of a big GeoTiff over HTTP -- as a way around the need to reprocess GeoTiffs into another format like TMS tiles. (and because if you reformat into TMS, you are kind of "stuck" in the available tile grid, png/jpg image compression, and zoom levels of the TMS format you choose, and it's hard to work back). Some background that's good to know -- https://www.gdal.org/gdal_utilities.html GDAL is perhaps the most authoritative standard toolset for satellite data, but it's not a web-based application, it's a commandline system. It could be interesting (though not directly related here) to look at how the new MapKnitter Exporter dual-track project is creating a web-based toolchain both based on GDAL/ImageMagick, and in parallel, a clone based on Image Sequencer: https://github.com/publiclab/mapknitter/issues/298 -- it will also include a GeoTiff converter for Image Sequencer, which could be useful to you, and in general may be an interesting way to look at how a GDAL-type system can be adapted for web, or replaced by a more optimal JS/Image Sequencer alternative!)

Anyways, i think the "serve subsections of GeoTiffs" idea is called HTTP Get Range requests -- more here: http://www.cogeo.org/in-depth.html which... i dunno, could then be piped into Image Sequencer?

Also, I'm guessing you've seen these, which are really minimal, but provide a model for using ImageSequencer in Leaflet:

• https://github.com/publiclab/leaflet-multispectral
• https://github.com/publiclab/leaflet-tile-filter

They're both using a TMS tile model for data, not GeoTiff, but as part of that I found a LOT of tile sources for satellite imagery here: https://github.com/publiclab/leaflet-tile-filter#multispectral-tms-tile-sources

So using only tiles is a viable path, even if it loses some of the original source data in Geotiffs.

One idea could be to adapt some of the tile-based approach in leaflet-tile-filter or leaflet-multispectral to filtering subselections of GeoTiffs -- maybe building on https://github.com/stuartmatthews/leaflet-geotiff

Here's an interesting mini-problem: how to preserve GeoTiff georeferencing data in non-Tiff file formats? Is there a standard for JPG or PNG that could essentially mirror GeoTiff (GeoJPEG or GeoPNG -- i bet something like this exists) and is it possible to convert lossessly between these? That could be really relevant for Leaflet.DistortableImage as well!

Some UI and logistical issues which could be great to solve to make the overall goal easier:

• a better UI for piping remote imagery (via URL? via a draggable map?) into ImageSequencer's sequencer UI -- maybe related somehow to the multiple-inputs plan in https://github.com/publiclab/image-sequencer/issues/212
• I think Image Sequencer has matured a lot, but it still lacks sufficient test coverage to be very stable. There are bugs in the crop module, and other modules, both in the UI and in the core module functions. Defaults are inconsistently provided. So I think a lot of work on test coverage might be a prerequisite to building a more complex stable library on top of IS. But the good news is that testing of the modules is pretty easy, and a lot of issues have been ironed out to open a pathway to near-100% coverage.

Finally, I'm interested in what the UI for a more advanced Image Sequencer based system might look like, for example within a Leaflet UI. This may or may not be the direction you're going, but could it be possible to select an imageOverlay or collection of tiles, and to open IS in a sidebar of a Leaflet map? Or would it be better to have a popup menu toolbar, as provided in https://github.com/publiclab/Leaflet.DistortableImage/, with https://github.com/leaflet/Leaflet.Toolbar ?

This is a really interesting and awesome project, @MaggPi, thanks so much! I think OpenCV.js will likely open up a huge set of possibilities, and this is a really interesting direction to go in. I think it's also possible that it may link up with @rexagod's proposal in some places, if both of you are able to work in well-documented standard ways -- for example, a number of OpenCV abilities may be relevant to feature point matching, for example.

Small question - what formats does Planet Labs provide?

Finally, i wonder what some specific workflows and abilities might be that you could describe that are /not/ possible from a web-based platform currently that you would be opening up and making easier for people through this project? Are there some applications using Planet Labs imagery that are currently only doable using complex or command-line software, or other use cases for NASA imagery that would be made more possible here? Some more examples could be great to outline.

Thanks a lot - i left a lot of thoughts here, you don't have to adopt them all but I hope they're interesting.

Hi, please upload your proposal at the Google Summer of Code website at the earliest. Please ignore this comment if already done.

Hi everyone, Just want to say thank you to my mentors (@warren , @gauravano , @sagarpreet ) for agreeing to help in GSOC 2019! Also, would like to introduce myself to the other Image sequencer developers ( @aashnaaashna , @lit2017001 ) and their mentors (@Harshith and @jainaman224 ).

A project comparison spreadsheet is available at , https://github.com/MargaretAN9/GSOC-2019

or copy and past the direct link https://github.com/MargaretAN9/GSOC-2019/blob/master/Comparison%20matrix%20Public%20Lab%20GSoC%20Outreachy%202019%20v1%20(1).xlsx .

I did this to see if there are common trends across the different programs. If you think there are other program connections please feel free to update the matrix.

One common theme is opencv. Asshna’s and my project directly depend on opencv and Divy’s project may also benefit from colorspace conversion typically used in color comparisons.

So, does anyone have ideas on the best way to add opencv to Image sequencer? My first thought would to try to add opencv.js as a new module to Image Sequencer? Since this would be a very big module I suspect that another approach would work better.

There is also the issue that some image sequencer modules may duplicate open. cv functions (see https://github.com/opencv/opencv/blob/master/modules/js/src/embindgen.py#L82-L171 for list of opencv functions). Not sure if this is a bad thing but it may mean that we don’t need to include all opencv functions or some of the inconsistent IS modules (see Warren’s ‘crop’ comments above) would be replaced by opencv?

I am very interested in how opencv is added to IS since I assume a similar approach can also be used for GDAL. (GDAL is a sort of open.cv for GEOTIFF satellite images).

Note that in the Note Editor some sort of bug avoids modifications in size. The full article is washed off the screen every time a shift is created.

@warren , @gauravano , @sagarpreet

This note is a GSOC Phase 1 summary and updates Phase 2 goals. Research notes are posted at https://publiclab.org/profile/MaggPi. Comments on software programs (posted at https://github.com/MargaretAN9) are listed below:

Work can be divided into three parts:

• Satellite image processing – Processed NDVI Landsat and Planet satellite images with a variety of software techniques (python, Image Sequencer, QDIS, Adobe ). This was done to establish a baseline for improved Image sequencer modules. Example processed images available at: https://mapknitter.org/profile/MaggPi

• Image Sequencer documentation – Developed draft Image Sequence User Manual. The manual will be updated for each phase of the project and will provide a summary of the GSOC effort. https://publiclab.org/notes/MaggPi/06-10-2019/draft-of-public-lab-image-sequencer-user-manual-comments-welcome

• OpenCV/Image Sequencer Installation - Installed OpenCV.js and Image Sequencer with mixed results:
o Spent several days trying to resolve a ‘throw error’ when loading Image Sequence on a Windows machine. Problem was resolved by using an older version of node (8.9.1 vs 10.16.0). Future documentation needs to reference node version requirements.
o Completed test case demo circle of openCV.js/IS circle detection algorithm. Code is posted at https://github.com/MargaretAN9/GSOC-2019/tree/master/opencvjsCircleDetect and example output is available at https://github.com/MargaretAN9/GSOC-2019/blob/master/circle%20picture.png . This example and @aashnaaashna ‘s breakthrough blob processing demo illustrate Image Sequencer’s potential and the IS evolution from Image Processing to Image Analysis tool.

o Currently working installation errors such as grunt build failure /heap running out of memory after loading OpenCV and new IS modules.

o Another issue is understanding different options to load and use openCV with Image Sequencer . It may take several designs/evaluations before limitations and advantages of each approach are understood.

Phase 2 will continue debugging OpenCV/IS. If the system is stable future modules will concentrate on analyzing geoTIFF images. Thanks to Warren for referencing Mappknitter-Exporter-js (see thread discussion above) . Is it possible to use the cloud feature to import/store large geoTIFF images? Looking for a way to get around the 10MB MapKnitter limitation and import larger (~200MB) geoTIFF files.

@warren , @gauravano , @sagarpreet

This note is a GSOC Phase 2 summary and updates Phase 3 goals.

Image Sequencer Manual Substantial changes to the manual were made over this rating period. Proposed future changes for the next period include: -Adding new modules such as Noise reduction, Minify Image, blob Analysis, colorimetry -Demonstration of Insert step functionality -Increasing the applications section to include blob detection and colorimetry -Adding an intro section which list modules according to their general functions; such as color modification, size or shape changes, text/QR,etc. (This approach may help develop submenus vs the current 40 long dropdown list) . Github pull at: https://github.com/publiclab/image-sequencer/pull/1171 Initial announcement: https://publiclab.org/notes/MaggPi/06-10-2019/draft-of-public-lab-image-sequencer-user-manual-comments-welcome Manual Version 0.3: https://github.com/MargaretAN9/GSOC-2019/blob/master/ImageSequencerUserManual.md#saturation-module

IS/OpenCV Demonstrated the ability to load opencv and then process images from datauri to string format and then to rgba. Have not been able to successfully transfer image from rgba back into IS datauri display format. At this point, aashna27 great work has superseded my efforts and it’s probably best to align with her designs. My initial code trying to develop IS/openCV in a single file is available at : https://github.com/MargaretAN9/GSOC-2019/tree/master/is%20w%20opencv Once opencv is pushed, several new options exist for IS modules. One possible option is a calibration module for microscope pictures which measure a known reference and provide data for the grid module.
Additional work includes a post demonstrating VS Code as an operating environment for OpenCV.js: https://publiclab.org/notes/MaggPi/07-04-2019/introduction-to-image-processing-with-opencv-js

Satellite Processing Steady progress using python to load and display satellite images (Landsat or Planet). I was hoping to develop a request to only download a portion vs the entire image. Comments from Planet.com indicate that this is not possible. The current approach is to use API’s to select thumbnail areas of interest, download geoTIFF files and then use gdal to crop images for easier processing.

Currently working an application which uses satellite imagery to update OSM data with environmental characteristics. This Mapknitter link demonstrates how overpass-turbo can be used to identify park areas in satellite images, which then can then be processed to update OSM markings. Code available at: https://github.com/MargaretAN9/GSOC-2019/edit/master/sattelliteImageProcess/greenOperpassExV1.ipynb

Collaboration efforts include Q/A’s to anaconda, opencv, planet.com and IS github sites.

This note is a GSOC 2019 Summary Report

Wrap up post with major major activities that were accomplished:

Image Sequencer Microscope Calibration:

Demonstrated several ways that Image Sequencer can be used to calibrate images recorded from digital microscopes. Designed a new Image Sequencer module with prestored calibration settings.

• https://publiclab.org/notes/MaggPi/08-19-2019/microscope-calibration-with-image-sequencer

Satellite Processing:

Demonstrated application which uses satellite imagery and OSM data with to highlight environmental characteristics. Documentation available at: https://publiclab.org/notes/MaggPi/08-17-2019/shades-of-green-openstreetmap-overlays-on-satellite-images. This Mapknitter link demonstrates how overpass-turbo can be used to identify park areas in satellite images, which then can then be processed to update OSM markings. Code available at:

- https://github.com/MargaretAN9/GSOC-2019/edit/master/sattelliteImageProcess/greenOperpassExV1.ipynb

Image Sequencer Manual:

New Image Sequencer manual developed that includes the following: - Adding new modules such as Noise reduction, Minify Image, blob Analysis, colorimetry - Demonstration of Insert step functionality - Increasing the applications section to include blob detection and colorimetry - Adding an intro section which list modules according to their general functions; such as color modification, size or shape changes, text/QR,etc. (This approach may help develop submenus vs the current 40 long dropdown list).

Github pull at:

• https://github.com/publiclab/image-sequencer/pull/1171

Initial announcement:

• https://publiclab.org/notes/MaggPi/06-10-2019/draft-of-public-lab-image-sequencer-user-manual-comments-welcome

Manual Version 0.3:
- https://github.com/MargaretAN9/GSOC-2019/blob/master/ImageSequencerUserManual.md#saturation-module

Collaboration efforts include Q/A’s to anaconda, opencv, planet.com and IS github sites.

IS/OpenCV

Established the ability to load OpenCV and then process images from data uri to string format and then to RGBA. Have not been able to successfully transfer image from RGBA back into IS datauri display format. At this point, aashna27 great work has superseded my efforts and it’s probably best to align with her designs. My initial code trying to develop IS/openCV in a single file is available at: https://github.com/MargaretAN9/GSOC-2019/tree/master/is%20w%20opencv

Once opencv is pushed, several new options exist for IS modules. One possible option is a calibration module for microscope pictures which measure a known reference and provide data for the grid module.

Additional work includes a post demonstrating VS Code as an operating environment for OpenCV.js:

• https://publiclab.org/notes/MaggPi/07-04-2019/introduction-to-image-processing-with-opencv-js

General Comments: The focus of the GSOC effort changed over the course of the project. The initial proposal concept of satellite processing with Image Sequencer was shifted to a analysis via a python/jupyter notebook environment that provided more comprehensive geospatial libraries. Image Sequencer work was shifted to the microscope calibration module to demonstrate and provide a well known use case.

@gauravano @sagarpreet @warren