Having played with geospatial a lot in the past, both "manually" and using libraries like cesium.js (which a lot of this is based on), my gut reaction is "I hav

Having played with geospatial a lot in the past, both "manually" and using libraries like cesium.js (which a lot of this is based on), my gut reaction is "I have no idea how hard it is." ;) Joking aside, I'm not sure. As you know, the math in the libraries and the datasets are tightly coupled to the projection model (e.g., on earth, things come back to ECEF coordinates, what cesium calls FIXED, and models of the planet like WGS84). So, I would suspect that this work could serve as a model, but a bunch of the internal math would need to change. Assuming there is a well defined model of Mars that can be used, akin to WGS84, and you can massage all the datasets into a form that can be reliably mapped to it, like AGI/Cesium has done with the geospatial data we are using, it should be possible. I know we would love to see someone do this, inspiring projects like this is one reason we release things in the open. Heck, you could imaging a new set of options for the a-terrain component that specified the globe model somehow ("WGS84, MARS18") and a base URL for the data server ...