[fdo-internals] WMS provider issue while consuming 1.3.0 server

[Jason Birch]

While I'd love to see FDO become more intelligent about CS handling
and reprojection in general, I guess the 400mb dependency is a bit
steep just for axis order support.

In the meantime could we maybe use CS-Map to generate a lookup file of
CS and axis-order pairs (or just the reverse-order ones)? Or somehow
query the EPSG registry at build time or once per release-cycle to
generate this list? Or extract the list from the EPSG database dumps
(though they tend to lag behind the registry considerably)?

Does WMS always use EPSG short-codes, or does it allow full URN
notation (and would we have to support that)?

Jason

On 2010-08-17, Orest Halustchak <orest.halustchak at autodesk.com> wrote:
> Well, that's part of the problem. From a WMS server, you'd get an EPSG
> number and would have to look up that definition in a catalog to determine
> the axis order.
>
> Thanks,
> Orest.
>
> -----Original Message-----
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
> Sent: Tuesday, August 17, 2010 11:37 AM
> To: fdo-internals at lists.osgeo.org
> Subject: [fdo-internals] RE: WMS provider issue while consuming 1.3.0 server
>
>
> I'd be fine with this approach as long as the only dependency is the logic
> in
> the CS-Map library, and not it's 400+ mb of CS dictionaries.
>
> - Jackie
> --
> View this message in context:
> http://osgeo-org.1803224.n2.nabble.com/WMS-provider-issue-while-consuming-1-3-0-server-tp5431259p5432654.html
> Sent from the FDO Internals mailing list archive at Nabble.com.
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>