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

Services Collection #8

Open
jpeterson opened this issue Jun 26, 2018 · 7 comments
Open

Services Collection #8

jpeterson opened this issue Jun 26, 2018 · 7 comments

Comments

@jpeterson
Copy link

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

@hhkaos
Copy link
Contributor

hhkaos commented Jun 27, 2018

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?:

Big Data Catalog Service, Data Reviewer for Server, Feature Service, GeoAnalytics, Geocode Service and toos, Geodata Service, Geometry Service, Geoprocessing Service, Globe Service, Image Service, Info, Linear Referencing Service, Map Service, Mobile Service, Network Diagrams Service, Network Service, RasterAnalytics, Relational Catalog Service, Scene Service, Schematic Service, Spatial Analysis Service, Stream Service, System, Uploads, Utilities, Utility Network Service, Vector Tile Service, Version Management Service, Administer Hosted Map and Feature Services

Thanks!

@jpeterson
Copy link
Author

@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:

  • http://<featurelayer-url>/addFeatures
  • http://<featurelayer-url>/deleteFeatures
  • http://<featurelayer-url>/updateFeatures
  • http://<featurelayer-url>/queryRelatedRecords
  • (+ many more)

@hhkaos
Copy link
Contributor

hhkaos commented Jul 2, 2018

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!

@hhkaos
Copy link
Contributor

hhkaos commented Sep 26, 2019

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
Copy link
Contributor

hhkaos commented Sep 26, 2019

It's in https://github.com/esri-es/ArcGIS-REST-API/tree/master/HostedFeatureServices

@jpeterson
Copy link
Author

@hhkaos This is brilliant, thanks so much for the hard work!

@hhkaos
Copy link
Contributor

hhkaos commented Sep 26, 2019

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 🤣

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

2 participants