grids: Define the grids that MapProxy uses to aligns cached images. The OpenStreetMap editors have a community moderated list of map providers which offer aerial imagery as background layer. Each layer can consist of multiple sources and caches. There are two ways to pass the layer order to the layer tree. The OpenLayers widget provides already the functionality, so maybe it's enough to allow users to add a custom URL? On the other hand it might be useful to offer a catalogue of aerial imagery providers? Layerset-instances contain the options how a WMS is called: image-format, info-format.
So my feature request is to allow users to add different online WMS/TMS providers.
The Mapproxy setup gives a great opportunity to make use of aerial imagery and maps also on your Laptop in the field.īut I guess for newcommers to this topic, the external setup might a bit complicated and parallel default OSM style a bit to generic to avoid obstacles on first flight mission plannings? Use a map implementation that retains the original order of the read yaml file. The mapproxy-seed command does not use a consistent order when seeding multiple layers. If MapProxy should use the same ordering of the layers for capability responses, you should put the definitions in a list (prepend a -before the key). Hi, first let me say that I'm new to UAVs but appreciate the iNAC ecosystem and your work ? My background is GIS and embedded systems. The layers should be seeded in the order they are defined in the seed.yaml (unless specified via command parameter).