I’ll admit, my professional GIS development experience is in the ESRI sphere. It’s what we use at work and it’s what I’ve been using for going on 10 years now. I’m familiar with FOSS4G, but have not really had the opportunity to develop any projects incorporating it. Because of this, I was not really aware that the ESRI REST spec for their JSON response really differed much from the standard GeoJSON spec. My naivety is a little embarrassing as a GIS professional.
So my interest was piqued a few days ago when I saw someone post a tweet about the request to have ESRI add a GeoJSON response to their REST API. For whatever reason, I got it on my head that it couldn’t be that hard to do. A quick Google search showed their were a couple of ways to do this with third party tools, but I figured there had to be a way to do this quickly in the browser or natively server side.
Recently, I have been practicing on little projects in various languages and frameworks and I thought Node.js would be a great solution to get this rolling. It’s fast, can work with JSON objects natively and should work pretty simple without having to worry about browser compatibility issues because it runs through Google’s V8 engine.
So I set out looking at what would need to be done to convert ESRI-JSON to GeoJSON. As an aside, this entire project was done inside Google Chrome using the Cloud9 IDE and deployed directly to Heroku from within Cloud9. I could probably do a whole write up on that experience.
It took me a couple of days and lots of debugging and running various ESRI-JSON through the converter, but I think I’ve got a very usable application running to demonstrate the conversion. If you’ve worked with this before, GeoJSON has a standard array called “coordinates” to hold x,y information. ESRI-JSON uses “rings” for polygons, “paths” for lines and just an array of x,y pairs for points. A little annoying to convert, but not a big deal.
You can also send your ESRI-JSON as a parameter to http://esritogeo.herokuapp.com/parse/esrijosngoeshere and get a JSON response. I should point out a caveat is that you need to make sure you are sending the correct projected data. GeoJSON uses standard Lat/Long, so your ESRI-JSON should be in Spatial Reference 4326.
The ESRI-JSON to GeoJSON application is on Heroku for now as an experiment. I don’t have any permanent Node.js hosting. So if it gets a lot of traffic it may just disappear. Heroku is for quick testing, not production. I don’t really have funds to put this up for wide use. I will get the whole application up on Github, as soon as I figure out how from within Cloud9.
I would however like to share the code that does the conversion, which is shown below.
I’m sure this functionality could be incorporated using Server Object Extensions on ArcGIS Server, but it works so cleanly this way. Maybe some people will find this useful and could incorporate it into their workflows.
edit: Project is now available on github.