Modify ↓
#6432 closed defect (fixed)
WMS and TMS do not handle projection/projection changes correct
| Reported by: | stoecker | Owned by: | team |
|---|---|---|---|
| Priority: | critical | Component: | Core |
| Version: | Keywords: | ||
| Cc: |
Description
WMS does not handle projection changes.
TMS does not handle projection at all (it only supports EPSG:4326 and Mercator).
Suggestion:
- add a SupportedProjections function to layer
- For TMS fill in EPSG:4326 and Mercator
- For WMS fill in the values supported by the server
- Either use capabilities request or
- Extend the SRS parameter in URL, so multiple projection can be passed
- On projection change check whether the layers support the new one and ask user accordingly.
- On creating a new layer ask to change projection when necessary.
Replace the current code in WMS with a more generic approach which also works with new layer types when projection data is filled in.
Attachments (0)
Change History (6)
comment:1 Changed 2 years ago by stoecker
comment:2 Changed 23 months ago by stoecker
- Resolution set to fixed
- Status changed from new to closed
In [4183/josm]:
comment:3 Changed 23 months ago by stoecker
Ticket #5621 has been marked as a duplicate of this ticket.
comment:4 Changed 23 months ago by stoecker
Ticket #6328 has been marked as a duplicate of this ticket.
comment:5 Changed 23 months ago by stoecker
Ticket #6017 has been marked as a duplicate of this ticket.
comment:6 Changed 23 months ago by stoecker
Ticket #5826 has been marked as a duplicate of this ticket.
Note: See
TracTickets for help on using
tickets.
Ticket #5142 has been marked as a duplicate of this ticket.