Skip to content

Commit 2b9db8b

Browse files
committed
update RFC5
1 parent ac2eb2e commit 2b9db8b

File tree

1 file changed

+4
-4
lines changed
  • docs/development/rfc

1 file changed

+4
-4
lines changed

docs/development/rfc/5.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ pygeoapi will define a `limits` configuration parameter that will allow a user t
2727

2828
```yaml
2929
limits:
30-
items_default: 10 # applies to vector data
31-
items_max: 500 # applies to vector data
30+
default_items: 20 # applies to vector data
31+
max_items: 500 # applies to vector data
3232
max_distance_x: 123 # applies to all datasets
3333
max_distance_y: 456 # applies to all datasets
3434
max_distance_units: m # as per UCUM https://ucum.org/ucum#section-Tables-of-Terminal-Symbols
@@ -38,8 +38,8 @@ limits:
3838
The `limits` setting will be applied as follows:
3939

4040
- pygeoapi administrator is able to use at both the `server` and `resources` levels, with `resources` limits overriding server wide `limits` settings
41-
- no limit specified by client: use `limits.items_default` to set the result set size
42-
- limit specified by client: calculate the minimum of the query parameter and `limits.items_max` to set the result set size
41+
- no limit specified by client: use `limits.default_items` to set the result set size
42+
- limit specified by client: calculate the minimum of the query parameter and `limits.max_items` to set the result set size
4343
- bbox or spatial dimensions: compare distance of request to maximum definition allowed in `limits.max_distance_x` and `limits.max_distance_y`
4444

4545
## Implementation

0 commit comments

Comments
 (0)