grid_map | Universal grid map library for mobile robotic mapping | Robotics library

Just add the transform parameter to the ax.contourf method.

CDO uses the attribute proj_params to identify the proj parameters. The corresponding attribute in your file is proj4. You need to rename this attribute to apply the proj parameters automatically:

Importing as a chain isn't useful, except for very specific instances where a module adds or defines functionality on an imported object or class. Since you're not using u, colors, grid or entity in main.py, there is no reason to import them at all.

And if you need to import them, you import them from the file where they are defined, not from objects.

In objects.py you only need to import entity from classes, and in classes you only need grid from map (btw, map is a bad name, since it shadows the internal map function).

There is no need to import symbols you don't use - you don't have to think about what the module you're importing needs; the module is responsible for that by itself.

(Another small nitpick; class names should have TitleCase, so Entity would be the correct capitalization (I'd also suggest a better class name, since Entity doesn't really say much)) (and it's True, not true).

You are not doing multiprocessing at all. You are calling visualize_path(grid, start, goal, path1) from the main process and passing to the Process constructor its return value, which is None and only then are you executing the next Process constructor and doing likewise. What you want to do is:

If you want to select all timeslices from ds2 which are also present in ds1 you can do

metpy.calc.wind_direction is unfortunately known not to work with Dask arrays--and in fact many places in MetPy don't work well with Dask, though we definitely want to. For now, to use wind_direction you'll need to turn stations_u, etc. into standard numpy arrays using e.g. .compute().

For information about chunk sizes, you can use the chunking() method on variables. Unfortunately, it looks like you can only access _FillValue if it's been set to a non-default value:

I made it work! I found this post https://stackoverflow.com/a/53816162/13872164, which explains that the lambda style function is not executed immediately. The following changes made my code work:

Does your data file have information about the original projection? This looks like it could be an issue with a globe mismatch (CartoPy defaults to WGS84) or missing some kind of projection parameter, like latitude at origin.

Edited based on other answer

So now with the proper projection information, this is how I would plot your data: