Skip to content

xyz:servers vs. xyz:subdomains #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DanielJDufour opened this issue Feb 8, 2022 · 3 comments
Closed

xyz:servers vs. xyz:subdomains #1

DanielJDufour opened this issue Feb 8, 2022 · 3 comments

Comments

@DanielJDufour
Copy link

Hi. I'm wondering if xyz:servers might be a little more intuitive to people who use LeafletJS if it was called xyz:subdomains. I'm not sure about the nomenclature for other libraries.

https://leafletjs.com/reference.html#tilelayer

@m-mohr
Copy link
Contributor

m-mohr commented Feb 8, 2022

  • OpenLayers does it completely differently, there it is {?-?} (e.g. {a-f}) so you need to do some preprocessing anyway to pass it over.
  • If I understand the MapBox docs correctly, there you can actually define different URLs via an array, so in principle you could provide https://{s}/maps/{z}/{x}/{y} and then set xyz:servers example.org and mirror.cloud.

That's the intention behind it. Thoughts, @DanielJDufour ?

@DanielJDufour
Copy link
Author

Ah okay. That makes a lot more sense. Hmmm... it's sorta tricky because it seems Mapbox and LeafletJS usage of {s} is in conflict. I'm not sure what to think, but I'll give it some thought.

@m-mohr
Copy link
Contributor

m-mohr commented Jan 27, 2023

What we'll do with {s} is that it's just expanded into multiple URLs.

If you have https://{s}/example and xyz:servers is ["a.com", "b.eu"] you'll expand that to ["https://a.com/example", "https://b.eu/example"]

@m-mohr m-mohr closed this as completed Jan 27, 2023
m-mohr added a commit that referenced this issue Jan 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants