-
Notifications
You must be signed in to change notification settings - Fork 29
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
Services Collection #8
Comments
Aha, do you mean to instead of having a big collection with many directories split it in many smaller collections?. Using kind of the same structure of the new REST documentation page?:
Thanks! |
@hhkaos I think that would be a good way to approach the organization of collections, yeah! Here are some examples of the types of requests I think may be helpful:
|
Cool, that would be easier to maintain and contribute too. I'll try to find some time but I have also added the tag "helped wanted", in case anyone has time to contribute ^_^. I suggest to use the Apache 2.0 License and something like this contributing guidelines. ^_^ Cheers! |
Ey @jpeterson I followed your advice and I'm starting a new collection starting by hosted feature services if you want to take a look to it 😉 |
@hhkaos This is brilliant, thanks so much for the hard work! |
Thanks @jpeterson I'm glad you like it 😄 . I'm preparing a session about the REST API for the next DevSummit Europe in Berlin, I'll do my best to make it very easy to understand and get familiar with it. Actually, I'm learning quite a few things preparing the content for this talk 🤣 |
I think a lot of people would find a "Services" collection super useful. In the most ambitious sense, this could roughly equate to this level in the docs:
https://developers.arcgis.com/rest/services-reference/get-started-with-the-services-directory.htm
I think the most important services are Feature Services, so if there's a first step, it would be to build a collection around them:
https://developers.arcgis.com/rest/services-reference/feature-service.htm
The text was updated successfully, but these errors were encountered: