-
Notifications
You must be signed in to change notification settings - Fork 1
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
Flexible "re-purposing" of resources #96
Labels
Milestone
Comments
p-a-s-c-a-l
added
enhancement
New feature or request
BB: Map Component
Map Component Building Block
labels
May 12, 2020
p-a-s-c-a-l
added a commit
that referenced
this issue
May 15, 2020
p-a-s-c-a-l
added a commit
that referenced
this issue
May 18, 2020
p-a-s-c-a-l
added a commit
that referenced
this issue
May 18, 2020
p-a-s-c-a-l
added a commit
that referenced
this issue
May 18, 2020
Example on how to configure an Extended iFrame: const additionalQueryParameters = {
clarityBackgroundLayersTagType:'taxonomy_term--dp_resourcetype',
clarityBackgroundLayersTagName:'clarity-background-layer',
clarityBackgroundLayersGroupName:'Elements at Risk',
overlayLayersTagType:'taxonomy_term--eu_gl',
overlayLayersTagName:'Exposure Evaluation',
overlayLayersGroupName:'Additional Elements at Risk',
overlayLayersGroupingTagType:'taxonomy_term--elements_at_risk'
}; |
Consider adding support for multiple overlayLayers groups. |
done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We have to implement a strategy for flexible "re-rurposing" of resources. The reason and details are explained in clarity-h2020/data-package#65 (comment).
In principle we have to arbitrarily groups/categorise resources/layers irrespective of their conceptual assignment to EU-GL modules. Instead of relying on EU-GL taxonomy for layer selection and grouping, we have not only to support multiple taxonomies but also to re-label certain layer groups depending on EU-GL context: CLARITY Backgrounds' (HC-LE input layers) --> 'Exposure' in 'Evaluate Exposure' step.
The text was updated successfully, but these errors were encountered: