We have loads of drone-derived DEMS and Orthophoto mosaics from beach surveys that we would like to serve up with VTS, and it was easy to get a sample going on the Melown Cloud:
https://www.melown.com/cloud/link/93m5EKtdHiYciGhLGVty
We have done a lot of work with the open source geospatial framework TerriaJS, and it would be super useful for us to be able to display the Melown terrain/imagery in TerriaJS (based on Cesium and Leaflet).
Is there documentation for client side developers on the encoding of tile services provided by VTSD, for example, descriptions of the surface format .bin, .mask, and .meta files?
There is no public documentation for the .bin and .meta files yet (.mask is just image file with changed file extension). But I will send you our internal documentation by mail.
We have loads of drone-derived DEMS and Orthophoto mosaics from beach surveys that we would like to serve up with VTS, and it was easy to get a sample going on the Melown Cloud: https://www.melown.com/cloud/link/93m5EKtdHiYciGhLGVty
It was also easy to get the VTS backend going on our own virtual ubuntu machine: http://jetstream.signell.us:8070/mapproxy/melown2015/surface/examples/srtm1-n47-e013
We have done a lot of work with the open source geospatial framework TerriaJS, and it would be super useful for us to be able to display the Melown terrain/imagery in TerriaJS (based on Cesium and Leaflet).
Is there documentation for client side developers on the encoding of tile services provided by VTSD, for example, descriptions of the surface format
.bin
,.mask
, and.meta
files?cc @kring