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

Add support for Esri Catalog Service #112

Open
jkerr5 opened this issue Jun 20, 2018 · 2 comments
Open

Add support for Esri Catalog Service #112

jkerr5 opened this issue Jun 20, 2018 · 2 comments

Comments

@jkerr5
Copy link

jkerr5 commented Jun 20, 2018

Would it make sense to add support for the Esri catalog service API as defined here: https://developers.arcgis.com/rest/services-reference/catalog.htm

See http://sampleserver3.arcgisonline.com/ArcGIS/rest/services for example.

It would also be nice to have the HTML rendering capability.

If this is already supported somehow, please point me to docs or an example.

@rgwozdz
Copy link
Member

rgwozdz commented Jun 20, 2018

I'm definitely open to exploring the idea. Note that this won't be possible for all providers, because some don't have a known set of services, or it would be prohibitive to discover them. For example, the koop-provider-geojson provider has an indeterminate number of services. So in that sense, I'm not sure it makes sense to add to koop-output-services/FeatureServer

We could however approach it similar to the new auth plugin where you add a new function fetchServices to your Model prototype that collects the available services. When a request arrives for :provider/rest/services, koop-output-services would see if a fetchServices function is defined; if it is, then the fetch is executed and data handed off to FeatureServer where the response is handled.

@dmfenton
Copy link
Contributor

dmfenton commented Jul 2, 2018

When a request arrives for :provider/rest/services, koop-output-services would see if a fetchServices function is defined;

I think this is the right thread to follow. Providers can stay simple and only support getData or they can add functionality:

  • authenticate
  • authorize
  • getServices
  • getLayers

We'll need to think about how we can abstract these things so that they could work for other types of catalogs and API formats.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants