Open gerbsen opened 6 years ago
I think an option like this would make sense -- @springmeyer second opinion?
I'm a little confused and not totally following this conversation. But I will try to help by saying that:
What about other coordinate systems? For instance in WMTS you can define your own TileMatrixSet, see this sample from Swiss that is currently in use.
http://wmts.geo.admin.ch/1.0.0/WMTSCapabilities.xml
<TileMatrixSet><ows:Identifier>21781_25</ows:Identifier>
<ows:SupportedCRS>urn:ogc:def:crs:EPSG:21781</ows:SupportedCRS>
<!-- This tileMatrixSet in **only** for tiles generated through TileGenerator ! -->
<TileMatrix>
<ows:Identifier>0</ows:Identifier>
<ScaleDenominator>14285750.5715</ScaleDenominator>
<TopLeftCorner>420000.0 350000.0</TopLeftCorner>
<TileWidth>256</TileWidth>
<TileHeight>256</TileHeight>
<MatrixWidth>1</MatrixWidth>
<MatrixHeight>1</MatrixHeight>
</TileMatrix>
etc
Hey there, I've described my case here and got the suggestion to re-add the issue here. To sum this up:
We have written our own vectortiles service based on vt-pbf, which queries a really large database and transports the tiles in gzipped-geojson (which have to be in 4326 as per the spec, I believe) to our clients. Currently the geometries in our database are still in 4326, but I thought it would be useful to transform those to 3857 in order to save the transformation from 4326 to 3857 in the frontend.
This is probably also relevant.
@anandthakker replied:
cheers, daniel
attn: @abenrob