<!– Class –> This class allows you to match a value with data in the feature to determine how to draw that feature.

Value Style:

The ValueStyle allows you to match data in the FeatureSource against a value string. If the value matches, then we will use the style defined in that item to do the drawing. For example, let's say you have some data that contains states, and each state is categorized as either a high, medium or low pollution state. Based on the string values of “High”, Medium“ and “Low”, we can match on these. If a feature's data for the column matched the string “High”, then we would use the high ValueItem's styles to draw that feature. This can be applied to all kinds of things, such as road classifications, etc.

This can be somewhat slow because we have to match data from the FeatureSource. If performance is key, then instead of using the ValueStyle, we recommend that you create a set custom index for your layer, one index with only “High” elements, one for “Medium” and so on. Then load each as a separate layer. In this way, you would only have one data set, but multiple indexes. This is the fastest way if you are working with Shape Files. If you are working with spatial databases, then we suggest creating a view to segment out each category.

*System.Object ThinkGeo.MapSuite.WindowsPhoneCore.Style *ThinkGeo.MapSuite.WindowsPhoneCore.ValueStyle

This is a constructor for the class.

This is the default constructor. If you use this constructor, you need to set the required properties manually.

If you use this constructor, you need to set the required properties manually.

Go Back

This is a constructor for this class.

Go Back

This method draws the shapes on the canvas you provided.

This method is the concrete wrapper for the abstract method DrawCore. In this method, we take the shapes you passed in and draw them on the canvas you provided. Each style (based on its properties) may draw each shape differently.

As this is a concrete public method that wraps a Core method, we reserve the right to add events and other logic to pre- or post-process data returned by the Core version of the method. In this way, we leave our framework open on our end, but also allow you the developer to extend our logic to suit your needs. If you have questions about this, please contact our support team as we would be happy to work with you on extending our framework.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

This method draws the features on the canvas you provided.

This method is the concrete wrapper for the abstract method DrawCore. In this method, we take the features you passed in and draw them on the canvas you provided. Each style (based on its properties) may draw each feature differently.

As this is a concrete public method that wraps a Core method, we reserve the right to add events and other logic to pre- or post-process data returned by the Core version of the method. In this way, we leave our framework open on our end, but also allow you the developer to extend our logic to suit your needs. If you have questions about this, please contact our support team as we would be happy to work with you on extending our framework.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

<!– System.Object –> Go Back

<!– System.Object –> Go Back

This method returns the column data for each feature that is required for the style to properly draw.

This method is the concrete wrapper for the abstract method GetRequiredColumnNamesCore. In this method, we return the column names that are required for the style to draw the feature properly. For example, if you have a style that colors areas blue when a certain column value is over 100, then you need to be sure you include that column name. This will ensure that the column data is returned to you in the feature when it is ready to draw.

In many of the styles, we add properties to allow the user to specify which field they need; then, in the GetRequiredColumnNamesCore we read that property and add it to the collection.

As this is a concrete public method that wraps a Core method, we reserve the right to add events and other logic to pre- or post-process data returned by the Core version of the method. In this way, we leave our framework open on our end, but also allow you the developer to extend our logic to suit your needs. If you have questions about this, please contact our support team as we would be happy to work with you on extending our framework.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

<!– System.Object –> Go Back

<!– System.Object –> Go Back

This method draws the features on the canvas you provided.

This overridden method is called from the concrete public method Draw. In this method, we take the features you passed in and draw them on the canvas you provided. Each style (based on its properties) may draw each feature differently.

When overriding this method, consider each feature and its column data values. You can use the full power of the GeoCanvas to do the drawing. If you need column data for a feature, be sure to override the GetRequiredColumnNamesCore and add the columns you need to the collection. In many of the styles, we add properties to allow the user to specify which field they need; then, in the GetRequiredColumnNamesCore, we read that property and add it to the collection.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style(overriden) –> Go Back

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

<!– System.Object –> Go Back

This method returns the column data for each feature that is required for the style to properly draw.

This abstract method is called from the concrete public method GetRequiredFieldNames. In this method, we return the column names that are required for the style to draw the feature properly. For example, if you have a style that colors areas blue when a certain column value is over 100, then you need to be sure you include that column name. This will ensure that the column data is returned to you in the feature when it is ready to draw.

In many of the styles, we add properties to allow the user to specify which field they need; then, in the GetRequiredColumnNamesCore, we read that property and add it to the collection.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style(overriden) –> Go Back

<!– System.Object –> Go Back

This property gets and sets the column name used to match with the value specified in the items.

This is the column we use for matching.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.ValueStyle –> Go Back

This property gets and sets the active status of the style.

If the style is not active then it will not draw.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

This property gets and set the name of the style.

This name is not used by the system; it is only for the developer. However, it can be used if you generate your own legend.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

This property gets the collection of fields that are required for the style.

This property gets the collection of fields that are required for the style. These are in addition to any other columns you specify in styles that inherit from this one. For example, if you have use a ValueStyle and it requires a column name for the value comparison, then that column does not need to be in this collection. You only use the RequiredColumnNames for columns you need beyond those required by specific inherited styles.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.Style –> Go Back

This property gets the collection of ValueItems. Each item can have its own value to match.

You will want to add ValueItems to this collection. Each item can have its own style and matching string.

<!– ThinkGeo.MapSuite.WindowsPhoneCore.ValueStyle –> Go Back

NOTOC WindowsPhoneMapSuiteCore ThinkGeo.MapSuite.WindowsPhoneCore UpdateDocumentation