This project is read-only.

WPF SharpMap Controls, as its name implies, is a set of WPF mapping controls, based on the SharpMap 2.0 GIS engine.
The main goal of this project is to provide an easy to use, high performing and comprehensive set of classes, which can be used “out of the box” to add a rich mapping experience to any WPF application.

A longer term goal, is to provide an extensible framework for WPF GIS applications, including the ability to create new editors, tools, and visualizes. The inspiration for the extensibility architecture is the Visual Studio 2008 WPF designer a.k.a “Cider”.

WPF ShapMap Controls is written in C# and requires .net framework 3.5. It is released under GNU Lesser General Public License.

A word of caution

Since this project is highly dependent on SharpMap, I’d like to mention several implications:
  1. Releases schedule is dependent on SharpMap 2.0 GIS engine. Except for “dev snapshots” there will be no releases of this project before SharpMap 2.0 Beta 2.0 release.
  2. Interfaces are dependent on SharpMap. Although I make an effort to have relatively orthogonal design and interface separation, the interfaces of WPF SharpMap Controls will remain pretty unstable due to the possible changes to SharpMap. This is extremely relevant due to the upcoming porting of the geometries to GeoAPI and NTS.
  3. SharpMapdesign decisions and interface definitions have higher priority - at least until this project matures, compatibility with SharpMap will be preferred to interface stability of the WPF Controls.

Finally, as this project is making its first steps, things aren’t stable in general.
Adding to it the fact that SharpMap is still in its deep (and important) refactoring stages, and as I found in SharpMap’s forum – people are still having trouble to build latest commits – the source tree of this project temporarily contains also the SharpMap tree (dated to somewhere around the beta1 release.
Of course, once everything get stabilized – SharpMap will be used here as external binary dependency, to avoid duplication and other mess..

High Level Design

Last edited Apr 24, 2008 at 5:40 AM by blackrussian, version 17