Table of Contents for
OpenLayers 3 : Beginner's Guide

Version ebook / Retour

Cover image for bash Cookbook, 2nd Edition OpenLayers 3 : Beginner's Guide by Erik Hazzard Published by Packt Publishing, 2015
  1. Cover
  2. Table of Contents
  3. OpenLayers 3 Beginner's Guide
  4. OpenLayers 3 Beginner's Guide
  5. Credits
  6. About the Authors
  7. About the Reviewers
  8. www.PacktPub.com
  9. Preface
  10. What you need for this book
  11. Who this book is for
  12. Sections
  13. Time for action – heading
  14. Conventions
  15. Reader feedback
  16. Customer support
  17. 1. Getting Started with OpenLayers
  18. Advantages of using OpenLayers
  19. What, technically, is OpenLayers?
  20. Anatomy of a web mapping application
  21. Connecting to Google, Bing Maps, and other mapping APIs
  22. Time for action – downloading OpenLayers
  23. Time for action – creating your first map
  24. Where to go for help
  25. OpenLayers issues
  26. OpenLayers source code repository
  27. Getting live news from RSS and social networks
  28. Summary
  29. 2. Key Concepts in OpenLayers
  30. Time for action – creating a map
  31. Time for action – using the JavaScript console
  32. Time for action – overlaying information
  33. OpenLayers' super classes
  34. Key-Value Observing with the Object class
  35. Time for action – using bindTo
  36. Working with collections
  37. Summary
  38. 3. Charting the Map Class
  39. Time for action – creating a map
  40. Map renderers
  41. Time for action – rendering a masterpiece
  42. Map properties
  43. Time for action – target practice
  44. Map methods
  45. Time for action – creating animated maps
  46. Events
  47. Views
  48. Time for action – linking two views
  49. Summary
  50. 4. Interacting with Raster Data Source
  51. Layers in OpenLayers 3
  52. Common operations on layers
  53. Time for action – changing layer properties
  54. Tiled versus untiled layers
  55. Types of raster sources
  56. Tiled images' layers and their sources
  57. Time for action – creating a Stamen layer
  58. Time for action – creating a Bing Maps layer
  59. Time for action – creating tiles and adding Zoomify layer
  60. Image layers and their sources
  61. Using Spherical Mercator raster data with other layers
  62. Time For action – playing with various sources and layers together
  63. Time For action – applying Zoomify sample knowledge to a single raw image
  64. Summary
  65. 5. Using Vector Layers
  66. Time for action – creating a vector layer
  67. How the vector layer works
  68. The vector layer class
  69. Vector sources
  70. Time for action – using the cluster source
  71. Time for action – creating a loader function
  72. Time for action – working with the TileVector source
  73. Time for action – a drag and drop viewer for vector files
  74. Features and geometries
  75. Time for action – geometries in action
  76. Time for action – interacting with features
  77. Summary
  78. 6. Styling Vector Layers
  79. Time for action – basic styling
  80. The style class
  81. Time for action – using the icon style
  82. Have a go hero – using the circle style
  83. Multiple styles
  84. Time for action – using multiple styles
  85. Style functions
  86. Time for action – using properties to style features
  87. Interactive styles
  88. Time for action – creating interactive styles
  89. Summary
  90. 7. Wrapping Our Heads Around Projections
  91. Time for action – using different projection codes
  92. Time for action – determining coordinates
  93. OpenLayers projection class
  94. Transforming coordinates
  95. Time for action – coordinate transforms
  96. Time for action – setting up Proj4js.org
  97. Time for action – reprojecting extent
  98. Time for action – using custom projection with WMS sources
  99. Time for action – reprojecting geometries in vector layers
  100. Summary
  101. 8. Interacting with Your Map
  102. Time for action – converting your local or national authorities data into web mapping formats
  103. Time for action – testing the use cases for ol.interaction.Select
  104. Time for action – more options with ol.interaction.Select
  105. Introducing methods to get information from your map
  106. Time for action – understanding the forEachFeatureAtPixel method
  107. Time for action – understanding the getGetFeatureInfoUrl method
  108. Adding a pop-up on your map
  109. Time for action – introducing ol.Overlay with a static example
  110. Time for action – using ol.Overlay dynamically with layers information
  111. Time for action – using ol.interaction.Draw to share new information on the Web
  112. Time for action – using ol.interaction.Modify to update drawing
  113. Understanding interactions and their architecture
  114. Time for action – configuring default interactions
  115. Discovering the other interactions
  116. Time for action – using ol.interaction.DragRotateAndZoom
  117. Time for action – making rectangle export to GeoJSON with ol.interaction.DragBox
  118. Summary
  119. 9. Taking Control of Controls
  120. Adding controls to your map
  121. Time for action – starting with the default controls
  122. Controls overview
  123. Time for action – changing the default attribution styles
  124. Time for action – finding your mouse position
  125. Time for action – configuring ZoomToExtent and manipulate controls
  126. Creating a custom control
  127. Time for action – extending ol.control.Control to make your own control
  128. Summary
  129. 10. OpenLayers Goes Mobile
  130. Using a web server
  131. Time for action – go mobile!
  132. The Geolocation class
  133. Time for action – location, location, location
  134. The DeviceOrientation class
  135. Time for action – a sense of direction
  136. Debugging mobile web applications
  137. Debugging on iOS
  138. Debugging on Android
  139. Going offline
  140. Time for action – MANIFEST destiny
  141. Going native with web applications
  142. Time for action – track me
  143. Summary
  144. 11. Creating Web Map Apps
  145. Using geospatial data from Flickr
  146. Time for action – getting Flickr data
  147. A simple application
  148. Time for Action – adding data to your map
  149. Styling the features
  150. Time for action – creating a style function
  151. Creating a thumbnail style
  152. Time for action – switching to JSON data
  153. Time for action – creating a thumbnail style
  154. Turning our example into an application
  155. Time for action – adding the select interaction
  156. Time for action – handling selection events
  157. Time for action – displaying photo information
  158. Using real time data
  159. Time for action – getting dynamic data
  160. Wrapping up the application
  161. Time for action – adding dynamic tags to your map
  162. Deploying an application
  163. Creating custom builds
  164. Creating a combined build
  165. Time for action – creating a combined build
  166. Creating a separate build
  167. Time for action – creating a separate build
  168. Summary
  169. A. Object-oriented Programming – Introduction and Concepts
  170. Going further
  171. B. More details on Closure Tools and Code Optimization Techniques
  172. Introducing Closure Library, yet another JavaScript library
  173. Time for action – first steps with Closure Library
  174. Making custom build for optimizing performance
  175. Time for action – playing with Closure Compiler
  176. Applying your knowledge to the OpenLayers case
  177. Time for action - running official examples with the internal OpenLayers toolkit
  178. Time for action - building your custom OpenLayers library
  179. Syntax and styles
  180. Time for action – using Closure Linter to fix JavaScript
  181. Summary
  182. C. Squashing Bugs with Web Debuggers
  183. Time for action – opening Chrome Developer Tools
  184. Explaining Chrome Developer debugging controls
  185. Time for action – using DOM manipulation with OpenStreetMap map images
  186. Time for action – using breakpoints to explore your code
  187. Time for action – playing with zoom button and map copyrights
  188. Using the Console panel
  189. Time for action – executing code in the Console
  190. Time for action – creating object literals
  191. Time for action – interacting with a map
  192. Improving Chrome and Developer Tools with extensions
  193. Debugging in other browsers
  194. Summary
  195. D. Pop Quiz Answers
  196. Chapter 5, Using Vector Layers
  197. Chapter 7, Wrapping Our Heads Around Projections
  198. Chapter 8, Interacting with Your Map
  199. Chapter 9, Taking Control of Controls
  200. Chapter 10, OpenLayers Goes Mobile
  201. Appendix B, More details on Closure Tools and Code Optimization Techniques
  202. Appendix C, Squashing Bugs with Web Debuggers
  203. Index

Time for action – geometries in action

The last example only used one linear ring for the polygon. Let's use the Web Inspector's console to create a polygon and then add a linear ring to see what happens. Open the vector_template.html file in your browser and then open the Web Inspector's Console. We'll be typing the commands into the console directly and observing the result on the map.

  1. First, create a polygon using the preceding example:
    var polygon = new ol.geom.Polygon([ [ [-20,-20],[-20,20],[20,20],[20,-20],[-20,-20] ] ]);
  2. We'll need to reproject the coordinates into our view's projection:
    polygon.transform('EPSG:4326', 'EPSG:3857');
  3. Now, we'll need a source and a layer:
    var source = new ol.source.vector({
      features: [new ol.Feature(polygon)],
      projection: 'EPSG:4326'
    });
    var layer = new ol.layer.vector({
      source: source,
      style: vectorStyle
    });
  4. And add it to the map:
    map.addLayer(layer);
  5. You should see something like the following screenshot:
    Time for action – geometries in action
  6. Now create a linear ring that will make a hole in our polygon.
    var linearRing = new ol.geom.LinearRing([ [-10,-10],[10,-10],[10,10],[-10,10],[-10,-10] ]);
    linearRing.transform('EPSG:4326','EPSG:3857');
    polygon.appendLinearRing(linearRing);
  7. Now, it should look like the following screenshot:
    Time for action – geometries in action

What just happened?

We've just seen linear rings in action. When you create a polygon, the first linear ring is the outer boundary of the polygon and any other linear rings you create define holes in the outer ring.

Have a go hero

Try the last example again, only this time add two or more linear rings to the polygon and observe what happens.

The GeometryCollection class

The GeometryCollection class, as the name suggests, is a collection of geometry objects. Unlike the MultiPoint, MultiLine, and MultiPolygon classes, a GeometryCollection can contain any type of geometry. You can create an instance of ol.geom.GeometryCollection by passing an array of geometries to it, for example:

var geomCollection = new ol.geom.GeometryCollection([geom1, geom2, geom3]);

The GeometryCollection methods

Although you can use a GeometryCollection as an ol.geom.Geometry class anywhere, you can't use any of the SimpleGeometry methods on a GeometryCollection. Instead there is a separate API for accessing the geometries managed by the collection.

Method

Parameters

Description

getGeometries()

None

This returns an array of geometries managed by the collection.

setGeometries

Array.<ol.geom.Geometry>

This sets the array of geometries managed by the collection.

The Feature class

To complete our discussion of vector layers, we'll finish with the Feature class. We've already seen features in action—in fact, you can't display vector data without them—but we haven't really talked about what they are and what they do.

In the previous section, we explored the various OpenLayers Geometry classes. They contain the geospatial coordinates that represent a particular shape. However, to display a shape on the map, we need to work with features. When we model things in the real world and build data structures to represent their position, we also want to capture other information about them. A polygon representing the outline of a building is an interesting thing to display on a map, but when we click on it, it's pretty reasonable to expect to get some information about the building such as its address, its height, and building type (that is, commercial, industrial, or residential). These nonspatial properties of a feature can also be used to change the style of a shape on the map.

A feature combines these two concepts—the spatial location of a thing, and nonspatial properties of the thing that we are interested in.

Creating a feature

Creating a new feature is pretty straightforward; you just need to provide a geometry object (to create a feature with no extra properties) or an object literal containing the geometry and other properties of the feature. For instance, given a point geometry, we can construct a simple feature like this:

var point = new ol.geom.Point([x, y]);
var feature = new ol.Feature(point);

To create a feature with information associated with the point, we do it this way:

var feature = new ol.Feature({
  geometry: point,
  name: 'My Cottage'
});

By convention, the geometry key is used to specify the geometry associated with the feature. It's possible, though, to use a different key and the setGeometryName() method to change this. For our purposes, we'll be doing it the default way.

The Feature class properties

We refer to this extra, nonspatial information associated with a feature as properties. The properties associated with a feature are almost completely free-form and contain any value. The geometry property is really the only exception.

You might wonder why we care about the nonspatial properties of a feature since we can create a feature without them and things work just fine. There are essentially two reasons:

  1. We want to provide users with information about the feature when they interact with them in some way. For instance, if we are displaying the country layer, we might want to show some information about the country – its name or population for instance.
  2. We want to style features based on some property. For instance, if we are displaying earthquake locations, we might draw circles of varying radii and intensity of color based on the magnitude of the earthquake recorded at that location.

We'll look at the first case—interactive information—in the last example for this chapter. We'll explore the second case in the next chapter when we look more closely at styling vector layers.

Feature methods

Before we jump into our last example, let's look at the methods available on a feature object. Note that Feature class is a subclass of ol.Object and inherits all the Event class and KVO properties, methods, and events. We won't include them here, but if you need a refresher jump back to Chapter 2, Key Concepts in OpenLayers for a moment.

Method

Parameters

Description

getGeometry()

None

This returns the geometry associated with this feature. This uses the geometry name to decide which property contains the geometry.

getGeometryName()

None

This returns the name of the property, which contains the geometry for this feature. By default, this will be geometry, unless setGeometryName has been used to change it.

getId()

None

This returns the unique ID associated with this feature, if any has been set.

getProperties()

None

This returns an object literal containing all the properties of this feature.

getStyle()

None

This returns the style, if any, associated with this feature.

getStyleFunction()

None

This returns the function that will be used to style the feature.

setGeometry(geom)

geom - ol.geom.Geometry

This sets the geometry of this feature. This will set a property based on the current geometry name (see setGeometryName)

setGeometryName(name)

name - string

This sets the property name to be used for getting the geometry associated with this feature.

setId(id)

id – number or string

This sets the ID of this feature, a value that uniquely identifies it.

setProperties(values)

values – object

This sets properties for this feature.

setStyle(style)

style – ol.style.Style | Array.<ol.style.Style> | function

This is a style to be used for this feature.

While we are not including the ol.Object methods in this list, it is relevant and important to note that feature properties are treated as object properties. This means that you can:

  • Change or create a property using feature.set(key, value)
  • Get the value of a property using feature.get(key)
  • Observe changes to a property using feature.on('change:<key>', observerFunction), where <key> is the name of a property
  • Change several properties at once using feature.setProperties(values)

One last thing before our final example—feature objects can have their own styles. Normally, styles are assigned to the vector layer and all features that are rendered as part of that layer use the layer's style. It is possible, however, to assign styles to individual features and that style will be used instead of the layer's style. Because a feature comes from a source, and a source can be used for more than one vector layer, this means that a feature without a style can be rendered differently depending on the layer's style while a feature with a style will be rendered the same way regardless of the different styles on different layers.