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 Oct 19, 2017
1 parent aa51f13 commit b49de2e
Showing 1 changed file with 4 additions and 8 deletions.
12 changes: 4 additions & 8 deletions docs/resources.md
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ Surface drivers generate a meshed surface that can be used directly as a single
a remote tileset.
In addition, a `freelayer.json` file is provided allowing generated surface to act as a `mesh-tiles` free layer.
### Commpon surdace driver configuration options
### Common surface driver configuration options
All surface drivers support these (optional) options:
```javascript
Expand Down Expand Up @@ -179,12 +179,9 @@ introspection = {
This driver generates meshed surface for reference frame's spheroid. If geoid grid is provided the resulting body
is in fact a geoid.
If a `textureLayerId` entry is present this ID is written into generated meshes as a default bound layer to use
if nothing else is mapped on the surface. Otherwise surface is completely texture less.
```javascript
definition = {
Optional Int textureLayerId // numeric bound layer ID
// see common surface driver configuration options above
}
```
Expand All @@ -202,15 +199,14 @@ vertical system to use geoid support. I.e. either they share the same ellipsoid
local system that approximates the geoid at given place. One working example is data in Krovak's projection that can
be reinterpreted as heights above WGS84+EGM96 without any significant error.
If a `textureLayerId` entry is present this ID is written into generated meshes as a default bound layer to use
if nothing else is mapped on the surface. Otherwise surface is completely texture less.
All `surface-dem` input datasets are registered in internal map od available DEM's under its `group-id` identifier
and can be referenced from various `geodata`resources for 2D features heightcofing. Optionially, input dataset can
be registered in this map under an alias. See more in the `geodata` resources documentation.
```javascript
definition = {
// see common surface driver configuration options above

String dataset // path to complex dataset
Optional String mask // optional mask, generated by mapproxy-rf-mask tool
Optional Int textureLayerId // numeric bound layer ID
Expand Down

0 comments on commit b49de2e

Please sign in to comment.