Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-29 Thread Nuno Oliveira 

Sorry, I lost track of this one 

Ok so basically if a mime type is specified in the request it should override 
the override, I guess it makes sense.


As far I can tell the supported output formats are this ones:
http://docs.geoserver.org/latest/en/user/services/wfs/outputformats.html#wfs-output-formats

On 06/09/2018 12:17 AM, Ben Caradoc-Davies wrote:
Yes, but the question is whether a WFS setting of "application/gml+xml; 
version=3.2" should override a request parameter of outputFormat="text/xml; 
subtype=gml/3.2".


I think that a request with outputFormat="text/xml; subtype=gml/3.2" should 
override the WFS settings. That is, override the override.  :-)


Kind regards,
Ben.

On 08/06/18 21:34, Nuno Oliveira wrote:

Hi all,
thank you for following up on this Andrea and Ben.

The only propose of the override setting I add is to override the MIME type 
of GML 3.2 documents produced by GeoServer, it should not have any other impact.
Which means that clients will still need to invoke WFS GetFeature operations 
(or similar operations) using the output formats supported by GeoServer, and 
for those output formats that produce a GML 3.2 encoded document the override 
setting will be used if configured.


Did I answer your question Ben ?

Regards,

Nuno Oliveira

On 06/08/2018 12:45 AM, Ben Caradoc-Davies wrote:

On 08/06/18 11:24, Ben Caradoc-Davies wrote:
Nuno, was this intended? Should a different GML 3.2 Content-Type specified 
in outputformat override the WFS GML 3.2 Content-Type settings if it 
matches a supported option? No doubt users specifying outputformat=gml32 
will not expect "Content-Type: gml32", but the behaviour could be different 
for outputformat "text/xml; subtype=gml/3.2" or "text/xml".


"text/xml" alone will never work because then GeoServer will not be able to 
determine the GML version.


Kind regards,







--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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

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

---

Con riferimento alla normativa sul trattamento dei dati
personali (Reg. UE 2016/679 - Regolamento generale sulla
protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto,
gli eventuali allegati, etc.) è un dato la cui conoscenza
è riservata al/i solo/i destinatario/i indicati dallo
scrivente. Se il messaggio Le è giunto per errore, è
tenuta/o a cancellarlo, ogni altra operazione è illecita.
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to
which it is addressed and may contain information that
is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European
Regulation 2016/679 “GDPR” - copying, dissemination or
use of this e-mail or the information herein by anyone
other than the intended recipient is prohibited. If you
have received this email by mistake, please notify
us immediately by telephone or e-mail.


--
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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-10 Thread Rahkonen Jukka (MML) 
Hi,

There is some history about this issue in 
https://osgeo-org.atlassian.net/browse/GEOS-4011. It is hard to read because of 
text formatting has suffered from the change from Codehaus into OSGeo Jira, but 
also the whole question is messy. For example the desired 
outputFormat="text/xml; subtype=gml/3.2" written like that breaks the HTTP/1.1 
standard.

-Jukka Rahkonen-

-Alkuperäinen viesti-
Lähettäjä: Ben Caradoc-Davies [mailto:b...@transient.nz] 
Lähetetty: 9. kesäkuuta 2018 2:18
Vastaanottaja: Nuno Oliveira 
Kopio: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

Yes, but the question is whether a WFS setting of "application/gml+xml; 
version=3.2" should override a request parameter of outputFormat="text/xml; 
subtype=gml/3.2".

I think that a request with outputFormat="text/xml; subtype=gml/3.2" 
should override the WFS settings. That is, override the override.  :-)

Kind regards,
Ben.

On 08/06/18 21:34, Nuno Oliveira wrote:
> Hi all,
> thank you for following up on this Andrea and Ben.
> 
> The only propose of the override setting I add is to override the MIME 
> type of GML 3.2 documents produced by GeoServer, it should not have 
> any other impact.
> Which means that clients will still need to invoke WFS GetFeature 
> operations (or similar operations) using the output formats supported 
> by GeoServer, and for those output formats that produce a GML 3.2 
> encoded document the override setting will be used if configured.
> 
> Did I answer your question Ben ?
> 
> Regards,
> 
> Nuno Oliveira
> 
> On 06/08/2018 12:45 AM, Ben Caradoc-Davies wrote:
>> On 08/06/18 11:24, Ben Caradoc-Davies wrote:
>>> Nuno, was this intended? Should a different GML 3.2 Content-Type 
>>> specified in outputformat override the WFS GML 3.2 Content-Type 
>>> settings if it matches a supported option? No doubt users specifying
>>> outputformat=gml32 will not expect "Content-Type: gml32", but the 
>>> behaviour could be different for outputformat "text/xml; 
>>> subtype=gml/3.2" or "text/xml".
>>
>> "text/xml" alone will never work because then GeoServer will not be 
>> able to determine the GML version.
>>
>> Kind regards,
>>
> 

--
Ben Caradoc-Davies 
Director
Transient Software Limited <https://transient.nz/> New Zealand

--
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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-08 Thread Ben Caradoc-Davies 
Yes, but the question is whether a WFS setting of "application/gml+xml; 
version=3.2" should override a request parameter of 
outputFormat="text/xml; subtype=gml/3.2".


I think that a request with outputFormat="text/xml; subtype=gml/3.2" 
should override the WFS settings. That is, override the override.  :-)


Kind regards,
Ben.

On 08/06/18 21:34, Nuno Oliveira wrote:

Hi all,
thank you for following up on this Andrea and Ben.

The only propose of the override setting I add is to override the MIME 
type of GML 3.2 documents produced by GeoServer, it should not have any 
other impact.
Which means that clients will still need to invoke WFS GetFeature 
operations (or similar operations) using the output formats supported by 
GeoServer, and for those output formats that produce a GML 3.2 encoded 
document the override setting will be used if configured.


Did I answer your question Ben ?

Regards,

Nuno Oliveira

On 06/08/2018 12:45 AM, Ben Caradoc-Davies wrote:

On 08/06/18 11:24, Ben Caradoc-Davies wrote:
Nuno, was this intended? Should a different GML 3.2 Content-Type 
specified in outputformat override the WFS GML 3.2 Content-Type 
settings if it matches a supported option? No doubt users specifying 
outputformat=gml32 will not expect "Content-Type: gml32", but the 
behaviour could be different for outputformat "text/xml; 
subtype=gml/3.2" or "text/xml".


"text/xml" alone will never work because then GeoServer will not be 
able to determine the GML version.


Kind regards,





--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-08 Thread Nuno Oliveira 

Hi all,
thank you for following up on this Andrea and Ben.

The only propose of the override setting I add is to override the MIME type of 
GML 3.2 documents produced by GeoServer, it should not have any other impact.
Which means that clients will still need to invoke WFS GetFeature operations (or 
similar operations) using the output formats supported by GeoServer, and for 
those output formats that produce a GML 3.2 encoded document the override 
setting will be used if configured.


Did I answer your question Ben ?

Regards,

Nuno Oliveira

On 06/08/2018 12:45 AM, Ben Caradoc-Davies wrote:

On 08/06/18 11:24, Ben Caradoc-Davies wrote:
Nuno, was this intended? Should a different GML 3.2 Content-Type specified in 
outputformat override the WFS GML 3.2 Content-Type settings if it matches a 
supported option? No doubt users specifying outputformat=gml32 will not 
expect "Content-Type: gml32", but the behaviour could be different for 
outputformat "text/xml; subtype=gml/3.2" or "text/xml".


"text/xml" alone will never work because then GeoServer will not be able to 
determine the GML version.


Kind regards,



--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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

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

---

Con riferimento alla normativa sul trattamento dei dati
personali (Reg. UE 2016/679 - Regolamento generale sulla
protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto,
gli eventuali allegati, etc.) è un dato la cui conoscenza
è riservata al/i solo/i destinatario/i indicati dallo
scrivente. Se il messaggio Le è giunto per errore, è
tenuta/o a cancellarlo, ogni altra operazione è illecita.
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to
which it is addressed and may contain information that
is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European
Regulation 2016/679 “GDPR” - copying, dissemination or
use of this e-mail or the information herein by anyone
other than the intended recipient is prohibited. If you
have received this email by mistake, please notify
us immediately by telephone or e-mail.


--
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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-07 Thread Ben Caradoc-Davies 

On 08/06/18 11:24, Ben Caradoc-Davies wrote:
Nuno, was this intended? Should a different GML 3.2 Content-Type 
specified in outputformat override the WFS GML 3.2 Content-Type settings 
if it matches a supported option? No doubt users specifying 
outputformat=gml32 will not expect "Content-Type: gml32", but the 
behaviour could be different for outputformat "text/xml; 
subtype=gml/3.2" or "text/xml".


"text/xml" alone will never work because then GeoServer will not be able 
to determine the GML version.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-07 Thread Ben Caradoc-Davies 

Bart,

the default "Content-Type: application/gml+xml; version=3.2" is required 
by the WFS 2.0 standard:


http://docs.opengeospatial.org/is/09-025r2/09-025r2.html#52
"The optional outputFormat parameter specifies the format used to encode 
resources in the response to a query operation. The default value is 
"application/gml+xml; version=3.2" indicating that resources in the 
response document shall be encoded using GML (see ISO 19136:2007)."


You can set a different value in the WFS settings if you prefer the old 
non-standard-compliant behaviour:

http://docs.geoserver.org/latest/en/user/services/wfs/webadmin.html#override-gml-3-2-mime-type

It also looks from your report that you would like the option to be able 
to request a text/xml Content-Type for GML 3.2 regardless of this 
setting. I do not think GeoServer supports this because it chooses the 
language from outputformat (GML 3.2, GML 3.1, GeoJSON, ...) and then, 
for GML 3.2, the corresponding Content-Type from the WFS settings, which 
will not match the behaviour you expect.


Nuno, was this intended? Should a different GML 3.2 Content-Type 
specified in outputformat override the WFS GML 3.2 Content-Type settings 
if it matches a supported option? No doubt users specifying 
outputformat=gml32 will not expect "Content-Type: gml32", but the 
behaviour could be different for outputformat "text/xml; 
subtype=gml/3.2" or "text/xml".


Kind regards,
Ben.

On 08/06/18 02:09, Verbeeck Bart (AIV) wrote:

Dear List

Why is the default outputformat for a wfs (2.0.0) request in version 2.13.1 
"Content-Type: application/gml+xml; version=3.2"

It used to be (2.11.1 for instance) "Content-Type: text/xml; subtype=gml/3.2"

Even if I ask for "text/xml; subtype=gml/3.2", I receive application/gml+xml; 
version=3.2

Thanks for the info

Bart

-Original Message-
From: Nuno Oliveira [mailto:nuno.olive...@geo-solutions.it]
Sent: donderdag 7 juni 2018 9:40
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver WFS 2.0 combined with app-schema

Good point Ben, thanks for the heads up !

On 06/07/2018 01:07 AM, Ben Caradoc-Davies wrote:

On 07/06/18 08:37, Nuno Oliveira wrote:

Regarding this request you are asking for GML3 ... which implies WFS
1.1.0 and GML 3 schemas. Your target INSPIRE schema uses GML32, so
you should request for GML32 output IMHO:
https://geo.sv.rostock.de/inspire/us-govserv-schools/ows?service=WFS&;
version=2.0.0&request=GetFeature&typeNames=us-govserv-schools:Governm
entalService&*outputFormat=gml32*&maxFeatures=1



Tim,

in my email client, viewing as plain text, this URL contains "*" for
bold around "outputFormat=gml32". Be sure to remove these if your
email client adds them.  :-)

Kind regards,



--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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

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

---

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa 
che ogni circostanza inerente alla presente email (il suo contenuto, gli 
eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i 
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per 
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita.
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed 
and may contain information that is privileged, confidential or otherwise 
protected from disclosure. We remind that - as provided by European Regulation 
2016/679 “GDPR” - copying, dissemination or use of this e-mail or the 
information herein by anyone other than the intended recipient is prohibited. 
If you have received this email by mistake, please notify us immediately by 
telephone or e-mail.


--
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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sour

Re: [Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-07 Thread Andrea Aime 
As far as I remember, the old format was not compliant with the WFS 2.0 OGC
specification and got fixed as a consequence.

Cheers
Andrea

On Thu, Jun 7, 2018 at 4:09 PM, Verbeeck Bart (AIV) <
bart.verbe...@kb.vlaanderen.be> wrote:

> Dear List
>
> Why is the default outputformat for a wfs (2.0.0) request in version
> 2.13.1 "Content-Type: application/gml+xml; version=3.2"
>
> It used to be (2.11.1 for instance) "Content-Type: text/xml;
> subtype=gml/3.2"
>
> Even if I ask for "text/xml; subtype=gml/3.2", I receive
> application/gml+xml; version=3.2
>
> Thanks for the info
>
> Bart
>
> -Original Message-
> From: Nuno Oliveira [mailto:nuno.olive...@geo-solutions.it]
> Sent: donderdag 7 juni 2018 9:40
> To: geoserver-users@lists.sourceforge.net
> Subject: Re: [Geoserver-users] Geoserver WFS 2.0 combined with app-schema
>
> Good point Ben, thanks for the heads up !
>
> On 06/07/2018 01:07 AM, Ben Caradoc-Davies wrote:
> > On 07/06/18 08:37, Nuno Oliveira wrote:
> >> Regarding this request you are asking for GML3 ... which implies WFS
> >> 1.1.0 and GML 3 schemas. Your target INSPIRE schema uses GML32, so
> >> you should request for GML32 output IMHO:
> >> https://geo.sv.rostock.de/inspire/us-govserv-schools/ows?service=WFS&;
> >> version=2.0.0&request=GetFeature&typeNames=us-govserv-schools:Governm
> >> entalService&*outputFormat=gml32*&maxFeatures=1
> >
> >
> > Tim,
> >
> > in my email client, viewing as plain text, this URL contains "*" for
> > bold around "outputFormat=gml32". Be sure to remove these if your
> > email client adds them.  :-)
> >
> > Kind regards,
> >
>
> --
> Regards,
> Nuno Oliveira
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
>
> Nuno Miguel Carvalho Oliveira
> @nmcoliveira
> Software Engineer
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:  +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita.
> Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
>
>
> 
> --
> 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:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-
> requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.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:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/comm/
> userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-
> requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>



-- 

Regards, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.

[Geoserver-users] outputformat getfeature 2.0.0 (2.13.1)

2018-06-07 Thread Verbeeck Bart (AIV) 
Dear List

Why is the default outputformat for a wfs (2.0.0) request in version 2.13.1 
"Content-Type: application/gml+xml; version=3.2"

It used to be (2.11.1 for instance) "Content-Type: text/xml; subtype=gml/3.2"

Even if I ask for "text/xml; subtype=gml/3.2", I receive application/gml+xml; 
version=3.2

Thanks for the info

Bart

-Original Message-
From: Nuno Oliveira [mailto:nuno.olive...@geo-solutions.it] 
Sent: donderdag 7 juni 2018 9:40
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Geoserver WFS 2.0 combined with app-schema

Good point Ben, thanks for the heads up !

On 06/07/2018 01:07 AM, Ben Caradoc-Davies wrote:
> On 07/06/18 08:37, Nuno Oliveira wrote:
>> Regarding this request you are asking for GML3 ... which implies WFS 
>> 1.1.0 and GML 3 schemas. Your target INSPIRE schema uses GML32, so 
>> you should request for GML32 output IMHO:
>> https://geo.sv.rostock.de/inspire/us-govserv-schools/ows?service=WFS&;
>> version=2.0.0&request=GetFeature&typeNames=us-govserv-schools:Governm
>> entalService&*outputFormat=gml32*&maxFeatures=1
>
>
> Tim,
>
> in my email client, viewing as plain text, this URL contains "*" for 
> bold around "outputFormat=gml32". Be sure to remove these if your 
> email client adds them.  :-)
>
> Kind regards,
>

--
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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

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

---

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa 
che ogni circostanza inerente alla presente email (il suo contenuto, gli 
eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i 
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per 
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita.
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed 
and may contain information that is privileged, confidential or otherwise 
protected from disclosure. We remind that - as provided by European Regulation 
2016/679 “GDPR” - copying, dissemination or use of this e-mail or the 
information herein by anyone other than the intended recipient is prohibited. 
If you have received this email by mistake, please notify us immediately by 
telephone or e-mail.


--
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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.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:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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