Opened 13 years ago
Closed 13 years ago
#3720 closed defect (invalid)
WMS 1.3.0: getFeatureInfo requests I,J should respect axis order
Reported by: | assefa | Owned by: | assefa |
---|---|---|---|
Priority: | normal | Milestone: | 6.0 release |
Component: | WMS Server | Version: | unspecified |
Severity: | normal | Keywords: | WMS GetFeatureInfo axis |
Cc: | bartvde@…, tomkralidis, dmorissette |
Description
Right now I,J are treated as x,y. But accrodint to spec:
7.4.3.7 I, J The mandatory I and J request parameters are integers that indicate a point of interest on the map that was produced by the embedded GetMap request (the “map request part” described in 7.4.3.3). The point (I,J) is a point in the (i,j) space defined by the Map CS (see 6.7.2). Therefore:
- the value of I shall be between 0 and the maximum value of the i axis
- the value of J shall be between 0 and the maximum value of the j axis
-the point I=0, J=0 indicates the pixel at the upper left
Change History (3)
comment:1 by , 13 years ago
Owner: | changed from | to
---|
comment:2 by , 13 years ago
Cc: | added |
---|
comment:3 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Thanks for verifying. Marking it as invalid.
Note:
See TracTickets
for help on using tickets.
Guys, I'm not convinced that I,J should be swapped.... have a look at 6.7.2 ... it sounds like in general I should be east to west, and J north to south. There is no mention of those conventions changing based on the CRS axis orientation.
Are we mixing Map CS and CRS here? What made you think that I,J need to be swapped? Do you have pointers to complementary info about this?