(Feature request) Any chance to use different source of rgb-dem tiles?

[2ktsch]

Hi! Is there any chance some parameters can be added (alongside mapbox api key) so that any source of rgb tiles (possibly even modifying offset and resolution depending on application) can be used?

[slutske22]

What other sources of rgb tiles are you thinking? What do you mean exactly by offset and resolution?

[slutske22]

Ok I've got a quick codesandbox going with the rgb_50k100 layer. What is the height function for this? meaning const height = (R, G, B) => ?. Is it -50000 + ((R * 256 * 256 + G * 256 + B) * 0.1)? What about for the rgb_10k10 tiles?

[2ktsch]

Almost- -50000 and 0.01 height = (R, G, B) => -50000 + ( ( 256 * 256 * R + 256 * G + B) * 0.01)
The 10k10 should work with the default function (-10000 and 0.1) height = (R, G, B) => -10000 + ( ( 256 * 256 * R + 256 * G + B) * 0.1)

[slutske22]

I'm pretty close to wrapping this up, but I'm stuck with getting a custom height function to work on a per-layer basis in the Topolayer visualizations. You can check out my dillema here, and read a bit more in the comments there. If I can get past that issue, I think we can wrap this up and publish a new version which will enable the features you need. If you have time and want to help me debug some web-worker stuff, please take a look. Otherwise I'm not sure how long it will be before I have time / can figure this out.

[slutske22]

I am having CORS issues with your tilelayer when testing things out. I set up my sample project to run on localhost:1234, and the tiles are fetched from there. The tile fetching function triggers a CORS error:

As you can see, we have referer: http://localhost:1234/

When accessing the tiles directly in the browser, or using them in a tilelayer in codesandbox, it seems fine. The referrer is actually referer: https://tileserver.tejidx.com/rgb_50k100/10/320/

Can you open up the referrer to 0.0.0.0:1234 (anything running on 1234), at least for testing? I'm getting close and I'd love to test this out. You can try to reproduce my issue by:

1. clone the repo
2. jump onto the custom-tile-url branch
3. npm install and npm run build
4. cd example-ts, and npm i and npm start
5. you should see the sample app running in the browser focused on puerto rico. Look into the network tab, and you'll see a bunch of failed network requests due to CORS

I'm sort of stuck until your tileserver allows cross origin requests, at least for a narrow range of IP/ports required to dev this thing.

Thanks!

[2ktsch]

whoops, sorry 'bout that! Should be fixed now-- open for anywhere ATM

[slutske22]

This is ready for testing. You can try this out with the following:

1. npm install leaflet-topography@next
2. Use the tilesUrl option to define your custom tile url. This can be used in liueu of the token option, either in the options passed to getTopography or a TopoLayer, or using the configure function. In your case, I'd recommend using the configure function
3. Use the heightFunction option to define your custom heightFunction. Same rules apply as for the tilesUrl option.

You can check out the readme on the custom-tiles-url branch, which has a bit more writeup on tilesUrl and heightFunction. There is still an issue using a custom heightFunction on a per-TopoLayer basis, but a workaround is described in the limitations section of the readme.

For a working example, follow these steps:

1. Clone this repo, switch to the custom-tiles-url branch
2. cd example-ts
3. npm install
4. npm start
5. Go to localhost:1234
6. You will see the demo app focused on puerto rico, using your custom tilelayer for the getTopography function and TopoLayers.

Please play around with this and let me know what you find. If it seems like its all working, I'll publish this as a 0.2.0 version.

[2ktsch]

Can't wait to try this out! Thanks! :D

[slutske22]

Ever get a chance to try this? If it’s working I’d like to publish to 0.2.0

[2ktsch]

Sorry 'bout the delay-- yes! Haven't found any strange behavior. Thanks again!