The workshop from openlayers

maps.opengeo.org/geowebcache/service/wms is down

A lot of the workshop examples rely on maps.opengeo.org/geowebcache/service/wms, which is down currently. For example, this request returns an "nginx error" web page.

@ahocevar, @bartvde, should we use another geowebcache instance?

Comments on Workshop v5.0.0-beta.en.4

Bear in mind that I use W10, and only started learning node.js yesterday. I am experienced in OL3 and js, and did the workshop today to see how things have changed. Some of these are bugs, and some suggestions. Generally I found the workshop excellent and well put together, so thanks.

in https://openlayers.org/workshop/en/vector/geojson.html
the sync(map); needs the map to be declared as const map = new Map({ NOT just new Map({
In https://openlayers.org/workshop/en/vector/style.html The lines

import {Fill, Stroke, Style} from 'ol/style'; 
import {getArea} from 'ol/sphere';
import colormap from 'colormap';

raised the questions for me (new to node) as to why some imports are upper case and some lower case, and why some are enclosed in {} and some not?
I did eventually find the answer at https://openlayers.org/en/latest/doc/tutorials/background.html and https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import, but a link in the text would have saved me some searching

In https://openlayers.org/workshop/en/vectortile/map.html it says The data source we are going to use requires an access key. Please read the terms at https://openmaptiles.com/hosting/, where you can also get your own key.
This confused me for a while as:
a. https://openmaptiles.com/hosting/ goes to https://cloud.maptiler.com/ and I could find no mention of terms or access key
b. I presumed I needed to sign up, and then continue with a free account, but could still find no mention of my access key (I actually already have a MapTiler account and I was not sure if this is the same or not)
c. I went to https://cloud.maptiler.com/maps/basic/openlayers and tin their code the key is arAKbT5Ce6Z448SNiGHA so I used const key = 'arAKbT5Ce6Z448SNiGHA'; in my code for the workshop
I do not know if I missed how you expected me to do it?
In https://openlayers.org/workshop/en/vectortile/interact.html
I initially had problems with addEventListener on undefined, but eventually after editing the js with a new blank line it worked OK.
I thought the popup was not working when I clicked, but then found that it only works in certain places - mostly in the sea and roads. Maybe you need to warn about this.
In https://openlayers.org/workshop/en/vectortile/bright.html
I did use bright.json and it worked but very, very slowly (taking minutes to respond) and consumed a lot of resources - maybe need to find a way for it not to be so resource-intensive or warn?
In https://openlayers.org/workshop/en/raster/elevation.html
Although I already had a free MapBox account, I found I was forced to change to a "Paid For" account (with a free tier of 50,000 map views / mo) and give my credit card details. I am not happy about that but hopefully I will never be charged. I cannot see how I can limit my use to just the free tier.
In https://openlayers.org/workshop/en/raster/raster.html
It took me a few minutes to see the sea level slider on my map, so I thought I had failed. When I added a background colour it made it more obvious. (Nice effect though to see Boston under water!)
In https://openlayers.org/workshop/en/deploying/
Excellent to have the deploy section. Most people may know this already but it took me a while to find out that I needed to use start rather than open at the command prompt
General: These are things I now want to find out, and hopefully will find by searching, but at the end it would have been useful to have links to:

a list of the main packages/modules used in the workshop and why - eg Babel, webpack etc (I intend to scan through the workshop's node_modules to find out about them so I know which I might find useful in my own development)
an indication as to whether the workshop set up is a good place to start an OL project (again I intend to ask people whether to start from the workshop, an example or elsewhere)

Clearer guidance on adding multiple layers

Great work Tim et al with OL and this important learning resource (esp. since exising OL3 books are becoming less useful).

Please consider that there maybe a need for clearer guidance on how to add multiple layers to a map object. From my limited OL experience, I think there are at least four ways that this is done in existing resources (various books, OL examples, workshop, API docs etc). As a new OL user I find this confusing.

My suggestion is that you include how to add multiple layers in the workshop examples/code. I appreciate there may be different use cases for adding layers in different ways. I also appreciate there are multiple types of layers.

A few suggested changes, typos, clarrifications etc

First, thanks for this important resource for learning OL. Second, I appreciate this resource is being refactored e.g. move to OL5, JS named imports etc. Third, I also appreciate multiple suggestions per issue/pull request are not best GH practice. Since Tim et al you are revising this repo, I wanted to share these suggestions from going through the workshop (it is great that in v5 you have improved the webpack config e.g. removed the webpack-dashboard dependence). Caveat: I am not an expert JS dev.

Suggested changes (SC), potential errors (pe), typos, clarifications and questions :
SC-provide links to main tools that are used to build this. It is great you are using webpack, and a link to the excellent webpack pages would help a reader use this valuable learning resource.
http://openlayers.org/workshop/en/basics/map.html
SC-already have an index.html and main.js in the root, so maybe refer to these.
http://openlayers.org/workshop/en/basics/geolocation.html
Typo- repeated ‘on’ first paragraph
http://openlayers.org/workshop/en/basics/point-feature.html
SC- create link to working code for each ‘when done, the result should look like this;’, the code is in the ‘examples’ folder.
http://openlayers.org/workshop/en/basics/popup.html
SC- replace var overlay with const (or let) overlay; used const elsewhere.
http://openlayers.org/workshop/en/vector/draw.html
SC- the point made is not clear (what is enum, why do this) “Note that we could have also imported the GeometryType enum (import GeometryType from 'ol/geom/geometrytype';) and used GeometryType.POLYGON instead of the 'Polygon' string above.”
http://openlayers.org/workshop/en/vector/style.html
PE- if ‘Static style: if we wanted to give all features…’ code is added then an error is returned
ReferenceError: Style is not defined at Object.defineProperty.value
SC- “Next we’ll write a couple of functions to determine a color based on area of a geometry’, need to provide more information on these two functions esp. what does ‘function clamp’ do.
Clarify- “And now we can add a function that creates a style with a fill color…” Is this a new function appended to existing code or modifying earlier ‘const layer = new VectorLayer({‘ ? It is the former, as when script started get an error “duplicate declaration ‘layer’”
SC- To render map, may need to say that countries.GeoJSON file needs to be added again.
NextSection: Vector Tiles
http://openlayers.org/workshop/en/vectortile/bright.html
SC- with all the ‘cleaning up’ (or refactoring) need to provide a link/text on revised code.
Q- what about the html style code (remove as well? If so, say explicitly).
NextLesson Raster Operations
http://openlayers.org/workshop/en/raster/
Check “You should now see some oddly colored tiles shown over your base layer.” Link is not showing the RGB tiles.
Typo “Add this layer (to) your map's layers array in..>”
Unable to show elevation /flood data in my example or their linked map.
SC- may be missing https://openlayers.org/en/latest/apidoc/ol.source.Raster.html
SC- Need to use this .js as main.js https://github.com/openlayers/workshop/blob/master/src/en/examples/raster/raster.js

issue on Geojson

I didn't use 'countries. json' in the example,instead,I just use my Geojson file,why is it didn't work?

Loading loader.js throwed an error

In workshop 1.1 step, create map.html
info serve-lib Debug server running http://localhost:4000/loader.js (Ctrl+C to stop)
/openlayers-workshop/node_modules/closure-util/lib/manager.js:172
throw new Error('Could not find base.js');
^
Error: Could not find base.js

npm on windows 10 issues

I am on Windows 10 with node v4.3.1

PS C:\Users\dan\Documents\openlayers\openlayers-workshop> npm install
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possib
le. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possib
le. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated [email protected]: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.
npm WARN deprecated [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possib
le. Use 'npm ls graceful-fs' to find it in the tree.

[email protected] install C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io
node_modules\engine.io\node_modules\ws\node_modules\utf-8-validate
node-gyp rebuild

C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\engine.io\node_mod
not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else
(node rebuild )
|
gyp ERR! configure error
gyp ERR! stack Error: Python executable "python" is v3.5.0, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at failPythonVersion (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:121:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:110:9
gyp ERR! stack at ChildProcess.exithandler (child_process.js:204:7)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack
at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at maybeClose (internal/child_process.js:821:16)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
gyp ERR! System Windows_NT 10.0.10586
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\engin
e.io\node_modules\ws\node_modules\utf-8-validate
gyp ERR! node -v v4.3.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm WARN deprecated [email protected]: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations yo
u were using wrench for. Thanks for all the usage over the years.
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

[email protected] install C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node
_modules\engine.io\node_modules\ws\node_modules\bufferutil
node-gyp rebuild

C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\engine.io\node_mod
ules\ws\node_modules\bufferutil>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-g
yp\bin\node-gyp.js" rebuild ) else (node rebuild )

gyp ERR! configure error
gyp ERR! stack Error: Python executable "python" is v3.5.0, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at failPythonVersion (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:121:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:110:9
gyp ERR! stack at ChildProcess.exithandler (child_process.js:204:7)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at maybeClose (internal/child_process.js:821:16)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
gyp ERR! System Windows_NT 10.0.10586
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\engin
e.io\node_modules\ws\node_modules\bufferutil
gyp ERR! node -v v4.3.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

[email protected] install C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io
node_modules\socket.io-client\node_modules\engine.io-client\node_modules\ws\node_modules\utf-8-validate
node-gyp rebuild

C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\socket.io-client\n
ode_modules\engine.io-client\node_modules\ws\node_modules\utf-8-validate>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bi
n\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild )
gyp ERR! configure error
gyp ERR! stack Error: Python executable "python" is v3.5.0, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at failPythonVersion (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:121:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:110:9
gyp ERR! stack at ChildProcess.exithandler (child_process.js:204:7)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at maybeClose (internal/child_process.js:821:16)
gyp ERR! stack at Socket. (internal/child_process.js:319:11)
gyp ERR! stack at emitOne (events.js:77:13)
gyp ERR! stack at Socket.emit (events.js:169:7)
gyp ERR! stack at Pipe._onclose (net.js:469:12)
gyp ERR! System Windows_NT 10.0.10586
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\socke
t.io-client\node_modules\engine.io-client\node_modules\ws\node_modules\utf-8-validate
gyp ERR! node -v v4.3.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]

[email protected] install C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node
_modules\socket.io-client\node_modules\engine.io-client\node_modules\ws\node_modules\bufferutil
node-gyp rebuild

C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\socket.io-client\n
ode_modules\engine.io-client\node_modules\ws\node_modules\bufferutil>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\no
de-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node rebuild )

gyp ERR! configure error
gyp ERR! stack Error: Python executable "python" is v3.5.0, which is not supported by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
gyp ERR! stack at failPythonVersion (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:121:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:110:9
gyp ERR! stack at ChildProcess.exithandler (child_process.js:204:7)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at maybeClose (internal/child_process.js:821:16)
gyp ERR! stack at Socket. (internal/child_process.js:319:11)
gyp ERR! stack at emitOne (events.js:77:13)
gyp ERR! stack at Socket.emit (events.js:169:7)
gyp ERR! stack at Pipe._onclose (net.js:469:12)

gyp ERR! System

Windows_NT 10.0.10586
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util\node_modules\socket.io\node_modules\socke
t.io-client\node_modules\engine.io-client\node_modules\ws\node_modules\bufferutil
gyp ERR! node -v v4.3.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok

npm WARN optional dep failed, continuing [email protected]
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm WARN optional dep failed, continuing [email protected]
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

[email protected] postinstall C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util
node ./bin/closure-util.js update

info install Downloading http://dl.google.com/closure-compiler/compiler-20151216.zip
info install Downloading https://github.com/google/closure-library/archive/5b25e65.zip
info install Download complete: C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util.deps\compiler\8b63a4d
aab7ca371906594910bdd91333c8e387a

info install Download complete: C:\Users\dan\Documents\openlayers\openlayers-workshop\node_modules\openlayers\node_modules\closure-util.deps\library\e2007315
d15a4c296321b220b84269a0d9c2d94c
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! Cannot read property 'emit' of null
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read

npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.3.1
npm ERR! npm v2.14.12

4.3.2-en nmp start fails on windows - backslash iso forward slash

npm start

[email protected] start C:\filefuif\workshop-4.3.2-en
mkdir -p doc/_book && npm run doc:serve

The syntax of the command is incorrect.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: mkdir -p doc/_book && npm run doc:serve
npm ERR! Exit status 1
npm ERR!

running the commands manually with a backslash i.e.
mkdir -p doc****_book
does the job.
(it starts on port 4000 iso 3000 and the link from the intro doc is wrong too)

Upgrade to openlayers 3.5

Working on this now.

Compass example has limited browser support

The compass example depends on the requestPermission method which currently has limited browser support. On other browsers/devices either no extra permissions are needed or a request is triggered by window.addEventListener('deviceorientation'). A more generic solution which maintains the existing structure might look like

if (window.DeviceOrientationEvent) {
  locate.addEventListener('click', function () {
    Promise.resolve(
      typeof DeviceOrientationEvent.requestPermission === 'function'
        ? DeviceOrientationEvent.requestPermission()
        : ''
    )

Custom builds chapter / example isn't working w/ Openlayers v3.17.1

ddd6922 upgraded the workshop to use Openlayers v3.17.1.

With the ol-custom.json from the custom-builds-chapter the command node node_modules/openlayers/tasks/build.js ol-custom.json ol-custom.js fails as follows.

$ node node_modules/openlayers/tasks/build.js ol-custom.json ol-custom.js
info ol Parsing dependencies
info ol Compiling 287 sources
ERR! compile externs/olx.js:1263: ERROR - Bad type annotation. Unknown type ol.control.ScaleLineUnits
ERR! compile  *     units: (ol.control.ScaleLineUnits|string|undefined)}}
ERR! compile                ^
ERR! compile 
ERR! compile 
ERR! compile externs/olx.js:1303: ERROR - Bad type annotation. Unknown type ol.control.ScaleLineUnits
ERR! compile  * @type {ol.control.ScaleLineUnits|string|undefined}
ERR! compile           ^
ERR! compile 
ERR! compile externs/olx.js:1794: ERROR - Bad type annotation. Unknown type ol.format.IGCZ
ERR! compile  * @typedef {{altitudeMode: (ol.format.IGCZ|undefined)}}
ERR! compile                              ^
ERR! compile 
ERR! compile externs/olx.js:1802: ERROR - Bad type annotation. Unknown type ol.format.IGCZ
ERR! compile  * @type {ol.format.IGCZ|undefined}
ERR! compile           ^
ERR! compile 
ERR! compile externs/olx.js:5899: ERROR - Bad type annotation. Unknown type ol.source.WMTSRequestEncoding
ERR! compile  *     requestEncoding: (ol.source.WMTSRequestEncoding|string|undefined),
ERR! compile                          ^
ERR! compile 
ERR! compile externs/olx.js:5981: ERROR - Bad type annotation. Unknown type ol.source.WMTSRequestEncoding
ERR! compile  * @type {ol.source.WMTSRequestEncoding|string|undefined}
ERR! compile           ^
ERR! compile 
ERR! compile 
ERR! compile 6 error(s), 0
ERR! compile  warning(s)
ERR! compile 
ERR! Process exited with non-zero status, see log for more detail: 6

Used ol-custom.json, click to expand

{
  "exports": [
    "ol.Map",
    "ol.View",
    "ol.format.KML",
    "ol.layer.Tile",
    "ol.layer.Vector",
    "ol.proj.fromLonLat",
    "ol.source.OSM",
    "ol.source.Vector",
    "ol.style.Fill",
    "ol.style.Stroke",
    "ol.style.Style",
    "ol.style.Text"
  ],
  "jvm": [],
  "umd": true,
  "compile": {
    "externs": [
      "externs/bingmaps.js",
      "externs/closure-compiler.js",
      "externs/esrijson.js",
      "externs/geojson.js",
      "externs/oli.js",
      "externs/olx.js",
      "externs/proj4js.js",
      "externs/tilejson.js",
      "externs/topojson.js"
    ],
    "define": [
      "goog.dom.ASSUME_STANDARDS_MODE=true",
      "goog.DEBUG=false",
      "ol.ENABLE_DOM=false",
      "ol.ENABLE_WEBGL=false",
      "ol.ENABLE_PROJ4JS=false",
      "ol.ENABLE_IMAGE=false"
    ],
    "jscomp_error": [
      "*"
    ],
    "jscomp_off": [
      "analyzerChecks",
      "lintChecks",
      "unnecessaryCasts",
      "useOfGoogBase"
    ],
    "extra_annotation_name": [
      "api", "observable"
    ],
    "compilation_level": "ADVANCED",
    "warning_level": "VERBOSE",
    "use_types_for_optimization": true,
    "manage_closure_dependencies": true
  }
}

Downgrading OpenLayers to v3.17.0 doesn't fixes it, same error.

Downgrading OpenLayers to v3.16.0 fixes this:

$ node node_modules/openlayers/tasks/build.js ol-custom.json ol-custom.js
info ol Parsing dependencies
info ol Compiling 311 source

/cc @bartvde, @tsauerwein Any idea how to fix this?

Update to OpenLayers 3.9.0

Update the workshop to OpenLayers 3.9.0 when this version is released, and release version 3.9.0 of the workshop.

Geoserver hosted by demo.opengeo.org is down for a long time (503 error)

Hi,

Why not change to https://ahocevar.com/geoserver/ (the same server used by OpenLayers' examples)?

I'd be happy to create the patch with the changes.

Thanks in advance.

map source code

is there's a way to retrieve code sources files of this nice map (with spots and popup) :
https://render.githubusercontent.com/view/geojson....
or
https://github.com/openlayers/workshop....

???
Thanks a lot

Markup not visible in online version

Actually workshop doesn't show any markup, instead it shows a broken link with the first line of the markup. For example, in Basics it shows up like this:

When starting it up locally from last release workshop-6.8.1-en, it shows up correctly:

workshop vectortile example

The vectortile example references a URL which no longer exists:

examples/vectortile/map.js

  source: new VectorTileSource({
    attributions: [
      '<a href="http://www.openmaptiles.org/" target="_blank">&copy; OpenMapTiles</a>',
      '<a href="http://www.openstreetmap.org/about/" target="_blank">&copy; OpenStreetMap contributors</a>'
    ],
    format: new MVT(),
    **url: `https://free-{1-3}.tilehosting.com/data/v3/{z}/{x}/{y}.pbf.pict?key=${key}`,**
    maxZoom: 14

The free*.tilehosting.com was apparently updated to maps.tilehosting.com and now api.maptiler.com.

https://www.maptiler.com/news/2019/04/maptiler-cloud-infrastructure-upgrade/

However, api.maptiler.com/data returns only 404s. api.maptiler.com/streets apparently returns a tile, but in the wrong format. I can't find the right thing to replace /data/, assuming /data/ is the offending directory.

Everything works for me except this example. Thank you for the workshop.

No setup page

The entry page for the workshop links to a non-existent setup page.

We need to either include a setup page or rework this text to describe the setup.

Use a v3.0.0 build

Update ol.css, ol.js, and ol-debug.js.

npm WARN deprectaed

I get a bunch of errors running npm install in \openlayers-workshop-en

npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: use uuid module instead
npm WARN deprecated [email protected]: wrench.js is deprecated! You should check out fs-extra (https://github.com/jprichardson/node-fs-extra) for any operations you were using wrench for. Thanks for all the usage over the years.

Win 10
node.js 6.9.1

Is all the node stuff really necessary to start a tutorial? Seems like a high entry threshold to get to know OpenLayers and it's harder to transfer the examples to my own application.

Import required for static style

Hello! In the 'Making it look nice' section of the workshop, the requirement for "import {Fill, Stroke, Style} from 'ol/style';" comes only in the 'Styling based on geometry area' subsection, but it is required to run the 'Static style' subsection.

Excellent work btw :)

Change from 2013 OpenLayers workshop to something else

Before FOSS4G 2014 we need to change the workshop title from "2013 OpenLayers workshop" to "2014 OpenLayers workshop" or "OpenLayers Workshop".

Windows?

Hi Tim,

I try to check out the "Openlayer Workshop". I'm on the point to start the workshop server with "npm install" and "npm start" ("In the resulting openlayers-workshop directory, run the following to get the workshop dependencies:....") Before that I have been installed node.js - is that right? But "npm" is unknown on my windows-7 machine. Please Is there a install-guide with a bit more introductions?

best
kbs170

Typescript Example?

It would be nice to see an example which uses typescript. Can the openlayers typings be generated from the source? I do not see it published anywhere. On the other hand, it seems the source is already typescript compatible so maybe we can just import the source without the typings? Some guidance in the form of a workshop would be helpful. I will say that the only issue I see with treating ol as typescript is in the pbf.js and ieee754.js commonjs modules, which are easily ported to javascript modules. Perhaps the authors of ieee754.js could be nudged to produce and es module.

ol.css removed form src/_book

The npm start script copies ol.css in src/_book. But run doc:serve, executed as part of the start script, removes it. For that reason we get 404s on ol.css when running the examples.

Bing API key?

The API key given in the workshop is '<Your Bing Maps Key Here>':
https://github.com/openlayers/workshop/blob/master/src/en/layers/proprietary.md#tasks

This does not work. :)

Change copyright?

stackoverflow: use the 'openlayers' tag instead of 'openlayers-3'

see openlayers/openlayers#6320

Add analyzerChecks in jscomp_off

When we will update ol3 to version v3.15.0, analyzerChecksmust be added to the closure-util config (in jscomp_off).

See #46

firefox fail

First Example loads in chrome , not in Firefox.

Uncorrect phrasing in doc/en/basics/popup.md?!

In https://github.com/openlayers/workshop/blob/master/doc/en/basics/popup.md, it seems there is a missing "to"

In addition to the css, we also need to add the markup for the container the body of our index.html:

should be

In addition to the css, we also need to add the markup for the container to the body of our index.html:

As I'm not a native English speaker, I may be wrong. Thanks for your feedback

Resources in the resources page are outdated

We need to update the branch with new ol builds for example.

Running examples while developing the workshop

Following the README.md page, I run npm start to start the workshop development server. I can then browse the workshop documentation as expected. But it looks like this development server does not serve loader.js and can therefore not be used for running the workshop examples. Is this correct? If so what do you use to run the examples while developing the workshop?

Release v4.0.2-alpha.2 with zip file of workshop in Portuguese

Hi,

The current alpha version has only zip files for English and French workshops. It'd be interesting making the Portuguese zip package available for download too.

Thanks.

Remove unnecessaryCasts from jscomp_off

unnecessaryCasts was removed from the closure-compiler in v20160517

How to update the workshop with a new release of OpenLayers?

What are the required steps to update the workshop with a new release of OpenLayers?

Here is a blind attempt:

Update the openlayers dependency in package.json
Run rm -rf node_modules/openlayers && npm install
Update the openlayers dependency in src/package.json

Why use loader.js?

Thinking about it I wonder why we make our participants use loader.js instead of a ol.js (the full OpenLayers build)? The problems I see with loader.js:

it's not how most people would use OpenLayers
it takes a lot of time each time you reload an example page

I am not sure I want to change this now though.

openlayers / workshop Goto Github PK

workshop's Introduction

OpenLayers Workshop

Building the workshop

Creating a new release

workshop's People

Contributors

Stargazers

Watchers

Forkers

workshop's Issues

Recommend Projects

Recommend Topics

Recommend Org