Extract track data from "search by region" feature on ENCODE

Question

[AlienPumpkinPie]

Hi all,

I'm very new here so if I am being ignorant please kindly correct me :)

I would like to extract the track information from the "search by region" feature of the ENCODE site (https://www.encodeproject.org/region-search/). This feature allows you to search for a chromosomal region or infer the chromosomal region for you if you searched for a gene.

And let's say I am searching for a region: chr8:79254007-79386806 in the search box, I will get a page looks like this:

If I understand right, the website will grep all the accession track files that are relevant in the website, and visualise for you here, addressing the binding sites or peaks from all theses data. My reasoning is that, the fact that I can see this visualisation means there are data behind each track being gathered. I'm not sure if I can automate this on my computer using ENCODE REST API or any other wacky tools so that I don't have to navigate through the website manually since there are a lot of track being visualised here. Essentially, what I would like to do on my computer is:

1) I can search using the coordinate, specifying my region of interest on human chromosome; 2) The ENCODE returns me with a list of all track that's relevant in this region; 3) I download the segmented file data exactly at this coordinate to my computer (sites and peaks), instead of hundreds to thousands of files that are gigabytes big.

I wonder if this is achievable, since I didn't see any introduction of such feature from the API guide page. Did I miss anything here? What should I do? Thank you very much for your time!

Best Wishes, APP

[GenoMax]

Examples of the API don't show any region based examples. Not saying that is not possible but it would be an obvious example that would have been included if possible. See --> https://www.encodeproject.org/help/rest-api/

All ENCODE data is supposed to be publicly available https://registry.opendata.aws/encode-project/ though that public bucket mentioned is coming up with an error on aws ls.

[AlienPumpkinPie]

Thank you for your reply! Yeah I thought the same. It feels weird to me that this is not an obvious feature.