-
These parameters only work for the FeatureServer interface, and are done in post-processing, after the database query. Any reason they're not incorporated into the initial query? The logic for this ap…
-
In the JSON returned for the /FeatureServer and /FeatureServer/0 requests, it would be nice to programatically generate some Dataset Description text that says:
- where the data came from
- what the l…
-
I am looking to make a change to the koop provider to do a better job of handling field types. I am logging field types to the info doc. I want to get access to the info doc in FeatureService.js but…
sirws updated
7 years ago
-
### Concept
As a user, I see faster performance on the following queries:
1. FeatureServer
2. FeatureServer/0
3. FeatureServer/query?where=1=1&returnCountOnly=true
4. FeatureServer/query?where=1=1&re…
-
For geojson exports (and other formats) of large datasets, I think we may want to consider reducing decimal degree precision to reduce filesize. For complex polygon layers, the geometry section of the…
-
Hi,
is it possible with koop to run a query on a gist geojson object?
Something like http://koop..../gist/6178185/query?where=ZIP=60647 ?
Thank you
-
download of csv was observed to be different on two different downloads, but should have been the same
On Friday, August 1, I did a download of the dataset as a CSV from the page http://jeremyadhocte…
-
Hi
this repo is pinned at https://github.com/koopjs page, but it is deprecated.
What about switching the pin to the `koop-provider`?
Regards
Arnaud
-
I get the following error on a basic koop install:
```
λ node .\index.js
warn: No cache configured, defaulting to local in-memory cache. No data will be cached across server sessions.
F:\github\koopt…
-
Hey Casey! Just wanted to make sure you were aware of [koop](http://koopjs.github.io/), an open source product Esri's built that has some parallels to this project. It pulls in data from a variety of …