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

ogc-example project is tough to get running #164

Open
notthatbreezy opened this issue Oct 15, 2019 · 3 comments
Open

ogc-example project is tough to get running #164

notthatbreezy opened this issue Oct 15, 2019 · 3 comments

Comments

@notthatbreezy
Copy link
Contributor

The ogc-example project's application conf includes resources that are not publicly accessible or easily reconfigured.

I think an improvement would be to use CogNode's instead of GeoTrellis layers (even if the resources are still not publicly accessible) since those can at least be more easily substituted in a development environment. This scenario happens sometimes when I've run into bugs/issues with some of the OGC services and had to figure out if the bug existed in my application code or exists in the library -- being able to quickly come up with a proof-of-concept that either reproduces or fails to reproduce the problem can be a blocker in that workflow.

@echeipesh
Copy link
Collaborator

echeipesh commented Oct 21, 2019

Would it be more helpful to have an easy way to standup an instance of a given service from console for this kind of thing?

For instance:

val service = WcsService.fromMap(
Map(
  "layer1" -> GeoTiffRasterSource(???), 
  "layer2" -> GeoTrellisRasterSource(???))

service.bind("0.0.0.0") // ??? --some kind of one command utility to standup an endpoint

@notthatbreezy
Copy link
Contributor Author

I think that could work, but that's not what I had in mind.

I was thinking the conf idea is still a good one, but having one that is more accessible and easier to get started with maybe a few different examples - and starting the server with one as an argument. Right now there is a lot to edit in the existing example conf and it's not even really possible to switch to using a COG rather than a GT source without making code changes.

@echeipesh
Copy link
Collaborator

I agree with all of that, lets keep this issue specifically for that conf cleanup and breakup work.

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