[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mapserver-dev
Subject:    [mapserver-dev] RE: INSPIRE compliancy - A request for comments on
From:       relet <thomas.hirsch () statkart ! no>
Date:       2010-10-26 7:38:13
Message-ID: 1288078693058-5673696.post () n2 ! nabble ! com
[Download RAW message or body]


Thanks Steve, (and hopefully a few others),

We consider the container layer as an abstraction view between the technical
requirements of mapserver (one layer connects to one data source) and the
representation requirements of the service (visibility, aggregation,
querying of layers). I believe that this model can be more widely useful
than just in the INSPIRE context - for example satisfying the requests for
multi-geometry support. 

What we are trying to find out, is whether the proposed aggregation model
covers all typical use cases, or if more parameters are needed in the
container layer. And, of course, how well it integrates into the existing
software architecture.

Any opinions, comments are very welcome. 
Thomas
-- 
View this message in context: \
http://osgeo-org.1803224.n2.nabble.com/INSPIRE-compliancy-A-request-for-comments-on-a-possible-RFC-tp5661761p5673696.html
 Sent from the Mapserver - Dev mailing list archive at Nabble.com.
_______________________________________________
mapserver-dev mailing list
mapserver-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev


[prev in list] [next in list] [prev in thread] [next in thread]