Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

HTTP Texture Tile Layer - Server Switching #70

Closed
Neutrinora opened this issue Jun 23, 2020 · 1 comment
Closed

HTTP Texture Tile Layer - Server Switching #70

Neutrinora opened this issue Jun 23, 2020 · 1 comment
Labels
feature request New feature or request

Comments

@Neutrinora
Copy link

Neutrinora commented Jun 23, 2020

Is your feature request related to a problem? Please describe.

Cannot use multiple URL sources for a single HTTP Texture Tile Layer.

Describe the solution you'd like

Ability to use multiple URL sources on a single HTTP Texture Tile Layer.

Describe alternatives you've considered

Alternatively, instead of using multiple URL sources, ability to use another replacement string {s} which refers to available server codes.

//Input via inspector
string[] serverCodes = new string[3] { "a","b","c" };

//URL source
https://{s}.tile.server.com/{z}/{x}/{y}.png

//Results
https://a.tile.server.com/6/36/24.png
https://b.tile.server.com/6/36/24.png
https://c.tile.server.com/6/36/24.png

Additional context

Possible conflict:

  • Treating a,b,c as different textures on cache systems

Possible feature:

  • Adaptive server(s) selection based on download speeds

Best regards

@Neutrinora Neutrinora added the feature request New feature or request label Jun 23, 2020
@kircher1
Copy link
Contributor

Added in 0.9.2.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants