Latest Contributions by BrandonCopeland

Thanks Derek. I agree. In hindsight, I guess my question was more of "What are the typical ways of accessing third party HTTP APIs and providing that data through RESTful applications/APIs?". Not really related to ESRI's API at all. 🙂 ... View more

By default, map services return a maximum of 1000 features. This configuration can be changed from the Parameters tab of the Map Service Properties in either ArcCatalog or ArcGIS Server Manager. ... View more

Good work! Glad you got what you needed Ben. My take on MVVM really comes down to responsibility and separation of concerns. The view is about receiving input and setting how to display information (map click, formatting and displaying the coordinates, etc...). The view model is about retrieving data from the model or view, performing some presentation logic (publishing the coordinates via Messenger or whatever else you would like to do with them), and being able to test that logic. The Action in this case is just a tool to better wire those two together. Because its an Action, there's also the added benefit of being reusable and blendable. In my opinion, lots of MVVM newbies get caught up with the no code behind nonsense. In this case, you could have just as easily added a handler for the Map control's MouseMove event and set the property on the View Model in the code behind directly. You would still have the same separation of concerns and still just as testable. Either way, the coordinate transformation logic and wiring to the view model is handled by the view. Without the use of an Action, you would have sacrificed the reuse and blendability, but maybe that's not a big deal for your situation. ... just my .02 ... View more

Darina makes a good point. This situation is better suited for a TriggerAction than a behavior. A nice solution would be an action to update a property on another object when invoked. Luckily, Microsoft already did this for us with the ChangePropertyAction in the Blend SDK. Using ChangePropertyAction, you can bind to TextBlock.Text or a property on your View Model - whatever you like. We do need to extend it and do 1 small override for our coordinate calculation. It ends up looking like... using System.Windows; using System.Windows.Input; using ESRI.ArcGIS.Client; using ESRI.ArcGIS.Client.Geometry; using ESRI.ArcGIS.Client.Projection; using Microsoft.Expression.Interactivity.Core; public class CoordinateChangePropertyAction : ChangePropertyAction {     protected override void Invoke(object parameter)     {         this.Value = GetCoordinateString(parameter as MouseEventArgs);         base.Invoke(parameter);     }     private string GetCoordinateString(MouseEventArgs e)     {         string mouseCoordString = string.Empty;         Map map = AssociatedObject as Map;         Point mouseLoc = e.GetPosition(map);         MapPoint coordLoc = map.ScreenToMap(mouseLoc);         if (coordLoc != null)         {             WebMercator webMercator = new WebMercator();             MapPoint latLon = webMercator.ToGeographic(coordLoc) as MapPoint;             mouseCoordString = string.Format("Lon {0:F4}° Lat {1:F4}°", latLon.X, latLon.Y);         }         return mouseCoordString;     } } and the XAML... (this is assuming you have a LayoutRoot bound to your view model) <esri:Map x:Name="map_BaseMap">              <i:Interaction.Triggers>               <i:EventTrigger EventName="MouseMove">                <MyActionNamespace:CoordinateChangePropertyAction TargetObject="{Binding DataContext, ElementName=LayoutRoot}" PropertyName="SomePropertyOnTheViewModelToBindTo"/>               </i:EventTrigger>              </i:Interaction.Triggers> </esri:Map> That's it - now you have it in your view model. Expose it in whatever view model is supporting your TextBlock. Of course if ChangePropertyAction is not available for your project or you can't use the Blend SDK for any reason, you could still use Darina's action from above. You would just need change the Type from TextBlock to whatever fits for you (your View Model perhaps or some abstraction of it). Instead of updating the .Text property, you would update the needed property on that object. One suggestion. You may want to consider eliminating the formatting to string from the action. Just return a MapPoint. Leave it up to the TextBlock displaying the data to decide how it should be formatted. Its really simple to do so using Binding's StringFormat property or IValueConverter. ... View more

Are the Map and coordinate TextBox in the same View or in 2 different Views? Knowing only about these 2 controls and no other features of your application, I would have them in the same view. This is simply because the TextBox involves no additional presentation logic, model data, or unique feature set. Its just an additional control displaying the same data as your map but in a different way. So lets tackle that option (both in the same view). Essentially, your TextBox would like to display some information from another control in the UI. This is no different than if it wanted to display the Width of the map. No need to have the View Model intervene there - just bind one control to the other. The only problem is mouse coordinates are not publicly exposed like Width. We need to find some way to expose those from the Map. A Behavior is a valid option. You could create a Behavior with a property (or properties) to describe mouse coordinates and bind your TextBox to that property. If they are in different Views, the idea could still be the same. Now, you just need some way of communicating the mouse coordinates between Views (View Models). You could TwoWay bind the coordinates to your View Model that is updating some underlying model. Implement some decoupled way of sharing that model like Messenger/Event Aggregator or a common Service. Expose as a property on the second View Model and bind your TextBox to that. ... View more

It seems that the visibility of your radio button is really just about UI, not the underlying model. 2 options taking that perspective... Create Visual States to represent different visual representations of your interface (RadioButton visible or not) and change the state based on whatever logic applies. This could be done with in XAML with a DataStateBehavior. If its only the visibility of a single control you're concerned about, that could be overkill. Alternatively, you could bind the visibility to whatever value is determining it and build an IValueConverter to return Visible or Collapsed based on that value. ... View more

How are the Layers created? Can you just set Visible = false (or xaml <Layer Visible=false />) at that time? ... View more

You can control compatibility mode from IIS or via html headers ... View more

Quick and untested, but something like... findTask.ExecuteCompleted += OnExecuteCompleted; private void OnExecuteCompleted(object sender, FindEventArgs e) {      Geometry zoomGeometry;      foreach (var result in e.FindResults)      {           if (zoomGeometry == null)           {                zoomGeometry = result.Feature.Geometry.Extent;                continue;           }           zoomGeometry = zoomGeometry.Extent.Union(result.Feature.Geometry.Extent);      }           YourMap.Extent = zoomGeometry; } YourMap is a reference to your map control ... View more

ESRI.ArcGIS.Client.Bing.Transform does just that ... View more

Can you give any examples or point me in the right direction for... using "an attached property that takes care of handling binding" Attached Property... public static class MapExtentHelper {     public static readonly DependencyProperty MapZoomGeometryProperty = DependencyProperty.RegisterAttached("MapZoomGeometry", typeof(Geometry), typeof(MapExtentHelper), new PropertyMetadata(new PropertyChangedCallback(OnMapZoomGeometryChanged)));     public static Geometry GetMapZoomGeometry(DependencyObject d)     {      return (Geometry)d.GetValue(MapZoomGeometryProperty);     }         public static void SetMapZoomGeometry(DependencyObject d, Geometry value)     {      d.SetValue(MapZoomGeometryProperty, value);     }         private static void OnMapZoomGeometryChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)     {         Map map = d as Map;         if (map == null) throw new ArgumentException("DependencyObject must be of type ESRI.ArcGIS.Client.Map");         Geometry newZoomGeometry = GetMapZoomGeometry(map);         if (map.Extent == null)         {                map.Extent = newZoomGeometry.Extent;         }         else         {             map.ZoomTo(newZoomGeometry); }     } } Use with Map control... <esri:Map Extensions:MapExtentHelper.MapZoomGeometry="{Binding SomeGeometryOnViewModel}"/> Where "Extensions" is the mapped namespace for your static class. ... View more

Agree with Jennifer. Expose properties like Layers from your view model (not UI elements like a map control) and bind to those. One workaround for properties like Map.Extent that will not support binding is attached properties. Create an attached property (maybe BindableExtent) and bind that to your view model. In the callback for the property change, do some work to set the actual map extent. Quick and dirty example:         public static readonly DependencyProperty BindableExtentProperty = DependencyProperty.RegisterAttached("BindableExtent", typeof(Geometry), typeof(OwnerClass), new PropertyMetadata(new PropertyChangedCallback(OnBindableExtentChanged)));         public static Geometry GetBindableExtent(DependencyObject d)         {             return (Geometry)d.GetValue(BindableExtentProperty);         }         public static void SetBindableExtent(DependencyObject d, Geometry value)         {             d.SetValue(BindableExtentProperty, value);         }         private static void OnBindableExtentChanged(DependencyObject d, DependencyPropertyChangedEventArgs e)         {             Map map = d as Map;             var newExtent = (Geometry)e.NewValue;             map.ZoomTo(newExtent);         } ... View more