[Geoserver-users] Hide layers in layer group

Hi,

My understanding of WFS was that SLD’s are not applied to the request as the service provides features rather than rendered outputs. I think you may need to put your restrictions into the filtering rather than the SLD but I accept that is more complex if you are trying to apply a number of scale dependencies by feature type within the SLD.

Perhaps you are rendering it with the SLD on the client side using something like OpenLayers; if so, you will still want to filter the original request from the GeoServer I would think.

Probably not a very helpful response but I hope it helps a bit if you haven’t already had a reply.

Thanks,

Paul

Hi,

My understanding of WFS was that SLD’s are not applied to the request as the service provides features rather than rendered outputs. I think you may need to put your restrictions into the filtering rather than the SLD but I accept that is more complex if you are trying to apply a number of scale dependencies by feature type within the SLD.

Perhaps you are rendering it with the SLD on the client side using something like OpenLayers; if so, you will still want to filter the original request from the GeoServer I would think.

Probably not a very helpful response but I hope it helps a bit if you haven’t already had a reply.

Thanks,

Paul

On Mon, Jul 24, 2017 at 10:36 AM, Paul Wittle via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

Hi,

My understanding of WFS was that SLD’s are not applied to the request as
the service provides features rather than rendered outputs. I think you may
need to put your restrictions into the filtering rather than the SLD but I
accept that is more complex if you are trying to apply a number of scale
dependencies by feature type within the SLD.

Hi Paul,
vector tiles are a WMS output, so they should be taking into account SLD.
What Dylan describes looks more like a bug to me.
Unfortunately we don't seem to be catching the module maintainer
attention...

Cheers
Andrea

--

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

Hi Andrea,

That’s good to know—I was sure the presentations I watched were using SLD, but figured it was me just “not getting it”!

If that’s the case, then this is almost certainly a bug, or I’m not writing my SLD correctly. Hopefully the module maintainer will be able to chip in on this and confirm whether it’s a bug or show an example of how to correctly write the SLD so that it does filter the data out rather than spend an inordinate amount of time processing it!

Thanks,

···

On 24/07/17 12:54, Andrea Aime wrote:

On Mon, Jul 24, 2017 at 10:36 AM, Paul Wittle via Geoserver-users <geoserver-users@lists.sourceforge.net> wrote:

Hi,

My understanding of WFS was that SLD’s are not applied to the request as the service provides features rather than rendered outputs. I think you may need to put your restrictions into the filtering rather than the SLD but I accept that is more complex if you are trying to apply a number of scale dependencies by feature type within the SLD.

Hi Paul,
vector tiles are a WMS output, so they should be taking into account SLD. What Dylan describes looks more like a bug to me.
Unfortunately we don’t seem to be catching the module maintainer attention…

Cheers
Andrea

Regards,

Andrea Aime

== GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY

Hi, Dylan,

The VT renderer should be taking the min/max scale range into consideration when querying the underlying data.

Do you have access to a dev environment? If you do, please look in VectorTileMapOutputFormat#produceMap(). About half way down, you should see;

Query query = getStyleQuery(layer, mapContent);

This should be taking the min/max scale denominator into consideration.

Questions;

  1. what’s your SLD
  2. what type of data set are you using (postgis? shp?)
  3. could you verify that all your CRSes are setup correctly for the layer and request? (it could be calculating the incorrect map scale)
  4. how are your requests setup? Are you using the SLD in #1? Could you give an example request that directly communicates with the WMS (that’s quick for an image format and slow for a mapbox VT format)?

Thanks,
Dave

···

On Mon, Jul 24, 2017 at 4:57 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Andrea,

That’s good to know—I was sure the presentations I watched were using SLD, but figured it was me just “not getting it”!

If that’s the case, then this is almost certainly a bug, or I’m not writing my SLD correctly. Hopefully the module maintainer will be able to chip in on this and confirm whether it’s a bug or show an example of how to correctly write the SLD so that it does filter the data out rather than spend an inordinate amount of time processing it!

Thanks,

On 24/07/17 12:54, Andrea Aime wrote:


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Mon, Jul 24, 2017 at 10:36 AM, Paul Wittle via Geoserver-users <geoserver-users@anonymised.comsourceforge.net> wrote:

Hi,

My understanding of WFS was that SLD’s are not applied to the request as the service provides features rather than rendered outputs. I think you may need to put your restrictions into the filtering rather than the SLD but I accept that is more complex if you are trying to apply a number of scale dependencies by feature type within the SLD.

Hi Paul,
vector tiles are a WMS output, so they should be taking into account SLD. What Dylan describes looks more like a bug to me.
Unfortunately we don’t seem to be catching the module maintainer attention…

Cheers
Andrea

Regards,

Andrea Aime

== GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Hi Dave/Jody,

Thanks for the replies. I’ll combine my replies to both of you as you asked similar questions :slight_smile:

Firstly, I’m using ShapeFiles for my data. I may move to use something else later, but during my development stage it’s simpler for me to be able to drop in replacement data etc if they are simple files.

The original data is in EPSG:27700 (British National Grid), and I’m serving it as EPSG:3857. This doesn’t appear to be the issue though—I repeated the experiments that I’ll detail below using both projections and got similar results in both. In all cases I chose a fairly large tile size to get the most extreme results.

Anyhow, here are the experiments I’ve tried:

— start —

With Point Data

···

On 26/07/17 00:22, Dave Blasby wrote:

Hi, Dylan,

The VT renderer should be taking the min/max scale range into consideration when querying the underlying data.

Do you have access to a dev environment? If you do, please look in VectorTileMapOutputFormat#produceMap(). About half way down, you should see;

Query query = getStyleQuery(layer, mapContent);

This should be taking the min/max scale denominator into consideration.

Questions;

  1. what’s your SLD
  2. what type of data set are you using (postgis? shp?)
  3. could you verify that all your CRSes are setup correctly for the layer and request? (it could be calculating the incorrect map scale)
  4. how are your requests setup? Are you using the SLD in #1? Could you give an example request that directly communicates with the WMS (that’s quick for an image format and slow for a mapbox VT format)?

Thanks,
Dave


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY

Dylan the vector tile code does not do any magic for reducing your data size - your SLD should have a series of scale based rules selecting what content you wish to display at each zoom level. This will make for a long style - but often the work was already done for performance reasons so we took this approach.

···

On 26 July 2017 at 02:17, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave/Jody,

Thanks for the replies. I’ll combine my replies to both of you as you asked similar questions :slight_smile:

Firstly, I’m using ShapeFiles for my data. I may move to use something else later, but during my development stage it’s simpler for me to be able to drop in replacement data etc if they are simple files.

The original data is in EPSG:27700 (British National Grid), and I’m serving it as EPSG:3857. This doesn’t appear to be the issue though—I repeated the experiments that I’ll detail below using both projections and got similar results in both. In all cases I chose a fairly large tile size to get the most extreme results.

Anyhow, here are the experiments I’ve tried:

— start —

With Point Data

SLD

<?xml version="1.0" encoding="ISO-8859-1"?>

<StyledLayerDescriptor version=“1.0.0”
xsi:schemaLocation=“http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd”
xmlns=“http://www.opengis.net/sld” xmlns:ogc=“http://www.opengis.net/ogc”
xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

red square point style red point 10000 square #ff0000 6

Results

WMS as PNG (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~126ms on first run (~81ms without SLD)

WMS as VectorTile (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~68ms on first run (~83ms without SLD)

WMS as PNG (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~93ms on first run (~109ms without SLD)

WMS as VectorTile (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~107ms on first run (~135ms without SLD)

With Polygon Data

SLD

<?xml version="1.0" encoding="ISO-8859-1"?>

<StyledLayerDescriptor version=“1.0.0”
xsi:schemaLocation=“http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd”
xmlns=“http://www.opengis.net/sld” xmlns:ogc=“http://www.opengis.net/ogc”
xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

Polygon Test A grey polygon style grey polygon 10000 #cccccc #000000 0.5

Results

WMS as PNG (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~242ms on first run (~220 without SLD)

WMS as VectorTile (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~184ms on first run (~189ms without SLD)

WMS as PNG (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~95ms on first run (~511ms without SLD)

WMS as VectorTile (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~5416ms on first run (~362ms without SLD)

— end —

The point data didn’t really show any issues. It’s possible that this is because that dataset is pretty sparse in comparison to other datasets that I’m working with. The real issues arise when using polygon data—serving as VectorTile with the SLD took a whopping 5.5 seconds to generate a completely empty tile, but if I turned off the SLD it only took 0.3 seconds!

In reality I’m using TMS combined with GWC, so I’d only see these times once when populating the cache, but it means that populating my cache is taking an inordinate amount of time longer than it ought to.

Is there a problem with the SLDs that I have used? I basically took the default templates and added a MaxScaleDenominator to them, which appears to do the job just fine for the PNG request, and also results in the correctly empty tile for VectorTile, but it shouldn’t be taking so long to produce them.

Thanks for your help!

On 26/07/17 00:22, Dave Blasby wrote:

Hi, Dylan,

The VT renderer should be taking the min/max scale range into consideration when querying the underlying data.

Do you have access to a dev environment? If you do, please look in VectorTileMapOutputFormat#produceMap(). About half way down, you should see;

Query query = getStyleQuery(layer, mapContent);

This should be taking the min/max scale denominator into consideration.

Questions;

  1. what’s your SLD
  2. what type of data set are you using (postgis? shp?)
  3. could you verify that all your CRSes are setup correctly for the layer and request? (it could be calculating the incorrect map scale)
  4. how are your requests setup? Are you using the SLD in #1? Could you give an example request that directly communicates with the WMS (that’s quick for an image format and slow for a mapbox VT format)?

Thanks,
Dave


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Jody Garnett

Thanks, Jody. I understand that, but surely it shouldn’t be taking 18 times longer to produce the same tile just because I’ve told it to not to show any data at that scale? When I had no SLD at all it was less than half a second to create a tile.

···

On 26/07/17 16:41, Jody Garnett wrote:

Dylan the vector tile code does not do any magic for reducing your data size - your SLD should have a series of scale based rules selecting what content you wish to display at each zoom level. This will make for a long style - but often the work was already done for performance reasons so we took this approach.


Jody Garnett

On 26 July 2017 at 02:17, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave/Jody,

Thanks for the replies. I’ll combine my replies to both of you as you asked similar questions :slight_smile:

Firstly, I’m using ShapeFiles for my data. I may move to use something else later, but during my development stage it’s simpler for me to be able to drop in replacement data etc if they are simple files.

The original data is in EPSG:27700 (British National Grid), and I’m serving it as EPSG:3857. This doesn’t appear to be the issue though—I repeated the experiments that I’ll detail below using both projections and got similar results in both. In all cases I chose a fairly large tile size to get the most extreme results.

Anyhow, here are the experiments I’ve tried:

— start —

With Point Data

SLD

<?xml version="1.0" encoding="ISO-8859-1"?>

<StyledLayerDescriptor version=“1.0.0”
xsi:schemaLocation=“http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd”
xmlns=“http://www.opengis.net/sld” xmlns:ogc=“http://www.opengis.net/ogc”
xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

red square point style red point 10000 square #ff0000 6

Results

WMS as PNG (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~126ms on first run (~81ms without SLD)

WMS as VectorTile (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~68ms on first run (~83ms without SLD)

WMS as PNG (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~93ms on first run (~109ms without SLD)

WMS as VectorTile (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~107ms on first run (~135ms without SLD)

With Polygon Data

SLD

<?xml version="1.0" encoding="ISO-8859-1"?>

<StyledLayerDescriptor version=“1.0.0”
xsi:schemaLocation=“http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd”
xmlns=“http://www.opengis.net/sld” xmlns:ogc=“http://www.opengis.net/ogc”
xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

Polygon Test A grey polygon style grey polygon 10000 #cccccc #000000 0.5

Results

WMS as PNG (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~242ms on first run (~220 without SLD)

WMS as VectorTile (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~184ms on first run (~189ms without SLD)

WMS as PNG (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~95ms on first run (~511ms without SLD)

WMS as VectorTile (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~5416ms on first run (~362ms without SLD)

— end —

The point data didn’t really show any issues. It’s possible that this is because that dataset is pretty sparse in comparison to other datasets that I’m working with. The real issues arise when using polygon data—serving as VectorTile with the SLD took a whopping 5.5 seconds to generate a completely empty tile, but if I turned off the SLD it only took 0.3 seconds!

In reality I’m using TMS combined with GWC, so I’d only see these times once when populating the cache, but it means that populating my cache is taking an inordinate amount of time longer than it ought to.

Is there a problem with the SLDs that I have used? I basically took the default templates and added a MaxScaleDenominator to them, which appears to do the job just fine for the PNG request, and also results in the correctly empty tile for VectorTile, but it shouldn’t be taking so long to produce them.

Thanks for your help!

On 26/07/17 00:22, Dave Blasby wrote:

Hi, Dylan,

The VT renderer should be taking the min/max scale range into consideration when querying the underlying data.

Do you have access to a dev environment? If you do, please look in VectorTileMapOutputFormat#produceMap(). About half way down, you should see;

Query query = getStyleQuery(layer, mapContent);

This should be taking the min/max scale denominator into consideration.

Questions;

  1. what’s your SLD
  2. what type of data set are you using (postgis? shp?)
  3. could you verify that all your CRSes are setup correctly for the layer and request? (it could be calculating the incorrect map scale)
  4. how are your requests setup? Are you using the SLD in #1? Could you give an example request that directly communicates with the WMS (that’s quick for an image format and slow for a mapbox VT format)?

Thanks,
Dave


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it’s just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave

···

On Wed, Jul 26, 2017 at 2:17 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave/Jody,

Thanks for the replies. I’ll combine my replies to both of you as you asked similar questions :slight_smile:

Firstly, I’m using ShapeFiles for my data. I may move to use something else later, but during my development stage it’s simpler for me to be able to drop in replacement data etc if they are simple files.

The original data is in EPSG:27700 (British National Grid), and I’m serving it as EPSG:3857. This doesn’t appear to be the issue though—I repeated the experiments that I’ll detail below using both projections and got similar results in both. In all cases I chose a fairly large tile size to get the most extreme results.

Anyhow, here are the experiments I’ve tried:

— start —

With Point Data

SLD

<?xml version="1.0" encoding="ISO-8859-1"?>

<StyledLayerDescriptor version=“1.0.0”
xsi:schemaLocation=“http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd”
xmlns=“http://www.opengis.net/sld” xmlns:ogc=“http://www.opengis.net/ogc”
xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

red square point style red point 10000 square #ff0000 6

Results

WMS as PNG (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~126ms on first run (~81ms without SLD)

WMS as VectorTile (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~68ms on first run (~83ms without SLD)

WMS as PNG (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~93ms on first run (~109ms without SLD)

WMS as VectorTile (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~107ms on first run (~135ms without SLD)

With Polygon Data

SLD

<?xml version="1.0" encoding="ISO-8859-1"?>

<StyledLayerDescriptor version=“1.0.0”
xsi:schemaLocation=“http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd”
xmlns=“http://www.opengis.net/sld” xmlns:ogc=“http://www.opengis.net/ogc”
xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

Polygon Test A grey polygon style grey polygon 10000 #cccccc #000000 0.5

Results

WMS as PNG (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~242ms on first run (~220 without SLD)

WMS as VectorTile (Approx 1:8500)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-251589.75115165487%2c6775967.934575723%2c-248658.86884834513%2c6778261.045424278

~184ms on first run (~189ms without SLD)

WMS as PNG (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Abuilding&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~95ms on first run (~511ms without SLD)

WMS as VectorTile (Approx 1:17k)

http://localhost:8080/geoserver/openmap-local/wms?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&FORMAT=application%2Fx-protobuf%3Btype%3Dmapbox-vector&TRANSPARENT=true&STYLES&LAYERS=openmap-local%3Aroundabout&SRS=EPSG%3A3857&WIDTH=1227&HEIGHT=960&BBOX=-253206.87203131313%2c6774771.217351635%2c-247345.1074246937%2c6779357.439048746

~5416ms on first run (~362ms without SLD)

— end —

The point data didn’t really show any issues. It’s possible that this is because that dataset is pretty sparse in comparison to other datasets that I’m working with. The real issues arise when using polygon data—serving as VectorTile with the SLD took a whopping 5.5 seconds to generate a completely empty tile, but if I turned off the SLD it only took 0.3 seconds!

In reality I’m using TMS combined with GWC, so I’d only see these times once when populating the cache, but it means that populating my cache is taking an inordinate amount of time longer than it ought to.

Is there a problem with the SLDs that I have used? I basically took the default templates and added a MaxScaleDenominator to them, which appears to do the job just fine for the PNG request, and also results in the correctly empty tile for VectorTile, but it shouldn’t be taking so long to produce them.

Thanks for your help!

On 26/07/17 00:22, Dave Blasby wrote:

Hi, Dylan,

The VT renderer should be taking the min/max scale range into consideration when querying the underlying data.

Do you have access to a dev environment? If you do, please look in VectorTileMapOutputFormat#produceMap(). About half way down, you should see;

Query query = getStyleQuery(layer, mapContent);

This should be taking the min/max scale denominator into consideration.

Questions;

  1. what’s your SLD
  2. what type of data set are you using (postgis? shp?)
  3. could you verify that all your CRSes are setup correctly for the layer and request? (it could be calculating the incorrect map scale)
  4. how are your requests setup? Are you using the SLD in #1? Could you give an example request that directly communicates with the WMS (that’s quick for an image format and slow for a mapbox VT format)?

Thanks,
Dave


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi Dave,

Thanks for looking into this for me. I've created a very small extract of a housing estate projected as EPSG:27700, and have uploaded it here https://we.tl/UY1Ubtdm64. It's a zip file containing the SHP, SHX, PRJ and DBF files.

Please let me know if it's a good enough extract for you to work with.

Thanks,

Dylan

On 26/07/17 18:49, Dave Blasby wrote:

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it's just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave

Hi, Dylan,

I tracked the problem down to an issue in the VT rendering. If no SLD rules apply (as in your case), then it does some funny business.

I think I’ve fixed this, just going to make a PR for it and you can give it a try.

Thanks,
Dave

···

On Thu, Jul 27, 2017 at 3:45 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave,

Thanks for looking into this for me. I’ve created a very small extract of a housing estate projected as EPSG:27700, and have uploaded it here https://we.tl/UY1Ubtdm64. It’s a zip file containing the SHP, SHX, PRJ and DBF files.

Please let me know if it’s a good enough extract for you to work with.

Thanks,

Dylan

On 26/07/17 18:49, Dave Blasby wrote:

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it’s just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

That’s excellent! Thanks :slight_smile: Will it be the nightly build I’ll need to try, or is there another way of getting the updated extension?

···

On 27/07/17 20:10, Dave Blasby wrote:

Hi, Dylan,

I tracked the problem down to an issue in the VT rendering. If no SLD rules apply (as in your case), then it does some funny business.

I think I’ve fixed this, just going to make a PR for it and you can give it a try.

Thanks,
Dave

On Thu, Jul 27, 2017 at 3:45 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave,

Thanks for looking into this for me. I’ve created a very small extract of a housing estate projected as EPSG:27700, and have uploaded it here https://we.tl/UY1Ubtdm64. It’s a zip file containing the SHP, SHX, PRJ and DBF files.

Please let me know if it’s a good enough extract for you to work with.

Thanks,

Dylan

On 26/07/17 18:49, Dave Blasby wrote:

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it’s just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi, Dylan,

I had some travis build issues, but it’s built now. I asked torben to kick-off a nightly build; it should be done in an hour or two.

Please give it a try when its done,
Dave

···

On Thu, Jul 27, 2017 at 12:16 PM, Dylan Parry <dylan.parry@anonymised.com> wrote:

That’s excellent! Thanks :slight_smile: Will it be the nightly build I’ll need to try, or is there another way of getting the updated extension?

On 27/07/17 20:10, Dave Blasby wrote:

Hi, Dylan,

I tracked the problem down to an issue in the VT rendering. If no SLD rules apply (as in your case), then it does some funny business.

I think I’ve fixed this, just going to make a PR for it and you can give it a try.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Thu, Jul 27, 2017 at 3:45 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave,

Thanks for looking into this for me. I’ve created a very small extract of a housing estate projected as EPSG:27700, and have uploaded it here https://we.tl/UY1Ubtdm64. It’s a zip file containing the SHP, SHX, PRJ and DBF files.

Please let me know if it’s a good enough extract for you to work with.

Thanks,

Dylan

On 26/07/17 18:49, Dave Blasby wrote:

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it’s just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi, Dylan,

Did it work for you?

Thanks,
Dave

···

On Fri, Jul 28, 2017 at 10:49 AM, Dave Blasby <dblasby@anonymised.com> wrote:

Hi, Dylan,

I had some travis build issues, but it’s built now. I asked torben to kick-off a nightly build; it should be done in an hour or two.

Please give it a try when its done,
Dave

On Thu, Jul 27, 2017 at 12:16 PM, Dylan Parry <dylan.parry@anonymised.com> wrote:

That’s excellent! Thanks :slight_smile: Will it be the nightly build I’ll need to try, or is there another way of getting the updated extension?

On 27/07/17 20:10, Dave Blasby wrote:

Hi, Dylan,

I tracked the problem down to an issue in the VT rendering. If no SLD rules apply (as in your case), then it does some funny business.

I think I’ve fixed this, just going to make a PR for it and you can give it a try.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Thu, Jul 27, 2017 at 3:45 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave,

Thanks for looking into this for me. I’ve created a very small extract of a housing estate projected as EPSG:27700, and have uploaded it here https://we.tl/UY1Ubtdm64. It’s a zip file containing the SHP, SHX, PRJ and DBF files.

Please let me know if it’s a good enough extract for you to work with.

Thanks,

Dylan

On 26/07/17 18:49, Dave Blasby wrote:

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it’s just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi Dave,

Apologies, I’ve been away for a few days and was unable to test it until this morning. Your fix appears to have worked!

Thanks,

···

On 31/07/17 23:02, Dave Blasby wrote:

Hi, Dylan,

Did it work for you?

Thanks,
Dave

On Fri, Jul 28, 2017 at 10:49 AM, Dave Blasby <dblasby@anonymised.com> wrote:

Hi, Dylan,

I had some travis build issues, but it’s built now. I asked torben to kick-off a nightly build; it should be done in an hour or two.

Please give it a try when its done,
Dave

On Thu, Jul 27, 2017 at 12:16 PM, Dylan Parry <dylan.parry@anonymised.com> wrote:

That’s excellent! Thanks :slight_smile: Will it be the nightly build I’ll need to try, or is there another way of getting the updated extension?

On 27/07/17 20:10, Dave Blasby wrote:

Hi, Dylan,

I tracked the problem down to an issue in the VT rendering. If no SLD rules apply (as in your case), then it does some funny business.

I think I’ve fixed this, just going to make a PR for it and you can give it a try.

Thanks,
Dave

On Thu, Jul 27, 2017 at 3:45 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave,

Thanks for looking into this for me. I’ve created a very small extract of a housing estate projected as EPSG:27700, and have uploaded it here https://we.tl/UY1Ubtdm64. It’s a zip file containing the SHP, SHX, PRJ and DBF files.

Please let me know if it’s a good enough extract for you to work with.

Thanks,

Dylan

On 26/07/17 18:49, Dave Blasby wrote:

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it’s just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY

Excellent - I will close the ticket.

Cheers,
Dave

···

On Tue, Aug 1, 2017 at 2:14 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave,

Apologies, I’ve been away for a few days and was unable to test it until this morning. Your fix appears to have worked!

Thanks,

On 31/07/17 23:02, Dave Blasby wrote:

Hi, Dylan,

Did it work for you?

Thanks,
Dave


Dylan Parry
Lead Developer, Blue Fox Technology Ltd


T: 01452 524901
W: www.opusmap.co.uk
LinkedInTwitterYouTubeGoogle+

Opus Map - Try it for free

Registered in England and Wales, Company No. 05908226.
Registered office: Windsor House, 26 Mostyn Avenue, Craig-Y-Don, Llandudno, Conwy LL30 1YY


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.com.382…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Fri, Jul 28, 2017 at 10:49 AM, Dave Blasby <dblasby@anonymised.com> wrote:

Hi, Dylan,

I had some travis build issues, but it’s built now. I asked torben to kick-off a nightly build; it should be done in an hour or two.

Please give it a try when its done,
Dave

On Thu, Jul 27, 2017 at 12:16 PM, Dylan Parry <dylan.parry@anonymised.com> wrote:

That’s excellent! Thanks :slight_smile: Will it be the nightly build I’ll need to try, or is there another way of getting the updated extension?

On 27/07/17 20:10, Dave Blasby wrote:

Hi, Dylan,

I tracked the problem down to an issue in the VT rendering. If no SLD rules apply (as in your case), then it does some funny business.

I think I’ve fixed this, just going to make a PR for it and you can give it a try.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Thu, Jul 27, 2017 at 3:45 AM, Dylan Parry <dylan.parry@anonymised.com> wrote:

Hi Dave,

Thanks for looking into this for me. I’ve created a very small extract of a housing estate projected as EPSG:27700, and have uploaded it here https://we.tl/UY1Ubtdm64. It’s a zip file containing the SHP, SHX, PRJ and DBF files.

Please let me know if it’s a good enough extract for you to work with.

Thanks,

Dylan

On 26/07/17 18:49, Dave Blasby wrote:

Dylan,

Do you think you could provide me with a little buildings shapefile (with a small amount of data - even if it’s just 2 polygons)?
The most likely problem will be CRSs issues causing scale calculation problems; I can quickly run it in the debugger.

Thanks,
Dave


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

Geoserver-users@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users