Latest Contributions by HolgerSchade

Crossdomain policy and clientaccess policy are configuration files of your webserver (specifically IIS) and they affect access to all http requests (this can be the WMS but also all other resources on the webserver). I think you worry too much - the web server administrators who run the WMS should know about the fact that they should have a clientaccesspolicy and crossdomain on their webserver, ... View more

Try something like this in the Execute Method of your ICommand             ESRI.ArcGIS.Client.ArcGISTiledMapServiceLayer layer = new ArcGISTiledMapServiceLayer();             layer.ID = "Overview LayerName";             layer.Url = "http://services.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer";                         ESRI.ArcGIS.Client.Toolkit.OverviewMap oMap = new ESRI.ArcGIS.Client.Toolkit.OverviewMap();             oMap.Map = MapApplication.Current.Map;             oMap.Width = 100;             oMap.Height = 100;             oMap.Layer = layer;             oMap.MaximumExtent = new Envelope(-41381301, -19971868, 41381301, 19971868);             MapApplication.Current.ShowWindow("Overview", oMap); ... View more

Can anyone confirm that, when you want to consume any WMS in the ArcGIS web part, that the host server of the WMS must have the ClientAccessPolicy.xml and/or CrossDomain.xml files installed on the server? If this is the case, is it not a problem when you want to consume WMSs from other organisations? With more and more GIS data being published as WMS, would we have to contact each organisation that publishes a WMS we wish to consume and ask them to kindly add the url of our SharePoint server to their xml files to enable us to access it (assuming some of these organisations aren't willing to open access to all potential users - eg. for fear of heavy traffic on their server)? And likewise, if we wish to publish our own WMS for consumption by other organisations, we'd have to add their urls to our .xmls files? Thanks. I think you are misunderstanding the concept of crossdomain and clientaccesspolicy. If it is a publicly available WMS, the crossdomain.xml and clientaccesspolicy.xml will typically "wildcard" the access to these specific services - so that it is not necessary to include each foreign domain in the xml file. If the WMS shall be restriced in access, you can use the XML files to restrict the access to the WMS to individual computers or domains. So I definitely would suggest to use crossdomain.xml and clientaccesspolicy.xml on your webserver root to allow or restrict foreign access. ... View more

Thanks a lot - that worked ! The "sde:sqlserver:" bit was the thing I was missing 🙂 ... View more

Do you have an answer on this - because I can't find the menu items as well :-((( ... View more

Since nobody answered I had to debug it further. Finally I found the problem. ArcGIS Server cannot handle custom coordinate systems. You need to make sure that your map service is authored with a coordinate system with a well known ID (WKID) otherwise you run into a number of troubles. I would wish the API would check for that or even better it should handle custom coordinate systems. Anyhow, as soon as the service is authored with a WKID things seem o.k.. ... View more