#2028 closed defect (fixed)
[WMS Server] Using non-EPSG-format projections
Reported by: | Owned by: | dmorissette | |
---|---|---|---|
Priority: | high | Milestone: | 6.0 release |
Component: | WMS Server | Version: | 5.0 |
Severity: | normal | Keywords: | |
Cc: | jmckenna |
Description (last modified by )
Best explained with an example: - wms data to be served is in a projection that is not part of the standard EPSG lookup file - wms-server mapfile sets the MAP.PROJECTION, and LAYER.PROJECTION to the following: # Map projection PROJECTION "proj=aea" "ellps=GRS80" "lat_0=59" "lon_0=-132.5" "lat_1=61.667" "lat_2=68" "x_0=500000.0" "y_0=500000.0" "units=m" "no_defs" END - however a GetCapabilities request response gives these errors for the layers: <!-- WARNING: Mandatory mapfile parameter '(at least one of) MAP.PROJECTION, LAYER.PROJECTION or wms_srs metadata' was missing in this context. --> **** Assefa and I looked into the code and MapServer is looking for an actual EPSG code here, so this appears to be a "limitation" of MapServer.
Attachments (1)
Change History (22)
comment:2 by , 17 years ago
Oh, I forgot to mention that if you set "wms_srs" "EPSG:4326" as suggested above then the WMS will be fully functional, but you'll have to pay the price of on-the-fly reprojection for every request.
comment:3 by , 17 years ago
Maybe i left out one thing: - map-level metadata is set to advertize the following epsg codes: "ows_srs" "EPSG:42304 EPSG:42101 EPSG:4269 EPSG:4326" So that is why I was confused to see that warning message from getcapabilities. So it would seem that MapServer requires that advertising to occur at the layer level as well (I need to add in "ows_srs" layer metadata as well). Anyway thanks for your response.
comment:4 by , 17 years ago
for the record, I still believe that there is a bug because in my example I had map.projection, layer.projection, and map srs metadata set and I still got an error stating that I must set one of those. To me that is a bug. Maybe the warning should state: <!-- WARNING: Mandatory mapfile parameter '(at least one of) MAP.PROJECTION in EPSG format, LAYER.PROJECTION in EPSG format, or LAYER.METADATA "wms_srs"' was missing in this context. -->
comment:5 by , 17 years ago
Milestone: | → 5.0 release |
---|---|
Resolution: | invalid |
Status: | closed → reopened |
Reopening. You had left out an important detail, i.e. that you had specified ows_srs at the map-level. This should have been enough to make MapServer happy, so yes there is a bug and the layer-level metadata should not be required in this case.
comment:6 by , 17 years ago
Description: | modified (diff) |
---|---|
Owner: | changed from | to
Status: | reopened → new |
I'll take this one.
comment:7 by , 17 years ago
Ticket #2254 seems to be about the same issue but adds an interesting piece of info: it happens only with WMS 1.1.1 and not with 1.1.0
comment:8 by , 17 years ago
Milestone: | 5.0 release → 5.0.1 release |
---|
comment:9 by , 16 years ago
Milestone: | 5.0.1 release → 5.2 release |
---|
comment:10 by , 16 years ago
Milestone: | 5.2 release → 5.4 release |
---|
comment:11 by , 15 years ago
Cc: | added |
---|
comment:12 by , 15 years ago
Milestone: | 5.4 release → 6.0 release |
---|
comment:13 by , 15 years ago
Daniel, do you have any new development on this one? If no could I reassign this ticket to someone else or do you prefer to fix it?
comment:15 by , 15 years ago
Milestone: | 6.0 release → 5.6.0 release |
---|
comment:17 by , 15 years ago
Jeff,
I attached a test case and was not able to reproduce. Notice that I commented out the EPSG:4326 in the epsg file. I tested with MapServer trunk. Could you verify if I forgot something in the test case?
<!-- MapServer version 5.5.0 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=GEOS SUPPORTS=RGBA_PNG INPUT=EPPL7 INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE -->
comment:18 by , 14 years ago
Milestone: | 5.6 release → 6.0 release |
---|
comment:19 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I finally came across a way to reproduce this issue... and fixed it in SVN trunk r9858 (future 6.0)
It turns out that when you had a valid ows_srs metadata or projection at the map level, but none at the layer level, you would get this warning when you shouldn't. Great to see that this one is finally behind us.