Identify Widget 2.5.3 Issues on Tiled Layer

Question

We have four operational layers in our GIS web application developed by ArcGIS Viewer for Flex, as shown below. The layer "Parcel Basemap" is a tiled layer. We set the Indentify Widget to identify all the visible layers. When I tried to run the Indentify Widget to identify layer "Sewer", we got the expected result. Just after we got the result, the CPU of the ArcGIS Server 10 is fully loaded (100%). After about 10 minutes, the ArcGIS Server returned to normal. I checked the ArcgIS Server log file carefully, it was found the Identify task was run against all the operational layers. The task run successfully with three layers except layer "Parcel Basemap". It seems to me that the Identify Widget may not work with Tiled layer. The log file shows that the Identify task times out for tiled layer. I also did another test. I moved the layer "parcel Basemap" under Basemaps section in Config.xml. Then I run the Identify Widget and it works perfectly. Since only one layer in Basemaps section can be displayed at the same time, we need to have at least one Bing map and Parcel Basemap displayed at the same time. Is there any workaround for this? Any help or suggestion is greatly appreciated.

LixinHuang · Answer

Robert,

I checked the parcel feature class and property table and found that there is a join between them. There is a total of more than 130 fields in the joined attribute table. The feature class and table is on ArcSDE geodatabase. It was also found that a relationship class was created between them. I copied the feature class and table into a file geodatabase without any relationship class created. I kept the join between them and publised the map service based on the new file geodatabase. I tried to use the Enhanced Identify Widget you develoepd against this new map service. It worked perfectly. I am guessing the relationship class may create the issue I encountered. Anyway, thanks for all your help and the great widgets you developed.

RobertScheitlin__GISP · Answer

Lixin,

This issue sounds specific to your data. I would try publishing a Map Service without the join and see what happens. Do you have hundreds of fields or something? Does it contain a special field like a GUID or RASTER field? Can you accomplish an identify task directly from the REST Services page?

LixinHuang · Answer

Since the users requested the functions of identifying parcel layer, I have to make the Identify Widget work for our parcel layer. I created a non-tiled map service only contains parcel boundary feature class and property table. Also we have parcel boundary feature class joined with property table. The Identify Widget still did not work with the newly created map service. It made our ArcGIS Server fully loaded until the memory was exhaused. I also checked the ArcGIS Server log file. The log files showed that the Identify task started for this map service and it never stopped. It seems that our parcel boundary feature class does not work with the identify widget. The parcel boundary feature class has about 300K records and the property table has about 349K records. Is it possible that the number of records caused this issue? Any suggestions are greatly appreciated.