Bryce Frank
Bryce Frank
Any interest in making a [light variant](https://atom.io/themes/monokai-light)?
Right now metrics are computed using all points, with the exception of cover metrics. Would be useful to allow the user to define a global height break.
``` ====================================================================== ERROR: test_write (pyfortest.test_pyfor.LAZCloudTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/travis/build/brycefrank/pyfor/pyfortest/test_pyfor.py", line 171, in setUp self.test_cloud = cloud.Cloud(test_laz) File "/home/travis/build/brycefrank/pyfor/pyfor/cloud.py", line 88, in __init__ las = laspy.file.File(self.filepath) File...
https://github.com/brycefrank/pyfor/blob/1700e58040b91c5f6604239886ca8abe27c03e90/pyfor/rasterizer.py#L188 It would be useful and perhaps cleaner to round the bbox to the nearest raster-compatible extent if the user did not supply one. The user should be warned if...
Currently, the pyfor conda-forge feedstock does not run the testing suite, as there were some issues with file locations. These errors should be resolved and testing for the master branch...
Due to the dependency stack, installation of the environment on travis is slow, it should be possible to cache arbitrary directories via `.travis.yml` for a speed up e.g. : https://github.com/theochem/qcgrids/issues/8
I am wondering if there is any interest in expanding the functionality of `laspy` to take advantage of spatial indexing, specifically the `.lax` files generated by `LASlib`?
`install_models` will not scale well, especially for automated testing done in our GitHub actions. Instead, we should seek to optimize `install_models` such that only newly updated publication or parameter files...
`replace_pub_models()` currently deletes and re-writes models regardless of whether or not any information about them has changed. Upserting would be more efficient