My application is a WordPress plugin for embedding Cesium maps in blog posts. It was born out of volunteer work developing a 3D avalanche hazard map that was kicked to the curb by Luddites. I don’t use the off-the-shelf version of Cesium’s base layer picker because, in order to customize it with several regional base layers, I need to set each image and terrain ProviderViewModel and push that to the collection. The image base layers are as small as a few square-mile area tile map service hosted on ArcGIS OnLine of a hiking trail map I prepared for the local Randolph Mountain Club; the state of New Hampshire’s 1-foot resolution aerial photos, hosted on their state GIS agency’s ArcGIS Server; and the latest addition was Austria’s OpenGovernmentData tile map service (I love the Alps in 3D!).
Hey, I’m open to suggestions if there’s a new way to streamline customization of the base layer picker. I wrote that part of my code 3 years ago for Cesium 1.5
I’m not a full-time programmer, this is a labor of love on my nights and weekends, and after finishing last weekend’s bug fixes and enhancements to my code, I said to my wife, “I really ought to roll this month’s Cesium update into this week’s WordPress plugin update. It will probably fix a few bugs, add some features I won’t use, and break something I do use”. I hate being so prophetic. I felt guilty for skipping over Cesium’s February 1.42 update, so I hastily downloaded and packaged 1.43 in my plugin installer without testing it on the localhost. Then I saw the console error regarding the missing STK.png, after updating my GoDaddy development site, when I opened the first page to test my other fixes and enhancements. Sometimes experiences like this make me glad I’m not a full-time programmer, other times I wish I was getting paid for the hours I spend coding. But when I start panning and zooming around in those 3D Cesium maps, the smile comes back to my face.