More map layers - Githubissues

hotosm / osm-tasking-manager2

Designed and built for Humanitarian OpenStreetMap Team collaborative emergency/disaster mapping, the OSM Tasking Manager 2.0 divides an area into individual squares that can be rapidly mapped by thousands of volunteers.

http://tasks.hotosm.org

Other

425 stars 156 forks source link

More map layers #497

Open althio opened 9 years ago

althio commented 9 years ago

Make more map layers available

humanitarian
standard
transport
imagery/imageries
special styles (stamen...)
custom URL
...

Features:

Allow admin to choose at project level the available layers and the layer by default.
Allow users to choose between the available layers.

Usages:

customised instances of TM2
adapted layers for particular projects (mapping for HOT or in western city or for public transportation / cycleways / hiking...)
view imagery available versus project grid
fallback if default layer is unavailable (tile server is down)

Examples on other OSM online maps:

openstreetmap.org	iD

bgirardot commented 9 years ago

@althio Could you please explain this more? I might be misunderstanding it entirely. Why would I need more rendered map layers for mapping? Where would I see these other rendered layers? In iD?

althio commented 9 years ago

Where? In tasking manager map, with the project grid overlay.

althio commented 9 years ago

Why? Not for mapping, the project map is only informative. But I can think of other use cases of tasking manager outside of HOT and the humanitarian community. For others communities other tiles would be nice to have.

It would be also useful in the event of an outage for one particular tile server.

ethan-nelson commented 9 years ago

The other thing is we have to think about the TM in the context of other instances. We should potentially set up a dictionary or other definition that is administrator-customizable in, say, a .ini file to add custom tile layers; then when leaflet loads we look at that for other potential layers. Otherwise everyone will be using the same tileservers that we specify, which could be a no-no in the event we have a HOT-specific tile layer from a provider (though now that I think about it, everyone may be using the osm.fr tile layer right now unless they specifically modify this in their deployment).