koopjs / koop-output-vector-tiles Goto Github PK

I am attempting to add the koop vector-tile endpoint as and ArcGIS Pro tile layer. I have tried the following:

• register koop vector tile layer as a tile layer in ArcGIS Online (AGOL) - success
• add koop AGOL tile layer to ArcGIS Pro - fail
• add koop vector tile layer to ArcGIS Pro with 'Add data from path' - fail

Both failures result in the same behavior. The layer is added to the Pro contents pane but with an invalid data source red exclamation. Upon inspecting the network traffic, I see Pro is attempting to load the following url:

.../VectorTileServer/resources/styles/?f=json

It fails with a 404. Is ArcGIS Pro supported?

I see vector tiles output uses an in-memory cache.

• Architecturally, is this the same caching layer as cache plugins?
• Are other caching options available beyond an in-memory cache?

Hi Team,

We are using koop.js to render hexagon polygons through vector tile services. Koop services are fetching the data from elasticsearch and sending back to UI (Angular + ArcGIS Javascript API) in the form of polygon geometry. We are observing that the hex tile layer is not clearing at times for some of the tiles. This is not a consistent issue w.r.t any place or data. Most of our users are facing this issue once in a while.

Details:
"@koopjs/provider-elasticsearch": "3.0.0",
"@koopjs/output-vector-tiles": "^2.1.1",
"@elastic/elasticsearch": "^7.13.0",
"dotenv": "^10.0.0",
"express": "4.16.4",
"koop": "^4.0.4",
"koop-output-geoservices": "^2.0.0"

Angular: 9
ArcGIS Javascript API: 4.20

Any help in resolving the issue is highly appreciated.

Is this still in development? I am looking at using Koop to add layers into AGOL using the feature server output from static geojson files. This seems like the simplest method for accomplishing this outside of loading the data into AGOL. If so I will add more issues. If not disregard.

If geojsonVT(data).getTile(z, x, y) is null then the plugin crashes as it calls vtpbf using a null tile. A simple fix would be something like the following:

  if (!tile) {
    res.writeHead(204, { 'Access-Control-Allow-Origin': '*' })
    return res.end()
  }

As the title, this plugin does not do anything if there is an authorisation plugin loaded.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

We are having compatibility issues with the output of the vector tiles
some mapping clients are rejecting as they are expecting v2 MapBox Spec and Koopjs is outputting v1