<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: QueryTask vs. IdentifyTask in ArcGIS JavaScript Maps SDK Questions</title>
    <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/querytask-vs-identifytask/m-p/706809#M65778</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I almost always use QueryTask, because I want to format the content of the infoWindow specific to the attributes that are available for a particular layer.&amp;nbsp; You'll notice in the identify examples that they generically format that content based on all the fields that are available in a layer and you end up with something that works for all, but isn't very nice looking.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Feb 2013 18:38:04 GMT</pubDate>
    <dc:creator>TracySchloss</dc:creator>
    <dc:date>2013-02-26T18:38:04Z</dc:date>
    <item>
      <title>QueryTask vs. IdentifyTask</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/querytask-vs-identifytask/m-p/706807#M65776</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm curious if I should use a QueryTask or an IdentifyTask.&amp;nbsp; I have a simple JS API map with an ArcGISDynamicMapServiceLayer over a basemap.&amp;nbsp; I want to display several attributes from a single layer in the dynamic service in an InfoWindow.&amp;nbsp; I can accomplish that with either a QueryTask or IdentifyTask, right?&amp;nbsp; Is there a best practice?&amp;nbsp; Can anyone suggest some pros and cons?&amp;nbsp; Thanks!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 13:35:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/querytask-vs-identifytask/m-p/706807#M65776</guid>
      <dc:creator>MattFancher</dc:creator>
      <dc:date>2013-02-26T13:35:56Z</dc:date>
    </item>
    <item>
      <title>Re: QueryTask vs. IdentifyTask</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/querytask-vs-identifytask/m-p/706808#M65777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I would say the biggest difference is that Query Task operates on 1 layer in your service and "selects" the records that match your query.&amp;nbsp; Where as an identify Task can be set up to select from multiple layers in your service and will simply return the records without actually "selecting" them.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As for performance, I do not know. Generally I use the Query task only because I am dealing with editing the records and I must select them inorder to perform any edits (since this is the way I have set up my FeatureLayer service). &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Eventhough you are only dealing with 1 layer, you may want to use the Identify Task since it can easily be implemented to select from multiple layers within your service should the need arise.&amp;nbsp; Also, the layer options seem very useful as well such as specifying if you want to identify from ALL layers, top most layer or Visible layers only. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Unless you see a performance issue or have a need to perform advance Selection queries (Query Task), it seems like the identify task should do what you need and allow you to add additional functionality as needed.&amp;nbsp; My two cents...&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 14:38:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/querytask-vs-identifytask/m-p/706808#M65777</guid>
      <dc:creator>DianaBenedict</dc:creator>
      <dc:date>2013-02-26T14:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: QueryTask vs. IdentifyTask</title>
      <link>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/querytask-vs-identifytask/m-p/706809#M65778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I almost always use QueryTask, because I want to format the content of the infoWindow specific to the attributes that are available for a particular layer.&amp;nbsp; You'll notice in the identify examples that they generically format that content based on all the fields that are available in a layer and you end up with something that works for all, but isn't very nice looking.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 18:38:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/querytask-vs-identifytask/m-p/706809#M65778</guid>
      <dc:creator>TracySchloss</dc:creator>
      <dc:date>2013-02-26T18:38:04Z</dc:date>
    </item>
  </channel>
</rss>

