@MassGIS And here we have support for WMTS in the TOC.
A slight tweak to the folderset entry so that we can piggy back on default tiled_overlay behavior as much as possible. This is what it should look like.
I also commented out this layer from the basemap list in the PHP. I'm not sure if they would clobber or what.
I will want to follow this up w/ one final pull request so that I can un-hardwire these WMTS instanced from the 1st entry in our new wmts.js. You may notice that I have wmts[0] in several places. That's fine for our 1 dataset, but I want it to be flexible.
Also, I am hardwiring any WMTS to 900913. If that needs to be more flexible, let me know.
@MassGIS And here we have support for WMTS in the TOC.
A slight tweak to the folderset entry so that we can piggy back on default tiled_overlay behavior as much as possible. This is what it should look like.
I also commented out this layer from the basemap list in the PHP. I'm not sure if they would clobber or what.
I will want to follow this up w/ one final pull request so that I can un-hardwire these WMTS instanced from the 1st entry in our new wmts.js. You may notice that I have
wmts[0]
in several places. That's fine for our 1 dataset, but I want it to be flexible.Also, I am hardwiring any WMTS to 900913. If that needs to be more flexible, let me know.