You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now LayerTMS generates a function that takes 3 integers and outputs a tile -- I think it would be good if this was extended to include allowing for a Well Known Tile Matrix Set.
There are currently 8 of them. Right now we actually already support one - the google maps compatible one - so we could make this change without having to worry about adding additional support/changes in that respect.
Alternatively, I could see this being a client/implementation specific detail - since one could provide a different TMSReification based on what it wants to support and pattern match which one to use at the route level.
The reason I'm bringing this up is because we're inching ever-closer to adding TMS support to Franklin for STAC and one thing that's clear from the OGC specs on tiles/maps is support for TileMatrixSets.
The text was updated successfully, but these errors were encountered:
Right now
LayerTMS
generates a function that takes 3 integers and outputs a tile -- I think it would be good if this was extended to include allowing for a Well Known Tile Matrix Set.There are currently 8 of them. Right now we actually already support one - the google maps compatible one - so we could make this change without having to worry about adding additional support/changes in that respect.
Alternatively, I could see this being a client/implementation specific detail - since one could provide a different
TMSReification
based on what it wants to support and pattern match which one to use at the route level.The reason I'm bringing this up is because we're inching ever-closer to adding TMS support to Franklin for STAC and one thing that's clear from the OGC specs on tiles/maps is support for TileMatrixSets.
The text was updated successfully, but these errors were encountered: