Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add support for Bavaria (WMS) DOP80 Germany #178

Closed
geowOSM opened this issue Aug 21, 2016 · 10 comments
Closed

Please add support for Bavaria (WMS) DOP80 Germany #178

geowOSM opened this issue Aug 21, 2016 · 10 comments

Comments

@geowOSM
Copy link

geowOSM commented Aug 21, 2016

@bhousel, please consider adding support for Bavaria DOP80 in iD: http://www.geodaten.bayern.de/ogc/ogc_dop80_oa.cgi?
It’s the best imagery (Bavarian State Survey, orthorectified, update cycle 2 years) for Bavaria/Germany available for use in OSM, see http://wiki.openstreetmap.org/wiki/Contributors#Bayern
But it’s available only as wms. I asked as you mentioned in #152 you might consider including some limited wms support in iD soon.
Thanks

@simonpoole
Copy link
Contributor

You are confusing two things here:

  • adding an entry to this index (there are lots of WMS entries)
  • support for WMS servers in iD (and other editors)

The easy solution for the later is to run a mapproxy service as an intermediary, if you don't have the (small) resources needed to do so, you could ask SOSM or FOSSGIS.

@geowOSM
Copy link
Author

geowOSM commented Aug 21, 2016

Thanks Simon, my fault, I meant wms support in iD and should have addressed bhousel directly. Corrected.

@simonpoole
Copy link
Contributor

@geowOSM still if nobody wants to do it in DE, we (SOSM) can add it to our mapproxy instance.

@tyrasd
Copy link
Member

tyrasd commented Aug 21, 2016

WMS support in iD should be discussed in iD's repository. There's an old ticket (openstreetmap/iD#1141) which could be re-opened if needed.

@geowOSM
Copy link
Author

geowOSM commented Aug 21, 2016

@tyrasd Thanks for re-opening openstreetmap/iD#1141.

@simonpoole Thanks, I appreciate your kind offer. I will check back tomorrow with the State Survey, if they might be able to provide a tms-url. If not, I would be happy with MapProxy. Do I understand correctly, that by adding it there, it can also be used in other editors, which rely on the editor-layer-index?

@simonpoole
Copy link
Contributor

simonpoole commented Aug 21, 2016

@geowOSM yes it then can be used as like a completely normal tileserver and if configured here will eventually turn up in iD and the other editors that use this index.

PS: a reasonably simple boundary polygon for Bayern in geo JSON would be helpful for adding the configuration.

PPS: mapproxy will reproject if necessary.

@bhousel
Copy link
Member

bhousel commented Aug 22, 2016

WMS support in iD should be discussed in iD's repository. There's an old ticket (openstreetmap/iD#1141) which could be re-opened if needed.

Yes, lets reopen that ticket.. I've ported the whoots code over to javascript, so it would be a small lift to bring that library into iD and support WMSs that can serve EPSG:3857.

@geowOSM
Copy link
Author

geowOSM commented Aug 22, 2016

@simonpoole Today the Bavarian Survey Authority has confirmed on request, that there are so far no plans providing a TMS for the DOP80. If your offer is still valid I (and many others) would greatly appreciate if SOSM would add it to their mapproxy.

A boundary polygon for Bavaria should be already available in the editor-imagery-index repository, as the DE / Bavaria (2 m) layer is included. As an appropriate projection EPSG:4326 is available (but not 3857).

@simonpoole
Copy link
Contributor

@geowOSM

http://mapproxy.osm.ch:8080/tiles/BAYERNDOP80/EPSG900913/{z}/{x}/{y}.png?origin=nw

should already work as custom imagery link in iD. I'll prepare a PR for adding it to the index.

@simonpoole
Copy link
Contributor

See #180

@tyrasd tyrasd closed this as completed Aug 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants