MapDotNet UX Help

MapDotNet UX support for visualization is based on tile-based mapping. Although the UX web services can serve up map images for traditional non-tiled mapping applications, the WPF and Silverlight RIM controls are tile-based. The maps displayed in Studio UX are also tile-based. This form of map visualization is like the popular consumer mapping application Bing Maps for Enterprise. Tile-based mapping has its pros and cons. For many applications the pros outweigh the cons.


  1. Seamless panning and zooming navigation. The advantages of this are widely accepted and are beyond the scope of this document.
  2. Greatly enhances the ability to cache maps for both vector and imagery data locally on the client as well as on the server since tiles are at fixed, pre-defined extents
  3. Provides easier integration with popular third-party data services such as Bing Maps


  1. Increased complexity of mapping applications as you deal with quad-tree pyramids of data as opposed to loosely defined and arbitrary individual maps - though much of this complexity is hidden from the end-user in UX
  2. Often forces data into the popular spherical Mercator projection used by services such as Bing Maps - though custom projections are supported in UX for tile-based mapping
  3. Zoom levels between discrete pyramid levels are interpolated - though this can be seen as an advantage as a new map does not have to be rendered upon slight changes in zoom-level