1.7.0

It's the end of the year, but never fear, v1.7 of the CLI is here.

✨🌟💫 NEW 💫🌟✨

🎯🎯🎯 Targeted Sharing 🎯🎯🎯

You can now request access to another user's space -- they send you the space ID, you use the interactive here xyz sharing command to request access, and they use it to grant you access (or not). You can also use it to list the spaces you've requested access to, the spaces you're sharing with others, as well as cancelling the request if necessary.

This method is more precise and, well, targeted, than the existing shared parameter which when set to true, allowed anyone with a HERE account to see that space.

Target Sharing can also be controlled in the Data Hub Console.

🏚🏘🏡 Delaunay neighbours 🏡🏘🏚

You can now generate a list of a point's neighbours in a space, in addition to generating the Delaunay polygons themselves.

here xyz gis spaceID --delaunay --neighbours

Note that this will add a new property, xyz_delaunay_neighbours, to the points in the source space containing an array of the neighbouring IDs.

⬣⬡⬢ Batch h3 hexbins ⬣⬡⬢

The client-side batch hexbin command can now create h3 hexbins and their centroids. (These are written to a second space, as opposed to being generated on-the-fly like Data Hub's server-side hexbins). This is useful for saving a high-resolution h3 hexbin grid of a space with a very large number of features to be viewed at low zoom levels (effectively simulating a heatmap).

here xyz hexbin spaceID --h3 --resolution | -z

You can specify one or more h3 resolution levels using either comma-separated values, or a range delineated by a dash.

For your convenience, we also let you choose a slippy map zoom level for h3 hexbin creation -- this uses the same table as Data Hub's server-side hexbins, giving you reasonably-sized h3 hexbins for a given map zoom level if you're not used to thinking in terms of h3 resolutions levels yet.

We also added the ability to generate hexbins from spaces with lines as well as points, which helps aggregate and visualize datasets with lots of short, choppy road segments.

Note that h3 hexbin density increases by a factor of 7, so you can quickly end up with… a lot of hexbins. For now you may need to give node more memory for dense, national datasets. For context, we have found that h3 resolution of 8 or 9 works well for visualizing the density of the German road network.

👩‍💻 💻 👨‍💻 Point at self-hosted servers 🖥 💻 🖥

You can now use the CLI with a self-hosted version of Data Hub running locally or on a server. (You knew you could run Data Hub locally using Docker, right?) Just specify the URL, localhost or otherwise, where it's running:

here configure server [url]

🛠🔨🗜 Fixed ⚙️🔩⛏

Better token management for spatial search results

In v1.6, we tightened the scope of the tokens we generate. This made it challenging to view the results of spatial searches of one space that pulled a feature from a second space. We now generate a token that grants read access to both spaces (similar to how we do it for the upstream spaces used in Virtual Spaces).

Ubuntu node environment fixes

Some Ubuntu users had reported node environment errors following a CLI upgrade. This should be behaving better now.