lonlat_box across meridian

[leips]

Hi,

I can't plot any data that cross the meridian. For example, I try

query.lonlat_box(north=45., south=39., east=4, west=-3).time(datetime.utcnow())

And stop at lon_0

And it's not inside de query

[0. 0.25 0.5 0.75 1. 1.25 1.5 1.75 2. 2.25 2.5 2.75 3. 3.25 3.5 3.75 4. ]

What I'm doing wrong? Or this something related to Thredds server?

Thank you

[lesserwhirls]

The current release of the TDS does not allow for cross data array boundaries. However, the next version does and should support this kind of ncss query.

[stefan-hofer]

Having a similar problem when defining a bounding box that crosses the prime meridian. Is there a workaround?

[dopplershift]

@shofer16450 is the data extent 0->360? (Rather than -180 -> 180)

[lesserwhirls]

The only workaround at this point would be to make two siphon requests - one for each edge of the grid. In the next version of the TDS, you will be able to do this in with one siphon request. It might be possible to have siphon automatically make two requests if needed, but that functionality does not exist yet.

[dopplershift]

Well, the two requests would result in two separate netCDF Datasets, so there would still be some work to put those back together. Maybe...OPeNDAP?

[lesserwhirls]

Maybe, but then you lose the ncss niceness of the request. Needs more thought :-/

[stefan-hofer]

@shofer16450 is the data extent 0->360? (Rather than -180 -> 180)

Yes, the data extent is indeed [0, 360].

Thanks for your input, I'll just split the request and merge the resulting netCDF datasets back together for now.

[floryISU]

Is this fixed in TDS 4.6.15 or do we have to wait for version 5?

[dopplershift]

TDS 5 will provide a service that can handle requests across the 0 degree meridian. Some work will be needed to access that service from Siphon and return this data in a usable form.

[floryISU]

Thanks, Ryan. I appreciate it and will watch for TDS 5.