Opened 22 years ago

Closed 15 years ago

#25 closed defect (fixed)

BBOX that crosses dateline

Reported by: warmerdam Owned by: dmorissette
Priority: high Milestone:
Component: WMS Server Version: 4.1
Severity: normal Keywords:


> My question is how is a BBOX supposed to be specified in geographic
> coordinates for a region that crosses the dateline? 
> If I want the 2x2 degree region with a top left corner of 179E,1N and
> a lower left corner of 179W and 1S would it be:
>   BBOX=179,1,181,-1
> or 
>   BBOX=179,1,-179,-1
> or 
>   BBOX=-179,1,179,1
> The second actually works with the newish WMS implementation 
> in MapServer
> (from UMN) but it freaks me out that xmin is greater than 
> xmax.  The third
> would normally be taken to define a 358x2 degree square not 
> crossing the 
> equator.  The first is only acceptable if degree values outside the 
> -180 to 180 / -90 to 90 range are allowed and even then we 
> would have to
> carefully consider the semantics. 

This is part of the 1.1 specification, par 6.5.6

----- Quote:

In the particular case of longitude, the following behavior applies
regarding the anti-meridian
at 180 degrees of longitude. There is a legitimate desire for maps that
span the
anti-meridian (for example, a map centered on the Pacific Ocean). If
Xmin is the west-most
longitude in degrees and Xmax is the east-most, then the following
-180 <= Xmin < Xmax < 540

EXAMPLES: Xmin,Xmax values and the corresponding scope of the bounding
-180,180 = Earth centered at Greenwich
0,360 = Earth with Greenwich at left edge
120,250 = Pacific Ocean

----- Unquote

Best regards,

Bart Adriaanse

Attachments (1)

world0-360.gif (3.2 KB ) - added by pramsey 15 years ago.
WMS request with 0-360 longitude

Download all attachments as: .zip

Change History (4)

comment:1 by dmorissette, 20 years ago

Cc: assefa@… added
Version: 3.54.1
Not sure how much we can or want to do about this.  Let's revisit in 4.1

comment:2 by fwarmerdam, 18 years ago

Well, hopefully we can addrses this in 4.5. 

I would also like to refer folks to the document at:

This seems to suggest strictly conforming servers would not allow request over 
180 for geographic coordinate systems. 

Perry is also wondering if we could make it possible to tell mapserver
(via metadata) whether the remote server is going to blow a gasket if we go
over 180.  I think we don't now.

by pramsey, 15 years ago

Attachment: world0-360.gif added

WMS request with 0-360 longitude

comment:3 by pramsey, 15 years ago

Resolution: fixed
Status: newclosed

Mapserver accepts longitude > 180, per the optional behavior described in the WMS specification document for anti-meridian crossing. If people want to publish data in that area, they will have to transform their data to also be in 0-360 range, but Mapserver can fit the bill. No fix required.

Note: See TracTickets for help on using tickets.