Carmenta Engine supports native reading of over 100 different data types. However, when developing a Carmenta Engine application, other types of data may be needed to complete the user experience.
This article aims to introduce the reader to the concept of MVVM (Model-View-ViewModel) as well
as how one could utilize it to create better Carmenta Engine WPF
applications. This will be done in three parts. First, we introduce the
reader to the concept of the MVVM-pattern. Secondly, we showcase a
standard C# WPF Carmenta Engine application, the HelloWorld sample.
Finally, we rewrite the sample application to comply with
When using Carmenta Engine, there are times in which you want to be more specific about your visualization. Perhaps your visualization is only suitable for certain type of observers, at certain zoom levels or at certain times of the day. These are what we refer to as dynamical runtime condition variables. They exist as a set of UpdateAttributes inside the View class. There is a set of predefined variables but it’s also possible to add custom variables.
When working with geospatial applications, a common operation is to convert coordinates between screen pixel coordinates and geographical coordinates. This can be useful in various cases, such as displaying the geographical coordinate for the mouse cursor position, working with custom tools for user interaction, editing feature geometries from code, and more.