Spatially Adjusted

Blog

  • ArcGIS Pro Licensing — Enabling

    So last week I was talking about how to now use ArcGIS Pro with “Classic Licensing”. Well after following the directions on Esri’s website which resulted in no new licenses we finally realized that despite what Esri says on their support page. The original suggestion was just use the ArcGIS Desktop license for Pro 1.2. What you actually need to do is find your ArcGIS Pro 1.2 license in My Esri and use that. Make sense when you think about it but the directions from Esri before was just use your ArcGIS Desktop.

    The disconnect was that you get ArcGIS Pro license code with your ArcGIS Desktop license. You just need to run the licensing wizard and then point your ArcGIS Pro to that license server. Then it works without an issue.

  • ArcGIS Pro Licensing — The Old Way

    ArcGIS Pro has always had somewhat of a non-standard way of being licensed. I’ve never really gotten into it mostly because it revolves around “provisioning” and “logging in” to ArcGIS Online. Even if I felt a real need to get it to work, it just seems like a very annoying method of licensing software. Now since technically we aren’t paying for ArcGIS Pro licenses just yet, I suppose it doesn’t really matter1. But as I do want to at least get an idea of what Pro is, how it works and what it means to GIS workflows when/if it replaces ArcGIS for Desktop, licensing matters. I’ve not been to an Esri conference in almost a year so the ins and outs of Pro licensing have been lost on me but this tidbit yesterday about ArcGIS Pro moving forward was interesting.

    So there you go, I’m guessing this means when 1.2 arrives this week, I can just point it at my existing license manager and away we go. I’ll install ArcGIS Pro, be impressed with the new UI and then realize it’s a dog and buggy as sin2. But 64-bit is a big carrot so depending on how the geoprocessing works, I can see myself embracing Pro, Python 3.x and 64-bit.

    From the “What’s New in ArcGIS Pro 1.2”:

    Before the 1.2 release, the only licensing option available for ArcGIS Pro was through Named User licensing. This license model required authorization through your organization administrator on Portal for ArcGIS or ArcGIS Online. At 1.2, you now have two new licensing models available that don’t require you to go through a Portal for ArcGIS or an ArcGIS Online organization: Single Use and Concurrent licensing. With a Single Use license, ArcGIS Pro points to a file for authorization. The file is stored on the same machine that runs ArcGIS Pro. With Concurrent licensing, a given number of licenses are hosted on a License Manager (the ArcGIS License Server Administrator). ArcGIS Pro is then configured to allow organization members to check out an available license from the pool of licences hosted on the License Manager.

    While I did spend a lot of time photoshopping the splash screen above, here is the ArcGIS Pro 1.2 splash screen.

    1. Beta software has always been sort of a different beast when it comes to licensing. ↩

    2. I’m thinking it will be ArcGIS Desktop 8.0.1 all over again. ↩

  • Washington Crossing the Esri

    Every year or so it seems like Esri gets written up in Forbes. Last week the following came out:

    …long before Google was born–even before its founders were born–it was Dangermond who essentially invented the digital map. Esri , the company he founded with his wife, Laura, in 1969, has toiled in relative obscurity to become one of the more improbable powerhouses in tech, having survived wrenching shifts in computing that destroyed scores of its fellow tech pioneers.

    Now before you think it is a puff piece like last years, think again. I was surprised in the honest assessment of Esri, Jack’s place in technology and the happiness of Esri employees. Working in the industry we do, we all know the place that Jack and Esri fit within the grow of GIS. The article focuses on Esri but I think it hits upon what everyone is doing, Esri itself, their business parters or those who avoid their software:

    “There’s been an explosion of people who think of their research in geospatial terms,” says Julie Sweetkind-Singer, Stanford’s assistant director of Geospatial, Cartographic and Scientific Data & Services.

    There has been, it might make “Jack bullish” but it really is built upon the doers of GIS. Visionaries may point the ship in the right direction but those on the ground have turned GIS from a specialized-niche profession into something that is part of almost every workflow imaginable. Read the article, it think it is worth your time.

  • WordPress to Jekyll again

    About 4 years ago I moved my blog from WordPress to Octopress. That process was a total hack and eventually I moved back to WordPress because I had just too many blog posts and Jekyll took 10 minutes to build the site before publishing. Since then I’ve dealt with WordPress and it’s issues but generally it has gotten much better. But I’ve grown tired of hosting my own blog and the security updates so I had two choices. Move to WordPress.com or move to Github Pages. Clearly you can see I took the latter route. The migration is a piece of cake, just used a simple python script and converted all my WordPress XML to markdown. Then just push to Github. The results as you see them?

    • Blog looks bare, I haven’t themed it yet
    • 404 errors galore
    • Feed probably spammed you
    • Killed comments1

    1. Not coming back ↩

  • GIS: From ActiveX and ColdFusion to Node.js

    When ArcIMS 3.0 arrived, it was literally the best day of my life (well from a GIS programming perspective). After hacking ArcView IMS 1.0 and then some crazy VB5/VB6 stuff with MapObjects IMS 2.0 (esrimap.dll is the work of the devil) there was finally something that was able to be truly a web server GIS development environment. With excitement I pulled myself into the Esri UC session for ArcIMS 3.0 and then sat down with pen and paper (this was before WiFi). I looked around and noticed that there was not many people in the room for the ActiveX session. But across the hall the ColdFusion session was packed and out the door). Now the less said about ArcIMS 3.0 the better but it was the start of real programming on Esri Server products.

    ColdFusion hung around for a while but the ActiveX stuff was quickly replaced with the WebADF. Now there is much on this blog about the WebADF and I don’t think I need to go back over it but while it was a complete mess, it did allow us to develop with .NET and actually create some amazing applications. Eventually the REST API replaced much of what we were doing with the WebADF Framework and we were free from all the limitations of that AJAX madness. I think the key with Esri Server development is the REST API. This is what freed us from siloed frameworks and allowed us to move into other languages such as Ruby/Rails.

    Now during the Ruby/Rails period, I was working for WeoGeo so my focus was on that stack, not the Esri one. I do recall Dave Bouwman showing Ruby/Rails stuff at the DevSummit but it never took off as an Esri development language. There isn’t anything inherently wrong with it, it just was never supported as well on Windows as other options so by the time Windows support was good enough to be used, we all moved on to Node.js.

    Now Node.js is probably the biggest impact on what we do with Esri Server since .NET. The best part though is development is basically cross platform so I can be on my MacBook Pro and my other Devs can roll on Ubuntu or Windows. Again, because of the REST API. If you go to the Esri Github repository or look on npm you’ll see lots of JavaScript and Node.js projects just ready for the taking.  It’s a far cry from the days of trying to register some stupid ActiveX control in VisualStudio (heck I still have nightmares about Visual InterDev).  Now I won’t sugarcoat npm because when it works it’s great, when it doesn’t it sucks.  But generally I can typed a couple words and have a new Node.js application installed in my project.

    As I’m getting back into ArcGIS for Server 10.3 and ArcGIS Online I’ve come to reflect on the crazy path we’ve taken from Avenue -> VB5 -> ActiveX -> .NET -> Ruby/Rails -> Node.js and on to whatever is next.  Not only that, during this whole time there were those Java guys (it was like 3-5 of them) in the corner trying to just get ArcGIS for Server Java installed.  But hey, they got free copies of MapObjects Java Edition.

  • 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).

  • 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….

  • 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.

  • Ben Carson’s Map Screws with New England

    He’s only running for president, close enough I say… Connecticut clearly wants to be close to Canada.  And lets be honest, Massachusetts was too large anyway.  It’s more manageable now.

  • Story Map Time

    I made a story map today. The process is a bit rough on the edges but I worked through it. I’ve used more Esri in the past month than the past 5 years.

    Interesting times…