Is it possible to set origin or resolutions info in UrlTemplateImageryProvider

In Openlayer, there is a tileGrid attributes in class ol/source/TileImage which can modify the tile origin, resolution info.

But I cannot find the corresponding attributes in Class UrlTemplateImageryProvider.
In Class UrlTemplateImageryProvider, only can i construct the url

How can I modify tile origin and resolutions info?

You can specify the min/max levels, but in general CesiumJS will automatically figure out the right resolution to load based on the distance to the camera and other metrics. You can tweak the screen space error on the globe to tweak this behavior:

Let me know if that answers this question. Are you trying to change the tile origin in order to move the the map itself? What kind of tiles are you loading in?

I want to add a third party WMTS map. But it is not standard WMTS service.

The thrid party give me the following openlayers code to load its map.

/*******************************code start***************************************/
  var resolutions = ;
  for (var i = 0; i < 21; i++) {
    resolutions[i] = 90 / 256 / Math.pow(2, i);
    var tilegrid = new ol.tilegrid.TileGrid({
        origin: [0,0], // 设置原点坐标
        resolutions: resolutions // 设置分辨率

  var urlTemplate2 = "{x}&y={y}&l={z}";
  var gisSource2 = new ol.source.TileImage({
        projection: 'EPSG:4326',
        tileGrid: tilegrid,
        tileUrlFunction: function(tileCoord, pixelRatio, proj){
            var z2 = tileCoord[0];
            var x2 = tileCoord[1];
            var y2 = tileCoord[2];

      return urlTemplate2.replace('{x}',x2.toString())

/*******************************code end***************************************/

From its demo, it reassign resolution and tile origin info and the layer is shown.

In cesium ,I simplely add a UrlTemplate Layer liks this

viewer.imageryLayers.addImageryProvider(new Cesium.UrlTemplateImageryProvider({

I cannot see the layer. So i guess i must reassign the origin and resolution info.

If it’s not a standard WMTS service, you might need to writ your own custom imagery provider. This is a recent PR that adds a new custom imagery provider, that might be a good source of inspiration:

If it works in OpenLayers, you might be able to figure out what they do there from their source code to make it work.