nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Data Interoperability and GeoJSON

ToddFagin

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.

Data Interoperability extension available

Data Interoperability extension installed

Find more posts tagged with

Accepted answers

bharold

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.

All comments

ThomasColson

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.

bixb0012

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

ToddFagin

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

dewright_ca

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

bharold

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.

bharold

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.

ToddFagin

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.

bixb0012

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.

bharold

Hello Todd

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

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.