Lucas
Lucas
Good idea. @CommanderStorm And I update some descriptions here to make it more clearly. (English is not my first language so feel free to edit them if needed)
A nested `custom_tile_schema` might be a little bit ugly. Another option is we could add the required fields for custom tile schema `tile size` `extent`(might reuse the `bounds` field ,...
1. Make services google compatible if it's google compatible. We should do this I guess. I will finish it [there](https://github.com/maplibre/martin/pull/1637) 2. Add custom tile schema fields nested. 3. Add custom...
It's still an early draft. We could decide flat or not after all fields added.
I believe it's almost there but got really busy these days, would be back next week
> If we want to modify tilejson, we may need to step back for a bit and come up with a "standard-compatible" way to: > > * support non-web-mercator projections...
If it's difficult to make a decision about where to place these fields maybe it's not bad to make a CLI to output them(or just print them in console log)....
I suggest to remove the doc about cog before we figure out how to support non Web Mercator tile grid and how to tell user the tile grid of cog....
> Thank you so much for your hard work on this! I am sure we can figure it out - clearly not an easy thing to do right, and even...