ArcGIS JS 3D Camera Setter
A simple way to grab arcgis js 4.x 3D camera json by copying the current camera state to your clipboard:
I’m building a 3D mapping app using the ArcGIS JS 4.x API that requires a new 3D camera position for each instance. This presented a funny problem because it is rather tedious to capture a specific camera position. Unlike a simpler, 2D map, in which you only have to set an extent or a center point with zoom level, a 3D camera has more variables that require you to take a pilot’s view of the earth. You need to set the position of the camera including coordinates and height, as well as the tilt of the camera and it’s heading.
While it’s kind of fun to just tweak it and refresh the page to get it just right, it takes a lot of tweaking!
So I built a simple tool that captures all of the properties of the camera and formats it in the json required to set the view of your 3D map and copies it to your clipboard.
It’s simple! A camera json object is created for the current 3D map view and displayed in the right panel. The copy button copies the json to your clipboard for direct use in your arcgis js 3D map view (sceneview). Just paste it right into your code.
Give it a try here
and you can find the code here
It includes a sample feature service for reference, but obviously you don’t have to. The 3D scene will work just fine.
Also, this could be used to create tour by using a series of camera positions, for example. (Potential future post…)
arcgis js api 4.x
icon from Icons
Many of the desktop GIS paradigms have unfortunately made their way to the web. Second only to the ‘Identify’ tool in popularity, the checkbox for toggling layers is still the most common way to turn map layers on and off. While I appreciate the simplicity it just doesn’t seem all that, well, elegant. And now that skeuomorphism is out and flat design is here to stay, the good ole checkbox might just be going the way of
This doesn’t hurt my feelings but it does leave some interesting voids and presents lots of possibilities.
Here’s my first departure from the old paradigm that I’m using pretty regularly. A sized
< div > floating directly over the map with some roundy edges and applying slight transparency. Position these togglable layer elements in a corner or off to the side and they work pretty well.
dual purpose layer toggler and legend
Set the css hover to
cursor: pointer and change the background color and it becomes obvious that you can interact with it. Adding an icon can be used to invite users and indicate what it does. This allows you to maximize space by using the element for both togglability and as a legend. Moving the element into the background by lightening the background color, removing the border and changing the icon indicates its in-visibility. Conversely, applying a solid border, increasing opacity and swapping icons give the visual cue that this thing is live.
Wire up a click event for each togglable-layer element to toggle the visibility of the layer on the map and also to toggle css classes that visually indicate the visibility state of that layer.
You can see this in action,
demo of togglable layers using recreation sites at Wenatchee National Forest
Source of demo on github.
I realize that there is a growing contingency of ‘no GIS’ proponents who would do away with the concept of turning layers of data on and off and, in some contexts, I agree. But there are many use cases where this can be extremely powerful and, if done well, dare I say, elegant.
On Tuesday MapBox announced the release of its new Satellite layer based, partially, on NAIP imagery in the US. So I said I’d like to test it for speed against the NAIP Web Map Service (WMS) hosted by USGS National Map I’m currently using.
I was initially planning to do some benchmarking on tile load speed etc but really, it just isn’t necessary. One zoom or pan of each will tell you that MapBox is faster, hands down. So since what I do is highly visual, and because it’s a helluvah lot more fun, I simply dropped the two maps side by side and wired up some events such that, as one side is panned or zoomed, the other is set to the same resulting extent. Some flying around in either map will indeed confirm the hypothesis that MapBox is faster. But this didn’t turn out to be the most interesting part really. You can see that the quality is higher with higher contrast and crispy colors on the MapBox side. I did not alter saturation, hues etc of the imagery but simply left the default. Lots of interesting experimentation to be done there too.
Take a look for yourself and you’ll see which is faster. You will likely also discover more interesting comparisons.
Pro tip: go full screen (F11 in Firefox and Chrome)
Hat tip: And it’s centered on DC by default, for @cageyjames – I get it, I used to be west coast.
- There isn’t a map event in Leaflet that fires when all tiles are loaded (didn’t consider using anything else)
- Map events are wired such that a slight advantage is given to the target map
- MapBox Satellite also has roads and labels so a bit more load (handicap, like bowling)