Discussion: Histogram Matching Demo, Client-side JS implementation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 97
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
First wanted to say thanks for this great rio-hist utility. I've been tempted to compute Histogram Matching client-side for a specific project for quite some time and finally took the leap.
This ended up with the below demo app histogram-matching-js.
Runs in 20ms on FHD images. If source is geotiff, geotiffjs is used to copy all its geoMetadata.
Lets you interactively tune:
source and targetinput raster images via File inputsmaxMpxto downsample input source/target Uint8 arrays for faster histogram computationcolor_space and bandsafter having a look at https://github.com/mapbox/rio-hist/issues/3 and how your CLI offers optional tweaking of these paramsbinCount: marginal compute time enhancement since interp on 256-length arrays is already fast with regards to extracting the RGB constituents from the input raster arrays
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked histogram-matching-js demo, its use of geotiffjs, and the parameter discussion in issue #3. The issue does not identify a repository file or a requested change; clarify whether maintainers want an integrated client-side implementation, documentation, or only a reference to the demo before defining what done means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100