Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split a gff3 file based on specified coordinates #73

Closed
sanyalab opened this issue Sep 30, 2020 · 2 comments
Closed

Split a gff3 file based on specified coordinates #73

sanyalab opened this issue Sep 30, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@sanyalab
Copy link

Hi Jacques,

I would like to suggest implementation of a module in AGAT to subset a gff3 file based on a chromosome and coordinate range/ranges. There is one such implementation in gffread. But the problem is that it will extract between a range only if there are genes/transcripts within that range. It will create an empty file if extraction is from a repeat rich region for example. Using an awk script where you specify coordinate ranges, will get you the contents. But the boundaries have the risk of being incomplete, if the coordinates lie in the middle of a level1 feature. In this case I would like to be inclusive and extend the coordinate at the boundaries to included the closest level 1 feature.

Thanks for the help

Best Regards
Abhijit

@Juke34 Juke34 added the enhancement New feature or request label Sep 30, 2020
@Juke34 Juke34 closed this as completed in 9c2b59a Mar 25, 2021
@ferrojm
Copy link

ferrojm commented Sep 17, 2024

Hi!

Has this been implemented in newer versions of AGAT (i.e., to extract by range or coordinates?)

Thanks!
Juan

@Juke34
Copy link
Collaborator

Juke34 commented Sep 17, 2024

Have a look here https://nbisweden.github.io/AGAT/tools/agat_sp_filter_record_by_coordinates/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants