Repository navigation
Services: follow-ups to #924 (a plainer note, /items in any case, the timeout hint only without bbox) - #944
Conversation
…in any case (opengeos#819) The note no longer says the service can't be asked for an area when the address already filters or is a plain file. An OGC API items path is found whatever its case, as an ArcGIS query is. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pengeos#819) When an area was asked for but its request couldn't carry it (WFS 1.0, the antimeridian), the timeout error no longer suggests the bbox already given. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
OGC API path matching crates/data/src/ogc.rs |
A private helper recognizes terminal /items paths without regard to case and after trimming trailing slashes. Tests cover mixed-case paths and near matches. |
Fallback notices and timeout guidance crates/engine/src/cmd/service.rs, crates/engine/src/tests.rs, crates/ui-egui/src/serviceui.rs |
Fallback handling tracks whether a bounding box was supplied independently of whether an area-specific request URL was produced. The notice distinguishes antimeridian areas from requests that cannot carry an area. Timeout guidance depends on whether an area was supplied. The test expectation and UI notice use the request-focused wording. |
Priority:
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Bug fix
Possibly related issues
- [Feature]: Feature services: ask for the map's area, not the whole layer (WFS, OGC API Features, ArcGIS) #819: The changes concern area-aware feature-service requests and their fallback handling.
- [Feature]: Read large ArcGIS layers live, a view at a time (an ArcGIS FeatureSource) #829: The changes relate to extent-based service requests, but do not implement the live
FeatureSourcebehavior described by the issue.
Possibly related PRs
- opengeos/RustGIS#924: This PR changes area-aware service request behavior introduced there, including
/itemsmatching and fallback handling. - opengeos/RustGIS#823: This PR changes timeout guidance in the feature-download path affected by that PR’s pagination behavior.
Suggested reviewers: giswqs
Merge Risk: 
Minimal · up to 3fe54
-
The updated path matching, fallback notice, and timeout guidance are ready to merge with no identified merge-blocking risk.
Pre-merge checks: 
4 · 
1
-
Failed checks: 1 warning Passed checks: 4 passed-
Full details: Description check
-
Explanation
The description includes complete Summary and Testing sections with clear change details and validation information. It does not include the required Related issue section, but the related issues are identified in the Summary, so the description is mostly complete.
-
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the path at night,
“/Items/” now matches right.
If bounds were sent, the notes reflect,
If none were sent, the hints direct.
The map can rest beneath the moon,
While fallback messages land in tune.
Comment @coderabbitai help to get the list of available commands.
Code reviewThis is a small PR. It makes the Bugs
Security
Performance
Quality
AGENTS.md
Change sizeCompared: the whole PR against main (merge base 2f08089 to PR head 7accbbf)
|
📖 Docs preview
GitHub Pages takes a minute or two to publish a new commit. |
…geos#819) features_asked_for_over_an_area covers an items path in another case and with a trailing slash (now matched without allocating), and a new a_slow_whole_layer_suggests_bbox_only_when_none_was_given covers the hint. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Code reviewI found no bugs or security issues in this PR. It changes four files and I read the whole diff. What I checked
Bugs
Security
Performance
Quality
AGENTS.md
Change sizeCompared: the whole PR against main (merge base 2f08089 to PR head 3fe54bf)
|
Summary
Three small follow-ups to #924 (#819), from its reviews, which were committed after it was merged:
service.addand the From Service dialog used to say "the service can't be asked for an area". That was misleading for an address that already filters (bbox,CQL_FILTER, …) or a plain file. Both now say "its request can't carry an area, so the whole layer is asked for"./itemsin any case.features_in_areafinds an OGC API items path after lowercasing it, asis_arcgis_querydoes.bbox. When a whole layer runs pastservice.add's 60 s, the error suggests"bbox". It now depends on whether abboxwas given, not on whether the request could carry it. So a WFS 1.0 service, or an area across the antimeridian, isn't told to add thebboxit already has.Testing
features_asked_for_over_an_area: an items path in another case and with a trailing slash.a_slow_whole_layer_suggests_bbox_only_when_none_was_given: the hint with and without abbox; other errors left alone.service_features_asked_for_over_an_area: the note's new wording.cargo xtask cion Windows (cargo fmt --all --check,cargo clippy --workspace --all-targets -- -D warnings,cargo test --workspace, 2,341 tests, withRUSTGIS_LANGUAGE=en), onmainat2f08089.🤖 Generated with Claude Code
Summary by CodeRabbit
/itemspaths are now recognized regardless of letter casing, including paths with trailing slashes.bboxor"view"is shown only when no area was supplied.