[Feature]: Support WMTS tile matrix sets with projections other than Web Mercator
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the WMTS capabilities parsing and tile rendering entry points to find where EPSG:3857 is assumed; the issue does not name specific files or tests. The requested work includes reading CRS and tile matrix definitions, handling different grids, and displaying layers with reprojection, and may be split into native matrix support and reprojection. Done means WMTS layers using non-Web Mercator projections can be added and displayed.
Written by the indexing model from the issue text.
Description
Before you start
- I searched the existing issues and roadmap and did not find a duplicate request.
What problem does this solve?
RustGIS currently only supports WMTS layers using a Web Mercator (EPSG:3857) tile matrix set. Especially on austrian open data platform (data.gv.at) most WMTS datasets are not in Web Mercator but in their own regional CRS.
Many WMTS services, especially national and regional geodata services, use other coordinate reference systems (e.g. EPSG:4326 or EPSG:2056). These layers currently cannot be added to RustGIS.
Proposed solution
Support WMTS tile matrix sets using coordinate systems other than EPSG:3857.
Ideally, RustGIS should:
- Read the CRS and tile matrix definitions from WMTS capabilities.
- Support different tile grid origins, resolutions and matrix dimensions.
- Display WMTS layers in maps using a different projection, with on-the-fly reprojection where necessary.
The implementation could be split into native tile matrix support and reprojection.
Estimated scope
Wishlist: a larger or longer-term idea.
Alternatives considered
Use a WMTS endpoint that provides EPSG:3857, if available.
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 268
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 611
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opengeos/RustGIS
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
unconfirmed possible issue
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
opengeos/RustGIS#846 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in opengeos/RustGIS
Similar issues
-
bug easy good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lacs-project/sysknife#659 ·
Maintainers usually reply within 2 days
-
E_FIT_INPUT_MISSING (mixture overrides): the message says ferx-r bundles lack mixture_overridesOpenP3
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
registrystack/registry-stack#2431 ·
Maintainers usually reply within 1 day
-
contribution
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
farion1231/cc-switch#8863 · 1 comment ·
Maintainers usually reply within 1 day