[Dachs-support] Clarifications about new coverage and limits

[Yannick Roehlly]

Hi Markus,

I'm currently upgrading from DaCHS 2.3 to 2.5.

If I understand correctly the releases notes, now the spatial coverage is no 
more inserted into the <coverage> tag of the resource descriptor.  What is not 
clear is what we now need in the RD file.

If I completely remove the <coverage> tag, "dachs limits" tells me it's 
getting the stats for the table but no coverage is displayed on the service 
information page.  I suppose it's only computing the limits of the columns.  
It's the same if I have an empty <coverage> tag in the RD.

So I suppose we still need to have the <coverage> tag with the inner <updater> 
tag.  Am I right?

In some cases, I have several tables in a resource that spans different 
locations in the sky (different fields).  What is the best approach here? 
Before I was manually computing the MOC of the spatial coverage because having 
two <updater> in the coverage was not working, is it still the case?

If I understand correctly, the spatial coverage is associated to the resource, 
not to the service; so I have a resources with two tables on two field and two 
associated cone searches, the information page of each cone search can only 
see the full coverage.  Am I right?

Best regards,

Yannick

PS: A note for users having troubles displaying the coverages on the web 
pages. You need to have python3-healpy installed which is only a 
"recommendation" for DaCHS packages and may not be installed depending on how 
you install them.

-- 
We don't know one millionth of one percent about anything.