# Wget functionality for DP2 and future data releases

**URL:** <https://www.rubin.community/t/wget-functionality-for-dp2-and-future-data-releases/12836>\
**Category:** Support\
**Tags:** dp2\
**Created:** [October 16, 2026, 2:03pm UTC](https://www.rubin.community/t/wget-functionality-for-dp2-and-future-data-releases/12836 "2026-10-16T14:03:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rance](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/rance/32/2599_2.png) [@Rance](https://www.rubin.community/u/Rance)\
**Post date:** [October 16, 2026, 2:03pm UTC](https://www.rubin.community/t/wget-functionality-for-dp2-and-future-data-releases/12836/1 "2026-10-16T14:03:16Z")

</div>

Is there already or will there be the ability to download Rubin data that is still in internal release via a wget command?

I need to have a copy of the Rubin data (coadds and object catalogs) moved over to a non-IDAC data facility where only Rubin members will have access. Making a bulk data transfer is fine for DP1 but DP2 and later releases are too large for this to be considered. A wget option could work with a “on-the-fly” data download as needed. Other considerations are welcomed.

---

<div class="post-metadata">

**Author:** ![MelissaGraham](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/melissagraham/32/2549_2.png) [@MelissaGraham](https://www.rubin.community/u/MelissaGraham)\
**Post date:** [October 16, 2026, 5:10pm UTC](https://www.rubin.community/t/wget-functionality-for-dp2-and-future-data-releases/12836/2 "2026-10-16T17:10:16Z")

</div>

Hi @Rance, thanks for posting this question. As Forum moderator I’ve moved it into the Support category to ensure it gets a response.

The implementation of a bulk download service for Rubin data remains in development, and the exact functionality to be determined – but it is planned and will exist. A bit more information can be found in the technical note [SQR-119](https://sqr-119.lsst.io/), “Metrics-driven user restriction for the RSP”, which is focused on scaleable, sustainable design for such a service for the very large future Rubin datasets.

I think this answers your main question, so I’m going to mark this reply post as the solution. But please feel free to post new topics for new or related questions anytime.

---

<div class="post-metadata">

**Author:** ![Rance](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/rance/32/2599_2.png) [@Rance](https://www.rubin.community/u/Rance)\
**Post date:** [October 19, 2026, 9:34am UTC](https://www.rubin.community/t/wget-functionality-for-dp2-and-future-data-releases/12836/3 "2026-10-19T09:34:30Z")

</div>

Thank you very much @MelissaGraham! This is great to see. For the tracking of the user usage it would be really cool if the tool is some how also user accessible so that they can track how much they are downloading and apply their own throttle. But anyways, if I wanted to keep up to date on the development of this and the potential bulk download feature, is there a channel to follow or will this document just occasionally be updated?

---

<div class="post-metadata">

**Author:** ![MelissaGraham](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/melissagraham/32/2549_2.png) [@MelissaGraham](https://www.rubin.community/u/MelissaGraham)\
**Post date:** [October 19, 2026, 4:17pm UTC](https://www.rubin.community/t/wget-functionality-for-dp2-and-future-data-releases/12836/4 "2026-10-19T16:17:52Z")

</div>

Hi @Rance, the best way to keep up-to-date with new RSP features is to check this page, which is updated with each data release and each major change to RSP functionality: [Updates — Rubin Science Platform](https://rsp.lsst.io/updates/index.html). There are also typically announcements in the [Data Services - Rubin Observatory LSST Community forum](https://www.rubin.community/c/news/data-services/64) category for major changes and updates as well. And always, new Support topics are welcome if you ever can’t find what you’re looking for.
