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

problem with geographical coordinates and GSTools Covmodel #217

Closed
Mercuron opened this issue Jan 9, 2022 · 2 comments · Fixed by #245
Closed

problem with geographical coordinates and GSTools Covmodel #217

Mercuron opened this issue Jan 9, 2022 · 2 comments · Fixed by #245
Assignees
Labels
Milestone

Comments

@Mercuron
Copy link

Mercuron commented Jan 9, 2022

Hi all!

  1. I can't figure out how to beat the dim error. I set dim=2, but there is still error ValueError: GSTools: model dim is not 1 or 2. It's probably very silly, but I can't find where it is.

  2. Why there is no predict method in the description of OK and UK methods? How then to predict results on new points?

values.csv

example_of_error.ipynb.zip

@MuellerSeb
Copy link
Member

Hi there,

sorry for the late reply. This is a compatibility issue between GSTools and PyKrige. You were using the latlon mode of the Spherical model and PyKrige doesn't check for that correctly.

I need to investigate this.

@MuellerSeb
Copy link
Member

This only affects OrdinaryKriging, since the support for geographic coordinates in UniversalKriging was not implemented.

TODOs:

@MuellerSeb MuellerSeb added the bug label Apr 20, 2022
@MuellerSeb MuellerSeb added this to the v1.6.2 milestone Apr 20, 2022
@MuellerSeb MuellerSeb self-assigned this Apr 20, 2022
@MuellerSeb MuellerSeb changed the title problem with dimension=2 problem with geographical coordinates and GSTools Covmodel Apr 20, 2022
@MuellerSeb MuellerSeb linked a pull request Aug 10, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants