[Geoserver-devel] Last minute 2.7.0 backports

Travis and Jody,

in your capacity as release managers for 2.7.0, I would like your approval, if you think it safe, for some last minute 2.7.0 backports of documentation improvements, WFS 2.0 demo requests, and minor app-schema test pom.xml preening. No code changes:
https://github.com/geoserver/geoserver/pull/967

These non-code changes are optional but should be quite safe. The WFS 2.0 demo requests and filter documentation are in response to discussion on the mailing list (from 2013!):
http://osgeo-org.1560.x6.nabble.com/Creating-Geoserver-Layer-from-custom-WFS-td5076277.html

I would also like to take this opportunity to call for anyone else with last minute backports to make themselves known.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand

Documentation back ports yes!

WFS 2.0 demos request yes (no real danger for client applications - there was also some broken demo requests in the 2.7-RC1 that may need fixing).

test pom.xml preening yes (no real danger for client applications).

There is one pull request from travis (addressing a catalog loading regression) that should make the cut …

… however Andrea had a good idea (to make this a global setting rather than a -D system property - not sure if that works (because if we turn the setting on the existing catalog may not load!).

···

On 9 March 2015 at 13:39, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Travis and Jody,

in your capacity as release managers for 2.7.0, I would like your approval, if you think it safe, for some last minute 2.7.0 backports of documentation improvements, WFS 2.0 demo requests, and minor app-schema test pom.xml preening. No code changes:
https://github.com/geoserver/geoserver/pull/967

These non-code changes are optional but should be quite safe. The WFS 2.0 demo requests and filter documentation are in response to discussion on the mailing list (from 2013!):
http://osgeo-org.1560.x6.nabble.com/Creating-Geoserver-Layer-from-custom-WFS-td5076277.html

I would also like to take this opportunity to call for anyone else with last minute backports to make themselves known.

Kind regards,


Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand


Jody Garnett

On Mon, Mar 9, 2015 at 10:01 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Documentation back ports yes!

WFS 2.0 demos request yes (no real danger for client applications - there
was also some broken demo requests in the 2.7-RC1 that may need fixing).

test pom.xml preening yes (no real danger for client applications).

There is one pull request from travis (addressing a catalog loading
regression) that should make the cut ...

.. however Andrea had a good idea (to make this a global setting rather
than a -D system property - not sure if that works (because if we turn the
setting on the existing catalog may not load!).

Same will happen if you set the sysvar that enables the checks... it's
easier for the admin to find (which its pros and cons), and would allow us
to lock down
the data dir by default in the release data dir for newer installations,
while preserving backwards compat for older ones.
The sysvar instead would have to be stay disabled forever to preserve
backwards compat, so we would end up locking the file names only if the
admin explicitly set the sysvar.

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
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.

-------------------------------------------------------

On 10/03/15 10:01, Jody Garnett wrote:

there was also some broken demo requests in the 2.7-RC1 that may need fixing

Jody, which requests were broken? I was only aware of OL3 preview problems.

The only demo request problems I encountered were caused by my browser configuration and were fixed by disabling NoScript application boundary enforcer.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand

Hi,
At least WFS_transactionInsert.xml and WFS_transactionUpdateGeometry use metric coordinates in geometries even the srsName is EPSG:4326. There are also some requests which do work with Geoserver but they are not valid according to standards. Like WFS_getFeatureBBOX.url which is missing mandatory &SERVICE=WFS:

http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=topp:states&propertyName=STATE_NAME,PERSONS&BBOX=-75.102613,40.212597,-72.361859,41.512517,EPSG:4326

-Jukka Rahkonen-
________________________________________
Ben Caradoc-Davies wrote:

On 10/03/15 10:01, Jody Garnett wrote:

there was also some broken demo requests in the 2.7-RC1 that may need fixing

Jody, which requests were broken? I was only aware of OL3 preview problems.

The only demo request problems I encountered were caused by my browser
configuration and were fixed by disabling NoScript application boundary
enforcer.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Jukka,

while we are on the topic of missing parameters, not one demo URL request contains a NAMESPACE (WFS 1.1.0) or NAMESPACES (WFS 2.0.0) parameter to define the namespace prefixes used for feature types and property names. GeoServer is by default quite permissive in this regard; it is happy to guess that an undefined prefix matches a workspace of the same name. However, XML namespace prefixes are always local to an instance document, and never have meaning across services. I do not think that deegree will accept these requests.

Kind regards,
Ben.

On 10/03/15 11:46, Rahkonen Jukka (MML) wrote:

Hi,
At least WFS_transactionInsert.xml and WFS_transactionUpdateGeometry use metric coordinates in geometries even the srsName is EPSG:4326. There are also some requests which do work with Geoserver but they are not valid according to standards. Like WFS_getFeatureBBOX.url which is missing mandatory &SERVICE=WFS:

http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=topp:states&propertyName=STATE_NAME,PERSONS&BBOX=-75.102613,40.212597,-72.361859,41.512517,EPSG:4326

-Jukka Rahkonen-
________________________________________
Ben Caradoc-Davies wrote:

On 10/03/15 10:01, Jody Garnett wrote:

there was also some broken demo requests in the 2.7-RC1 that may need fixing

Jody, which requests were broken? I was only aware of OL3 preview problems.

The only demo request problems I encountered were caused by my browser
configuration and were fixed by disabling NoScript application boundary
enforcer.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand

Jukka,

I checked and the values supplied in these demo requests are faithfully inserted into the data set, honouring the supplied CRS. I can also confirm that the numbers are bogus, misleading, and look like eastings and northings; they should be changed.

Kind regards,
Ben.

On 10/03/15 11:46, Rahkonen Jukka (MML) wrote:

At least WFS_transactionInsert.xml and WFS_transactionUpdateGeometry use metric coordinates in geometries even the srsName is EPSG:4326.

--
Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand

On 10/03/15 14:33, Ben Caradoc-Davies wrote:

I checked and the values supplied in these demo requests are faithfully
inserted into the data set, honouring the supplied CRS.

I take that back. Even before the transactions, there is something weird going on: all the coordinates are in three dimensions. WFS 1.1 and 2.0 requests confirm that this is a 3D CRS (tested on master):

Each point has 3 coordinates, with latitude duplicated as z:
http://localhost:8080/geoserver/wfs?service=WFS&version=1.0.0&request=GetFeature&typename=topp:tasmania_roads

srsDimension="3", and latitude is duplicated as z (WFS 1.1):
http://localhost:8080/geoserver/wfs?service=WFS&version=1.1.0&request=GetFeature&typename=topp:tasmania_roads

srsDimension="3", and latitude is duplicated as z (WFS 2.0):
http://localhost:8080/geoserver/wfs?service=WFS&version=2.0.0&request=GetFeature&typenames=topp:tasmania_roads

Can anyone please explain why this might be the case? I do not see anything unusual in the layer settings. I will not fix the values until I understand whether this is a bug,

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Software Engineer
Transient Software <http://transient.nz>
New Zealand

-----Original Message-----
From: Ben Caradoc-Davies [mailto:ben@…4191…]
Sent: 09 March 2015 23:25
To: Rahkonen Jukka (MML); Jody Garnett
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Last minute 2.7.0 backports

Jukka,

while we are on the topic of missing parameters, not one demo URL
request contains a NAMESPACE (WFS 1.1.0) or NAMESPACES (WFS 2.0.0)
parameter to define the namespace prefixes used for feature types and
property names. GeoServer is by default quite permissive in this regard;
it is happy to guess that an undefined prefix matches a workspace of the
same name. However, XML namespace prefixes are always local to an
instance document, and never have meaning across services. I do not
think that deegree will accept these requests.

The correct namespaces WFS 2.0.0 KVP Get requests will not currently work (https://jira.codehaus.org/browse/GEOS-6885) so you can't put that as a demo request yet.

Marcus Sen
British Geological Survey
Keyworth
Nottingham
NG12 5GG

Web: http://www.bgs.ac.uk

This message (and any attachments) is for the recipient only. NERC is subject to the Freedom of Information Act 2000 and the contents of this email and any reply you make may be disclosed by NERC unless it is exempt from release under the Act. Any material supplied to NERC may be stored in an electronic records management system.