Categories
Thoughts

GeoJSON Ballparks Update

Just in time for spring training, I’ve added the Grapefruit League ballparks to the GeoJSON-Ballparks Github repository. Right now there are over 250 ballparks mapped in GeoJSON.

I plan to focus on China and Europe next and eventually fill out some college conferences (Pac-12, SEC, ACC, Big 12).

Categories
Thoughts

Extensions for ArcGIS for Server

One of the more confusing things for new ArcGIS users is that they probably need either Spatial Analyst or 3D Analyst to do their work. It’s almost a foregone conclusion that every ArcGIS for Desktop license will have at some point either one of those extensions. As I’m getting back into Server though I’m starting to take a look at those extensions as well. Specifically the GeoEvent Extension has caught my eye. Conversations on Twitter basically expose that it either works or it doesn’t and it’s either great or maddening. Sounds like typical Esri software.

The thing about Server extensions though is they mostly have a Windows requirement to run (thankfully GeoEvent doesn’t). As I’ve jumped back into ArcGIS for Server I’ve been impressed with it’s maturity but alas it’s still a windows only product which limits its use in hosted environments. I’m not oblivious to the reasons why these things go Windows only but it is a shame that Workflow and Data Reviewer require windows. Hopefully as Esri transitions into a more software agnostic development environment, they’ll start fixing these Windows only requirements.

At least GeoEvent Extension runs on Linux, wish me luck with that….

Categories
Thoughts

Editor Choices

I’ve been a BBEdit user since probably 1994 (that’s the oldest floppy disk I can find) and I’ve loved it. Back when I worked at WeoGeo though, I flirted with TextMate as did many others who worked with Ruby. But that project imploded with the 2.0 beta so I moved back to BBEdit with MacVim running when I needed command line editing. I’ve dabbled in Sublime Text but I just never cared for it so I stuck with BBEdit.

With my new job though I’m knee deep in Node.js and Express.js and BBEdit just isn’t working for me so I’m looking at a new editor. My choices as I see them right now are:

I’ve used Atom on and off since GitHub had their beta but I stuck with BBEdit for what I’m guess are “historic reasons”. Atom, being born out of GitHub is modern and has what appears to be a robust community behind it with packages and themes.

Brackets is intriguing but I just can’t get my head behind using an Adobe product (even if it is open source). I feel like Adobe PageMill might just suddenly appear on my desktop. The biggest +/- of Brackets is that it is designed for web design. It doesn’t concern itself with Objective C or Swift coding. It’s focused on web technology which simplifies it a bit but limits my use of it. I like the idea of just using one editor and staying with it.

Now Microsoft Studio Code is very good. I’ve really liked using it and it too has a robust community developing extensions. Plus it is built on Electron which is the underpinnings of Atom.

I’m torn between using Microsoft Studio Code and Atom. I’ve been locked on Atom the past week and while I do like what Microsoft has done with Code, I think I’m going to be staying on Atom moving forward. The best part of JavaScript development though is you really don’t need to standardize on any editor. Just let Git control the project and edit in TextEdit.