Nadeem,Have you tried using <layers onlythese="false"> as your config file you have just posted has still got it set to true,RegardsAnthonyP.S here is a link that explains REST and how you access it:http://servicesbeta2.esri.com/arcgis/sdk/rest/index.html
Nadeem,Why are you setting the following fields:<field name="ZONING_NAME" alias="Zoning Name"/><field name="ZONING_TYPE" alias="Zoning Type" popuponly="true"/>In the data you sent me you do not have these fieldsTry setting <layers onlythese="false">And see if you get a result, if you do have a look at your REST endpoint and configure the widget with the appropiate field namesRegardsAnthony
Nadeem, It shouldn't make any xml files, just the swf when you compile. However, if you do have two xml files, did you make sure that your widget tag in the config.xml points to the one you are modifying? <widget label="Identify" left="430" top="80" height="150" icon="assets/images/i_info.png" config="widgets/Identify/IdentifyWidget_1.xml" url="widgets/Identify/IdentifyWidget.swf"/> R_
<widget label="Identify" left="430" top="80" height="150" icon="assets/images/i_info.png" config="widgets/Identify/IdentifyWidget_1.xml" url="widgets/Identify/IdentifyWidget.swf"/>
Nadeem,I published your data using 9.3.1 on our server and tested the identify widget which returned no result. Using firebug in Firefox I examined the request that was getting sent and the response. It seems that the server does not like the spatial reference details that it is being sent and is returning an error.The solution I found was to put the attribute wkid="29900" in the map tag in the main config file to force the application to use the correct spatial reference.All I had set in the identify tool was excludebasemaps set to false and <fields all="true" />. This returned the correct pixel value.I must add this was done with v2.5 and server 9.3.1RegardsAnthony
All, I just need to interject that you need to be careful not to confuse attributes between my widgets. The <fields all="true" /> is from the eSearch widget and not the Identify widget. There is no code what so ever in the Identify widget that uses all="true" in the fields element. 😉
<fields all="true" />
<layers onlythese="true"> <layer> <name>Elevation</name> <fields all="false"> <field name="Pixel Value" alias="NAVD88 (m)" numberformat="2|,|." /> </fields>
Nadeem,How big is the file? If it is small enough to email then by all means send it to me, my email address is the same as my username for this forum. I will not be able to look at it till later next week though.RegardsAnthony
Nadeem,I have published elevation data in the exact same way in which you are publishing your data. I found that although the alias in the REST endpoint for the pixel value says Value it actually returns as 'Pixel value' so the layers tag looks like this:<layer><name>DTED2</name><fields><field alias="Height" name="Pixel Value" /></fields>.......</layer>Are your field names an exact match to the Alias field in the REST endpoint?Is your service publicly available so we can look at itRegardsAnthony
Nadeem,Have you added your layer as a basemap or operational layer? If it is a basemap make sure you have changed the tag called excludebasemaps to falseRegardsAnthony
Once you get it configured to use your layers instead of the default in the identifyWidget.xml, you may have issues with raster data.I had to set <fields all="true" /> in the identifyWidget.xml for my raster layer in order to get the results.In case this help,R_
Nadeem,If you publish your image as part of a map service you can use the identify tool to return pixel values:http://www.arcgis.com/home/item.html?id=39cf66d58c234279ba728c50461a1a89This advise has been given before in this post:http://forums.arcgis.com/threads/67208-kernel-density-on-raster-image-using-flex-API-or-geoprocessing?p=233863#post233863Are you having difficulty with the process, if so please explain RegardsAnthony
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.