RE: Vector Data Node and ROIs

2009-11-20T07:32:00Z

Luis Veci:

The vector data node is looking very good. Has it settled now and we can begin using the API?

Yes, but still you need to be aware of changes. The class org.esa.beam.framework.datamodel.VectorDataNode is currently used only as a data source for bitmasks derived from shapes (FeatureCollection). There is no other support, e.g. we still cannot read/write vector data or let the user add new vector datasets.

Luis Veci:

As far as the ROIs go, what plans do you have in the next couple of weeks?
Should the AbstractCreateFigureTool insert the figure into the products vectorData node?
Should the drawingEditor display all vectors in the product or should something be specifically be designated as an ROI?

We are focusing our work on shape creation, selection & editing. The existing Figure (beam-core) and Tool (beam-ui) APIs will completely revised or deprecated or even removed. The new idea is as as you guess: at the time a user creates a new shape, a vector data node is created which will serve as the data container for the shape and its attributes. While new vector data nodes are being created, corresponding shape bitmasks will be available on the fly. These can be used as ROI, same as for all other types of bitmasks (e.g. band math masks). The statistics dialog will then also work for multiple, user-selectable bitmasks (=ROIs).

Norman

Vector Data Node and ROIs

2009-11-11T19:19:20Z

The vector data node is looking very good. Has it settled now and we can begin using the API?

As far as the ROIs go, what plans do you have in the next couple of weeks?
Should the AbstractCreateFigureTool insert the figure into the products vectorData node?
Should the drawingEditor display all vectors in the product or should something be specifically be designated as an ROI?

Thanks
Luis