Skip to content
This repository has been archived by the owner on Aug 22, 2023. It is now read-only.

Commit

Permalink
Update resources.md
Browse files Browse the repository at this point in the history
  • Loading branch information
vaclavblazek authored Nov 27, 2019
1 parent 9308a9b commit 32e8c81
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions docs/resources.md
Original file line number Diff line number Diff line change
Expand Up @@ -354,25 +354,27 @@ This driver is a special kind of beast. It combines existing surface with TMS to
It doesn't generate any content on its own but forward all requests to existing surface and TMS resources.
These drivers must exist in the system.
Caveats:
Caveats/TODO:
* This driver does not support any introspection. If introspection is instroduced in the future it would lack the boundlayer
specification (TMS) because this driver already produces its own imagery.
* Keeps original surface's credits burned in the metatiles.
* Also, this driver does not support any other common surface configuration.
* Keeps original surface's credits burned in the metatiles nor `tileset.conf`. In the future, TMS credits (plus any other credits
configured in this resource) would be included as well.
* So far, during runtime, this driver doesn't watch for changes in the underlying surface/TMS and keeps the old driver
instance alive while the original resource has been reconfigured and is being served by new driver instance.
instance alive while the original resource has been reconfigured and is being served by new driver instance. Restart mapproxy
if this becomes a problem.
```javascript
definition = {
// see common surface driver configuration options above
ResourceId surface // Resource ID od underlying surface resource
ResourceId tms // Resource ID od underlying tms resource
}
```
## Geodata drivers
Geodata drivers generate vector geographic data in the form of VTS free layer.
Expand Down

0 comments on commit 32e8c81

Please sign in to comment.