Hi, I also think we should store it either in a file, in the same directory as the image or in the CouchDB. For now I am not sure what the better solution is. The only requirement is that once a user downloads the data, the labels should be provided in a Coco-JSON file, but this is possible with both options.
Since we have now multiple locations where we store data, we probably should start a discussion of how to Store application data within StreamPipes. It might make sense to have an internal (or external) API for components and other service. How do you think about that? What kind of features would such an API need? Philipp > On 19. Feb 2020, at 22:00, Johannes Tex <[email protected]> wrote: > > Hi, > > I starts with @Dominik question: The first Intention was to be part of the > Data-Explorer, with toggling between simple exploring and labelling. @Philipp > opened an Issue [STREAMPIPES-79] to refactoring the Data explorer, maybe in > this context we could extend the data explorer for this two modes? > To display images, for example, we need almost the same mechanism like it is > necessary for the image labelling, except the Labeling itself. We also need > to extend the datalake API for images, which leads to @Philipp question. > > The data lake API supports, at the moment, just data that can be aggregated > (numeric data). For the Image Labeling and viewing we need to extend the API. > My proposal would be to create a paging API for images to the receive the > next e.g. 10 images: It could be like this "/datalake/<index> > /<timestamp>/<page>". What do you think? While this necessary extension we > also can create the API to save the annotation. > > I see three different options to save the annotations: > * Influx -> save annotation direct with data point > - when exporting need to create COCO file > - need extra place to save (image) Labels/Categories > - need to 'manupilate' data point, which is not possible in influx (just > delete and create new one) > * File > - need to handle a file > * CouchDB > - file generation is needed > My proposal is to use the CouchDB to use the annotations. > > Johannes > > > On 2020/02/17 21:12:38, Philipp Zehnder <[email protected]> wrote: >> Hi Johannes, >> >> as for the API, do you think we can extend the dataset API, or should we >> create a separate REST API for image annotation? >> >> Where do you plan to store the coco annotation information? In files or in a >> DB? >> >> Philipp >> >>> On 16. Feb 2020, at 19:51, Dominik Riemer <[email protected]> wrote: >>> >>> Hi Johannes, >>> sounds good! >>> I think bounding boxes and polygons are totally fine for the first >>> prototype. >>> >>> How to you plan to integrate the labeling tool, will it be part of the data >>> explorer or do you plan to add a new component? >>> >>> Dominik >>> >>> On 2020/02/14 16:30:17, Johannes Tex <[email protected]> wrote: >>>> Hi, >>>> >>>> Philip started to extend the datalake sink to store images >>>> [STREAMPIPES-75]. >>>> I started now to create an Image labeler that allows users to label images >>>> in the datalake. [STREAMPIPES-78]. The Labels will be stored in the COCO >>>> Annonation Format. [1] After labeling, the images can be used to train an >>>> NN. >>>> >>>> The main features that the labeler should support >>>> - Labeling with Bound boxes >>>> - Labeling with Polygons >>>> >>>> Do you have additional features that should also be supported? >>>> >>>> Johannes >>>> >>>> >>>> [1] http://cocodataset.org/#format-data >>>> >>>> >>>> >> >> >>
