Select to view content in your preferred language

Roberts Identify Widget Issue with a Particular feature

4933
32
Jump to solution
01-10-2012 02:30 AM
AlanHope
Occasional Contributor
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
Tags (2)
0 Kudos
32 Replies
RobertScheitlin__GISP
MVP Emeritus
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]
0 Kudos
AlanHope
Occasional Contributor
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
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
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:
0 Kudos