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

Imagery with multiple URLs #24

Closed
tyrasd opened this issue Oct 24, 2013 · 5 comments
Closed

Imagery with multiple URLs #24

tyrasd opened this issue Oct 24, 2013 · 5 comments

Comments

@tyrasd
Copy link
Member

tyrasd commented Oct 24, 2013

Let's say there is an imagery that supports more than one type of service. For example WMS as well as tiles. Would it make sense to add both to this repository? Because while WMS may support more different projections, tiles would be more suitable for applications (e.g. the iD editor).

How exactly should one add such imagery?

@tmcw
Copy link
Contributor

tmcw commented Oct 24, 2013

My initial reaction is: different endpoints for imagery should be different entries in this code, and if down the line we want a fancier UI there should be a group or id property that imagery could be grouped on.

@jfirebaugh
Copy link
Contributor

Is this a hypothetical question or is there a specific example we can consider?

@tyrasd
Copy link
Member Author

tyrasd commented Oct 24, 2013

Yeah, there is a secondary access point for geoimage.at which has been available in iD before it switched to this repo. (See the report in the talk-at mailing list.)

@jfirebaugh
Copy link
Contributor

Ok, so the issue is that geoimage.at in this index is WMS only, which iD doesn't support, but there's a TMS source that could be used instead.

tyrasd added a commit to tyrasd/editor-imagery-index that referenced this issue Oct 29, 2013
@bhousel
Copy link
Member

bhousel commented May 7, 2016

looks like this was done..

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

4 participants