# Selecting projection for comparison with satellite data

**URL:** <https://openradar.discourse.group/t/selecting-projection-for-comparison-with-satellite-data/372>\
**Category:** General\
**Created:** [December 12, 2023, 9:02am UTC](https://openradar.discourse.group/t/selecting-projection-for-comparison-with-satellite-data/372 "2023-12-12T09:02:40Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![atmoboran](https://avatars.discourse-cdn.com/v4/letter/a/ecccb3/32.png) [@atmoboran](https://openradar.discourse.group/u/atmoboran)\
**Post date:** [December 12, 2023, 2:50pm UTC](https://openradar.discourse.group/t/selecting-projection-for-comparison-with-satellite-data/372/6 "2023-12-12T14:50:27Z")

</div>

So do I understand correctly, that the interpolation method you suggest in ([Georeferencing single sweep data and converting to numpy array - #2 by kmuehlbauer](https://openradar.discourse.group/t/georeferencing-single-sweep-data-and-converting-to-numpy-array/353/2)) is only “totally” correct if the data is on an equal area projection?  
And 32632 is basically close enough to equal area?

---

_[View the full topic](https://openradar.discourse.group/t/selecting-projection-for-comparison-with-satellite-data/372)._