archesproject / arches-koop Goto Github PK

resourceinstanceid, tileid and nodeid properties get excluded by the property map, which causes the esri addin edit actions to fail.

As it stands, the koop services requests all data from the Arches GeoJSON api and can lead to long wait times or timeouts when requesting data from models with a lot of geometries.

The service needs to be able to pass more of the geoservice query parameters to the Arches GeoJSON api so that the data can be streamed back as required.

If no resources are present the model then the koop service does not provide information to ArcPro about the schema of the service. This makes preparing layer symbology in advance difficult.

Currently the geojson endpoint returns with only the properties that is not Null and the Koop will create a schema based on the first one passing.
So, even if the service is supposed to have 5 columns, if the first record happens to have 2 columns all other record that has more the 2 columns seems to have some issues (including of not displaying the attribute values though geometry shows up).

Also, some of geometry collection have {nodeId} inside geojson as a property which makes things more complicated.

So, it would be great if the Koop service can define schema before the 1st actual record or ways to clean up the incoming geojson.

Issue description - We are getting issues where multiple cards are saved against a resource. When any resource of a certain resource type has multiple cards brought back by a field configuration, e.g., multiple descriptions (full/summary), an error message displays when trying to view the attribute table in ArcGIS Pro, and you cannot see attributes for any of the geometries:

Testing using ArcGIS Pro 2.8.

We need to consider what a recommended production architecture for running this application will look like. It may be nice to create a Docker based solution that could easily integrate with the Arches Docker composition.

From the SOW:
Our software development will start by transforming Arches data into an esri GeoService. We will use Koop (https://github.com/koopjs/koop) and Arches’ elastic search engine to support on-the-fly transformation of Arches data into the appropriate GeoService for ArcGIS Pro.

Our approach will allow developers to create an “Arches Data Provider” that publishes esri GeoServices. The Arches Data Provider can be configured on a model-by-model basis so that developers can specify the exact Arches fields to expose in the GeoService. Once configured, the Arches Data Provider will publish esri GeoServices that can be accessed by ArcGIS Pro.

This development effort will extend the Arches Platform code base, making it possible for all Arches users to publish data in real-time in a native esri proprietary format. Esri users will then be able to access and display Arches data (read-only) within ArcGIS Pro and esri’s GIS server products.

We will need to be able to access data in Arches as an authenticated user in order to access restricted business data.

One possibility would be to create a Koop authorization plugin that would use Arches authentication API on the backend