Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
When adding vector data to a product, either by importing a shapefile or by drawing the geometry masks are created automatically. Those masks of type 'geometry' are not stored in BEAM-DIMAP. They are automatically recreated when the product is reopened based on the vector data nodes, but changed styling information gets lost. So, the geometry masks need to be stored in BEAM-DIMAP.
Environment
None
GitHub Work
None
Activity
Show:
Marco Peters 14 July 2021 at 07:28
After implementing that the geometry masks are saved to BEAM-DIMAP we tested the behaviour and observed issues which I have expected. Those have been resolved by handling masks a bit different, e.g. checking if masks are already present and then don’t generate a mask automatically.
stephen.plummer 30 June 2021 at 13:00
What has been done here to resolve your comment?
Marco Peters 2 June 2021 at 07:04
When implementing/testing attention should be payed to the reopen behaviour and if it works properly. There might be a conflict between automatic masks generation based on the VDNs and the created masks by the reader after implementing the change.
When adding vector data to a product, either by importing a shapefile or by drawing the geometry masks are created automatically.
Those masks of type 'geometry' are not stored in BEAM-DIMAP.
They are automatically recreated when the product is reopened based on the vector data nodes, but changed styling information gets lost. So, the geometry masks need to be stored in BEAM-DIMAP.