topic Re: Data Interoperability and GeoJSON in ArcGIS Pro Questions

Data Interoperability and GeoJSON

ToddFagin — Fri, 09 Aug 2019 18:54:24 GMT

I am running ArcGIS Pro 2.4.1 and have the Data Interoperability extension installed. However, when I try to add a GeoJSON file, it simply is not reading it (doesn't show in the add data dialog box). I also have the Data Interoperability extension for ArcGIS Desktop and I am having no problem reading the same file (I can also read it with QGIS).

I have uninstalled and re-installed the extension several times, still no avail. I would really like to resolve this issue.

Re: Data Interoperability and GeoJSON

BruceHarold — Fri, 09 Aug 2019 19:05:33 GMT

Hello Todd

ArcGIS Data Interoperability for Pro does not support direct read of non-native formats like ArcMap does.

The GeoJSON file has to be converted to a recognized format like Geodatabase. The core tool JSON to Features can do this, or you can use Data Interoperability Quick Import or a Spatial ETL tool or interactively by starting Workbench from the Analysis ribbon.

Re: Data Interoperability and GeoJSON

JoshuaBixby — Fri, 09 Aug 2019 19:18:30 GMT

Bruce, this goes against Esri's own open standards marketing hype: Open Standards | Supporting Your Data Formats, Metadata & Services Standards

Esri has a long-standing commitment to standards and interoperability. That’s why ArcGIS supports more than 100 established standards including data formats, metadata, and services.

Maybe that should read "Esri has a long-standing commitment to backing away from standards and interoperability." Having to convert the GeoJSON to a native Esri file format to consume in Pro is neither supporting the standard nor the spirit of interoperability.

Re: Data Interoperability and GeoJSON

ToddFagin — Fri, 09 Aug 2019 20:19:57 GMT

While I appreciate the reply, this begs the question of what, then, is the point of the Data Interoperability extension? This is so maddening. There are times I cannot help but think Esri really doesn't want people to adopt ArcGIS Pro.

Re: Data Interoperability and GeoJSON

BruceHarold — Fri, 09 Aug 2019 20:27:46 GMT

Hi Joshua, this is one of those cases people might not thank us for introducing a weakly typed read-only layer. It would have to be like CAD, split by geometry class contained in each file and scanned for each file to figure out an attribute schema, which might change file to file. Personally, with Data Interoperability available, if i had to deal with consistent GeoJSON from some supplier on a regular basis I would create a custom format in Workbench (note to self, needs better doc) to output a designed and repeatable attribute schema every time and use Quick Import to bring the files in.

Re: Data Interoperability and GeoJSON

BruceHarold — Fri, 09 Aug 2019 20:34:59 GMT

Todd, it is our ETL solution, here are some links to get you started:

Open Platform, Standards and Interoperability

One more point: We are seeing less file-based formats in use (barring CAD, which we support in core), and in the case of GeoJSON, the source is often a URL, which the core JSON to Features tool can accept as an input provided the URL triggers a download.

Re: Data Interoperability and GeoJSON

DEWright_CA — Fri, 09 Aug 2019 21:03:21 GMT

Bruce Harold‌ why would ESRI decide to disable/limit Data-Interop reading GeoJSON? I know Full FME does this without question; so this was a ESRI choice.

I'm just curious of that thought process...

Re: Data Interoperability and GeoJSON

BruceHarold — Fri, 09 Aug 2019 21:08:44 GMT

David we have the same GeoJSON support as FME in Data Interoperability, meaning in the Workbench application. Have you found any issues?

Re: Data Interoperability and GeoJSON

DEWright_CA — Fri, 09 Aug 2019 21:13:24 GMT

No I was asking as a extension of his question; we actually run Full FME Desktop and Server. We still have a license for Data-Interop; but that is used by other folks that don't need the full power and flexibility of FME.

Re: Data Interoperability and GeoJSON

BruceHarold — Fri, 09 Aug 2019 21:25:11 GMT

OK then that's a good question. Historically we didn't have all of FME's functionality, like raster/imagery processing and writing, but a couple of releases ago we decided to include as much of FME as possible, so now (Pro 2.4, 10.7) you'll find very few formats or transformers different - basically things we cannot license. In one area - DBMS connectivity - Data Interoperability includes connectivity you'll find only in individual targeted FME editions. Another area we differ is Data Interoperability does not publish to FME Server from within Data Interoperability Workbench - if you would like that we can take a look at it. You can use a Data Interpoerability workspace with FME Server, just not from Workbench we ship.

Re: Data Interoperability and GeoJSON

ToddFagin — Fri, 09 Aug 2019 21:57:16 GMT

Bruce,

While it might be true that more individuals are moving away from file-based formats, they are still used extensively. For instance, there are occasions when I will have a GeoJSON file and all I need to do is open and inspect it (there are a variety of reasons for this--one of which is to ensure the GeoJSON file I created is working correctly. For instance, I will get requests for GeoJSON files from time to time). In such an instance, converting the file to an Esri-compatible format is self-defeating. Fortunately, I can just use ArcMap or even QGIS for this, though my desire would be really to stay within one environment at a time (and, sadly, the Pro conversion tool, which projects to WGS 84 and supports aliases, is superior to ArcGIS Desktop's Feature to JSON tool).

Todd

Re: Data Interoperability and GeoJSON

JoshuaBixby — Sat, 10 Aug 2019 01:47:55 GMT

Hi Joshua, this is one of those cases people might not thank us for introducing a weakly typed read-only layer.

I disagree, people might not exalt Esri for introducing this functionality, but I highly doubt people would be saying, "I can't believe they implemented a weakly-typed read-only layer for GeoJSON support."

My beef on this issue isn't with Data Interoperability but with the core product. If ArcGIS Online can create a layer directly from a saved GeoJSON, why can't ArcGIS Pro; if QGIS can do it, why not ArcGIS Pro; etc....

Re: Data Interoperability and GeoJSON

BruceHarold — Mon, 12 Aug 2019 13:35:39 GMT

Todd. how about this: create a shortcut for the Data Inspector app at C:\Program Files\ArcGIS\Data Interoperability for ArcGIS Pro\fmedatainspector.exe and open it whenever you want to, well, inspect any data. You can browse to the data or drag files into the app. Don't forget to set your background map in the FME Options area. We're thinking of adding a control in the Analysis ribbon alongside the Workbench control to start Data Inspector. Once you are done visualizing the data you can even Save As (say) File Geodatabase, just like doing a Quick Import.

Anyone else looking at this thread, do you like the idea of surfacing Data Inspector to the ribbon?

Re: Data Interoperability and GeoJSON

ToddFagin — Mon, 12 Aug 2019 14:06:33 GMT

I have tested this and it works. I don't find it to be the optimal solution, but it is better than nothing. I do, however, very much like the ribbon idea so that I do not have to launch the data inspector from a shortcut or from the directory.

Re: Data Interoperability and GeoJSON

ThomasColson — Mon, 12 Aug 2019 14:16:05 GMT

https://community.esri.com/ideas/13080-arcgis-pro-direct-geojson-support

You'll note in the original text of the idea, "... load GeoJSON Features directly into a ArcGIS Pro Project without converting it.". No mention of having to (buy and) install another add on (interop or FME) to utilize the format. Leaflet, QGIS, Boundless Desktop, CartoDB, Mapbox, all support native reading of GeoJSON.