# Imagery provider attribution positioning

**URL:** <https://community.cesium.com/t/imagery-provider-attribution-positioning/385>\
**Category:** CesiumJS\
**Created:** [April 15, 2013, 4:44pm UTC](https://community.cesium.com/t/imagery-provider-attribution-positioning/385 "2013-04-15T16:44:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg\_Beatty](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/greg_beatty/32/3623_2.png) [@Greg\_Beatty](https://community.cesium.com/u/Greg_Beatty)\
**Post date:** [April 15, 2013, 4:44pm UTC](https://community.cesium.com/t/imagery-provider-attribution-positioning/385/1 "2013-04-15T16:44:57Z")

</div>

I see that the imagery provider attribution positioning is currently set via CentralBody.logoOffset. All other Cesium positioning seems to be done via CSS. Why does this still have to be set explicitly in code?

---

<div class="post-metadata">

**Author:** ![Ed\_Mackey](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/ed_mackey/32/2226_2.png) [@Ed\_Mackey](https://community.cesium.com/u/Ed_Mackey)\
**Post date:** [April 15, 2013, 5:04pm UTC](https://community.cesium.com/t/imagery-provider-attribution-positioning/385/2 "2013-04-15T17:04:59Z")

</div>

Hi Greg,

All of the other positioning is widget-level positioning. Imagery credits are for the imagery layer, and we render them into the canvas itself rather than depending on a wrapper widget to composite them via DOM elements. This helps make sure the proper credits appear even in apps that don’t use the widget, and appear in canvas.toDataUrl screenshots, etc. But it means that CSS doesn’t affect their position.

–Ed.

---

<div class="post-metadata">

**Author:** ![Greg\_Beatty](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/greg_beatty/32/3623_2.png) [@Greg\_Beatty](https://community.cesium.com/u/Greg_Beatty)\
**Post date:** [April 15, 2013, 5:15pm UTC](https://community.cesium.com/t/imagery-provider-attribution-positioning/385/3 "2013-04-15T17:15:28Z")

</div>

I guess this makes sense. It does, however, make positioning difficult in larger applications. For example, aligning attribution with the right side of the screen, or relative to other widgets/icons/etc that appear in applications.

---

<div class="post-metadata">

**Author:** ![Matt\_Amato](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/matt_amato/32/1993_2.png) [@Matt\_Amato](https://community.cesium.com/u/Matt_Amato)\
**Post date:** [April 15, 2013, 5:17pm UTC](https://community.cesium.com/t/imagery-provider-attribution-positioning/385/4 "2013-04-15T17:17:37Z")

</div>

I’m pretty sure we all agree that ultimately logo positioning should be CSS aware, no matter how it’s ultimately rendered. We even have a Google SoC project about it. It’s incredibly difficult to manage the logo the way it is now. If this is something you’re interested in working on, we’d be happy to have the help. It’s a fairly isolated project, which makes it great as a spare-time style thing.