<!– Class –> This layer is backed by memory and is typically used for temporary features.

This layer is backed by memory and is typically used for temporary features. You can use the MapShapes layer for user-drawn InternalFeatures, InternalFeatures that come from an external device such as a GPS unit, or any InternalFeatures that are not saved to disk or a database.

*System.Object ThinkGeo.MapSuite.WindowsPhoneCore.Layer *ThinkGeo.MapSuite.WindowsPhoneCore.FeatureLayer ThinkGeo.MapSuite.WindowsPhoneCore.InMemoryFeatureLayer

This is a constructor for the class.

This is the default constructor. If you use this constructor, then you need to specify the FeatureSource column manually.

If you use this constructor, then you need to specify the FeatureSource column manually.

Go Back

This is a constructor for the class.

This constructor allows you to provide the FeatureSource columns and features for the layer.

This constructor gets the layer ready to use.

Go Back

This is a constructor for the class.

This constructor allows you to provide the FeatureSource columns and shapes for the layer.

This constructor gets the layer ready to use.

Go Back

This method build a spatial index for a passed group of featurs which increases access speed.

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

This method closes the Layer and releases any resources it was using.

This method is the concrete wrapper for the abstract method CloseCore. The close method plays an important role in the life cycle of the Layer. It may be called after drawing to release any memory and other resources that were allocated since the Open method was called.

If you override this method, it is recommended that you take the following things into account: This method may be called multiple times, so we suggest you write the method so that that a call to a closed Layer is ignored and does not generate an error. We also suggest that in the Close you free all resources that have been opened. Remember that the object will not be destroyed, but will be re-opened possibly in the near future.

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.Layer –> Go Back

This method draws the Layer.

This method is the concrete wrapper for the abstract method DrawCore. This method draws the representation of the layer based on the extent you provided.

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.Layer –> Go Back

<!– System.Object –> Go Back

This method returns the bounding box of the Layer.

This method is the concrete wrapper for the abstract method GetBoundingBoxCore. This method returns the bounding box of the RasterLayer.

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.Layer –> Go Back

This method returns the columns of data for the InternalFeatures in this Layer.

You should set the column names for the data that the InternalFeatures will hold. For example, if you have some features that represent road signs, then one column you may want to add is “Sign Type”. Then, for every Feature you add to the layer, you need to add the “Sign Type” and a value to the InternalFeatures' ColumnValues dictionary. If you provide this information, then you can use things like ValueStyles, Labeling, etc. based on the columns you have defined.

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

<!– System.Object –> Go Back

<!– System.Object –> Go Back

This method opens the Layer so that it is initialized and ready to use.

This method is the concrete wrapper for the abstract method OpenCore. The open method plays an important role, as it is responsible for initializing the Layer. Most methods on the Layer will throw an exception if the state of the Layer is not opened. When the map draws each layer, the layer will be opened as one of its first steps; then, after it is finished drawing with that layer, it will close it. In this way, we are sure to release all resources used by the Layer.

When implementing the abstract method, consider opening the FeatureSource or RasterSource. You will get a chance to close these in the Close method of the Layer.

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.Layer –> Go Back

<!– System.Object –> Go Back

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

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

This method will draw on the canvas when the layer.Draw throw exception and the DrawExceptionMode is set to DrawException instead of ThrowException.

This method can be overriden its logic by rewrite the DrawExceptionCore.

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

This method will draw on the canvas when the layer.Draw throw exception and the DrawExceptionMode is set to DrawException instead of ThrowException.

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

<!– System.Object –> Go Back

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

<!– System.Object –> Go Back

This method raises the DrawingFeatures event.

<list type=“bullet”> <item>You can call this method from a derived class to enable it to raise the event. This may be useful if you plan to extend the FeatureLayer and you need access to the event.

This event is meant to allow you to add or remove the features to be drawn.</item> </list>

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

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

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

This method opens the Layer so that it is initialized and ready to use.

This abstract method is called from the concrete public method Open. The open method plays an important role, as it is responsible for initializing the Layer. Most methods on the Layer will throw an exception if the state of the Layer is not opened. When the map draws each layer, the layer will be opened as one of its first steps; then, after it is finished drawing with that layer, it will close it. In this way, we are sure to release all resources used by the Layer.

When implementing the abstract method, consider opening the FeatureSource or RasterSource. You will get a chance to close these in the Close method of the Layer.

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

This method sets up the EditTools and QueryTools objects.

This method is the concrete wrapper for the abstract method SetupToolsCore. The SetupTools method allows you to create the QueryTool, EditTools and other tools you may need on your object. We created this method so that if you want to extend one of the tool classes, you can override the SetupToolsCore and create any class you want.

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.FeatureLayer –> Go Back

This method sets up the EditTools and QueryTools objects.

This method is the concrete wrapper for the abstract method SetupTools. The SetupTools method allows you to create the QueryTool, EditTools and other tools you may need on your object. We created this method so that if you want to extend one of the tool classes, you can override the SetupToolsCore and create any class you want.

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

This property gets the columns of data for the InternalFeatures in this Layer.

You should set the column names for the data that the InternalFeatures will hold. For example, if you have some features that represent road signs, then one column you may want to add is “Sign Type”. Then, for every Feature you add to the layer, you need to add the “Sign Type” and a value to the InternalFeatures' ColumnValues dictionary. If you provide this information, then you can use things like ValueStyles, Labeling, etc. based on the columns you have defined.

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

Gets or sets the DrawExcpetionMode when exception happens.

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

This property gets and sets the extra drawing margin as a percentage around the map that draw to ensure that labeling is correct.

This extra margin that we draw exists so that labels match up if they are partially cut off.

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

This property gets the last drawing time for the layer.

We track the drawing time for the layer and report it back in this method. This is useful for determining the speed of various layers.

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

This property gets the EditTools that allow you to easily edit InternalFeatures in the Feature Layer.

The EditTools are supplied as an easily accessible wrapper for the editing methods of the FeatureSource.

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

A collection of strings representing record id of features not to get in the Layer.

This string collection is a handy place to specify what records not to get from the source. Suppose you have a shape file of roads and you want to hide the roads within a particular rectangle, simply execute GetFeaturesInsideBoundingBox() and add the id of the return features to the collection and forget about them. Since you can set this by Layer it makes is easy to determine what to and what not to.

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

This property gets the FeatureSource for the FeatureLayer.

The FeatureSource is the provider of data to the FeatureLayer. There are different FeatureSource classes to match the various ways that feature data is stored. It is important that, when you inherit from the FeatureLayer, in the constructor you set the FeatureSource you want to use.

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

This property checks to see if a Layer has a BoundingBox or not. If it has no BoundingBox, it will throw an exception when you call the GetBoundingBox() and GetFullExtent() APIs. In InMemoryFeatureLayer, we override this API and mark it as true.

The default implementation in the base class returns false.

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

This property gets the dictionary that holds your InternalFeatures.

The dictionary is a quick way to access your InternalFeatures. You can easily add, remove or edit features in this dictionary and they instantly take effect in the layer. You can always use the EditTools to do the same thing, but this is a shortcut, as the data is backed in memory so it is very pliable.

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

This property returns true if the Layer is open and false if it is not.

This method is the concrete wrapper for the abstract method IsOpenCore. Various methods on the Layer require that it be in an open state. If one of those methods is called when the state is not open, then the method will throw an exception. To enter the open state, you must call the Layer Open method. The method will raise an exception if the current Layer is already open.

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.Layer –> Go Back

This property gets and set the visible state of the layer.

If this property is set to false, the layer will not draw. We ensure this in the Draw method. This is useful for legends and other controls that control the visibility of layers.

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

This property gets and sets the name for the layer.

The name is user defined. It is useful to set, as it may be used for higher level components such as legends, etc.

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

This property gets the QueryTools that allow you to easily query Features from the Feature Layer.

This property gets the QueryTools that allow you to easily query Features from the Feature Layer. The QueryTools are supplied as an easily accessible wrapper for the query methods of the FeatureSource.

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

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

Thie property gets or sets whether allow wrap date line.

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

This property gets and sets the ZoomLevelSet, which contains the specific zoom levels for the FeatureLayer.

The ZoomLevelSet is a class that contains all of the ZoomLevels for the FeatureLayer. Each ZoomLevel contains the styles that are used to determine how to draw the InternalFeatures.

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

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

This event is raised when features are about to be drawn in the layer.

This event is raised when features are about to be drawn in the layer. In the event arguments, there is a collection of features to be drawn. You can easily add or remove items from this collection so that extra items will draw or not draw.

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

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

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

NOTOC WindowsPhoneMapSuiteCore ThinkGeo.MapSuite.WindowsPhoneCore UpdateDocumentation