{modalLayerInfo && (
);
case 'cmr':
@@ -89,6 +89,7 @@ export function Layer(props: LayerProps) {
hidden={!isVisible}
opacity={opacity}
onStatusChange={onStatusChange}
+ colorMap={colorMap}
/>
);
case 'raster':
@@ -105,6 +106,7 @@ export function Layer(props: LayerProps) {
hidden={!isVisible}
opacity={opacity}
onStatusChange={onStatusChange}
+ colorMap={colorMap}
/>
);
default:
diff --git a/app/scripts/components/exploration/data-utils-no-faux-module.ts b/app/scripts/components/exploration/data-utils-no-faux-module.ts
index 01d4583f9..3bf0d5c66 100644
--- a/app/scripts/components/exploration/data-utils-no-faux-module.ts
+++ b/app/scripts/components/exploration/data-utils-no-faux-module.ts
@@ -58,6 +58,10 @@ function getInitialMetrics(data: DatasetLayer): DataMetric[] {
return foundMetrics;
}
+function getInitialColorMap(dataset: DatasetLayer): string {
+ return dataset.sourceParams?.colormap_name ?? 'viridis';
+}
+
export function reconcileDatasets(
ids: string[],
datasetsList: EnhancedDatasetLayer[],
@@ -75,7 +79,6 @@ export function reconcileDatasets(
if (!dataset) {
throw new Error(`Dataset [${id}] not found`);
}
-
return {
status: DatasetStatus.IDLE,
data: dataset,
@@ -83,7 +86,8 @@ export function reconcileDatasets(
settings: {
isVisible: true,
opacity: 100,
- analysisMetrics: getInitialMetrics(dataset)
+ analysisMetrics: getInitialMetrics(dataset),
+ colorMap: getInitialColorMap(dataset)
},
analysis: {
status: DatasetStatus.IDLE,
@@ -130,6 +134,77 @@ export function resolveLayerTemporalExtent(
}
}
+const hasValidSourceParams = (params) => {
+ return params && 'colormap_name' in params && 'rescale' in params;
+};
+
+/**
+ * Util to flatten and process rescale values,
+ *
+ * The need for flattening is because the `rescale` values can be received
+ * in different formats depending on their source. When parsing through Parcel,
+ * `rescale` values are typically a flat array (e.g., [0, 0.1, 0.01, 0.2]).
+ * However, when these values come from the back-end, they may be nested,
+ * like `[[0, 0.1], [0.01, 0.2]]`.
+ *
+ * To ensure consistency across the application and guard against any nesting
+ * issues (especially when working with multiple pairs of tuples from the back-end),
+ * this function flattens the input array and calculates the global minimum and maximum values.
+ * This guarantees that the `rescale` values are always returned in the correct [min, max] format.
+ *
+ * @param rescale - A potentially nested array of rescale values.
+ * @returns A tuple containing the minimum and maximum values [min, max].
+ */
+function flattenAndCalculateMinMax(rescale: number[]): [number, number] {
+ const flattenArray = (arr: number[]): number[] => arr.flat(Infinity);
+
+ const rescaleArray = flattenArray(rescale);
+
+ const min = Math.min(...rescaleArray);
+ const max = Math.max(...rescaleArray);
+
+ return [min, max];
+}
+
+// renderParams precedence: Start with sourceParams from the dataset.
+// If it's not defined, check for the dashboard render configuration in queryData.
+// If still undefined, check for asset-specific renders using the sourceParams' assets
+// property.
+export function resolveRenderParams(
+ datasetSourceParams: Record | undefined,
+ queryDataRenders: Record | undefined
+): Record | undefined {
+ let renderParams: Record | undefined;
+ // Start with sourceParams from the dataset.
+ if (hasValidSourceParams(datasetSourceParams)) {
+ renderParams = datasetSourceParams;
+ }
+
+ // Check for the dashboard render configuration in queryData if not defined.
+ if (!renderParams && queryDataRenders?.dashboard) {
+ renderParams = queryDataRenders.dashboard;
+
+ if (renderParams?.rescale) {
+ renderParams.rescale = flattenAndCalculateMinMax([renderParams.rescale]);
+ }
+ }
+
+ // Check for asset-specific renders using the sourceParams' assets property.
+ if (!renderParams && queryDataRenders?.[datasetSourceParams?.assets]) {
+ renderParams = queryDataRenders[datasetSourceParams?.assets];
+
+ if (renderParams?.rescale) {
+ renderParams.rescale = flattenAndCalculateMinMax(renderParams.rescale);
+ }
+ }
+
+ if (renderParams?.rescale) {
+ renderParams.rescale = flattenAndCalculateMinMax(renderParams.rescale);
+ }
+
+ return renderParams;
+}
+
export function getTimeDensityStartDate(date: Date, timeDensity: TimeDensity) {
switch (timeDensity) {
case TimeDensity.MONTH:
diff --git a/app/scripts/components/exploration/data-utils.ts b/app/scripts/components/exploration/data-utils.ts
index e677b350d..845eeefa8 100644
--- a/app/scripts/components/exploration/data-utils.ts
+++ b/app/scripts/components/exploration/data-utils.ts
@@ -10,17 +10,10 @@ import eachMonthOfInterval from 'date-fns/eachMonthOfInterval';
import {
EnhancedDatasetLayer,
StacDatasetData,
- TimeDensity,
- TimelineDataset,
- DatasetStatus
+ TimeDensity
} from './types.d.ts';
-import {
- DataMetric,
- DATA_METRICS,
- DEFAULT_DATA_METRICS
-} from './components/datasets/analysis-metrics';
import { veda_faux_module_datasets } from '$data-layer/datasets';
-import { DatasetLayer, DatasetData, VedaDatum } from '$types/veda';
+import { DatasetData, VedaDatum } from '$types/veda';
import { utcString2userTzDate } from '$utils/date';
// @TODO: This file should be deprecated and merged with `data-utils-no-faux-module`
@@ -85,80 +78,6 @@ export const datasetLayers = Object.values(veda_faux_module_datasets).flatMap(
}
);
-/**
- * Returns an array of metrics based on the given Dataset Layer configuration.
- * If the layer has metrics defined, it returns only the metrics that match the
- * ids. Otherwise, it returns all available metrics.
- *
- * @param data - The Datase tLayer object to get metrics for.
- * @returns An array of metrics objects.
- */
-function getInitialMetrics(data: DatasetLayer): DataMetric[] {
- const metricsIds = data.analysis?.metrics ?? [];
-
- if (!metricsIds.length) {
- return DEFAULT_DATA_METRICS;
- }
-
- const foundMetrics = metricsIds
- .map((metric: string) => {
- return DATA_METRICS.find((m) => m.id === metric)!;
- })
- .filter(Boolean);
-
- return foundMetrics;
-}
-
-/**
- * Converts the datasets to a format that can be used by the timeline, skipping
- * the ones that have already been reconciled.
- *
- * @param ids The ids of the datasets to reconcile.
- * @param datasetsList The list of datasets layers from VEDA
- * @param reconciledDatasets The datasets that were already reconciled.
- */
-
-// @TODO: Assuming that all the datasets are added only through this method
-// We can find a dataset that a layer belongs to in this method
-// Include it as a part of returned value
-
-export function reconcileDatasets(
- ids: string[],
- datasetsList: EnhancedDatasetLayer[],
- reconciledDatasets: TimelineDataset[]
-): TimelineDataset[] {
- return ids.map((id) => {
- const alreadyReconciled = reconciledDatasets.find((d) => d.data.id === id);
-
- if (alreadyReconciled) {
- return alreadyReconciled;
- }
-
- const dataset = datasetsList.find((d) => d.id === id);
-
- if (!dataset) {
- throw new Error(`Dataset [${id}] not found`);
- }
-
- return {
- status: DatasetStatus.IDLE,
- data: dataset,
- error: null,
- settings: {
- isVisible: true,
- opacity: 100,
- analysisMetrics: getInitialMetrics(dataset)
- },
- analysis: {
- status: DatasetStatus.IDLE,
- data: null,
- error: null,
- meta: {}
- }
- };
- });
-}
-
export function resolveLayerTemporalExtent(
datasetId: string,
datasetData: StacDatasetData
diff --git a/app/scripts/components/exploration/hooks/use-stac-metadata-datasets.ts b/app/scripts/components/exploration/hooks/use-stac-metadata-datasets.ts
index 505d5c057..9ce184919 100644
--- a/app/scripts/components/exploration/hooks/use-stac-metadata-datasets.ts
+++ b/app/scripts/components/exploration/hooks/use-stac-metadata-datasets.ts
@@ -11,7 +11,10 @@ import {
DatasetStatus,
VizDataset
} from '../types.d.ts';
-import { resolveLayerTemporalExtent } from '../data-utils-no-faux-module';
+import {
+ resolveLayerTemporalExtent,
+ resolveRenderParams
+} from '../data-utils-no-faux-module';
import { useEffectPrevious } from '$utils/use-effect-previous';
import { SetState } from '$types/aliases';
@@ -43,12 +46,19 @@ function reconcileQueryDataWithDataset(
if (queryData.status === DatasetStatus.SUCCESS) {
const domain = resolveLayerTemporalExtent(base.data.id, queryData.data);
+
+ const renderParams = resolveRenderParams(
+ base.data.sourceParams,
+ queryData.data.renders
+ );
+
base = {
...base,
data: {
...base.data,
...queryData.data,
- domain
+ domain,
+ sourceParams: renderParams
}
};
}
@@ -112,13 +122,16 @@ async function fetchStacDatasetById(
? data.summaries.datetime
: data.extent.temporal.interval[0];
+ const renders = data.renders;
+
if (!domain?.length || domain.some((d) => !d)) {
throw new Error('Invalid datetime domain');
}
return {
...commonTimeseriesParams,
- domain
+ domain,
+ renders
};
}
}
diff --git a/app/scripts/components/exploration/types.d.ts.ts b/app/scripts/components/exploration/types.d.ts.ts
index 2b8aa9fc3..b6daad9f4 100644
--- a/app/scripts/components/exploration/types.d.ts.ts
+++ b/app/scripts/components/exploration/types.d.ts.ts
@@ -18,6 +18,7 @@ export interface StacDatasetData {
isPeriodic: boolean;
timeDensity: TimeDensity;
domain: string[];
+ renders?: Record | undefined;
}
export interface AnalysisTimeseriesEntry {
@@ -102,6 +103,8 @@ export interface DatasetSettings {
opacity?: number;
// Active metrics for the analysis chart.
analysisMetrics?: DataMetric[];
+ // Active colormap of the layer.
+ colorMap?: string;
}
// Any sort of meta information the dataset like:
diff --git a/app/scripts/styles/styles.scss b/app/scripts/styles/styles.scss
index fe8a60858..6ad56627d 100644
--- a/app/scripts/styles/styles.scss
+++ b/app/scripts/styles/styles.scss
@@ -4,4 +4,5 @@
@use "usa-layout-grid";
@use "usa-banner";
@use "usa-button";
-@use "usa-card";
+@use "usa-icon";
+@use "usa-card";
\ No newline at end of file
diff --git a/app/scripts/types/veda.ts b/app/scripts/types/veda.ts
index 1a4edf7fa..0bbfcdbbb 100644
--- a/app/scripts/types/veda.ts
+++ b/app/scripts/types/veda.ts
@@ -132,6 +132,7 @@ export interface LayerLegendGradient {
min: string | number;
max: string | number;
stops: string[];
+ colorMap?: string;
}
interface CategoricalStop {
diff --git a/docs/content/frontmatter/layer.md b/docs/content/frontmatter/layer.md
index b52dd7785..c2c9332b3 100644
--- a/docs/content/frontmatter/layer.md
+++ b/docs/content/frontmatter/layer.md
@@ -34,85 +34,93 @@ info: Info
> 🙋 Several layer properties support functions to provide the app with dynamic values. See [Function values](#function-values) at the end of the document for details.
-**id**
-`string`
-Id of the layer, using lowercase characters and dashes (Example: `no2-monthly-diff`).
-Must be unique in a dataset.
+**id**
+`string`
+Id of the layer, using lowercase characters and dashes (Example: `no2-monthly-diff`).
+Must be unique in a dataset.
-**stacCol**
-`string`
+**stacCol**
+`string`
The stac collection that this layer should load.
-**stacApiEndpoint**
-`string`
+**stacApiEndpoint**
+`string`
The stac api endpoint that has the collection. If not defined, environment variable `API_STAC_ENDPOINT` is used.
-**tileApiEndpoint**
-`string`
+**tileApiEndpoint**
+`string`
The tile endpoint to use. If not defined, environment variable `API_RASTER_ENDPOINT` is used.
-**name**
-`string`
+**name**
+`string`
Name of the layer for display purposes.
-**type**
-`raster | vector`
-The type of the layer will define how the data is displayed on the map.
+**type**
+`raster | vector`
+The type of the layer will define how the data is displayed on the map.
⚠️ Vector datasets are should be in vector titles format with a source layer named `default`. It is currently not possible to customize the style of the dataset's features.
-**description**
-`string`
+**description**
+`string`
Brief description of the layer. Will be shown in an info box.
-**initialDatetime**
-`'oldest' | 'newest' | Date(YYYY-MM-DD) = 'newest'`
+**initialDatetime**
+`'oldest' | 'newest' | Date(YYYY-MM-DD) = 'newest'`
Define the initial date that is shown when enabling a timeseries layer. This value is used if no valid date is provided via the url parameters
-**zoomExtent**
-`[int, int] | fn(bag)`
-Minimum and maximum zoom values for the layer. Below the minimum zoom level the layer will not be shown, but markers will be displayed to indicate where data is available.
+**zoomExtent**
+`[int, int] | fn(bag)`
+Minimum and maximum zoom values for the layer. Below the minimum zoom level the layer will not be shown, but markers will be displayed to indicate where data is available.
For raster and zarr layer, only minimum zoom will be respected and the maximum zoom will be automatically fetched from STAC endpoint.
-**sourceParams**
-`object`
-Parameters to be appended to the tile source. The values will be used as provided as query string parameters.
-These values may vary greatly depending on the layer being added but some may be:
-- **rescale**
- `[int, int] | fn(bag)`
- Minimum and maximum value for the rescale. This value is used for the color mapping, such that the minimum value corresponds to the starting color of the color map, and the maximum value corresponds to the ending. Adjusting this value changes the underlying data values mapped to the colors allowing for the analysis of different trends.
-- **colormap_name**
- `string`
- The colormap to use for the layer. One of https://cogeotiff.github.io/rio-tiler/colormap/#default-rio-tilers-colormaps
+**sourceParams**
+`object`
+Parameters to be appended to the tile source. These values will be used as query string parameters and their priority is determined based on the following precedence:
+
+1. **Start with the configuration in the `sourceParams` of the dataset.**
+2. **If not defined, fallback to the dashboard render configuration from the STAC endpoint.**
+3. **If still undefined, check for asset-specific renders using the `sourceParams`' `assets` property.**
+4. **Finally, default to `{colormap_name: 'viridis'}` if all else fails.**
+
+These values can vary depending on the layer being added, but common parameters include:
+
+- **rescale**
+ `[int, int] | fn(bag)`
+ The minimum and maximum values for rescale, used for color mapping. The minimum value corresponds to the start of the color map, and the maximum value corresponds to the end. Adjusting these values changes the data-to-color mapping, allowing for analysis of different data trends. Rescale values follow the defined precedence, starting with the `sourceParams` configuration.
+- **colormap_name**
+ `string`
+ The colormap to be used for the layer. This can be one of the supported color maps from [rio-tiler](https://cogeotiff.github.io/rio-tiler/colormap/#default-rio-tilers-colormaps) or from the curated list of color maps in the back-end, as described [here](https://openveda.cloud/api/raster/colorMaps). The precedence follows the same rules as `rescale`, and if no colormap is specified or found, the default will be `viridis`.
- **minzoom**
-The minimum zoom of the layer. Map tiles below the minzoom will not be loaded/shown.
+ `integer`
+ The minimum zoom level for displaying the layer. Map tiles below this zoom level will not be loaded or shown.
- **maxzoom**
-The maximum zoom of the layer. Map tiles over the maxzoom will not be loaded/shown.
-
+ `integer`
+ The maximum zoom level for displaying the layer. Map tiles above this zoom level will not be loaded or shown.
-**bounds**
-`[int, int, int, int] | fn(bag)`
+**bounds**
+`[int, int, int, int] | fn(bag)`
Initial bounds for the map. This is useful for adjusting the initial view on datasets for which the STAC bounds are not appropriate.
This property should be an array with 4 numbers, representing the minimum and maximum longitude and latitude values, in the following order: [minLongitude, minLatitude, maxLongitude, maxLatitude].
Example (world bounds)
```yml
-bounds: [-180, -90, 180, 90]
+bounds: [-180, -90, 180, 90]
```
-Note on bounds and dataset layer switching:
+Note on bounds and dataset layer switching:
The exploration map will always prioritize the position set in the url. This is so that the user can share a link to a specific location. However, upon load the map will check if the position set in the url is within or overlapping the bounds of the dataset layer. If it is not, the map will switch to the dataset layer bounds avoiding showing an empty map when the user shares a link to a location that is not within the dataset layer bounds.
If there are no bounds set in the dataset configuration, the bbox from the STAC catalog will be used if available, otherwise it will default to the world bounds.
-**basemapId**
-`'dark' | 'light' | 'satellite' | 'topo' | fn(bag)`
+**basemapId**
+`'dark' | 'light' | 'satellite' | 'topo' | fn(bag)`
Initial basemap used when a dataset layer is enabled.
### Projection
-**projection**
-`object`
+**projection**
+`object`
Define the starting [projection](https://docs.mapbox.com/mapbox-gl-js/guides/projections/) to use for this layer. The user will still be able to change the projection as they explore the map, but an initial one may be defined.
```yaml
@@ -121,22 +129,22 @@ center: [int, int]
parallels: [int, int]
```
-**projection.id**
-`albers | equalEarth | equirectangular | lambertConformalConic | mercator | naturalEarth | winkelTripel | globe | polarNorth | polarSouth`
+**projection.id**
+`albers | equalEarth | equirectangular | lambertConformalConic | mercator | naturalEarth | winkelTripel | globe | polarNorth | polarSouth`
The id of the projection to set. Besides all the projections offered by mapbox, veda supports two additional ones `polarNorth | polarSouth`. These are not true polar projections but are achieved using specific `center` and `parallels` values of the `lambertConformalConic` projection.
-**projection.center**
-`[int, int]`
+**projection.center**
+`[int, int]`
Projection center. Required for Conic projections like `lambertConformalConic` and `albers`.
-**projection.parallels**
-`[int, int]`
+**projection.parallels**
+`[int, int]`
Projection parallels. Required for Conic projections like `lambertConformalConic` and `albers`.
### Legend
-**legend**
-`object`
+**legend**
+`object`
Legend for this layer. This is shown in the interface as a visual guide to the user. The resulting legend will depend on the selected type.
```yaml
@@ -152,8 +160,8 @@ stops: string[] | object[]
label: string
```
-**legend.type**
-`categorical | gradient`
+**legend.type**
+`categorical | gradient`
@@ -182,27 +190,27 @@ A `categorical` legend will display discreet color buckets according to the defi
-**legend.unit**
-`object`
+**legend.unit**
+`object`
Settings for the unit.
-**legend.unit.label**
-`string`
+**legend.unit.label**
+`string`
Unit label. Shown whenever a label for the values is needed. (Ex: The chart axis on the analysis page)
-**legend.min**
-`string`
-The label for the legend’s minimum value.
+**legend.min**
+`string`
+The label for the legend’s minimum value.
⚠️ Not used when the legend is `categorical`.
-**legend.max**
-`string`
-The label for the legend’s maximum value.
+**legend.max**
+`string`
+The label for the legend’s maximum value.
⚠️ Not used when the legend is `categorical`.
-**legend.stops**
-`string[] | object[]`
-The legend stops define the colors that should be rendered.
+**legend.stops**
+`string[] | object[]`
+The legend stops define the colors that should be rendered.
In the case of `gradient` legends, this should be an array of color strings:
```yaml
@@ -225,8 +233,8 @@ stops:
### Analysis
-**analysis**
-`object`
+**analysis**
+`object`
Configuration options for the analysis of the dataset layer.
```yaml
@@ -236,9 +244,9 @@ sourceParams:
exclude: boolean
```
-**analysis.metrics**
-`string[]`
-List of metric ids to enable by default when analysis is performed. The user will then be able to select which metrics to display.
+**analysis.metrics**
+`string[]`
+List of metric ids to enable by default when analysis is performed. The user will then be able to select which metrics to display.
Available metrics:
- min (Min)
- mean (Average)
@@ -247,24 +255,24 @@ Available metrics:
- median (Median)
- sum (Sum)
-**analysis.sourceParams**
+**analysis.sourceParams**
`object`
-Parameters to be appended to the `/statistics` endpoint as query parameters. Check [Titler documentations's /statistics POST request section](https://developmentseed.org/titiler/endpoints/cog/#statistics) to see which parameter is available.
+Parameters to be appended to the `/statistics` endpoint as query parameters. Check [Titler documentations's /statistics POST request section](https://developmentseed.org/titiler/endpoints/cog/#statistics) to see which parameter is available.
-**analysis.exclude**
-`boolean`
+**analysis.exclude**
+`boolean`
Controls whether this layer should be excluded from the analysis page. If set to `true` the layer will not be available for analysis.
-**media**
-`Media`
+**media**
+`Media`
Image to identify this layer. If not defined, the layer will use dataset level Media. See [media.md](./frontmatter/media.md) for details.
### Info
**info**
-List of key-value pair to describe layer level information.
+List of key-value pair to describe layer level information.
-Example:
+Example:
```yaml
info:
source: NASA
@@ -275,7 +283,7 @@ info:
**info.source**
`string`
-This key indicates the origin or the provider of the data.
+This key indicates the origin or the provider of the data.
**info.spatialExtent**
`string`
@@ -283,19 +291,19 @@ This key describes s the geographic coverage of the data.
**info.temporalResolution**
`string`
-This key describes the periodicity of the data.
+This key describes the periodicity of the data.
**info.unit**
`string`
-The unit key specifies the measurement unit in which the data values are expressed.
+The unit key specifies the measurement unit in which the data values are expressed.
### Compare
-**compare**
-`object`
-Through the compare settings it is possible to define which layer should be loaded when the comparison gets enabled.
+**compare**
+`object`
+Through the compare settings it is possible to define which layer should be loaded when the comparison gets enabled.
There are 2 ways of defining compare layers:
1. The first, and easiest, is when the layer we want to compare to, is defined as a layer of a dataset. In this case we only need to reference the `datasetId` and the `layerId` (besides the other meta properties).
@@ -324,18 +332,18 @@ compare:
mapLabel: string | fn
```
-**compare.mapLabel**
-`string | fn(bag)`
+**compare.mapLabel**
+`string | fn(bag)`
When the comparison is enabled, the user should be informed about what is being shown. Could be a static string like “Modeled vs Real” or something dynamic computed from input parameters. It is often used for operations with dates.
-**compare.datasetId**
-`string`
-Id of the dataset from which to get the layer.
+**compare.datasetId**
+`string`
+Id of the dataset from which to get the layer.
⚠️ Only used when the layer belongs to a dataset present in the application.
-**compare.layerId**
-`string`
-Id of the layer we want to compare to. The layer must belong to the dataset defined through `layer.compare.datasetId`.
+**compare.layerId**
+`string`
+Id of the layer we want to compare to. The layer must belong to the dataset defined through `layer.compare.datasetId`.
⚠️ Only used when the layer belongs to a dataset present in the application.
@@ -355,7 +363,7 @@ property: |
}
```
-All these functions will be resolved by the app with a parameter (`bag`) containing helpers and internal values to help determining the correct value.
+All these functions will be resolved by the app with a parameter (`bag`) containing helpers and internal values to help determining the correct value.
Properties of `bag`:
```js
{
@@ -368,7 +376,7 @@ Properties of `bag`:
Usage example:
```yaml
-property: |
+property: |
::js (bag) => {
return bag.foo ? 'bar' : 'baz'
}
diff --git a/mock/datasets/data-from-ghg.data.mdx b/mock/datasets/data-from-ghg.data.mdx
index b3e280d12..b32bfa0cc 100644
--- a/mock/datasets/data-from-ghg.data.mdx
+++ b/mock/datasets/data-from-ghg.data.mdx
@@ -59,7 +59,6 @@ layers:
- 20
sourceParams:
assets: npp
- colormap_name: purd
rescale:
- 0
- 0.3
@@ -108,7 +107,7 @@ layers:
- 20
sourceParams:
assets: rh
- colormap_name: purd
+ colormap_name: blues
rescale:
- 0
- 0.3
@@ -152,7 +151,7 @@ layers:
- 20
sourceParams:
assets: nee
- colormap_name: coolwarm
+ colormap_name: seismic
rescale:
- -0.1
- 0.1
diff --git a/parcel-resolver-veda/index.d.ts b/parcel-resolver-veda/index.d.ts
index 95bae9347..216313165 100644
--- a/parcel-resolver-veda/index.d.ts
+++ b/parcel-resolver-veda/index.d.ts
@@ -271,21 +271,21 @@ declare module 'veda' {
interface InternalNavLink {
title: string;
to: string;
- type: 'internalLink'
+ type: 'internalLink';
}
interface ExternalNavLink {
title: string;
href: string;
- type: 'externalLink'
+ type: 'externalLink';
}
- type NavLinkItem = (ExternalNavLink | InternalNavLink);
+ type NavLinkItem = ExternalNavLink | InternalNavLink;
export interface ModalNavLink {
title: string;
type: 'modal';
src: string;
}
-
- export interface DropdownNavLink {
+
+ export interface DropdownNavLink {
title: string;
type: 'dropdown';
children: NavLinkItem[];
@@ -334,7 +334,16 @@ declare module 'veda' {
export const getBoolean: (variable: string) => boolean;
export const getBannerFromVedaConfig: () => BannerData | undefined;
- export const getNavItemsFromVedaConfig: () => {mainNavItems: (NavLinkItem | ModalNavLink | DropdownNavLink)[]| undefined, subNavItems: (NavLinkItem | ModalNavLink | DropdownNavLink)[] | undefined } | undefined;
+ export const getNavItemsFromVedaConfig: () =>
+ | {
+ mainNavItems:
+ | (NavLinkItem | ModalNavLink | DropdownNavLink)[]
+ | undefined;
+ subNavItems:
+ | (NavLinkItem | ModalNavLink | DropdownNavLink)[]
+ | undefined;
+ }
+ | undefined;
/**
* List of custom user defined pages.
diff --git a/utils/fetch_colormaps.sh b/utils/fetch_colormaps.sh
new file mode 100755
index 000000000..96f343732
--- /dev/null
+++ b/utils/fetch_colormaps.sh
@@ -0,0 +1,75 @@
+#!/bin/bash
+
+# This script generates a TypeScript object containing colormaps grouped into three categories:
+# sequential, diverging, and mixed/rest colormaps. The colormaps are categorized based on the
+# groupings defined by Matplotlib (https://matplotlib.org/stable/users/explain/colors/colormaps.html).
+# It fetches the data from the specified URL and writes the fetched colormap data to 'colorMaps.ts'.
+# The currently hardcoded colormap lists (sequential and diverging) will eventually be replaced by
+# dynamically fetching the full list of colormaps directly from the colorMaps endpoint.
+
+# Sequential colormaps list (grouped based on Matplotlib's sequential colormaps)
+sequentialColorMaps=("afmhot" "algae" "autumn" "balance" "binary" "blues" "bone" "bugn" "bupu" "cividis" "cmrmap" "cool" "copper" "cubehelix" "gnbu" "gray" "greens" "greys" "haline" "hot" "inferno" "jet" "magma" "matter" "nipy_spectral" "ocean" "oranges" "pink" "plasma" "prgn" "pubu" "pubugn" "purd" "purples" "rain" "reds" "rplumbo" "schwarzwald" "thermal" "turbid" "turbo" "twilight" "twilight_shifted" "viridis" "wistia" "ylgn" "ylgnbu" "ylorbr" "ylorrd")
+
+# Diverging colormaps list (grouped based on Matplotlib's diverging colormaps)
+divergingColorMaps=("brbg" "brg" "bwr" "coolwarm" "piyg" "prgn" "puor" "rdbu" "rdgy" "rdpu" "rdylbu" "rdylgn" "seismic")
+
+# Array of colormaps supported by current VEDA back-end
+allColorMaps=("accent" "afmhot" "algae" "amp" "autumn" "balance" "binary" "blues" "bone" "brbg" "brg" "bugn" "bupu" "bwr" "cfastie" "cividis" "cmrmap" "cool" "coolwarm" "copper" "cubehelix" "curl" "dark2" "deep" "delta" "dense" "diff" "flag" "gist_earth" "gist_gray" "gist_heat" "gist_ncar" "gist_rainbow" "gist_stern" "gist_yarg" "gnbu" "gnuplot" "gnuplot2" "gray" "greens" "greys" "haline" "hot" "hsv" "ice" "inferno" "jet" "magma" "matter" "nipy_spectral" "ocean" "oranges" "orrd" "oxy" "paired" "pastel1" "pastel2" "phase" "pink" "piyg" "plasma" "prgn" "prism" "pubu" "pubugn" "puor" "purd" "purples" "rain" "rainbow" "rdbu" "rdgy" "rdpu" "rdylbu" "rdylgn" "reds" "rplumbo" "schwarzwald" "seismic" "set1" "set2" "set3" "solar" "spectral" "speed" "spring" "summer" "tab10" "tab20" "tab20b" "tab20c" "tarn" "tempo" "terrain" "thermal" "topo" "turbid" "turbo" "twilight" "twilight_shifted" "viridis" "winter" "wistia" "ylgn" "ylgnbu" "ylorbr" "ylorrd")
+
+url="https://openveda.cloud/api/raster/colorMaps"
+
+# Output file for TypeScript object
+outputFile="colorMaps.ts"
+
+# Start writing the TypeScript objects
+echo "export const sequentialColorMaps = {" > $outputFile
+
+for colorMap in "${allColorMaps[@]}"; do
+ response=$(curl -s "${url}/${colorMap}")
+
+ if [[ $response == \{* ]]; then
+ if [[ " ${sequentialColorMaps[@]} " =~ " ${colorMap} " ]]; then
+ echo " $colorMap: $response," >> $outputFile
+ fi
+ else
+ echo "Warning: Failed to fetch data for $colorMap"
+ fi
+done
+
+echo "};" >> $outputFile
+
+# Write diverging colormaps object
+echo "export const divergingColorMaps = {" >> $outputFile
+
+for colorMap in "${allColorMaps[@]}"; do
+ response=$(curl -s "${url}/${colorMap}")
+
+ if [[ $response == \{* ]]; then
+ if [[ " ${divergingColorMaps[@]} " =~ " ${colorMap} " ]]; then
+ echo " $colorMap: $response," >> $outputFile
+ fi
+ else
+ echo "Warning: Failed to fetch data for $colorMap"
+ fi
+done
+
+echo "};" >> $outputFile
+
+# Write rest/mixed colormaps object
+echo "export const restColorMaps = {" >> $outputFile
+
+for colorMap in "${allColorMaps[@]}"; do
+ response=$(curl -s "${url}/${colorMap}")
+
+ if [[ $response == \{* ]]; then
+ if [[ ! " ${sequentialColorMaps[@]} " =~ " ${colorMap} " && ! " ${divergingColorMaps[@]} " =~ " ${colorMap} " ]]; then
+ echo " $colorMap: $response," >> $outputFile
+ fi
+ else
+ echo "Warning: Failed to fetch data for $colorMap"
+ fi
+done
+
+echo "};" >> $outputFile
+
+echo "Color maps have been written to $outputFile"