This proposal makes sense to me and my only additional comment is just whether or not the page might be better described as ‘Preview’ given that it only relays information and a preview link.
···
Hi Paul,
as discussed in the ticket, a “random” tiled preview would be slower, not faster, than the single tile one, because
it won’t hit a tile cache and will end up drawing a larger image (768x768 vs 768x300).
Issues in the preview that prevent tile caching:
- The bounds are the ones of the layer and the tile grid is aligned to them (not to a gridset)
- The CRS is the native one of the layer, which might or might not be cached (e.g., often only 3857 and 4326 are tile cached)
- The zoom levels are typically not a match for the gridset
The GWC preview instead is setup based on the chosen gridset, and its code is quite different from the one of the normal preview.
I would not go for having a “tiled” option, on master we already have a choice between OL2 and OL3 (see previous discussion on
this list on why OL3+ is sometimes problematic), if we go for tiled and untiled we’d end up with 4 options, and as seen above,
for no gain in the common case.
Modest proposition: why, instead of having one more option, don’t we expose the tiled layer page to the public, maybe hiding
the admin related portions (info about disk quota, blobstore, seeding). Something like this:
![Inline image 1]()
At least this would have guarantee it is being cached, and thus “fast” (if the cache is not full, it’s actually
going to be slower than then normal preview at the first hit, because the meta-tiling factor
is even higher than with the standard preview, 4x4 by default, but many pump it up to a higher value).
Cheers
Andrea
On Mon, Nov 27, 2017 at 3:10 PM, Paul Wittle via Geoserver-devel <geoserver-devel@lists.sourceforge.net> wrote:
Hi,
I think I said I would try to move this discussion to the dev list; not sure if that is the right method but here we go anyway.
The basic comments appear to be summarised as follows:
→ I have noticed that some of our layers are very slow loading in the layer preview and I would usually switch it straight to cache mode. On this basis and in discussion with Ian T we raised the ticket 8413 to suggest that tiled ‘might’ be a preferable starting situation.
→ Andrea noted that in some cases it is preferable to use single tiles due to labelling etc. Suggested a configuration option instead of default?
→ Jukka noted that the default map window is 768x330 so the single tile request may not actually be that much different
→ Andrea noted that the default tiled map is 3x3 which is actually an area of 768x768 in reality.
So in terms of the comments I do take the point that the area requested may be actually smaller in terms of the data behind the scenes but I had primarily raised the issue on the basis if the general feeling when using the layer preview. In my view the point of tiling is primarily to ensure that the user can see the data loading rather than waiting for the single render. I do accept the points raised but I do still feel there may be some benefit in allow the user to decide.
I think Andrea was indicating that the tiles may not actually come from the tile cache but my understanding is that this would be the case if you open the links via the Tile Layers screen.
Primarily I had added this one as I hoped it might be something very simple that I could look at whilst I’m learning to be a contributing developer but of course I will be guided by your views.
Could we just add an extra option to the dropdown list as OpenLayers is already duplicated in that list?
The proposal would simply be to add OpenLayers (Tiled) as an option in the UI.
Cheers,
Paul
“This e-mail is intended for the named addressee(s) only and may contain information about individuals or other sensitive information and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this email in error, kindly disregard the content of the message and notify the sender immediately. Please be aware that all email may be subject to recording and/or monitoring in accordance with relevant legislation.”
Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
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.
