Add more config options for layers in the Map Config #2187
Assignees
Labels
cesium
DRP
Issues related to the Defense Resiliency Platform
enhancement
pdg
Permafrost Discovery Gateway
Requested by: Hosted repo
Features requested by a DataONE hosted repository
Comments
robyngit
added
enhancement
pdg
robyngit
added a commit
that referenced
this issue
Aug 31, 2023
- Add MapInteraction, GeoPoint and GeoBoundingBox models - Make the CesiumWidgetView methods smaller and more modular - Move Map model attributes to the MapInteraction model (selectedFeatures, currentPosition, currentScale, and currentViewExtent) - In MapAsset models, listen for changes to cesiumOptions and update Cesium model - In map connectors, don't use new models as defaults to avoid instantiating new models unnecessarily - Pass GeoPoint and GeoScale models directly to the ScaleBarView Issues #2189, #2180, #2187
|
|
iannesbitt
added
the
Requested by: Hosted repo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The layers that show in the Cesium map are configured with JSON. We would like to add a few more configuration options to the layer config:
clickFeatureAction: This is currently set at the map level, to either "showDetails" or "zoom". With show details, a layer panel pops up with additional info about the feature. With zoom, the map zooms into the bounding sphere for that feature. There are cases where some layers should zoom on click(geohashes) and others should show details on click (other vector layers in a data catalog). If no action is set, it should default to the map-level behaviour.showOpacitySlider: Set to false to hide the opacity slider for layers that don't really need one, e.g. the Permafrost Tours layer in the PDG which has only one PIN on the map. This should default to true to be consistent with the current functionality.showInLayerList: Set to false to hide this layer in the layer list. Defaults to true. This will be used for issue Enable drawing arbitrary polygons on the Cesium map #2180, because we don't want to show the layer that we create that stores the polygon a user draws on the map. It could also be useful for any layers a portal wants shown all the time - e.g. a base layer.The text was updated successfully, but these errors were encountered: