TMS with TileLayer?

[jfuehner]

I am trying to use the TileLayer with a TMS (MapProxy) service. With the TileLayer by default supporting slippy map tilenames/(zxy) my initial thought was I could simply flip the y coordinate (Math.pow(2, z)-y-1) to be TMS compliant via the getTileData.

Flipping the y coordinate within the getTileData function appeared to put the tiles in the correct order. However, no matter what my viewState is the map always loads tiles around South America...

For example, if my viewState is...

{
   latitude: 37.77,
   longitude: 122.41,
   zoom: 0
}

I get tiles loaded looking like the below screen capture. The rest of the world tiles do not load....

I also tried explicitly specifying the TileLayer's extent property to the bounds of the TMS service...

[-20037508.342789244, -20037508.342789244, 20037508.342789244, 20037508.342789244]

The TMS/MapProxy service provides a test page which uses OpenLayers and is rendering the tiles correctly. I would mockup a Codepen but I can't seem to find a freely available TMS server on the open Internet.

Appreciate any help and insights on how I can correctly render using deck...

[kylebarron]

You can either use an indexing: tms prop or use {-y} in the data URL field, though it appears that isn't documented on the TileLayer docs page. See #4958

[kylebarron]

I think indexing might've been removed before merge. Just use {-y} in the data url

[jfuehner]

@kylebarron unfortunately for my use case I am not using the data property. I am overriding the getTileData to call a web socket connection with the xyz.

Unless I can use both the data prop and the getTileData function?

[kylebarron]

The url prop is resolved from data https://deck.gl/docs/api-reference/geo-layers/tile-layer#gettiledata

[jfuehner]

So, I can make using the data prop in conjunction with the getTileData work. However, it's a bit weird.

If I provide a data prop /{z}/{x}/{-y} for example I see in the getTileData function tile object providing back the resolved url prop with the y flipped. However, the same tile object's y prop is the non-flipped value. I would expect the tile objects y prop to be the flipped value to be consistent with what was requested/provided in the data prop?

For my use-case though, the use of the data props seems a bit redundant. With my current implementation I don't actually supply a data prop to the TileLayer. I only provide a handler function to the getTileData which calls an already open web socket passing the tile object directly to the socket.

With having to use the data prop in conjunction with getTileData and the y values not being consistent I will have to parse the url prop out to get the correct y value...

[kylebarron]

If I provide a data prop /{z}/{x}/{-y} for example I see in the getTileData function tile object providing back the resolved url prop with the y flipped. However, the same tile object's y prop is the non-flipped value. I would expect the tile objects y prop to be the flipped value to be consistent with what was requested/provided in the data prop?

I think I raised this before. Might be worth reading through the discussion in the previous PR and the issue that created it #4958 (comment) #4757 (comment)