Thanks for the additions.
Torben
On Thu, Feb 22, 2018 at 1:44 AM, Andrea Aime <andrea.a...@geo-solutions.it>
wrote:
> Hi all,
> several new features and improvements were missing from the announcement,
> I've updated it on the blog, please see here:
>
> http://blog.geoserver.org/2018/02/22/geoserver-2-13-beta-released/
>
> Cheers
> Andrea
>
>
> On Thu, Feb 22, 2018 at 1:52 AM, Torben Barsballe <
> tbarsba...@boundlessgeo.com> wrote:
>
>> We are happy to announce the release of GeoServer 2.13-beta
>> <http://sourceforge.net/projects/geoserver/files/GeoServer/2.13-beta/>.
>> Downloads are available (zip
>> <http://sourceforge.net/projects/geoserver/files/GeoServer/2.13-beta/geoserver-2.13-beta-bin.zip/download>
>> , war
>> <http://sourceforge.net/projects/geoserver/files/GeoServer/2.13-beta/geoserver-2.13-beta-war.zip/download>
>> , and exe
>> <http://sourceforge.net/projects/geoserver/files/GeoServer/2.13-beta/geoserver-2.13-beta.exe/download>)
>> along with docs and extensions.
>>
>> This is a beta release of GeoServer made in conjunction with GeoTools
>> 19-beta.
>>
>> We want to encourage people to test the release thoroughly and report
>> back any issue found. With no further delay, let’s see what’s new, that is,
>> what is there to test!
>> Isolated Workspaces
>>
>> The concept of an “Isolated Workspaces” has been added to GeoServer, to
>> allow for reusing a namespace among multiple workspaces. In particular, an
>> isolated workspace allows reuse of a namespace already used by another
>> workspace, but its resources (layers, styles, etc …) can only be retrieved
>> when using that workspace’s virtual services and will only show up in those
>> virtual service capabilities documents.
>>
>> When reusing a namespace among workspaces, exactly one of those must be
>> non-isolated, and the rest must be isolated; i.e. isolated workspaces have
>> no restrictions in namespaces usage but the existing restrictions still
>> apply for non isolated workspaces.
>>
>> For more details, refer to the original proposal
>> <https://github.com/geoserver/geoserver/wiki/GSIP-165---Add-isolated-workspaces-concept-to-GeoServer>
>> .
>> GeoWebCache REST API
>>
>> Two new endpoints have been added to the GeoWebCache REST API:
>>
>> - /gwc/rest/blobstores:
>> - GET /gwc/rest/blobstores for a list of the blobstores
>> - GET /gwc/rest/blobstores/{blobStoreName} for details about a
>> single blobstore
>> - PUT /gwc/rest/blobstores/{blobStoreName} to create or update a
>> blobstore
>> - DELETE /gwc/rest/blobstores/{blobStoreName} to remove a blobstore
>> - /gwc/rest/gridsets:
>> - GET /gwc/rest/gridsets for a list of the gridsets
>> - GET /gwc/rest/gridsets/{gridSetName} for details about a single
>> gridset
>> - PUT /gwc/rest/gridsets/{gridSetName} to create or update a
>> gridset
>> - DELETE /gwc/rest/gridsets/{gridSetName} to remove a gridset
>>
>> API docs for these endpoints will be added to the GeoServer documentation
>> shortly. Until then, the request body syntax for PUT requests closely
>> matched the equivalent structures in geowebcache.xml: BlobStores
>> <http://geowebcache.org/docs/latest/configuration/storage.html#blobstore-configuration>
>> and GridSets
>> <http://geowebcache.org/docs/latest/concepts/gridsets.html#corresponding-xml>
>> .
>>
>> The ArcGISCache backed layers are now also configurable via the REST API.
>>
>> This release sees a major reworking of the configuration system in
>> GeoWebCache that will allow for plugging in alternate configuration
>> persistence mechanisms in future. While these changes should be largely
>> invisible to users, it is a huge update that impacts all of GeoWebCache.
>> However, due to these changes, we ask that you *please test the embedded
>> GeoWebCache*.
>> UI Improvements
>>
>> Entering in URLs for data files has been improved with autocomplete – now
>> GeoServer will scan the path that has already been typed, and suggest
>> existing files within that path.
>> <http://blog.geoserver.org/wp-content/uploads/2018/02/34523743-0b6ba4b2-f099-11e7-99bd-1af27da0ddea.png>
>>
>> In addition, autocomplete support has been added to a number of dropdowns
>> which contain a long list of values, such as stores or layers. You can now
>> start typing the name of an option, and the visible options will be
>> filtered to match.
>> <http://blog.geoserver.org/wp-content/uploads/2018/02/store_chooser.png>
>> Removed OS X installers
>>
>> Due to lack of resources and interest, the OS X dmg installers are no
>> longer being built. OS X users can still use
>> <http://docs.geoserver.org/stable/en/user/installation/linux.html#installation>
>> the system-independent binary
>> <http://sourceforge.net/projects/geoserver/files/GeoServer/2.13-beta/geoserver-2.13-beta-bin.zip/download>
>> .
>> New community modules
>>
>> The 2.13 series comes with a few new community modules, in particular:
>>
>> - Do you want to generate GHRSST compliant outputs from GHRSST
>> inputs? Try out the new GHRSST NetCDF output community module.
>> - There is also a new community module
>>
>> <http://docs.geoserver.org/latest/en/user/community/nsg-profile/index.html>
>> introducing NSG profiles for the WFS and WMTS services.
>>
>> Not that community modules are not part of the release; instead you can
>> find them in the nightly builds
>> <https://build.geoserver.org/geoserver/2.13.x/>.
>> Other assorted improvements
>>
>> There are many bug fixes and improvements to look at in the release notes
>> <https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=10000&version=16702>,
>> cherry picking a few here:
>>
>> - Autocomplete support for dropdowns with long lists of values
>> - Upgrade JDom library
>> - REST API CORS support
>> - REST improvements to list all layers in a workspace, and include
>> the workspace prefix in layer listings
>> - Style POST does not support non-SLD styles
>> - Add WMTS RESTful API
>> - Installing the XSLT plugin may cause random REST endpoints to
>> report lists with transforms/transform
>> - WCS 1.0.0 does not handle FORMAT parameter properly
>> - Cache small amount of features in memory to avoid repeated data
>> scans in GetFeature requests
>> - Allow requesting both OL3 and OL2 from the client side
>> - Simple feature GML 3.2.1 output schema-invalid as geometries lack
>> mandatory gml:id
>> - GeoPackage generated via WPS has y coordinates starting from bottom
>> left
>> - Numerous WFS 2.0 bugfixes
>> - Submitting a seed/truncate request for a tile layer results in a
>> “406, not acceptable”
>> - GWC Seed Form returns “Chunk [] is not a valid entry” message error
>> when seeding a layer.
>> - Demo Page does not send password
>>
>> Test, test, test!
>>
>> Now that you know about all the goodies, please go, download and test
>> <http://sourceforge.net/projects/geoserver/files/GeoServer/2.13-beta/> your
>> favourite ones. Let us know how it went!
>> About GeoServer 2.12
>>
>> GeoServer 2.13 is scheduled for March 2018 release.
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> 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
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> 55054 Massarosa
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> (LU)
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39 339 8844549 <+39%20339%20884%204549>
>
> 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.
>
>
------------------------------------------------------------------------------
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
