Eugene Cheipesh

Sorry for the word dumb, but this is the setup for our thinking and experiments that @pomadchin has been running. It seems to do something good. **TLDR** is the its...

- **Data**: HRPD USA is on `s3://azavea-humdata/facebook/hrpd/` (requester pays) - **Process**: Summaries were generated with https://github.com/echeipesh/geotrellis-hrpd - **Result**: [us-county-hrpd-v1.csv](https://gist.github.com/echeipesh/78c324e1faac937bd9f96ff65626600d/raw/f38866659cdbda3c8f46e533d718ab4c8fa6a023/us-county-hrpd-v1.csv) - **Verification**: [notebook](https://gist.github.com/echeipesh/78c324e1faac937bd9f96ff65626600d#file-validate-hdpr-ipynb) Verification is very light, I poked around lightly...

Would it be more helpful to have an easy way to standup an instance of a given service from console for this kind of thing? For instance: ```scala val service...

I agree with all of that, lets keep this issue specifically for that conf cleanup and breakup work.

Current implementation of STAC in this project requires the user to do the job of assembling the asset bands and defining a MAML expression to either render or return them...

Adding a bit of context here. This issue came up again and @pomadchin and I discussed the idea of having `Histogram` be a MAML expression. This would allow the interpreter...

I started by creating a sample STAC catalog we can train from to think through the data formatting issues. See https://gist.github.com/echeipesh/2d2a18b59d634ecbfd97b7d32bba6164 Note that `image-` and `label-` prefix in file names...

@pomadchin It'd be nice to get 3.6.3 out with spark 3.2.0 and then 3.7.0 with CES3 and spark 3.2.1. That'd allow this to sync with frameless 0.11 and later with...

I've been looking at the python side of the project enough to form strong enough opinions of it. I think it's actually going to need some work and it doesn't...

Outcome: Test the PDAL created no-cull option to see the effect on degenerate case.