Update Dev Guide - Add new missing GeoServer Extensions#10436
Merged
Update Dev Guide - Add new missing GeoServer Extensions#10436
Conversation
7 tasks
tdipisa
requested changes
Jul 5, 2024
| - [WMTS Multidimensional](https://docs.geoserver.org/stable/en/user/extensions/wmts-multidimensional/index.html) despite the name, this service provides multidimensional discovery services for GeoServer in general, not only for WMTS, and it is **required** to use the timeline plugin of MapStore. | ||
|
|
||
| - [SLD Rest Service](https://docs.geoserver.org/latest/en/user/extensions/sldservice/index.html): This extension can be used by the MapStore styler to classify Vector and Raster data. It can inspect the real layer data to apply classification based on values contained in it. It allows to select various classification types (quantile, equalInterval, standardDeviation…) and to customize the color scales based on parameters | ||
| - [SLD Rest Service](https://docs.geoserver.org/latest/en/user/extensions/sldservice/index.html): this extension can be used by the MapStore styler to classify Vector and Raster data. It can inspect the real layer data to apply classification based on values contained in it. It allows to select various classification types (quantile, equalInterval, standardDeviation…) and to customize the color scales based on parameters |
Member
There was a problem hiding this comment.
if you decided to use docs.geoserver.org/stable always use it. Thank you
| - **gs:PagedUnique**: provide a way to query layer attribute values with pagination and filtering by unique values. It enables autocomplete of attribute values for feature grid, attribute table, filter layer and other plugins. | ||
| - **gs:Aggregate**: allows aggregation operation on vector layers. This can be used by the charts (widgets, dashboards) to catch data | ||
| - **gs:Bounds**: allows to calculate bounds of a filtered layer, used to dynamically zoom in dashboards map, when filtering is active. | ||
| - **geo:buffer**: provide a way to create a new vector layer around the source layer. This can be used from the *GeoProcessing* plugin buffer option. |
Member
There was a problem hiding this comment.
please put a link to the geoprocessing tool section
| - **gs:Aggregate**: allows aggregation operation on vector layers. This can be used by the charts (widgets, dashboards) to catch data | ||
| - **gs:Bounds**: allows to calculate bounds of a filtered layer, used to dynamically zoom in dashboards map, when filtering is active. | ||
| - **geo:buffer**: provide a way to create a new vector layer around the source layer. This can be used from the *GeoProcessing* plugin buffer option. | ||
| - **gs:IntersectionFeatureCollection**: allows to return the intersection between two feature collections adding the attributes from both of them. This can be used from the *GeoProcessing* plugin intersection option. |
Member
There was a problem hiding this comment.
Suggested change
| - **gs:IntersectionFeatureCollection**: allows to return the intersection between two feature collections adding the attributes from both of them. This can be used from the *GeoProcessing* plugin intersection option. | |
| - **gs:IntersectionFeatureCollection**: allows to return the intersection between two feature collections adding the attributes from both of them. This is mandatory for the *GeoProcessing* plugin intersection option. |
Member
There was a problem hiding this comment.
please put a link to the geoprocessing tool section
| - **gs:PagedUnique**: provide a way to query layer attribute values with pagination and filtering by unique values. It enables autocomplete of attribute values for feature grid, attribute table, filter layer and other plugins. | ||
| - **gs:Aggregate**: allows aggregation operation on vector layers. This can be used by the charts (widgets, dashboards) to catch data | ||
| - **gs:Bounds**: allows to calculate bounds of a filtered layer, used to dynamically zoom in dashboards map, when filtering is active. | ||
| - **geo:buffer**: provide a way to create a new vector layer around the source layer. This can be used from the *GeoProcessing* plugin buffer option. |
Member
There was a problem hiding this comment.
Suggested change
| - **geo:buffer**: provide a way to create a new vector layer around the source layer. This can be used from the *GeoProcessing* plugin buffer option. | |
| - **geo:buffer**: provide a way to create a new vector layer around the source layer. This is mandatory for the *GeoProcessing* plugin buffer option. |
| - **gs:CollectGeometries**: allows to collect all the default geometries in a feature collection and returns them as a single geometry collection. This can be used by the *GeoProcessing* plugin to create a new layer. | ||
|
|
||
| - [WPS download community module](https://docs.geoserver.org/stable/en/user/community/wps-download/index.html): This additional module allows to improve the default download plugin, based on WFS, with more functionalities. | ||
| - [WPS download community module](https://docs.geoserver.org/stable/en/user/extensions/wps-download/index.html): this additional module allows to improve the default download plugin, based on WFS, with more functionalities. |
Member
There was a problem hiding this comment.
Suggested change
| - [WPS download community module](https://docs.geoserver.org/stable/en/user/extensions/wps-download/index.html): this additional module allows to improve the default download plugin, based on WFS, with more functionalities. | |
| - [WPS download community module](https://docs.geoserver.org/stable/en/user/extensions/wps-download/index.html): this additional module allows to improve the exporter plugin, based by default only on the WFS, providing asynchronous download capabilities. |
| - Define width and height of internal tiles | ||
|
|
||
| - [CSW Extension](https://docs.geoserver.org/latest/en/user/services/csw/installing.html): Activating this extension, MapStore can browse data of GeoServer using the CSW protocol. This is particularly useful when GeoServer contains hundreds or thousands of layers, so the WMS capabilities services can be too slow. | ||
| - [CSW Extension](https://docs.geoserver.org/latest/en/user/services/csw/installing.html): activating this extension, MapStore can browse data of GeoServer using the CSW protocol. This is particularly useful when GeoServer contains hundreds or thousands of layers, so the WMS capabilities services can be too slow. |
Member
There was a problem hiding this comment.
Suggested change
| - [CSW Extension](https://docs.geoserver.org/latest/en/user/services/csw/installing.html): activating this extension, MapStore can browse data of GeoServer using the CSW protocol. This is particularly useful when GeoServer contains hundreds or thousands of layers, so the WMS capabilities services can be too slow. | |
| - [CSW Extension](https://docs.geoserver.org/latest/en/user/services/csw/installing.html): activating this extension, MapStore can browse data of GeoServer using the CSW protocol, improving performances with paginated requests. This is particularly useful when a GeoServer instance contains hundreds or thousands of layers, so the output of the WMS capabilities services can be too slow. |
| - [CSW Extension](https://docs.geoserver.org/latest/en/user/services/csw/installing.html): activating this extension, MapStore can browse data of GeoServer using the CSW protocol. This is particularly useful when GeoServer contains hundreds or thousands of layers, so the WMS capabilities services can be too slow. | ||
|
|
||
| - [Query Layer Plugin](https://docs.geoserver.org/stable/en/user/extensions/querylayer/index.html#installing-the-querylayer-module): This plugin allows the possibility to do cross-layer filtering. Cross layer filtering is the mechanism of Filtering a layer using geometries coming from another layer. The plugin allows this filtering to be performed on the server side in an efficient way. | ||
| - [Query Layer Plugin](https://docs.geoserver.org/stable/en/user/extensions/querylayer/index.html#installing-the-querylayer-module): this plugin allows the possibility to do cross-layer filtering. Cross layer filtering is the mechanism of Filtering a layer using geometries coming from another layer. The plugin allows this filtering to be performed on the server side in an efficient way. |
Member
There was a problem hiding this comment.
Suggested change
| - [Query Layer Plugin](https://docs.geoserver.org/stable/en/user/extensions/querylayer/index.html#installing-the-querylayer-module): this plugin allows the possibility to do cross-layer filtering. Cross layer filtering is the mechanism of Filtering a layer using geometries coming from another layer. The plugin allows this filtering to be performed on the server side in an efficient way. | |
| - [Query Layer Plugin](https://docs.geoserver.org/stable/en/user/extensions/querylayer/index.html#installing-the-querylayer-module): this plugin allows the possibility to do cross-layer filtering. Cross layer filtering is the mechanism of filtering a layer using geometries coming from another layer. The plugin allows this filtering to be performed on the server side in an efficient way. |
|
|
||
| - [DDS/BIL Plugin](https://docs.geoserver.org/stable/en/user/community/dds/index.html): this plugin add to geoserver the possibility to publish raster data in DDS/BIL format (World Wind). This particular plugin is useful if we want to use a raster data as elevation model for MapStore. This elevation model will be used in 3D mode or with the mouse coordinates plugin (displaying the elevation of a point on the map, together with the coordinates). | ||
|
|
||
| - [WPS longitudinal profile process](https://docs.geoserver.org/stable/en/user/community/wps-longitudinal-profile/index.html): this plugin added to geoserver gives the possibility to calculate an altitude profile for the specified linestring and it is required to use the *Longitudinal Profile* plugin of MapStore. |
Member
There was a problem hiding this comment.
Suggested change
| - [WPS longitudinal profile process](https://docs.geoserver.org/stable/en/user/community/wps-longitudinal-profile/index.html): this plugin added to geoserver gives the possibility to calculate an altitude profile for the specified linestring and it is required to use the *Longitudinal Profile* plugin of MapStore. | |
| - [WPS longitudinal profile process](https://docs.geoserver.org/stable/en/user/community/wps-longitudinal-profile/index.html): this plugin added to geoserver gives the possibility to calculate an altitude profile on a given path and it is required to use the *Longitudinal Profile* plugin of MapStore. |
Member
There was a problem hiding this comment.
please put a link to the longitudinal profile tool section
tdipisa
approved these changes
Jul 8, 2024
tdipisa
added
the
BackportNeeded
Member
|
@ElenaGallo please check and backport once done. Thank you. |
ElenaGallo
removed
the
BackportNeeded
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update the GeoServer section on Dev Guide