Martin Raspaud

@tmlunde thanks for reporting this. The problem is probably that `geosSettings[sat]['meta'][10.8].area` is `None`...

ok, it's actually the opposite, `geosSettings[sat]['meta'].area` is `None`, which is quite logical since there could be channels with different areas in the scene object. A workaround is to do ```...

I will mark this issue as a feature request for mpop 2.0.

@jshn9515 I think the angles are computed if not to be found in the data. The result should not be impacted significantly.

yes, we need to do that. For the benchmarking there, we already have some data locally too.

No I haven't checked yet. It would great if you could check some of the examples, thanks

Thanks a lot for reaching to us about this issue! I am a little familiar with S1A data, and I am curious as to whether the longitudes and latitudes you...

No, this should be fine. What I mean is that every tie point has an associated line and column number assigned to it. The way you build the grid, you...

By the way, if you are reading Sentinel 1 GRD data, I can recommend the satpy package we are developing too. See an example usage here: https://www.kaggle.com/martinraspaud/sar-ice-imagery

If you are using H5 data then it's probably not the same than I am using. Could you produce the line and column numbers for each lon lat points so...