Latest Contributions by DominiqueBroux

ArcGIS Pro .Net SDK allows customizing and extending the new ArcGIS pro application‌ It's not identical to the Runtime .Net API but it follows the same principal. .AFAIK the ArcGIS pro SDK is not released yet (planned Q1 2015) ... View more

Could you share the tiled layer service that allows reproducing the issue? Thanks ... View more

The current WPF SDK is now the version 10.2.3. It can be downloaded from here. If you start a new project you should also consider using the new .Net API. ... View more

The current WPF SDK is now the version 10.2.3. It can be downloaded from here. If you start a new project you should also consider using the new .Net API. ... View more

You can try to set the FeatureLayer DisableClientCaching property to true. That will prevent from using the browser cache when updating the feature layer. Not sure it's your issue but it's worth the try. ... View more

Hi, You are right. The proxy used in the sample is sometimes not stable. We'll try to get that fixed ASAP. If you comment the proxy url it works only for the url (Real Time Earth Quakes) below. I think it depends on where the KMX/KML file is downloading from?. The SL proxy is mainly useful as a workaround to the SL cross domain access restrictions. Without proxy, SL can only access to sites that allow cross domain access such as the Earth Quake site: http://earthquake.usgs.gov/crossdomain.xml Without this cross access permission Silverlight can't access to the KML file. Note that you can (and should for production) set your own proxy server: Esri/resource-proxy · GitHub ... View more

- I do not know what to use for the tokenUrl. You don't have to know the token url, the first url parameter of GenerateCredentialTaskAsync is the ArcGIS secured resource  you want to access to. The token wil be discovered automatically internally. I would prefer to somehowget this taken care of during application startup. I want the layer to display as soon as the application is loaded. Yes. That's possible. You have actually 2 options: 1) Option 1: Generate a token when an authorization error is intercepted by the IdentityManager (i.e at runtime when trying to access to the secured services) To do that you have to define a challenge method that will handler the error and can, for example, generate a token with an hardcoded username/password. As, in this case ,the challenge method is just a call to GenerateCredentialAsync, the IM initialization can be as simple as: IdentityManager.Current.ChallengeMethod += (url, handler, options) => IdentityManager.Current.GenerateCredentialAsync(url, "<username>", "<password>", handler, options); 2) Option 2: At startup, generate a token and add it to IM which will use it when trying to access to the service Something like: // generate a token var crd = await Client.IdentityManager.Current.GenerateCredentialTaskAsync(<resource url>, <username>, <password>); // add the token to IM Client.IdentityManager.Current.AddCredential(crd); // activate IM without challenge (or set a challenge method for managing access to secure services not declared at startup) Client.IdentityManager.Current.Enabled = true; ... View more

Hi, Thanks for this info. This confirms there is something wrong at server side. The node coordinates returned by the query REST End Point are the same whatever the out spatial reference (example with WebMercator or WGS84). Concerning the join, it's not the same issue, the coordinates returned seem good but when too much data are requested the server returns an internal error. Not sure if these are bugs in ArcGIS server or if it's due to the way the features have been published. You might get better answers by posting the question on the server forum.. Thanks /Dominique ... View more

That beats me. It looks like a projection issue at server side but I don't get the reason. I'll try to reproduce locally (I guess your service is not publicly accessible?). As a workaround you might try publishing your service in 'WGS_1984_UTM_Zone_44N' instead of Web Mercator. May be the projection works in this case? ... View more

Humm, the issue doesn't seem to be at client side. The display is consistent with the returned geometry (x, y around 1000000 mean around Nigeria). Maybe an issue at server side or an issue due to how you published the service. If you try to display your published service in ArcMap, is it working well? If you try to display your published service in Silverlight by using an ArcGISDynamicMapServiceLayer, is it working well? ... View more

OK. Now the outSR parameter is set, unfortunately it doesn't seem to solve your issue. Could you show us how the geometry of the returned features look like (as in Jennifer's screenshot)? ... View more

Hi Sadanand, From your screenshoot, it seems you didn't set the OutSpatialReference as I suggested above. This parameter drives the SR of the returned features and is key to fix your issue. Once set, you should see a 'outSR' parameter in the query request sent to the server. Dominique. ... View more

No you don't need to create feature layers to get infos about features. You can use an Identify task that is executed at server side and returns info about the features under the specified geometry. There is a sample here: arcgis-runtime-samples-dotnet/IdentifySample.xaml.cs at master · Esri/arcgis-runtime-samples-dotnet · GitHub ... View more