Opened 14 years ago

Closed 14 years ago

#1462 closed defect (fixed)

New CRSs cannot be supported in WMS service

Reported by: liuar Owned by: liuar
Priority: low Milestone:
Component: WMS Interface Version: 2.2.0
Severity: trivial Keywords:
Cc: External ID: 1353781

Description

  1. add one new CRS:EPSG 4626 for Samples data
  2. open ​http://<serverIP>/mapguide/mapagent
  3. WMS -> getcapabilities with version 1.3.0

result: 

<Layer queryable="0" cascaded="0" noSubsets="0" opaque="0">
  <Name>Samples/Sheboygan/Layers/Districts</Name> 
  <Title>Districts</Title> 
  <CRS>EPSG:4326</CRS> 
  <CRS>EPSG:4326</CRS> 
- <EX_GeographicBoundingBox>

both CRS are EPSG 4326

expected: new added CRS could be supported.

Change History (2)

comment:1 by liuar, 14 years ago

All published layer headers use SRS to indicate the coordinate system which is a standard of WMS 1.1.0. But WMS 1.3.0 uses CRS to define the coordinate system.

Because there's no CRS defined in the published layer header, parent layer's CRS will be used as all children layers' CRS, which is EPSG:4326.

I update all the CRS to SRS in the template file Server/src/Wms/1.3.0.xml.awd for the backward compatibility issue.

comment:2 by liuar, 14 years ago

Resolution: → fixed
Status: new → closed

Changeset [5278] by liuar

Note: See TracTickets for help on using tickets.