Latest Contributions by LixinHuang

Robert, The Minimun Scale is 9029 and Maximu Scale is 0. The spatial reference is 102100. I am using the compiled version. Thanks. ... View more

Robert, Thanks for your reply. My map application is not publicly available. The parcel boundary feature class is not in a layer group in MXD. There is a scale dependency for that feature class. The  map service which includes the parcel boundary feature class is cached. I tried your Identify widget 2.5.5 with the same layer. It works. ... View more

Lixin,    I currently do not have any plans to support a Stand Alone Table Relate to have support for zoom to features. Thanks for your reply. ... View more

Hi Robert, Thanks for your latest Search Widget 2.5.1.7f. I like the new widget which can search on standalone table. I have a parcel standalone table and parcel boundary feature class. I created a relationship class between the table and feature class. I searched on the parcel table and clicked the Relate Table button to bring up the parcel feature class attribute table successfully. However, it seems to me that I cannot zoom to the related featue class. Does your widget support this? Any helps or suggestions would be greatly appreciated. ... View more

My issue was solved by your Idenftiy Widget 2.5.6. Thanks for your hard work and wonderful widget. ... View more

Thanks Robert. I am looking forward to your next release of Idenify widget. ... View more

Lixin,    This is default behavior for Polylines that only have two points as there is no easy way to calculate the mid point on client side. If you search a polyline that has more than two vertexes than it will use a vertex that is closest to the middle. Thanks for your quick reply, robert. ... View more

One of our users reported to me that the infowindow pointed to the end point of the polyline line feature returned from the search results for polyline feature class search. I am assuming infowindow should by default point to the center point of the ployline feature. Please see the attached screen capture of the result. The line from the search result is highlighted by yellow and the point the infowindow points to is in green. Any suggestions or helps would be greatly appreciated. ... View more

Robert, Thanks for your answers. I would appreciate if you could point me to the thread where you have helped other in the pass to setup an open SQL query expression. ... View more

Robert, Thanks for developing this wonderful widget. I have two questions on this widget. First, does it support querying standalone table with relationship class? Second, does it support multiple fields query with the logic like AND or OR? ... View more

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. ... View more

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. ... View more

I tried to change the layer type from tiled to dynamic. The same thing happened again. I finally figured out a workaround. I created another map service with the same MSD file as what map service Parcel Basemap uses. I removed the Query and Data capabilities from Parcel Basemap. The new map service has the Query and Data capabilities which is only used for Search Widget developed by you. Our GIS application works so far. Thanks for your help. Lixin,    Please try and change the Parcel Basemap type to dynamic and test again. <layer label="Parcel Basemap" type="dynamic" visible="true" alpha="0.6" url="http://mjcwgiststv01/GISSRV/rest/services/Parcel_Basemap/MapServer"> </layer> This just to test if the issue is with the layer being type tiled or if it is just something about your Map Service in general. ... View more