feature_merge
Merge features in GFF files
Installation:
pip install feature-merge
or:
conda install feature_merge
or:
git clone https://github.com/brinkmanlab/feature_merge.git cd feature_merge ./setup.py install
Usage:
feature_merge [-i] [-e] [-x] [-s] [-v] [-m merge|append|error|skip|replace] [-f type[,type..]].. <input1> [<input_n>..]
Accepts GFF or GTF format.
-v Print version and exit
-f Comma seperated types of features to merge. Must be terms or accessions from the SOFA sequence ontology, \"ALL\", or \"NONE\". (Can be provided more than once to specify multiple merge groups)
-i Ignore strand, merge feature regardless of strand
-s Ignore sequence id, merge feature regardless of sequence id
-x Only merge features with identical coordinates
-t Threshold distance between features to merge
-e Exclude component features from output
-m Merge strategy used to deal with id collisions between input files.
merge: attributes of all features with the same primary key will be merged
append: entry will have a unique, autoincremented primary key assigned to it (default)
error: exception will be raised. This means you will have to edit the file yourself to fix the duplicated IDs
skip: ignore duplicates, emitting a warning
replace: keep last duplicate
See CONTRIBUTING.rst for information on contributing to this repo.
Metadata
Release files for feature-merge 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| feature_merge-1.3.0.tar.gz | 13.2 kB | Without provenance | Details |
Release files / feature_merge-1.3.0.tar.gz
| Download URL | feature_merge-1.3.0.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
164a5e90016aefa0d0f6ea6b2187f5a8eb97ec792ed1aa4df9ab7876fd4c40fe
|
|
BLAKE2b-256 checksum How to use checksums |
6142d5462e83b2fecfb14b97d1d7e59f47e89218e2b322db5d3fd25282e34802
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.54.0 CPython/3.8.6
|
Security for feature-merge 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.