Skip to content

Commit

Permalink
Document snapping wfsMaxScale
Browse files Browse the repository at this point in the history
  • Loading branch information
manisandro committed Jan 4, 2024
1 parent 314e137 commit b0cce69
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions src/topics/Snapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,16 +11,18 @@ QWC2 ships a plugin for snapping support while drawing (redlining / measuring /
"max": <max_scale>
}
],
"featureCount": <feature_count>
"featureCount": <feature_count>,
"wfsMaxScale": <wfs_max_scale>
}
...
```
where:

- `layername` is the name of the theme sublayer from which to retreive the snapping geometries
- `min` is the minimum scale denominator (inclusive) from which this layer should be used for snapping
- `max` is the maximum scale denominator (exclusive) up to which this layer should be used for snapping
- `layername` is the name of the theme sublayer from which to retreive the snapping geometries.
- `min` is the minimum scale denominator (inclusive) from which this layer should be used for snapping.
- `max` is the maximum scale denominator (exclusive) up to which this layer should be used for snapping.
- `feature_count` is the maximum number of snapping geometries to retreive for the current map extent (default: 500).
- `wfs_max_scale` is the maximum scale denominator (exclusive) up to which loaded WFS layers should be used for snapping.

*Note*: Snapping works by querying the geometries of all snapping layers inside the scale range via WMS GetFeatureInfo and refreshing the geometries every time the map extent changes. Therefore, it is recommended to ensure the geometry complexity of the snap layers is appropriate for the specified scale ranges to avoid overloading the server with the GetFeatureInfo requests. Also, the QGIS project will need to be configured so that snap layers are queryable and that feature info responses contain geometries.

Expand Down

0 comments on commit b0cce69

Please sign in to comment.