Cameron,
The solution as done now with only works for 1 layer and is
intended to have an easy way to have a single google layer in 1.5. We
will need to modify the code to handle multiple baselayer-types in a
context doc and allow for switching baselayers. We can discuss OWS
context as well in
Steven, I think this is a good solution for 1.5, but think we can do a
better job with OWS Context for future versions.
I think that we should aim to make OWS Context simple and for that I
think that , and should all be merged. Ie:
...
Our applications then decide whether we treat a servi
Hi all,
After discussing this with Andreas we decided for the following approach
for the 1.5 release:
GMAPS, VE, YMAPS and non WMS-baselayers are only supported in OWSContext
So if we have a standard WMC, we will add a hidden baseLayer, just as
Andreas did already, nothing changes there. It will
On Wed, Nov 21, 2007 at 09:45:52AM +1100, Cameron Shorter wrote:
> Steven,
> Brainstorming on this topic, without having thought through all the details:
>
> * A baselayer by definition is not transparent. Right?
No. You can have a transparent baselayer. I've used this in the past for
creating o
Steven,
Brainstorming on this topic, without having thought through all the details:
* A baselayer by definition is not transparent. Right? In that case, in
MapPaneOL, we should be able to render all the layers until we get to
the baselayer, then we don't render the rest. (Will be slightly more
Andreas, you solution sounds good for the 1.5 release.
For 1.5 release candidate we want minimal impact changes and it sounds
like you have that covered.
Andreas Hocevar wrote:
> Hi,
>
> while all that was said by Steven should be considered for the trunk,
> we have to find a reliable solution fo
Hi again,
I have a refined proposal which might be more satisfying to those of
you that are in favour of a context-based solution:
IIRC, all map and layer control widgets only look for "Layer" and
"FeatureType" nodes in the context.
So why don't we add "BaseLayer" nodes? Since OWSContext is more
Hi,
while all that was said by Steven should be considered for the trunk,
we have to find a reliable solution for the upcoming release. I just
had a little chat with Steven, and we came up with the following
proposal:
- Base layers are strongly tied with resolutions. Resolutions are
currently in
Hi all,
While refactoring MapPaneOL to accomodate non-wms baselayers I
discovered that I missed an important problem during the last discussion:
If we have multiple baselayers we will need a solution similar to OL's
list of baselayers:
We need to parse all layers in the context doc and pick thos
