# Expanding template coverage for Alert Production

**URL:** <https://www.rubin.community/t/expanding-template-coverage-for-alert-production/12024>\
**Category:** Alerts & Brokers\
**Created:** [May 22, 2026, 4:07pm UTC](https://www.rubin.community/t/expanding-template-coverage-for-alert-production/12024 "2026-05-22T16:07:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebellm](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ebellm/32/771_2.png) [@ebellm](https://www.rubin.community/u/ebellm)\
**Post date:** [May 22, 2026, 4:07pm UTC](https://www.rubin.community/t/expanding-template-coverage-for-alert-production/12024/1 "2026-05-22T16:07:49Z")

</div>

On May 21 we deployed a significant expansion to the template coverage available to Alert Production. We selected the best-covered subset of the templates generated as part of the forthcoming Data Preview 2, increasing the total sky area which will produce alerts by more than a factor of ten depending on the band.

Current coverage is approximately

u: 53 sq. deg  
g: 211 sq. deg  
r: 905 sq. deg  
i 1444 sq. deg  
z: 1197 sq. deg  
y: 25 sq. deg

Current template coverage can be visualized [here](https://s3df.slac.stanford.edu/people/ebellm/template_coverage/template_coverage.html). More detailed programatic access to template coverage is in the works.

Further expansion of the template coverage using data from DP2 as well as pre-LSST survey observations is planned ([RTN-011.lsst.io](http://RTN-011.lsst.io)).

---

<div class="post-metadata">

**Author:** ![talister](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/talister/32/875_2.png) [@talister](https://www.rubin.community/u/talister)\
**Post date:** [June 11, 2026, 4:10pm UTC](https://www.rubin.community/t/expanding-template-coverage-for-alert-production/12024/3 "2026-06-11T16:10:03Z")

</div>

Hi @ebellm , nice to see the sky coverage expanding - world/sky domination soon… Are there any more details on the programmatic access ? An idea on what format the coverage maps would be available e.g. MOCs would help in developing user code to receive and make use of them.

Ta muchly,  
Tim

---

<div class="post-metadata">

**Author:** ![ebellm](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ebellm/32/771_2.png) [@ebellm](https://www.rubin.community/u/ebellm)\
**Post date:** [June 11, 2026, 5:58pm UTC](https://www.rubin.community/t/expanding-template-coverage-for-alert-production/12024/4 "2026-06-11T17:58:33Z")

</div>

Hi @talister, we are planning to provide MOCs for template coverage although I don’t have a timeline estimate at the moment.

---

<div class="post-metadata">

**Author:** ![talister](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/talister/32/875_2.png) [@talister](https://www.rubin.community/u/talister)\
**Post date:** [June 11, 2026, 8:56pm UTC](https://www.rubin.community/t/expanding-template-coverage-for-alert-production/12024/5 "2026-06-11T20:56:06Z")

</div>

Thanks @ebellm that’s perfect. Happy developing (or developer management)