-
Connector code is skipping objectIds parameter while aggregation. Hence it returns the count for all documents in a layer.
URL : /marklogic/GDeltGKG/FeatureServer/0/query?objectIds=56577%2C56576&re…
-
The current implementation requires the column to be selected from the view in order to be in scope for the Optic plan but there is no way to select it only to extract the geometry an not include it i…
-
Opening attribute table creates 500 internal server error. Postman get for the query
FeatureServer/0/query?f=json&returnIdsOnly=true&where=(DT_FIELD > timestamp '2023-01-02 05:59:59') AND (1=1)&retur…
-
DWR staff would like to be able to access roadkill data in AGOL/Pro/etc. Feature services seem to be the best end goal.
The plan is to give [Koop](http://koopjs.github.io/) + https://github.com/donei…
-
The Koop framework from ESRI appears to understand a geometryType of "LineString" but the koop-provider-marklogic project only has test cases for geometryType="Polygon" and geometryType="Point". We n…
-
Load koop-provider-marklogic project with npm since marklogic-geo-data-services has removed several dependencies.
-
Esri tools sometimes make queries that have values exceeding the extents of WGS-84. Implement functions to handle these queries gracefully.
-
In support of exporting data to CSV, rather than running the optic plan, return the output of Plan.export(), which can then be passed into the v1/rows MarkLogic REST API call.
A complication is tha…
-
Koop currently authenticates to MarkLogic as a single user and the feature service exposed by Koop does not have authentication enabled.
Investigate if/how to enable authentication for feature serv…
-
koop-auth-direct-file references Koop ^3.7.2, so when using 4.x, this dependency won't resolve.
I suppose this can be fixed by simply altering the version in [package.json](https://github.com/koop…