[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #BXM-118058]: VMS Service on Thredds

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #BXM-118058]: VMS Service on Thredds
  • Date: Tue, 01 Mar 2011 17:32:10 -0700
Hi Tiziano,

Tiziano Minuzzo wrote:
> Goodmorning, I'm a TDS end user and
> I've a question about vms service on Thredds.
> 
> In all our catalogues we get these capabilities
> 
> <Layer>
> <Title>back to top level</Title>
> <CRS>EPSG:4326</CRS>
> <CRS>CRS:84</CRS>
> <CRS>EPSG:41001</CRS>
> <CRS>EPSG:27700</CRS>
> <CRS>EPSG:3408</CRS>
> <CRS>EPSG:3409</CRS>
> <CRS>EPSG:32661</CRS>
> <CRS>EPSG:32761</CRS>
> -
> <Layer>
> 
> Is there any way to add also EPSG:900913 (google Spherical Mercator  
> Projection)?

Though we have plans to make this CRS list configurable, currently it cannot be 
changed without re-building the TDS.

As of TDS 4.2.4, this list includes EPSG:3857 ("WGS 84 / Pseudo-Mercator") 
which is used by GoogleMaps and such. EPSG:900913 is not actually a valid EPSG 
CRS code. I believe it was used as a stand-in CRS code at some point by some 
applications for what eventually became EPSG:3857.

Hope that helps.

Ethan
 
> Thanks a lot.
> 
> Tiziano Minuzzo
> CNR-ISMAR Venice

Ticket Details
===================
Ticket ID: BXM-118058
Department: Support THREDDS
Priority: Normal
Status: Closed