Author: James Fee

Yes everyone knows about What3Words. It was an attempt to come up with an easy way to assign addresses for places where there are none. In the end, a proprietary addressing system will never gain traction, and of course the inevitable eventually happened. My personal feeling is that What3Words never really got us beyond x/y numbering and the logic behind an addressing system was not there. Enter Plus codes which comes at this problem from a different perspective. There is a very detailed analysis of existing methods and why they choose to go this direction that I’ll leave it up to you to read.

Probably the biggest reason to pay attention is that this open addressing system was developed by Google. In fact, they are already implementing it in India as we speak which goes a very long way to making this happen.

All these systems are built on the idea the world is a grid, and how deeply you drill down into that grid is your address so things need not be a single point, they can be an area which opens up many exciting ideas for addressing, especially outside of North America and Europe. Check out the Github project to learn more.

So this time of year nothing says March more than March Madness (well maybe Easter when Easter is in March). Lots of companies play off the theme, and it appears Mapbox is jumping on that sports bandwagon themselves with Map Madness.

I’ve clicked the play button myself, and I’m waiting for the start. I have no idea what the challenge will be, but I’m up for any of the prizes. The Mapbox team is full of brilliant people so I can only assume the challenges will be more than just guess where a satellite photo was taken.

Several geospatial systems use Well Known Text (WKT) as their preferred/only format for geospatial objects. What if you wanted to use Elasticsearch for your geospatial data though? Until 6.2, Elasticsearch has only provided the option of providing shapes in GeoJSON format. To get your WKT data into Elasticsearch, you may have to go through a complicated export + conversion process. No longer! You can now index a shape in a WKT string directly to Elasticsearch.

I’ve been using WKT quite a bit because it supports curves and now I can load WKT natively into Elasticsearch without converting it beforehand. There is much here to think about for sure!

I know, I used the buzzword IoT in my title above. Stay with me though! We think about IoT as a link between a physical device (your Nest thermostat for example) and the digital world (your Nest app on your iPhone), but it is so much more. While we have been working with many IoT providers such as Current by GE we’ve also fundamentally changed how our backend APIs work to embrace this messaging and communication platform.

Using AWS IoT Services everything that happens in our backend API can alert our front end apps to their status. This ties very nicely into our Unity front-end Smart World Professional application because it can tell you exactly what is happening to your data. Uploading a detailed Revit model? The conversion to glTF occurs in the background, but you know exactly where the process is and exactly what is going on. Those throbber graphics web apps throw up while they wait for a response from the API are worthless. Is the conversion process two thirds the way through or just 10%? Makes a big difference don’t you think?

Where this really starts to matter is our analytics engine, Mapalyze. If I’m running a line of sight analysis for a project in downtown Chicago, there is a ton that is going on from the 3D models of all the buildings to trees, cars and the rest that can affect what you can see and can’t see. Or detailed climate analysis where there are so many variables from the sun, weather (wind, temperature, rain) and human impacts that these models can take a very long time to run. By building the AWS IoT platform into our backend, we can provide updates on the status of any app, not just ours. So if you want to call Smart World Professional Mapalyze from within Grasshopper or QGIS, you won’t get a black box.

In the end what this means is Smart World Professional is “just another IoT device” that you will be able to bring into your own workflows. Really how this is all supposed to work, isn’t it? For those who want to get deeper on how we’re doing this, read up on MQTT, there is a standard under here that everyone can work with even if you’re not on the AWS platform.

The GovTech 100 is an annual list compiled and published by Government Technology as a compendium of 100 companies focused on, making a difference in, and selling to state and local government agencies across the United States. We were excited to find this month that GovTech has put Cityzenith on this list.

There are a lot of spatial companies on that list which just shows how important this space is. We’re getting ready to release our Smart World Professional tools later this quarter which are built on Unity and the Mapbox Unity SDK. It’s been a crazy 6 months from being part of Dreamit to now being on the GovTech 100 and then on to Smart World Professional.

If you’ve ever seen Cityzenith before, you would know that the basic premise is a 3D Google Earth like world in the browser. The way we accomplish this is using a JavaScript library called Cesium. There is much to like about Cesium and if you’ve never checked it out I highly encourage you to do so. Not only is Cesium we’ll supported/developed, it has a great community around it and lots of great documentation. Cityzenith had been on Cesium for years and you’ll see our screenshots on the Cesium webpages as a use case. When our customers first see Cesium running in the browser they’re all very excited and impressed with how well it works, how good it looks, and we’ve built a business around it. But in August we decided to go another direction and move to Unity3D. I’ll write more about that move later but this is a post on what worked for us with Cesium, where we had problems and what you can expect if you use it. If people ask me about a 3D solution in the browser, I can still equivocally say that I would recommend Cesium.

The choice of Cesium predates me, so I was not involved with the decision. That said those who made the decision have explained why they went that way. Cesium was probably not the original choice but at the time in 2014/2015 it was the best solution of a “game engine” for our product. We did look at other engines such as Unreal but the 64-bit support and the ease of use in the browser, Cesium won out. In implementing Cesium what were we able to do?

We were able to implement a cross platform 3D world in a browser. That’s not an insignificant accomplishment. Our Cesium team really did an amazing job of making Smart World feel like a regular desktop application even if it was in a browser. No extensions to load, Java or Flash to configure. In a modern browser it basically just worked (more on this though later).

While normally a pain in the rear, the fast updates and quick support for new features on the Cesium project gave us access to new features regularly. We were able to continually update our support for better graphics, performance and features almost by just loading up a new version of Cesium. Of course, in reality it is not that easy but the feature improvements were regular and powerful.

JavaScript is an accessible language. Yes, it has its problems but finding people to code in JavaScript is not difficult. Plus it made it easy to combine other JS libraries we needed into the application.

Open source is very liberating on many levels. Not having to fight a licensing battle and focus on the product is a nice change from other development libraries and SDKs. Also having direct access to the developers. If you don’t follow Patrick Cozzi yet you should. Amazing work and they listen to feedback.

glTF support is second to none. I’ll be talking about glTF soon as well and why we absolutely love it.

OK, so what didn’t work with Cesium? Why leave it?

There are really only two reasons we have left. Most of everything else we get with Unity we would either have with Cesium very soon or it’s being implemented today. But the two reasons have been killer for Smart World. I don’t think everyone runs into the same problem we have with their apps so this is more of a specific issue with what we are doing rather than a problem with Cesium.

Cross browser support. Remember when I said that we had cross platform support? Well that really only works if you use Google Chrome. Other browser support is poor at best. Microsoft Edge? Yea not going to happen. Being an enterprise app, we don’t always have the latest and greatest browsers that our customers can use. It’s not an IE8 problem but Edge and Firefox support really killed it for us. It got so bad that we had to put up a modal dialog box that basically said you couldn’t use Smart World without Google Chrome. That’s just unacceptable to us and while we tried to work on solving this the reality of support in other browsers was not coming quick enough and I’m not sure it was a problem that Cityzenith could have solved throwing money at the problem.

Performance in the browser. Chrome is many things and one of them is that it is a memory hog. Loading up cities in Chrome really would put a strain on our user’s computers. The browser is great for simpler 3D mapping but streaming gigabytes of data into a browser really tasked computers. We worked on a ton of LOD workarounds but the compromises to make the application work on a typical enterprise desktop or laptop really left a bad taste in our mouths.

Roadmap for Cityzenith

We want to provide the best 3D analytical tools and we’ll continue to do so. Combined with AWS Lambda and AWS IoT services, we’re making a huge leap in how people perform spatial analysis. Not only are we working on our own planning tools such as rooftop solar analysis, LEED-ND analysis and traffic analysis, we’re integrating RhinoGrasshopper plugin support, so anyone can use their existing workflows. As I said above, we’re moving our 3D engine to Unity. In fact we’ll be having a closed beta very soon for our customers to try it out. One of the biggest reasons we went with Unity was Mapbox’s Unity SDK. We are already a big user of Mapbox and thus moving to the SDK made a ton of sense. I’ll go more into this in another article.

We all get busy from time to time and the past year has been so busy that it feels like a blur for me. That’s a good thing though, so much good going on. At Cityzenith we’ve hired a great team to migrate our platform from cesium.js to Unity. More on this later in the post.

Now on to the news we were able to talk about last month was Cityzenith was selected for the Dreamit UrbanTech. This is startup accelerator founded in partnership with Strategic Property Partners (a joint venture by Jeff Vinik and Bill Gates). SPP is leading the $3B redevelopment of the Tampa Bay waterfront, one of the largest real estate projects in the United States and a rare opportunity to build a smart, connected city in an existing urban zone.

I’ll be in Tampa all next week meeting with many of the companies who are going to use Cityzenith to build the Tampa Bay Waterfront Project. We are excited to use the project to scale Cityzenith into a tool that can be part of the workflows for all Architecture, Engineering and Construction companies who want to integrate, BIM, GIS, CAD, IoT, web services and visualize them in a worldwide 3D tool that gives them the ability to plan for the future and the impacts of current development. Should be an amazing time.

In the coming weeks I will be diving deeply into why Cesium is actually pretty damn awesome even if we didn’t select it for Cityzenith Smart World 2.0, why we’re really liking glTF 2.0, Mapbox Unity SDK, using AWS IoT and AWS Lambda for some great serverless file conversions and what we’re diving into deeply, City Information Modeling or CIM.