This seems a bit like you are just defining a new highlight layer, poorly
using different parameters? Like you your proposed vendor options are a
"mini" layer definition:
- layer name
- CQL filter
- highlight color
- WKT shape identifier
- stroke size (optional)
- margin size (optional)
You can
On Wed, 6 May 2020 at 14:54, wrote:
> Hi Ian,
>
> The approach with dynamic highlighting is that the client can dynamically
> request unlimited mark combinations of color, shape, marked features, and
> obtain them in the same WMS GetMap picture without defining new styles for
> every highlight
On Wed, 6 May 2020 at 15:52, Imran Rajjad wrote:
> My two cents to this.
>
> @Ian
>
> Your approach is correct but it does not work on moving data because we
> can certainly request the same layer twice with different style and CQL but
> the underlying database request will be redundant and
My two cents to this.
@Ian
Your approach is correct but it does not work on moving data because we can
certainly request the same layer twice with different style and CQL but the
underlying database request will be redundant and might end up fetching
same feature at different locations. So this
Marco Volpini (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5a129c3cb35ed9014cf6b480
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiODMzY2I3ZTY5Y2Q0NDkzM2I3MTRmYmFmMWFhNmIxNTkiLCJwIjoiaiJ9
) / Bug (
Hi Ian,
The approach with dynamic highlighting is that the client can dynamically
request unlimited mark combinations of color, shape, marked features, and
obtain them in the same WMS GetMap picture without defining new styles for
every highlight mark layer/color/shape.
And the
I'm not clear on why this can't just be another WMS request - pass in a new
style or SLD and a CQL_FILTER and away you go. Since there is no point in
highlighting more than a handful of points on any map it should be fast and
easy (assuming the ID or what ever is indexed).
Am I missing something?
Hi Jody,
Thanks for your nice hints, indeed those are interesting solutions, but I
think they are unsuitable for the use case I would like to implement (I can be
wrong, if I am please help me to understand how to use the existing tooling to
achieve this task).
Probably, as you say,
Marco Volpini (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5a129c3cb35ed9014cf6b480
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiOGU2OGIxZmI2OTNhNDMyZGFlMDM1MmRhOWIxYThhYTQiLCJwIjoiaiJ9
) / Bug (
On Tue, May 5, 2020 at 1:37 AM Torben Barsballe
wrote:
> The issue with format characters in log outputs (e.g. [1;34m ...[m) seems
> to be back. I have configured MAVEN_OPTS=-Dstyle.color=never, but that
> has had no effect. Anyone got any other ideas?
>
No me, sorry!
>
> *Project-specific
Marco Volpini (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5a129c3cb35ed9014cf6b480
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNWZmNDc3ZDIyYzlkNDMwMGJiNDU4ZmM1ZTdlOGQzZTgiLCJwIjoiaiJ9
) / Bug (
11 matches
Mail list logo
