jw3 / greyhound-s2i

Greyhound and Entwine automated on OpenShift v3

Greyhound Point Cloud s2i

Goal to automate the building and serving of point cloud through Greyhound by using configuration as code in git repo.

There is a repo with sample sources here https://github.com/jw3/example-pointcloud-source

To serve that example data in OpenShift do a

#! oc new-app jwiii/greyhound-s2i~https://github.com/jw3/example-lidar-sources.git --name=greyhound

See

• https://github.com/hobu/greyhound
• https://github.com/connormanning/entwine
• https://vimeo.com/245073446

Sample Data

• https://entwine.io/sample-data/red-rocks.laz

greyhound-s2i's Issues

Volume for entwine index

For very large pointclouds the build could put the entwine index in a volume and then deploy mounting that volume.

Support preserving the entwine index

Ensure that when specified the build appends to the previous entwine index.

• implement save-artifacts

Explain how sources are added

Add details to readme

• source file name
• entries in source file

example https://github.com/jw3/example-lidar-sources

Add instructions to readme

Specify bounds

https://github.com/connormanning/entwine/blob/master/doc/configuration.md#bounds

Total bounds for all points to be index. These bounds are final, in that they may not be expanded later after indexing has begun. Typically this field does not need to be supplied as it will be inferred from the data itself. This field is specified as an array of the format [xmin, ymin, zmin, xmax, ymax, zmax].

{ "bounds": [0, 500, 30, 800, 1300, 50] }