Today I uploaded Part 2 of the Leaflet Video Tutorial series for the GISC. This tutorial introduces the basics for adding markers to maps, and using GeoJSON datasets with Leaflet. Be sure to watch Part 1 if you need a refresher on Basemap Initialization with Leaflet.
The Atlas of Design has opened its doors once again for those wanting to be a part of the beautiful world of cartography. Volume I was a great success that produced a hard cover publication showcasing some of the finest maps recently made.
You can submit on their website and all you need is your name, map title, email, map description, and a small file of your map to upload.
Submissions are open until February 28th so make sure to polish up your projects before then!
Mike from SoCalGIS.org just posted an excellent tutorial showing how one could use Python within the field calculator to break apart string values and add them to a new field.
For example, say you have a field with values such as “Census Tract 12345″ and you want to have a field that only contains the tract number (e.g., 12345). You can use python within the field calculator to extract that third word from the field, pretty sweet!
Check it out:
I was searching for some elevation data for San Diego and came upon a dataset with a .e00 extension. I downloaded it and I wasn’t able to add the file to ArcMap. It just didn’t show up in the folder as a file to select. What gives?
Files with the .e00 extension are ArcInfo Workstation interchange files, and they are used to transport coverages, INFO tables, text files, and other ArcInfo files. Adding .e00 files to ArcGIS is fairly simple, but you first need to convert them to a coverage.
To convert .e00 files to a coverage you need to use the Import from E00 script tool. The tool is located in the toolbox under Conversion Tools > To Coverage > Import from E00. Specify the input/output parameters and run the file.
Your .e00 will be converted to a grid file and will be able to be added to the Table of Contents in ArcGIS.
Mike Bostock released TopoJSON 1.4.0 today, which revisits the algorithm used to simplify topological data. This is an exciting release, as it really aims to widen the precision inputs when using the command line references to look at points that aren’t exact but assuming they are in the same location. Described by Bostock:
An issue of particular importance to topology inference is messy inputs. For example, if you have two points [-122.416712304917, 37.783305712306] and [-122.416712304916, 37.783305712306], then in regards to the topology they are as distinct as San Francisco and New York. The TopoJSON reference implementation eliminates many of these errors by quantizing inputs, rounding them to lower precision.
He recently put together a great visual explanation on how topojson works from a practical and geographic perspective. It’s a great article explaining the four-step process. Hats off to an exciting release!