Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map overlay problem #910

Open
yvesclousier opened this issue Jan 21, 2024 · 5 comments
Open

Map overlay problem #910

yvesclousier opened this issue Jan 21, 2024 · 5 comments

Comments

@yvesclousier
Copy link

Hello everyone. Great job with this app.
Since the last version I noticed that the base map does not correspond perfectly with the images received. do you have an idea ?
See the images here:

http://15.188.192.50/captures?page_no=1

Looking online, I realized that I wasn't the only one with the same problem. thanking you in advance for your return.

@Sasszem
Copy link
Contributor

Sasszem commented Feb 24, 2024

Sadly I could not open the link. Is the problem a small offset between the overlaid map and the actuall terrain?

See this picture:
METEOR-M2-3-20240223-091331-spread_221
(The offset is quite noticable at the island above Berlin)

@yvesclousier
Copy link
Author

yvesclousier commented Feb 25, 2024

Hi,
Sorry for the link, you can check here https://clousier.com/captures/listImages?pass_id=424
All Noaa captures processed by WxtoImg seem to have this offset.
On the other hand, the reception of Meteor with processing by Satdump does not show this offset.
The server is synchronized well on an NTP server.
Capture1

@Sasszem
Copy link
Contributor

Sasszem commented Feb 25, 2024

In our case, the problem seems to only happen with Meteor, not with NOAA. Even there, it's inconsistent - we just switched on Meteor on friday, but the images on sunday are lined up correctly.

EDIT:
Seems like the false-colored images somehow hide this fact - I see many misaligned landmasses on images with Enhancement: ZA or Enhancement: HVCT. Don's look at Enhancement: MCIR - it hides the problems!

I'm not sure but it seems like our offset problem with Meteor just vanished.

It also seems like both of our ground stations have a similar offset. I wonder if that's just a coincidence, or something else.

I noticed that you also mentioned using RTL-TCP for reception, I wonder if that makes any difference - it should not imho.

@MihajloPi
Copy link
Collaborator

Thanks for reporting the issue! This should have been solved by now so please try updating your OS and the RN2 and run the install script again. In settings.yml file now there is a variable to tune map offsets for NOAA which only happen when decoding with WXtoImg and never with SatDump. The reason it doesn't happen with Meteor is, the satellite transmits its on-board time along with the image. NOAA doesn't so it can suffer from clock on the Pi being inaccurate by a few seconds.

@athisha1
Copy link

Hello everyone. Great job with this app. Since the last version I noticed that the base map does not correspond perfectly with the images received. do you have an idea ? See the images here:

http://15.188.192.50/captures?page_no=1

Looking online, I realized that I wasn't the only one with the same problem. thanking you in advance for your return.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants