Website updates

Author: tschaub

dist/en/main/apidoc/module-ol_control_defaults.html

@@ -204,12 +204,10 @@ <h4 class="name">
     <div class="description">
         <p>Set of controls included in maps by default. Unless configured otherwise,
 this returns a collection containing an instance of each of the following
-controls:</p>
-<ul>
-<li><a href="module-ol_control_Zoom-Zoom.html"><code>Zoom</code></a></li>
-<li><a href="module-ol_control_Rotate-Rotate.html"><code>Rotate</code></a></li>
-<li><a href="module-ol_control_Attribution-Attribution.html"><code>Attribution</code></a></li>
-</ul>
+controls:
+<a href="module-ol_control_Zoom-Zoom.html"><code>Zoom</code></a>
+<a href="module-ol_control_Rotate-Rotate.html"><code>Rotate</code></a>
+<a href="module-ol_control_Attribution-Attribution.html"><code>Attribution</code></a></p>
     </div>
 
 

dist/en/main/apidoc/module-ol_expr_expression.html

@@ -364,50 +364,50 @@ <h4 class="name">
         <p>Base type used for literal style parameters; can be a number literal or the output of an operator,
 which in turns takes <a href="module-ol_expr_expression.html#~ExpressionValue"><code>ExpressionValue</code></a> arguments.</p>
 <p>See below for details on the available operators (with notes for those that are WebGL or Canvas only).</p>
+<p>Reading operators:
+  <code>['band', bandIndex, xOffset, yOffset]</code> For tile layers only. Fetches pixel values from band
+    <code>bandIndex</code> of the source's data. The first <code>bandIndex</code> of the source data is <code>1</code>. Fetched values
+    are in the 0..1 range. <a href="module-ol_source_TileImage-TileImage.html"><code>TileImage</code></a> sources have 4 bands: red,
+    green, blue and alpha. <a href="module-ol_source_DataTile-DataTileSource.html"><code>DataTileSource</code></a> sources can have any number
+    of bands, depending on the underlying data source and
+    <a href="module-ol_source_GeoTIFF.html#~Options"><code>configuration</code></a>. <code>xOffset</code> and <code>yOffset</code> are optional
+    and allow specifying pixel offsets for x and y. This is used for sampling data from neighboring pixels (WebGL only).
+  <code>['get', attributeName]</code> fetches a feature property value, similar to <code>feature.get('attributeName')</code>.
+  <code>['get', attributeName, keyOrArrayIndex, ...]</code> (Canvas only) Access nested properties and array items of a
+    feature property. The result is <code>undefined</code> when there is nothing at the specified key or index.
+  <code>['geometry-type']</code> returns a feature's geometry type as string, either: 'LineString', 'Point' or 'Polygon'
+    <code>Multi*</code> values are returned as their singular equivalent
+    <code>Circle</code> geometries are returned as 'Polygon'
+    <code>GeometryCollection</code> geometries are returned as the type of the first geometry found in the collection (WebGL only).
+  <code>['resolution']</code> returns the current resolution
+  <code>['time']</code> The time in seconds since the creation of the layer (WebGL only).
+  <code>['var', 'varName']</code> fetches a value from the style variables; will throw an error if that variable is undefined
+  <code>['zoom']</code> The current zoom level (WebGL only).
+  <code>['line-metric']</code> returns the M component of the current point on a line (WebGL only); in case where the geometry layout of the line
+     does not contain an M component (e.g. XY or XYZ), 0 is returned; 0 is also returned for geometries other than lines.
+     Please note that the M component will be linearly interpolated between the two points composing a segment.</p>
+<p>Math operators:
+  <code>['*', value1, value2, ...]</code> multiplies the values (either numbers or colors)
+  <code>['/', value1, value2]</code> divides <code>value1</code> by <code>value2</code>
+  <code>['+', value1, value2, ...]</code> adds the values
+  <code>['-', value1, value2]</code> subtracts <code>value2</code> from <code>value1</code>
+  <code>['clamp', value, low, high]</code> clamps <code>value</code> between <code>low</code> and <code>high</code>
+  <code>['%', value1, value2]</code> returns the result of <code>value1 % value2</code> (modulo)
+  <code>['^', value1, value2]</code> returns the value of <code>value1</code> raised to the <code>value2</code> power
+  <code>['abs', value1]</code> returns the absolute value of <code>value1</code>
+  <code>['floor', value1]</code> returns the nearest integer less than or equal to <code>value1</code></p>
 <ul>
-<li><p>Reading operators:</p>
-<ul>
-<li><code>['band', bandIndex, xOffset, yOffset]</code> For tile layers only. Fetches pixel values from band
-<code>bandIndex</code> of the source's data. The first <code>bandIndex</code> of the source data is <code>1</code>. Fetched values
-are in the 0..1 range. <a href="module-ol_source_TileImage-TileImage.html"><code>TileImage</code></a> sources have 4 bands: red,
-green, blue and alpha. <a href="module-ol_source_DataTile-DataTileSource.html"><code>DataTileSource</code></a> sources can have any number
-of bands, depending on the underlying data source and
-<a href="module-ol_source_GeoTIFF.html#~Options"><code>configuration</code></a>. <code>xOffset</code> and <code>yOffset</code> are optional
-and allow specifying pixel offsets for x and y. This is used for sampling data from neighboring pixels (WebGL only).</li>
-<li><code>['get', attributeName]</code> fetches a feature property value, similar to <code>feature.get('attributeName')</code>.</li>
-<li><code>['get', attributeName, keyOrArrayIndex, ...]</code> (Canvas only) Access nested properties and array items of a
-feature property. The result is <code>undefined</code> when there is nothing at the specified key or index.</li>
-<li><code>['geometry-type']</code> returns a feature's geometry type as string, either: 'LineString', 'Point' or 'Polygon'
-<code>Multi*</code> values are returned as their singular equivalent
-<code>Circle</code> geometries are returned as 'Polygon'
-<code>GeometryCollection</code> geometries are returned as the type of the first geometry found in the collection (WebGL only).</li>
-<li><code>['resolution']</code> returns the current resolution</li>
-<li><code>['time']</code> The time in seconds since the creation of the layer (WebGL only).</li>
-<li><code>['var', 'varName']</code> fetches a value from the style variables; will throw an error if that variable is undefined</li>
-<li><code>['zoom']</code> The current zoom level (WebGL only).</li>
-<li><code>['line-metric']</code> returns the M component of the current point on a line (WebGL only); in case where the geometry layout of the line
- does not contain an M component (e.g. XY or XYZ), 0 is returned; 0 is also returned for geometries other than lines.
- Please note that the M component will be linearly interpolated between the two points composing a segment.</li>
-</ul>
+<li><p><code>['round', value1]</code> returns the nearest integer to <code>value1</code></p>
 </li>
-<li><p>Math operators:</p>
-<ul>
-<li><code>['*', value1, value2, ...]</code> multiplies the values (either numbers or colors)</li>
-<li><code>['/', value1, value2]</code> divides <code>value1</code> by <code>value2</code></li>
-<li><code>['+', value1, value2, ...]</code> adds the values</li>
-<li><code>['-', value1, value2]</code> subtracts <code>value2</code> from <code>value1</code></li>
-<li><code>['clamp', value, low, high]</code> clamps <code>value</code> between <code>low</code> and <code>high</code></li>
-<li><code>['%', value1, value2]</code> returns the result of <code>value1 % value2</code> (modulo)</li>
-<li><code>['^', value1, value2]</code> returns the value of <code>value1</code> raised to the <code>value2</code> power</li>
-<li><code>['abs', value1]</code> returns the absolute value of <code>value1</code></li>
-<li><code>['floor', value1]</code> returns the nearest integer less than or equal to <code>value1</code></li>
-<li><code>['round', value1]</code> returns the nearest integer to <code>value1</code></li>
-<li><code>['ceil', value1]</code> returns the nearest integer greater than or equal to <code>value1</code></li>
-<li><code>['sin', value1]</code> returns the sine of <code>value1</code></li>
-<li><code>['cos', value1]</code> returns the cosine of <code>value1</code></li>
-<li><code>['atan', value1, value2]</code> returns <code>atan2(value1, value2)</code>. If <code>value2</code> is not provided, returns <code>atan(value1)</code></li>
-<li><code>['sqrt', value1]</code> returns the square root of <code>value1</code></li>
-</ul>
+<li><p><code>['ceil', value1]</code> returns the nearest integer greater than or equal to <code>value1</code></p>
+</li>
+<li><p><code>['sin', value1]</code> returns the sine of <code>value1</code></p>
+</li>
+<li><p><code>['cos', value1]</code> returns the cosine of <code>value1</code></p>
+</li>
+<li><p><code>['atan', value1, value2]</code> returns <code>atan2(value1, value2)</code>. If <code>value2</code> is not provided, returns <code>atan(value1)</code></p>
+</li>
+<li><p><code>['sqrt', value1]</code> returns the square root of <code>value1</code></p>
 </li>
 <li><p>Transform operators:</p>
 <ul>

dist/en/main/apidoc/module-ol_interaction_defaults.html

@@ -210,18 +210,16 @@ <h4 class="name">
 them into a <a href="module-ol_Collection-Collection.html"><code>Collection</code></a> in the order you want
 before creating your <a href="module-ol_Map-Map.html"><code>Map</code></a> instance. Changing the order can
 be of interest if the event propagation needs to be stopped at a point.
-The default set of interactions, in sequence, is:</p>
-<ul>
-<li><a href="module-ol_interaction_DragRotate-DragRotate.html"><code>DragRotate</code></a></li>
-<li><a href="module-ol_interaction_DoubleClickZoom-DoubleClickZoom.html"><code>DoubleClickZoom</code></a></li>
-<li><a href="module-ol_interaction_DragPan-DragPan.html"><code>DragPan</code></a></li>
-<li><a href="module-ol_interaction_PinchRotate-PinchRotate.html"><code>PinchRotate</code></a></li>
-<li><a href="module-ol_interaction_PinchZoom-PinchZoom.html"><code>PinchZoom</code></a></li>
-<li><a href="module-ol_interaction_KeyboardPan-KeyboardPan.html"><code>KeyboardPan</code></a></li>
-<li><a href="module-ol_interaction_KeyboardZoom-KeyboardZoom.html"><code>KeyboardZoom</code></a></li>
-<li><a href="module-ol_interaction_MouseWheelZoom-MouseWheelZoom.html"><code>MouseWheelZoom</code></a></li>
-<li><a href="module-ol_interaction_DragZoom-DragZoom.html"><code>DragZoom</code></a></li>
-</ul>
+The default set of interactions, in sequence, is:
+<a href="module-ol_interaction_DragRotate-DragRotate.html"><code>DragRotate</code></a>
+<a href="module-ol_interaction_DoubleClickZoom-DoubleClickZoom.html"><code>DoubleClickZoom</code></a>
+<a href="module-ol_interaction_DragPan-DragPan.html"><code>DragPan</code></a>
+<a href="module-ol_interaction_PinchRotate-PinchRotate.html"><code>PinchRotate</code></a>
+<a href="module-ol_interaction_PinchZoom-PinchZoom.html"><code>PinchZoom</code></a>
+<a href="module-ol_interaction_KeyboardPan-KeyboardPan.html"><code>KeyboardPan</code></a>
+<a href="module-ol_interaction_KeyboardZoom-KeyboardZoom.html"><code>KeyboardZoom</code></a>
+<a href="module-ol_interaction_MouseWheelZoom-MouseWheelZoom.html"><code>MouseWheelZoom</code></a>
+<a href="module-ol_interaction_DragZoom-DragZoom.html"><code>DragZoom</code></a></p>
     </div>
 
 

dist/en/main/apidoc/module-ol_layer_VectorTile-VectorTileLayer.html

@@ -558,16 +558,14 @@ <h4 class="name">
 
             <td  class="description last">
 
-                <p>Render mode for vector tiles:</p>
-<ul>
-<li><code>'hybrid'</code>: Polygon and line elements are rendered as images, so pixels are scaled during zoom
-animations. Point symbols and texts are accurately rendered as vectors and can stay upright on
-rotated views, but get lifted above all polygon and line elements.</li>
-<li><code>'vector'</code>: Everything is rendered as vectors and the original render order is maintained. Use
-this mode for improved performance and visual epxerience on vector tile layers with not too many
-rendered features (e.g. for highlighting a subset of features of another layer with the same
-source).</li>
-</ul></td>
+                <p>Render mode for vector tiles:
+ <code>'hybrid'</code>: Polygon and line elements are rendered as images, so pixels are scaled during zoom
+   animations. Point symbols and texts are accurately rendered as vectors and can stay upright on
+   rotated views, but get lifted above all polygon and line elements.
+ <code>'vector'</code>: Everything is rendered as vectors and the original render order is maintained. Use
+   this mode for improved performance and visual epxerience on vector tile layers with not too many
+   rendered features (e.g. for highlighting a subset of features of another layer with the same
+   source).</p></td>
         </tr>
 
 

dist/en/main/apidoc/module-ol_layer_VectorTile.html

@@ -507,16 +507,14 @@ <h5 class="subsection-title">Properties:</h5>
             </td>
 
             <td class="description last">
-                <p>Render mode for vector tiles:</p>
-<ul>
-<li><code>'hybrid'</code>: Polygon and line elements are rendered as images, so pixels are scaled during zoom
-animations. Point symbols and texts are accurately rendered as vectors and can stay upright on
-rotated views, but get lifted above all polygon and line elements.</li>
-<li><code>'vector'</code>: Everything is rendered as vectors and the original render order is maintained. Use
-this mode for improved performance and visual epxerience on vector tile layers with not too many
-rendered features (e.g. for highlighting a subset of features of another layer with the same
-source).</li>
-</ul>
+                <p>Render mode for vector tiles:
+ <code>'hybrid'</code>: Polygon and line elements are rendered as images, so pixels are scaled during zoom
+   animations. Point symbols and texts are accurately rendered as vectors and can stay upright on
+   rotated views, but get lifted above all polygon and line elements.
+ <code>'vector'</code>: Everything is rendered as vectors and the original render order is maintained. Use
+   this mode for improved performance and visual epxerience on vector tile layers with not too many
+   rendered features (e.g. for highlighting a subset of features of another layer with the same
+   source).</p>
 
             </td>
         </tr>

dist/en/main/apidoc/module-ol_proj_Projection-Projection.html

@@ -123,17 +123,15 @@ <h2 class="my-3">
 instance.</p>
 <p>The library includes support for transforming coordinates between the following
 projections:</p>
-<ul>
-<li>WGS 84 / Geographic - Using codes <code>EPSG:4326</code>, <code>CRS:84</code>, <code>urn:ogc:def:crs:EPSG:6.6:4326</code>,
-<code>urn:ogc:def:crs:OGC:1.3:CRS84</code>, <code>urn:ogc:def:crs:OGC:2:84</code>, <code>http://www.opengis.net/gml/srs/epsg.xml#4326</code>,
-or <code>urn:x-ogc:def:crs:EPSG:4326</code></li>
-<li>WGS 84 / Spherical Mercator - Using codes <code>EPSG:3857</code>, <code>EPSG:102100</code>, <code>EPSG:102113</code>, <code>EPSG:900913</code>,
-<code>urn:ogc:def:crs:EPSG:6.18:3:3857</code>, or <code>http://www.opengis.net/gml/srs/epsg.xml#3857</code></li>
-<li>WGS 84 / UTM zones - Using codes <code>EPSG:32601</code> through <code>EPSG:32660</code> for northern zones
-and <code>EPSG:32701</code> through <code>EPSG:32760</code> for southern zones. Note that the built-in UTM transforms
-are lower accuracy (with errors on the order of 0.1 m) than those that you might get in a
-library like <a href="https://github.com/proj4js/proj4js">proj4js</a>.</li>
-</ul>
+<p> WGS 84 / Geographic - Using codes <code>EPSG:4326</code>, <code>CRS:84</code>, <code>urn:ogc:def:crs:EPSG:6.6:4326</code>,
+   <code>urn:ogc:def:crs:OGC:1.3:CRS84</code>, <code>urn:ogc:def:crs:OGC:2:84</code>, <code>http://www.opengis.net/gml/srs/epsg.xml#4326</code>,
+   or <code>urn:x-ogc:def:crs:EPSG:4326</code>
+ WGS 84 / Spherical Mercator - Using codes <code>EPSG:3857</code>, <code>EPSG:102100</code>, <code>EPSG:102113</code>, <code>EPSG:900913</code>,
+   <code>urn:ogc:def:crs:EPSG:6.18:3:3857</code>, or <code>http://www.opengis.net/gml/srs/epsg.xml#3857</code>
+ WGS 84 / UTM zones - Using codes <code>EPSG:32601</code> through <code>EPSG:32660</code> for northern zones
+   and <code>EPSG:32701</code> through <code>EPSG:32760</code> for southern zones. Note that the built-in UTM transforms
+   are lower accuracy (with errors on the order of 0.1 m) than those that you might get in a
+   library like <a href="https://github.com/proj4js/proj4js">proj4js</a>.</p>
 <p>For additional projection support, or to use higher accuracy transforms than the built-in ones, you can use
 the <a href="https://github.com/proj4js/proj4js">proj4js</a> library. With <code>proj4js</code>, after adding any new projection
 definitions, call the <a href="module-ol_proj_proj4.html#.register"><code>register</code></a> function.</p>

dist/en/main/apidoc/module-ol_render_Feature.html

@@ -274,9 +274,7 @@ <h4 class="name">
 
 <span class="param-type">string</span>
 
-
-                
-                    (defaults to 'geometry')
+ | undefined
 
 
             </td>

dist/en/main/apidoc/module-ol_renderer_webgl_PointsLayer-WebGLPointsLayerRenderer.html

@@ -326,12 +326,10 @@ <h4 class="name">
             <td  class="description last">
 
                 <p>These attributes will be read from the features in the source and then
-passed to the GPU. The <code>name</code> property of each attribute will serve as its identifier:</p>
-<ul>
-<li>In the vertex shader as an <code>attribute</code> by prefixing it with <code>a_</code></li>
-<li>In the fragment shader as a <code>varying</code> by prefixing it with <code>v_</code>
-Please note that these can only be numerical values.</li>
-</ul></td>
+passed to the GPU. The <code>name</code> property of each attribute will serve as its identifier:
+ In the vertex shader as an <code>attribute</code> by prefixing it with <code>a_</code>
+ In the fragment shader as a <code>varying</code> by prefixing it with <code>v_</code>
+Please note that these can only be numerical values.</p></td>
         </tr>
 
 

dist/en/main/apidoc/module-ol_renderer_webgl_PointsLayer.html

@@ -523,12 +523,10 @@ <h5 class="subsection-title">Properties:</h5>
 
             <td class="description last">
                 <p>These attributes will be read from the features in the source and then
-passed to the GPU. The <code>name</code> property of each attribute will serve as its identifier:</p>
-<ul>
-<li>In the vertex shader as an <code>attribute</code> by prefixing it with <code>a_</code></li>
-<li>In the fragment shader as a <code>varying</code> by prefixing it with <code>v_</code>
-Please note that these can only be numerical values.</li>
-</ul>
+passed to the GPU. The <code>name</code> property of each attribute will serve as its identifier:
+ In the vertex shader as an <code>attribute</code> by prefixing it with <code>a_</code>
+ In the fragment shader as a <code>varying</code> by prefixing it with <code>v_</code>
+Please note that these can only be numerical values.</p>
 
             </td>
         </tr>

dist/en/main/apidoc/module-ol_source_Source.html

@@ -274,12 +274,10 @@ <h4 class="name">
 
     <div class="description">
         <p>A type that can be used to provide attribution information for data sources.</p>
-<p>It represents either</p>
-<ul>
-<li>a simple string (e.g. <code>'© Acme Inc.'</code>)</li>
-<li>an array of simple strings (e.g. <code>['© Acme Inc.', '© Bacme Inc.']</code>)</li>
-<li>a function that returns a string or array of strings (<a href="module-ol_source_Source.html#~Attribution"><code>Attribution</code></a>)</li>
-</ul>
+<p>It represents either
+a simple string (e.g. <code>'© Acme Inc.'</code>)
+an array of simple strings (e.g. <code>['© Acme Inc.', '© Bacme Inc.']</code>)
+a function that returns a string or array of strings (<a href="module-ol_source_Source.html#~Attribution"><code>Attribution</code></a>)</p>
     </div>