#12140 closed defect (fixed)
WMTS loop for irisnet.be
Reported by: | A_Pirard | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 15.12 |
Component: | Core imagery | Version: | latest |
Keywords: | performance capabilities xml stax | Cc: |
Description
When a WMTS layer configured with
http://geoserver.gis.irisnet.be/gwc/service/wmts?REQUEST=getcapabilities
is opened, JOSM loops (100% CPU, the Imagery pull-down menu doesn't even close).
almost bare 9060.
Hoping this will help.
Attachments (0)
Change History (8)
follow-up: 2 comment:1 by , 9 years ago
follow-up: 3 comment:2 by , 9 years ago
Component: | Core → Core imagery |
---|---|
Keywords: | performance capabilities added |
comment:3 by , 9 years ago
comment:5 by , 9 years ago
I had imagined a long time but not 3 min on my however decent bi-processor hogged with 60% by Firefox activity ;-)
I leave it for you to judge. You got the picture.
But I don't ;-) I'd have to investigate WMTS.
But you might like to know that I can also use WMS or my trickery to get JOSM WMS simulate REST.
Their WMS does not support 3857; it supports 4326 but almost by OSM asking; their flag is Lambert.
Also, WMS has a lot of layers to be specified in the request.
REST supports 3857 (any EPSG) and includes all layers by default, easy to exclude a few.
So, I've just dropped WMS presets for REST.
BTW, there an annoyance with WMS and the message:
The layer ... does not support 3857. Supported ... 4326 ...
Is there a way to suppress this message (configure an "OK, OK, we know").
It's nice to warn the user the first time he uses the layer.
But more annoying later or if it's an ("incompetent") admin configuration!
I'm glad I've been some help.
Take it easy.
comment:8 by , 9 years ago
Keywords: | xml stax added |
---|---|
Milestone: | → 15.12 |
It looks like this imagery provider serves huge GetCapabilities document (around 2MB). As right now DOM parser is used, it requires a bit more processing power and memory.
On my machine, after ~60 seconds (on my machine) imagery loads. I'll check, if there is something we can easily optimize and gain significant improvement