Hi Robert You had been assisting me with an Issue regarding the identify widget in a separate thread located here. I wanted to start a new thread so that you could get credit for answering a question should you be able to do that for me (I have no doubts that you will be able to help) The previous thread is located In this link I have now narrowed this down to an Issue with the particular feature I added our Manholes to the XML and these were identifiable using the following XML false visible 5 2000 true false true true true false false false point Click to Zoom to Point Identify Results Use the identify tool to identify features on the map: Identify by Point Identify by Polyline Identify by Rectangle Identify by Polygon Clear Loading... Imagery Manholes UGS_ID,NEIGHBORHO 2000 false Pole Master POLEID,MUNI 2000 false However the Pole Master features are not returned in the identify results Here is my REST end point Layer: Pole Master (ID: 0) Display Field: POLEID Type: Feature Layer Geometry Type: esriGeometryPoint ...... Fields: OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID) POLEID (Type: esriFieldTypeString, Alias: POLEID, Length: 16 ) MUNI (Type: esriFieldTypeString, Alias: MUNI, Length: 20 ) ....... The Pole Master Table is a bit of beast and we are in the process of restructuring it however this wont be for the next 6-12 months. Any ideas why the Manholes show but the Poles do not? I will post the IE Dev mode response in the next post as it took me over the limit Thanks for any assistance you are able to provide Al

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Roberts Identify Widget Issue with a Particular feature

AlanHope

Hi Robert
You had been assisting me with an Issue regarding the identify widget in a separate thread located here.
I wanted to start a new thread so that you could get credit for answering a question should you be able to do that for me (I have no doubts that you will be able to help)
The previous thread is located In this link
I have now narrowed this down to an Issue with the particular feature
I added our Manholes to the XML and these were identifiable using the following XML

<?xml version="1.0" ?> <configuration>  <betareturngeometryfix>false</betareturngeometryfix>  <identifylayeroption>visible</identifylayeroption>  <identifytolerance>5</identifytolerance>  <defaultzoomscale>2000</defaultzoomscale>  <keepidentifyactive>true</keepidentifyactive>  <returngeometryforzoom>false</returngeometryforzoom>  <enablelineselect>true</enablelineselect>  <enbleextentselect>true</enbleextentselect>  <enablepolyselect>true</enablepolyselect>  <enablemouseovergraphicsinfo>false</enablemouseovergraphicsinfo>  <enablemouseoverrecordinfo>false</enablemouseoverrecordinfo>  <usemaptime>false</usemaptime>  <autoactivatedtool>point</autoactivatedtool><!-- possible values are extent or polygon or mappoint or polyline or nothing -->  <labels>   <zoom2message>Click to Zoom to Point</zoom2message>   <identifylabel>Identify</identifylabel>   <resultslabel>Results</resultslabel>   <descriptionlabel>Use the identify tool to identify features on the map:</descriptionlabel>   <pointlabel>Identify by Point</pointlabel>   <linelabel>Identify by Polyline</linelabel>   <rectlabel>Identify by Rectangle</rectlabel>   <polylabel>Identify by Polygon</polylabel>   <clearlabel>Clear</clearlabel>   <loadinglabel>Loading...</loadinglabel>  </labels>  <useproxy>   <proxylayer>    <!--name>Imagery</name-->   </proxylayer>  </useproxy>  <layers onlythese="true">   <layer>    <name>Manholes</name>    <fields>UGS_ID,NEIGHBORHO</fields>    <links>     <link includeinresults="false" field="" alias="">      <linkprefix></linkprefix>      <linksuffix></linksuffix>      <iconfield></iconfield>      <iconprefix></iconprefix>      <iconsuffix></iconsuffix>     </link>    </links>    <zoomscale>2000</zoomscale>    <forcescale>false</forcescale>   </layer>     <layer>    <name>Pole Master</name>    <fields>POLEID,MUNI</fields>    <links>     <link includeinresults="false" field="" alias="">      <linkprefix></linkprefix>      <linksuffix></linksuffix>      <iconfield></iconfield>      <iconprefix></iconprefix>      <iconsuffix></iconsuffix>     </link>    </links>    <zoomscale>2000</zoomscale>    <forcescale>false</forcescale>   </layer>  </layers>  <symbols>      <simplefillsymbol color="0x448ccb" alpha="0.4" style="solid">       <outline color="0x448ccb" alpha="0.8" width="2"/>      </simplefillsymbol>      <simplemarkersymbol style="circle" size="12" color="0x448ccb" alpha="0.8" xoffset="0" yoffset="0" angle="0">       <outline style="solid" color="0xffffff" alpha="0.8" width="1"/>      </simplemarkersymbol>      <picturemarkersymbol url="assets/images/i_info.png" height="30" width="30" xoffset="0" yoffset="0" />   <simplelinesymbol color="0x448ccb" alpha="0.8" width="2"/>     </symbols> </configuration>

However the Pole Master features are not returned in the identify results
Here is my REST end point
Layer: Pole Master (ID: 0)
Display Field: POLEID
Type: Feature Layer
Geometry Type: esriGeometryPoint
......
Fields:
OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID)
POLEID (Type: esriFieldTypeString, Alias: POLEID, Length: 16 )
MUNI (Type: esriFieldTypeString, Alias: MUNI, Length: 20 )
.......

The Pole Master Table is a bit of beast and we are in the process of restructuring it however this wont be for the next 6-12 months.
Any ideas why the Manholes show but the Poles do not?

I will post the IE Dev mode response in the next post as it took me over the limit

Thanks for any assistance you are able to provide
Al

Find more posts tagged with

Accepted answers

RobertScheitlin__GISP

Alan,

Well here is the bad news and good news... The Good is that I was successfully able to identify the mapservice I produced using they FGDB you provided. That means the bad news is that you have a configuration or an actual map service corruption issue. Next recommended step would be to has your GIS Manager export out the whole layer and publish a new seperate map service for this layer and test it with the identify widget.

[ATTACH=CONFIG]11082[/ATTACH]

Alan.jpg

congruent_points.xlsx

All comments

RobertScheitlin__GISP

Alan,

Sounds good. Though your issue is not actually solved I believe you can say I have answered your post on this.

So please click the top arrow (promote) and to click the Mark as answer check as shown below:

AlanHope

Robert
Thanks for looking into this - We are in the process of restructuring the polemaster table so once this is done I will publish out a new service based on this. We are also in consultation with ESRI Geodatabase support due to an ArcPAD Issue we are experiencing. Once we get this problem worked through my hope is that we may find this problem also disappears.
Al

RobertScheitlin__GISP

Alan.jpg

congruent_points.xlsx

MLowry

Could you post a screenshot of your REST services directory showing where the layer that's not working is located?

AlanHope

Robert
Attached is what you requested - I had our GIS manager produce this so if it isn't what you need let me know and I will work to get it for you
Thanks
Al

FileGDB2ESRI_011112.gdb.zip

Clip_10.jpg

AlanHope

Robert I will attempt to accomplish this tomorrow or Thursday and post it here
Thanks again for all your efforts - I am kinda relieved that it is not something obvious on my part

RobertScheitlin__GISP

Alan,

I believe that the only course of action left for me to attempt to help you with would be if you could export out about 50 to 100 features to a File Geodatabase and let me make a web service from that here in house on my dev machine so that I can debug in Flash Builder and see why this particular service is causing issues. The identify widget code is very mature and has been used by thousands with out issue so this error is unusual. I though that my recient addition of the multi link supoprt could have introduced a bug but I am not leaning that way after carefully going over the code and all the back and forth we have done thus far.

AlanHope

Here you go

<?xml version="1.0" ?>
<configuration>
    <title>Duquesne Light Company GIS</title>
    <subtitle>GIS Asset Mapping Application</subtitle>
    <logo>assets/images/H_Logo_Blue.gif</logo>
    <style>
        <colors>0xffffff,0x39628c,0x355d89,0x294867,0xcee7f4</colors>
        <alpha>0.8</alpha>
        <titlefont name="Broadway"/>
        <subtitlefont name="null"/>
        <font name="Verdana" size="14"/>
    </style>
    <!-- replace the following url with your own geometryservice -->
    <geometryservice url="http://tasks.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer" useproxy="false"/>
    <!-- UI elements -->
    <!-- widgets organized into widget containers that manage close/open etc -->
    <!-- supported layout property options: horizontal(default)|float|vertical|fix-->
    <widgetcontainer layout="float">
        <widget left="430" top="90" icon="assets/images/i_bookmark.png" label="Bookmarks" config="widgets/Bookmark/BookmarkWidget.xml" url="widgets/Bookmark/BookmarkWidget.swf"/>
        <widget url="widgets/Search/SearchWidget.swf" config="widgets/Search/SearchWidget_Search.xml" label="Search" icon="assets/images/i_search.png"/>
        <widget url="widgets/Legend/LegendWidget.swf" config="widgets/Legend/LegendWidget_Legend.xml" label="Legend" icon="assets/images/Legend32.png"/>
        <widget left="100" top="90" icon="assets/images/i_target.png" label="Find an address" config="widgets/Locate/LocateWidget_Bing.xml" url="widgets/Locate/LocateWidget.swf"/>
        <widget left="390" top="400" icon="assets/images/i_print.png" label="Print" config="widgets/Print/PrintWidget.xml" url="widgets/Print/PrintWidget.swf"/>
    <widget url="widgets/Identify/IdentifyWidget.swf" config="widgets/Identify/IdentifyWidget.xml" label="Identify" icon="assets/images/i_info.png"/>
    </widgetcontainer>
    <widget url="widgets/OverviewMap/OverviewMapWidget.swf" config="widgets/OverviewMap/OverviewMapWidget.xml" right="-2" bottom="-2"/>
    <widget url="widgets/MapSwitcher/MapSwitcherWidget.swf" config="widgets/MapSwitcher/MapSwitcherWidget.xml" right="20" top="55"/>
    <widget url="widgets/HeaderController/HeaderControllerWidget.swf" config="widgets/HeaderController/HeaderControllerWidget.xml" left="0" top="0"/>
    <widget url="widgets/Coordinate/CoordinateWidget.swf" config="widgets/Coordinate/CoordinateWidget.xml" label="Coordinate" icon="assets/images/i_globe.png" left="3;" bottom="3"/>
    <widget url="widgets/Navigation/NavigationWidget.swf" config="widgets/Navigation/NavigationWidget.xml" left="10" top="50"/>
  <widget url="widgets/Splash/SplashWidget.swf" config="widgets/Splash/SplashWidget.xml" label="Splash" icon="assets/images/i_globe.png"/>
  
    <map esrilogovisible="true" openhandcursorvisible="true" scalebarvisible="true" zoomslidervisible="false" wraparound180="true" initialextent="-8965423.97778172 4898407.752194342 -8837162.644319147 4974539.032366407" top="40">
        <basemaps>
            <layer type="tiled" label="Streets" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer" visible="true"/>
            <layer type="tiled" label="Imagery" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer" visible="false"/>
            <layer type="tiled" label="Topographic" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer" visible="false"/>
        </basemaps>
        <operationallayers>
            <layer type="dynamic" label="Landbase" alpha="0.5" url="http://wasgist/ArcGIS10/rest/services/Maps/Landbase/MapServer" visible="true">
                <sublayer id="0" popupconfig="popups/PopUp_Orig_Pole.xml"/>
                <sublayer id="1" popupconfig="popups/PopUp_GIS_PoleMap.xml"/>
        <sublayer id="8" popupconfig="popups/PopUp_ccu.xml"/>
            </layer>
            <layer type="dynamic" label="DLC Web Map" url="http://wasgist/ArcGIS10/rest/services/Maps/DLCWebMap/MapServer" visible="true">
                <sublayer id="0" popupconfig="popups/PopUp_Poles.xml"/>
                <sublayer id="6" popupconfig="popups/PopUp_TransCkt.xml"/>
                <sublayer id="7" popupconfig="popups/PopUp_TransStruct.xml"/>
                <sublayer id="10" popupconfig="popups/PopUp_kv345.xml"/>
                <sublayer id="9" popupconfig="popups/Popup_kv138.xml"/>
                <sublayer id="8" popupconfig="popups/Popup_kv69.xml"/>
                <sublayer id="5" popupconfig="popups/PopUp_River_X_tower.xml"/>
                <sublayer id="1" popupconfig="popups/PopUp_Manholes.xml"/>
                <sublayer id="4" popupconfig="popups/PopUp_Subs.xml"/>
                <sublayer id="24" popupconfig="popups/PopUp_BVR_PDOT.xml"/>
                <sublayer id="23" popupconfig="popups/PopUp_AGHST_PDOT.xml"/>
                <sublayer id="12" popupconfig="popups/PopUp_Parcels.xml"/>
                <sublayer id="42" popupconfig="popups/PopUp_Muni050603.xml"/>
            </layer>
        </operationallayers>
    </map>
</configuration>

RobertScheitlin__GISP

Alan,

What does your main config.xml look like?

AlanHope

Robert
I updated the XML it now reads as follows

<?xml version="1.0" ?>
<configuration>
 <betareturngeometryfix>false</betareturngeometryfix>
 <identifylayeroption>visible</identifylayeroption>
 <identifytolerance>5</identifytolerance>
 <defaultzoomscale>2000</defaultzoomscale>
 <keepidentifyactive>true</keepidentifyactive>
 <returngeometryforzoom>false</returngeometryforzoom>
 <enablelineselect>true</enablelineselect>
 <enbleextentselect>true</enbleextentselect>
 <enablepolyselect>true</enablepolyselect>
 <enablemouseovergraphicsinfo>false</enablemouseovergraphicsinfo>
 <enablemouseoverrecordinfo>false</enablemouseoverrecordinfo>
 <usemaptime>false</usemaptime>
 <autoactivatedtool>point</autoactivatedtool><!-- possible values are extent or polygon or mappoint or polyline or nothing -->
 <labels>
  <zoom2message>Click to Zoom to Point</zoom2message>
  <identifylabel>Identify</identifylabel>
  <resultslabel>Results</resultslabel>
  <descriptionlabel>Use the identify tool to identify features on the map:</descriptionlabel>
  <pointlabel>Identify by Point</pointlabel>
  <linelabel>Identify by Polyline</linelabel>
  <rectlabel>Identify by Rectangle</rectlabel>
  <polylabel>Identify by Polygon</polylabel>
  <clearlabel>Clear</clearlabel>
  <loadinglabel>Loading</loadinglabel>
 </labels>
 <useproxy>
  <proxylayer>
   <!-- <name>Imagery</name> -->
  </proxylayer>
 </useproxy>
 <layers onlythese="false">
  <layer>
   <name>Pole Master</name>
    <fields></fields>
     <links>
      <link includeinresults="false" field="" alias="">
       <linkprefix></linkprefix>
       <linksuffix></linksuffix>
       <iconfield></iconfield>
       <iconprefix></iconprefix>
      <iconsuffix></iconsuffix>
      </link>
     </links>
          <zoomscale>2000</zoomscale>
          <forcescale>false</forcescale>
  </layer>
 </layers>
 <symbols>
     <simplefillsymbol color="0x448ccb" alpha="0.4" style="solid">
      <outline color="0x448ccb" alpha="0.8" width="2"/>
     </simplefillsymbol>
     <simplemarkersymbol style="circle" size="12" color="0x448ccb" alpha="0.8" xoffset="0" yoffset="0" angle="0">
      <outline style="solid" color="0xffffff" alpha="0.8" width="1"/>
     </simplemarkersymbol>
     <picturemarkersymbol url="assets/images/i_info.png" height="30" width="30" xoffset="0" yoffset="0" />
  <simplelinesymbol color="0x448ccb" alpha="0.8" width="2"/>
    </symbols>
</configuration>

When I intially made this change I got the following message after performing an ID operation on a point - Data was returned in Fiddler the message remained in the widget
[ATTACH=CONFIG]11057[/ATTACH]

Capture1.PNG

pdf rendering.jpg

RobertScheitlin__GISP

Alan,

Try this:

onlythese="false" and

        <layer>
            <name>Pole Master</name>
            <fields></fields>
            <links>
                <link includeinresults="false" field="" alias="">
                    <linkprefix></linkprefix>
                    <linksuffix></linksuffix>
                    <iconfield></iconfield>
                    <iconprefix></iconprefix>
                    <iconsuffix></iconsuffix>
                </link>
            </links>
            <zoomscale>2000</zoomscale>
            <forcescale>false</forcescale>
        </layer>

AlanHope

I added the new version and here is what I found
1) Attempted with ONLYTHESE TRUE with both Manholes and Pole Master - same result - Manholes features show data and are highlighted and Pole Master features do NOT show data or highlight - Data showed in FIDDLER 2
2) Attempted with ONLYTHESE TRUE with only PoleMaster - No data or feature highlighted - Data returned in FIDDLER 2
3) Attempted with ONLYTHESE FALSE - Widget is still in a loading state after 10 minutes - Data is returned in FIDDLER 2

If you have a debug version you would like me to run through I can do...
Also if there are any other scenarios you would like me to run let me know, the invite to perform a remote session via join.me is still open
Thanks again for all your hard work
Al

RobertScheitlin__GISP

Alan,

I want you to try this new compiled version of the IdentifyWidget and see if you get any different results. I sounds more nad more like a widget bug now.

Identify.zip

Code.zip

AlanHope

I published a service which contained only the fields suggested and while fiddler 2 showed data being returned from the tables correctly nothing was displayed within the widget
I am stumped.....
Any ideas?
Al

AlanHope

Alan,

No that's fine leave it as true. Are you using the compiled or uncompiled version of the viewer?

Using the Compiled version

RobertScheitlin__GISP

Alan,

No that's fine leave it as true. Are you using the compiled or uncompiled version of the viewer?

AlanHope

Alan,

So when you see in fiddler that you are getting results in the http response is this when you have the onlythese="false"? if so what happens when you set it back to true?

I actually had it set to true when I saw that
Would you like me to set it to False?
No Joins or Relates on that feature class according to the mxd file used to create the msd
I am working on creating the single layer mxd as we speak

RobertScheitlin__GISP

Alan,

So when you see in fiddler that you are getting results in the http response is this when you have the onlythese="false"? if so what happens when you set it back to true?

AlanHope

Update
I attempted to Debug this with Fiddler 2 and found that the service is returning values
In the JSON tab I get the following
[ATTACH=CONFIG]11047[/ATTACH]
So the data is coming back from the end point, dont know if this provides any insight...
I am going to hit another service connected to the same data
and also
Create a service looking at only the fields necessary.
I will also PM you
Thanks again
Al

I noticed that you have PM'ing disabled so I will extend this invite to a remote screen session if you are willing...

Capture.PNG

2020-03-25_16-17-09.png

AlanHope

Alan,

I was just hoping that I could hit the service here and debug what is going on... Going forward from here is tough... Does the table have joins? If it was me I would make a brand new mxd with just this layer and hide any unneeded fields (except "shape" and ObjectId) and publish that mxd as a map service for testing. I am really getting low on ideas for you.

Robert
Thanks for the work you have already put in on this. I will give your suggestion a try to see if it resolves the Issue. I will update once I get results
Al

RobertScheitlin__GISP

Alan,

I was just hoping that I could hit the service here and debug what is going on... Going forward from here is tough... Does the table have joins? If it was me I would make a brand new mxd with just this layer and hide any unneeded fields (except "shape" and ObjectId) and publish that mxd as a map service for testing. I am really getting low on ideas for you.

AlanHope

Alan,

Is your map service publicly accessible?

No it is not.
I tweaked the XML slightly and it now shows the loading dialog instead of the false when loading the data but it remains at the loading stage

This table has approx 300,000 records and over 100 columns is it possible that this could be the source of the Issue?

What did you want to review on the map service?

RobertScheitlin__GISP

Alan,

Is your map service publicly accessible?

AlanHope

Alan,

Try leaving the manholes commented out but change the onlythese to false and see what happens.

Tried this

 <layers onlythese="false">
<!--<layer>
   <name>Manholes</name>
   <fields>UGS_ID,NEIGHBORHO</fields>
   <links>
    <link includeinresults="false" field="" alias="">
     <linkprefix></linkprefix>
     <linksuffix></linksuffix>
     <iconfield></iconfield>
     <iconprefix></iconprefix>
     <iconsuffix></iconsuffix>
    </link>
   </links>
   <zoomscale>2000</zoomscale>
   <forcescale>false</forcescale>
  </layer> -->
    <layer>
   <name>Pole Master</name>
   <fields>POLEID,OWNERSHIP,MUNI</fields>
   <links>
    <link includeinresults="false" field="" alias="">
     <linkprefix></linkprefix>
     <linksuffix></linksuffix>
     <iconfield></iconfield>
     <iconprefix></iconprefix>
     <iconsuffix></iconsuffix>
    </link>
   </links>
   <zoomscale>2000</zoomscale>
   <forcescale>false</forcescale>
  </layer>
 </layers>

and here is what I got
[ATTACH=CONFIG]11041[/ATTACH]
Which makes me think that may XML is not getting parsed correctly??

Capture.PNG

geocode.docx

RobertScheitlin__GISP

Alan,

Try leaving the manholes commented out but change the onlythese to false and see what happens.

AlanHope

Alan,

Have you tried to only having the Pole Master layer listed in the IdentifyWidget.xml?

Robert
I tried the following after clearing the REST cache and the browser cache - and got nothing presented in the widget after drawing a rectangle around 2 points, I also attempted with the point selector and got nothing in the results.

<layers onlythese="true">
  <!-- <layer>
   <name>Manholes</name>
   <fields>UGS_ID,NEIGHBORHO</fields>
   <links>
    <link includeinresults="false" field="" alias="">
     <linkprefix></linkprefix>
     <linksuffix></linksuffix>
     <iconfield></iconfield>
     <iconprefix></iconprefix>
     <iconsuffix></iconsuffix>
    </link>
   </links>
   <zoomscale>2000</zoomscale>
   <forcescale>false</forcescale>
  </layer> -->
    <layer>
   <name>Pole Master</name>
   <fields>POLEID,OWNERSHIP,MUNI</fields>
   <links>
    <link includeinresults="false" field="" alias="">
     <linkprefix></linkprefix>
     <linksuffix></linksuffix>
     <iconfield></iconfield>
     <iconprefix></iconprefix>
     <iconsuffix></iconsuffix>
    </link>
   </links>
   <zoomscale>2000</zoomscale>
   <forcescale>false</forcescale>
  </layer>
 </layers>

I uncomment the Manholes section and get manholes results? I'm confused (although this is a normal state of affairs!!) 🙂

RobertScheitlin__GISP

Alan,

Have you tried to only having the Pole Master layer listed in the IdentifyWidget.xml?

DEAF_PROBERT_68_0-1775668085418.png

RachelWillmore_2-1775668548569.png

AlanHope

Alan,

In ArcCatalog find the feature Pole Master and right click on it and choose properties and under the general tab see if the "Coordinates include Z values. Used to store 3D data." has a check next to it.

This option is unchecked
I also verified and the manholes are configured the same way (Manholes are functional)

RobertScheitlin__GISP

Alan,

In ArcCatalog find the feature Pole Master and right click on it and choose properties and under the general tab see if the "Coordinates include Z values. Used to store 3D data." has a check next to it.

AlanHope

Alan,

Does this point feature z aware?

Robert
I am farily new to GIS so please forgive my ignorance but how would I verify that the point is Z aware?
Thanks
Al

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.