Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling of Mosaics in MSv4 #314

Open
dpetry opened this issue Nov 21, 2024 · 0 comments
Open

Handling of Mosaics in MSv4 #314

dpetry opened this issue Nov 21, 2024 · 0 comments

Comments

@dpetry
Copy link

dpetry commented Nov 21, 2024

As discussed with Jan-Willem, the MSv4 originally was meant to contain data for only one Field
such that multi-field MSs would need to be stored in several MSv4 inside one Processing Set.
Later the MSv4 was modified to permit more than one Field.
So, for mosaics, i.e. observations of the same target with the same array in one execution block
sequentially moving over a set of Fields (in the ASDM and MSv2, they all have the same Field Name
but not the same Field ID), the questions are:

  1. Do the data belonging to the many fields (potentially hundreds) of the same mosaic all get stored
    in one MSv4 or do they get spread over many MSv4s?
    What should be the default behaviour?
  2. How can a piece of software reading the data recognise that it is dealing with a Mosaic?
  3. How can the reading software determine the extend of the Mosaic (total number of fields, spatial extent)?
    In other words, how is the metadata of the mosaic set in the first place and then made available?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant