MapDotNet UX Help

What is in the box?

  1. WCF (SOAP and REST) Services for performing a variety of GIS tasks such as map and tile generation, spatial queries and edits and other GIS tasks
  2. A set of assemblies called Engine for providing the same functionality as the services but in disconnected and mobile applications
  3. A desktop tool for map design, ETL and tile caching called Studio
  4. A .NET SDK for Silverlight, WPF and HTML5 GIS application development
  5. Samples for Microsoft Visual Studio 2012.

What can I do first?

  1. Import spatial data into a SQL Server 2008/2012 (SQLServer) or SQL Azure instance. Use MapDotNet Studio to extract and transform data from shapefiles, ArcSDE™, or PostGIS and then load SQLServer. Even though you may consume and render spatial data directly from any source supported by MapDotNet UX, SQLServer is an excellent spatial database with plenty of support within the .NET development environment. If you plan on visualizing data in HTML5, WPF or Silverlight, use the popular Spherical Mercator projection when importing your data into SQLServer to improve performance and save the renderer having to re-project the data when rendering map tiles.

  2. Create a new map. Studio lets you add layers to your map from the supported data sources. Then symbolize those layers and save your map locally using the Studio Engine or to a MapDotNet UX Server to stand up a multi-user spatially-enabled HTML5, WPF or Silverlight application. You can always test your map deployed to the services by accessing the built-in data viewer (e.g. http://localhost/MapDotNetUX[your product version]/viewer.aspx)

  3. Develop an HTML5, Silverlight or WPF application.  There are different SDK components for the platforms, but once you learn to develop MapDotNet UX applications for one platform, you are well on your way to developing on other client platforms since the RIM (Rich Interactive Mapping) APIs are very similar. The quickest way to get started is with one of the installed sample applications.