Opened 15 years ago
Closed 14 years ago
#3982 closed enhancement (fixed)
Move layer like in WMS plugin
Reported by: | Bürste | Owned by: | hansendc |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core imagery | Version: | |
Keywords: | Cc: |
Description
After slippymap is now used for nearmap satellite-data in au shifting would be a nice feature like possible for WMS layers. You can't use the data if it's shifted so this is a blocker.
Attachments (0)
Change History (8)
comment:1 by , 15 years ago
Owner: | changed from | to
---|---|
Priority: | blocker → minor |
comment:3 by , 15 years ago
I knew you were going to say that. :)
Any idea who is actively working on WMS? I'll look into what it would take to pull some WMS tiles into the slippymap code since I know it better than WMS, but it would be nice for someone to do the same on the WMS side.
comment:4 by , 15 years ago
Actually I would not join the way the plugins handle the data, but only the plugins itself and the user interface. The data handling and lots of other stuff still may be separate. But when in one code base, then code reusage gets possible and some time in future it gets unified. Probably walking papers is then the next candidate for inclusion.
New name may be "map" plugin.
comment:5 by , 15 years ago
Would be nice if it's possible to move both layers with the same tool. Isn't wms and slippymap using the same type of layer?
If you implement it in JOSM core it is nice if the icon would disappear (not only greyed out) if not the map is selected as active layer ... Else moving GPX layers would be nice if you see theres a glitch of 10 metres in one direction for the whole track.
But it should be displayed if the layer is shifted and should be easy to snap back to unshifted state.
Btw: You saw the second report about slippymap seems to block higher zoom levels than 18?
---
About merging WMS and Slippymap ... would be nice, but WMS is currently damn hacky if you see everybody complains about not working states and such. Might be a good solution if both plugins are in stable state.
comment:6 by , 15 years ago
When both are stable, they move into core anyway. What do you think is the reason WMS is not yet in core JOSM? :-)
comment:7 by , 14 years ago
I'd also like to see this implemented. I'd like to use JOSM to digitize some historic maps, which are shifted a bit. Otherwise I'd need to apply the shift in the DB.
comment:8 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Included in core and TMS/WMS are unified.
How would you want this implemented? Drag-n-move like WMS?
For any other developers watching this, should we do this in the JOSM core since more than one plugin wants it?
Also, changing the priority down because it isn't blocking use of the plugin for existing users.