depthTestAgainstTerrainin the config and UI?
DatasourceCatalogItemI'll have to find time to explore this a bit more
setInvervalthat on each interval calls the
onNextButtonClickedcallback, which will advance the layer to the next time step.
DataSourceCatalogItem. I’m not sure if the clustering would work in 2D leaflet view, but it should work in 3D view.
Following yesterdays discussion, if I do a fresh clone of TerriaMap and an
npm install, when I then
npm run gulpI do get a
WARNING in ./node_modules/terriajs-cesium/Source/Core/TaskProcessor.js 145:117-124 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted @ ./node_modules/terriajs-cesium/Source/Core/loadCRN.js @ ./node_modules/terriajs-cesium/Source/Scene/ImageryProvider.js @ ./node_modules/terriajs-cesium/Source/Scene/BingMapsImageryProvider.js @ ./node_modules/terriajs/lib/Models/BingMapsCatalogItem.js @ ./node_modules/terriajs/lib/Models/registerCatalogMembers.js @ ./index.js @ ./entry.js
with a bunch of noise after it. But it looks to have built.
npm run gulp releaseit fails the first time with the below, but then succeeds if I run it again. I get that it could run out of memory, but I don't see how running it again fixes things, unless it doesn't start clean each time. I don't think this is causing an issue but thought to feed it back. I don't see the release build error on my workstation, only when I build on a VM.
0.0.05, the only upcoming change to this will be when mobx gets merged and we'll have to manage that within terriajs.
The great thing about my work with Terria is that it has exposed me to a world of new technology. At times this is one of the more frustrating things. With the blacklistedAddresses discussed above should be there be any difference between "npm start" or a "npm run gulp release" started per
./node_modules/.bin/pm2 start ecosystem-production.config.js --update-env --env productionI do edit ecosystem-production.config.js to fix the instances as I have had mixed experiences with
Math.max(4, os.cpus().length)on different windows computers. I have in mind this configuration doesn't feed into the build?
I see now that devserverconfig.json doesn't pipe into the production release and there is a different production config file I previously missed. Progress is being made. I mention these things incase others find it similarly confusing.