Skip to main content
Archived

ESRI ArcGIS REST Query Service Transformer

siennaatsafe
j.botterill
runneals
bruceharold
helmoet
+6
  • siennaatsafe
    siennaatsafe
  • j.botterill
    j.botterill
  • runneals
    runneals
  • bruceharold
    bruceharold
  • helmoet
    helmoet
  • qmarquette
  • rowdy
  • dandgetz
  • joshuadamron
    joshuadamron
  • lene.bukholm
  • davecook

runneals
Contributor

It would be nice to have a transformer where you could query a REST service (both Feature Service and Map Service) and have all of the fields be autoparsed out as attributes.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

7 replies

bruceharold
Contributor
Forum|alt.badge.img+17
  • Contributor
  • August 28, 2017

Feature service is there already with Online, Portal and Server feature service readers, but as you say image services are not supported.


runneals
Contributor
Forum|alt.badge.img+19
  • Author
  • Contributor
  • September 22, 2017
I meant as a transformer instead of a reader, so you can take attributes from features and do a query on them with various REST services.

chriswilson
Supporter
Forum|alt.badge.img+11
  • Supporter
  • September 25, 2017

Would a Feature Reader not work for this? Building the URL based on certain attributes to then send as a query? Or are you trying to get the schema back from the service first and then work with that?


bruceharold
Contributor
Forum|alt.badge.img+17
  • Contributor
  • September 26, 2017
How about just using the Query API with HTTPCaller?

 

 


runneals
Contributor
Forum|alt.badge.img+19
  • Author
  • Contributor
  • September 27, 2017
That's how I think I'm gonna have to tackle it now, but I have to then parse out the json (which means like 2+ transformers). I was hoping for 1 nice transformer where you could provide a URL and the where clause (and the other inputs that the query supports) and output the results as attributes (or a list - which ever makes more sense).

runneals
Contributor
Forum|alt.badge.img+19
  • Author
  • Contributor
  • September 27, 2017
That might actually do the trick :P I never thought of using the feature reader!

chriswilson
Supporter
Forum|alt.badge.img+11
  • Supporter
  • September 29, 2017
That's what I usually use for reading online services, either with a creator beforehand or maybe a polygon going in to define a spatial filter (where possible). It's a very flexible way of doing things.

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings