Thanks for the hint. Yes it is used for further processing, so this should be redone.

Firstly I want to put satellite data (Meteosat) over it. And the satellite data is in lat lon, but I can also download it in other projections.

So I thought of maybe using the Lambert cylindrical equal-area projection (EPSG:9835), but somehow osr, doesn’t recognize it.

proj = osr.SpatialReference()

proj.ImportFromEPSG(9835)

→ proj stays empty

Do you have suggestions for a crs, that makes sense to use here?

@atmoboran

I’m no expert on projections, so I’d appreciate any suggestions here.

AFAICT EPSG:9835 is just referring to the projection method, but is no projection. You would need to pick some projection which best suits your downstream use cases. A search for `equal area`

brought up several projections including these two **EPSG:3035** and **EPSG:19986**.

HTH,

Kai

P.S. We can swap this projection question out to a new topic if you like.

Why is 32636 always used in the recipes? Is this one equal-area?

It’s actually **EPSG:32632** (UTM Zone 32N). It covers most of Germany. And you are right it’s not really equal area but the distorsions are minimized compared to normal tranverse mercator projection.

So do I understand correctly, that the interpolation method you suggest in (Georeferencing single sweep data and converting to numpy array - #2 by kmuehlbauer) is only “totally” correct if the data is on an equal area projection?

And 32632 is basically close enough to equal area?

Nothing is “totally” correct, as Earth is no sphere, unfortunately. I’m using the UTM Zone32N in that example as it covers Germany nicely and it’s used by several agencies.

Sorry, but my knowledge in projections is somewhat limited.