Differences

This shows you the differences between two versions of the page.

--- map_suite_windows_phone_edition_faq_layers_featuresources [2015/09/16 08:01]
admin [How do I efficiently display a subset of a shape file without splitting it?]
+++ map_suite_windows_phone_edition_faq_layers_featuresources [2015/09/16 08:02] (current)
admin
@@ Line 16: / Line 16: @@
 [[Map_Suite_Windows_Phone_Edition_Layers_FeatureSources_Samples#Build_Custom_Shapefile_Indexes|Sample: Build Custom Shapefile Indexes ]]
-This sample shows how you can display a subset of a shapefile without splitting the physical shapefile. For example, you may have a single shapefile that contains both highways and local roads. To improve display speed, you may be temped to split it into two separate shapefiles so you can quickly display local roads with one style and highways with another style (and avoid using a value style, which can be slow). But at this project demonstrates, rather than split your shapefile you can simply build two custom indexes, one for each road type. Then, when you create your ShapeFileFeatureLayer, you'll simply use your original shapefile and specify a custom index. Each custom index will limit the records that can be seen by the Layer, making it very fast and efficient.<br>
+This sample shows how you can display a subset of a shapefile without splitting the physical shapefile. For example, you may have a single shapefile that contains both highways and local roads. To improve display speed, you may be temped to split it into two separate shapefiles so you can quickly display local roads with one style and highways with another style (and avoid using a value style, which can be slow). But at this project demonstrates, rather than split your shapefile you can simply build two custom indexes, one for each road type. Then, when you create your ShapeFileFeatureLayer, you'll simply use your original shapefile and specify a custom index. Each custom index will limit the records that can be seen by the Layer, making it very fast and efficient.
+\\
 For more information and a real-world example, please see the Map Suite discussion forum post at:
 [[http://gis.thinkgeo.com/Support/DiscussionForums/tabid/143/aff/21/aft/6894/afv/topic/Default.aspx|Forum Post]]
@@ Line 25: / Line 26: @@
 [[Map_Suite_Windows_Phone_Edition_Layers_FeatureSources_Samples#Build_Custom_Shapefile_Indexes|Sample: Build Custom Shapefile Indexes ]]
-This sample shows how you can display a subset of a shapefile without splitting the physical shapefile. For example, you may have a single shapefile that contains both highways and local roads. To improve display speed, you may be temped to split it into two separate shapefiles so you can quickly display local roads with one style and highways with another style (and avoid using a value style, which can be slow). But at this project demonstrates, rather than split your shapefile you can simply build two custom indexes, one for each road type. Then, when you create your ShapeFileFeatureLayer, you'll simply use your original shapefile and specify a custom index. Each custom index will limit the records that can be seen by the Layer, making it very fast and efficient.<br>
+This sample shows how you can display a subset of a shapefile without splitting the physical shapefile. For example, you may have a single shapefile that contains both highways and local roads. To improve display speed, you may be temped to split it into two separate shapefiles so you can quickly display local roads with one style and highways with another style (and avoid using a value style, which can be slow). But at this project demonstrates, rather than split your shapefile you can simply build two custom indexes, one for each road type. Then, when you create your ShapeFileFeatureLayer, you'll simply use your original shapefile and specify a custom index. Each custom index will limit the records that can be seen by the Layer, making it very fast and efficient.
+\\
 For more information and a real-world example, please see the Map Suite discussion forum post at:
 [[http://gis.thinkgeo.com/Support/DiscussionForums/tabid/143/aff/21/aft/6894/afv/topic/Default.aspx|Forum Post]]
@@ Line 34: / Line 36: @@
 [[Map_Suite_Windows_Phone_Edition_Layers_FeatureSources_Samples#Compass|Sample:Compass]]
-In the project “North Arrow”, you saw how to extend AdornmentLayer to create a North Arrow AdormentLayer. In this project, we expand on that idea and create a more sophisticated class. You will see how you can combine two images to create a compass. Compare to “North Arrow” project, we also added some other handy properties such as a Position property. Also, the compass can be of varied sizes thanks to the SizePercentage property. Finally, if you pass just one image, the compass can behave just like a regular north arrow.<br>
+In the project “North Arrow”, you saw how to extend AdornmentLayer to create a North Arrow AdormentLayer. In this project, we expand on that idea and create a more sophisticated class. You will see how you can combine two images to create a compass. Compare to “North Arrow” project, we also added some other handy properties such as a Position property. Also, the compass can be of varied sizes thanks to the SizePercentage property. Finally, if you pass just one image, the compass can behave just like a regular north arrow.
+\\
 We also added new designs of compass in smaller version. See the attached file: Rotating Compass New Smaller Designs.zip.
@@ Line 42: / Line 45: @@
 [[Map_Suite_Windows_Phone_Edition_Layers_FeatureSources_Samples#Compass|Sample:Zedgraph]]
-In our “How Do I” apps, there is sample app that shows how to add graphs to the map using the ZedGraph library. In this project, using the same data, the US cities, we elaborate a little bit on the pie chart. You will see how to add some gradient colors to the chart, how to label the different pie slices, how to add a title etc. Zedgraph is a truly massive library for graphics and Pie chart is only one type of chart among many others. As you can add pie charts to your map, you can also add bar charts, trend charts etc. I suggest you check out this site for more info on ZedGraph <br>
+In our “How Do I” apps, there is sample app that shows how to add graphs to the map using the ZedGraph library. In this project, using the same data, the US cities, we elaborate a little bit on the pie chart. You will see how to add some gradient colors to the chart, how to label the different pie slices, how to add a title etc. Zedgraph is a truly massive library for graphics and Pie chart is only one type of chart among many others. As you can add pie charts to your map, you can also add bar charts, trend charts etc. I suggest you check out this site for more info on ZedGraph
-http://zedgraph.org/wiki/index.php?title=Main_Page<br>
+\\
-With Map Suite, you have the whole ZedGraph API available with an easy interface to add the graphs to the map. <br>
+http://zedgraph.org/wiki/index.php?title=Main_Page
+\\
+With Map Suite, you have the whole ZedGraph API available with an easy interface to add the graphs to the map.
+\\
 For this project, in addition to the MapSuiteCore.dll, you will also need the ZedGraph.dll and ZedGraphStyleExtension.dll references.
 We will have several projects showing how to integrate other types of charts to your map.
@@ Line 168: / Line 174: @@
 [[Map_Suite_Windows_Phone_Edition_Layers_FeatureSources_Samples#Oledb_Point_FeatureSource|Sample:Oledb Point FeatureSource]]
-This project shows the power of MapSuite by giving to the developer the possibility to create its own layer based on an existing format containing spatial information. If the developer is familiar with a certain format like oledb, he can create its own FeatureSource reading the database and its own FeatureLayer wrapping the FeatureSource and providing the drawing logic.<br>
+This project shows the power of MapSuite by giving to the developer the possibility to create its own layer based on an existing format containing spatial information. If the developer is familiar with a certain format like oledb, he can create its own FeatureSource reading the database and its own FeatureLayer wrapping the FeatureSource and providing the drawing logic.
+\\
 In this project, we create the class OledbPointFeatureSource inheriting from FeatureSource and OledbPointFeatureLayer inheriting from FeatureSource.

User Tools

Site Tools

Differences

Page Tools