Latest Contributions by DavidMartin

If that's happening, it sounds like you're using an ArcGIS tool or arcpy command to create the text file?? ArcGIS often keeps metadata on its datasets in xml files. I'd switch to using Python's built-in open() function: with open("filename.txt", "w") as f:     f.write("my_list_of_files_as_a_string") ... View more

This is simply because the Clip_Management tool doesn't honour the Cell Size Environment setting. To see which Environment settings are honoured by a tool, check the "Environments" section near the bottom of any tool's Help page. For Clip_Management, you can see that Cell Size is not included in this section: http://resources.arcgis.com/en/help/main/10.1/index.html#//00170000009n000000 To change the cell size, you would therefore need to use the Resample tool: http://resources.arcgis.com/en/help/main/10.1/index.html#/Resample/00170000009t000000/ ... where you can specify Cell Size as one of the parameters. ... View more

Thanks, although that would only affect the display of the raster after it has been created. I'm faced with trying to create multi-band rasters with, say, 10 bands. Each band represents an environmental variable. I will later want to apply an Extract Band Raster Function to these rasters in order to pull out specific environmental variables, and so each variable must correspond to a constant band number. But if, when I'm creating the raster, I have a missing variable, then omitting it could affect the band numbers of all the other bands, UNLESS I can in some way have a "missing" band (or a quick and simple way of filling it with NODATA). And as stated above, I have the difficulty that if the variable for the first band is missing, then I don't yet know the extent or cell size of my raster in order to create a suitable constant raster that is filled with NODATA. ... View more

Go to this link and click on "Download Sample Application" (top right)... http://resources.arcgis.com/en/help/runtime-wpf/samples/index.html#/SubLayer_List/02q20000003t000000/ ... View more

Thanks for testing it! However, one of my issues is that I don't know until runtime what the extent of the multi-band raster will be. Meanwhile, to create my NODATA raster, I'd clearly need an extent (and I guess I might also need to ensure that its cell size is the same as the other bands??). If the variable that should go in Band 1 is missing, then I don't yet have any other bands to refer to in order to get the extent or cell size... which is why I was hoping that it might be possible simply to have a "missing" band... ... View more

That looks a lot easier to understand! However, refer back to my first post in this thread. It seems that while the visibility of a layer in your map package is captured by LayerInfo.DefaultVisibility, the default for Layer.Visibility is nevertheless always Visible. I'd say you'll therefore need to set your Layer.Visibility explicitly by referring to the relevant LayerInfo.DefaultVisibility. If you do this before your Legend initializes, then I'd imagine you'd see what you'd expect in terms the layer selection therein. If the Legend has already initialized, then you may need to call Legend.Refresh() to get it to sync with the map again (I'm guessing here!). ... View more

All the information you should need to know can be found under the "Licensing and Deploying Applications" section of this url: http://resources.arcgis.com/en/help/runtime-wpf/concepts/index.html#//017000000031000000 Assuming you have an EDN subscription, then you will have already authorised your software for development purposes on your machine. You can now use the "License Viewer" tool that comes with your installation of the SDK (access it from the Start menu) to get the appropriate license code for a Testing scenario. This provides you with code that needs to be pasted into Application.xaml.cs in your solution. You'll then need to rebuild a release copy of your solution which you can deploy according to the instructions in the above link (which also involves using the Deployment Builder tool). With a Test deployment, every time a user fires up your application, they will get a message to remind them that it is only for test purposes. To use a Deployment license, you'll need to have bought a pack of 25 Standard Deployment licenses from your local distributor UNLESS your code doesn't use much by way of local services and is able to run on a free Basic Deployment license - which can be obtained from your Customer Care portal. Whichever type of deployment license you wish to use, you'll need to run the Software Authorisation Wizard again (that comes with your installation of the SDK), and provide it with your deployment license string, so as to ensure that you're then able to get the necessary code out of the License Viewer tool, before following the same deployment process as before. Simple, eh(?!) ... View more

I may be showing my ignorance here, but I don't understand your distinction between a visible layer and a selected layer. If a layer is selected in the TOC (i.e. its checkbox is ticked) then wouldn't you expect it to be visible in the Map? (Unless it was outside its scale range perhaps?) Your data template also looks rather complicated. For one thing, you have a checkbox that binds its IsEnabled property to the layer's IsVisible property. That would mean that as soon as the layer is no longer visible, you'd have no means by which to make it visible again (because the checkbox would be disabled). I'd refer to the example given here for a useful starting point: http://resources.arcgis.com/en/help/runtime-wpf/samples/index.html#/Interactive_Legend/02q2000000nr000000/ ... View more

@Francois, I'm no longer clear now by what you mean when you say the layers are selected in the legend. Do you simply mean they're listed when you want them not to be? If this is the case, you can set Legend.ShowOnlyVisibleLayers = true ... View more

If you're using the esri:Legend control as a TOC, then you must have skinned the control by overriding its default DataTemplates. I'll guess that you have used CheckBoxes in the DataTemplate? So these must have their IsChecked property binding to the IsEnabled property of the LayerItemViewModel class? If this class isn't initializing the IsEnabled property according to the layer visibilities of the Map, then it could be worth calling Legend.Refresh() after you have set the Map's layer visibilities. If that doesn't work, you could always initialize the IsEnabled property in code using the DefaultVisibility previously discussed? Also worth checking (copied from the doc) : Note: The Legend.LayerItemsMode Property has great impact on what is displayed in the Legend. For users who want to see the most information available in the Legend, developers should set the LayerItemsMode to Tree. If customizations are made to the MapLayerTemplate and they seem to be overridden at runtime back to a default setting, it is most likely that the LayerItemsMode is set to the default of Flat and it should be set to Tree. ... View more

ESRI.ArcGIS.Client.LayerInfo.DefaultVisibility is probably what you need here. Here's a sample: http://resources.arcgis.com/en/help/runtime-wpf/samples/index.html#/SubLayer_List/02q20000003t000000/ ...where in the code behind, the ArcGISLocalDynamicMapServiceLayer.VisibleLayers is being set on initialization by the method "GetDefaultVisibleLayers", which simply returns an array of Layer IDs, the LayerInfo.DefaultVisibility of which is true. ... View more

I can't offer a solution, but I know what I'd try next - using absolute uri's to the images instead of relative ones. I'm guessing your images have a build action of "Resource"? You could also try setting this to "Content" and using the uri syntax: <Image Source="/WPFApplicationName;component/Assets/ImageName.png" /> Could be a red herring, but it's where I'd look next... ... View more