Skip to content
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

Capability: Define a data source for a tile layer #74

Open
NickFitz opened this issue Jun 14, 2019 · 2 comments
Open

Capability: Define a data source for a tile layer #74

NickFitz opened this issue Jun 14, 2019 · 2 comments
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete

Comments

@NickFitz
Copy link
Contributor

@NickFitz NickFitz commented Jun 14, 2019

This issue is for discussion of the required API capability "Define a data source for a tile layer".

@NickFitz NickFitz added discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? status: placeholder there's a matching section heading / some text in the report, but it's far from complete section: client-side API Capabilities & use cases for client-side APIs labels Jun 14, 2019
@prushforth
Copy link
Member

@prushforth prushforth commented Jun 17, 2019

In the document, it says "Based on the limited data, we are undecided about whether this should be a requirement." which is hard to understand. Even image maps need data sources, and geospatial maps are not different. Just because the big mapping providers don't support mixing data sources doesn't mean it's not a requirement for the Web. By analogy, just imagine if you could only use YouTube for videos in Chrome, etc.

OTOH, maybe I am misunderstanding something here.

@NickFitz
Copy link
Contributor Author

@NickFitz NickFitz commented Jun 17, 2019

@prushforth "Undecided" is the default conclusion from the template (found towards the end of index.html with id "capability-template"). I'm currently working on fleshing out the use cases, required capabilities, and examples for the Client APIs section, and will be updating the conclusions accordingly. And as you say, this one in particular will be a necessity :-)

@NickFitz NickFitz changed the title Capability: Define a data source for a map Capability: Define a data source for a tile layer Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion: capability a specific capability or feature: should it be included? what details? should it be a requirement? section: client-side API Capabilities & use cases for client-side APIs status: placeholder there's a matching section heading / some text in the report, but it's far from complete
Projects
None yet
Development

No branches or pull requests

2 participants