Hi,
I found a new funny detail from WFS specs. Have a look at WFS 1.1.0 standard:
The element is used to request a capabilities document from a
web feature service.
It is defined by the following XML Schema fragment:
Notice that “service” is optional. Because of that the /ows endpoint
On Tue, Mar 15, 2016 at 3:46 PM, Damiano Albani
wrote:
> Yes, it would be nice to have that discussion about the service endpoints.
> Although the current behavior provides a lot a flexibility (simply by
> adding the appropriate "&service=XYZ"), it makes things messy and not very
> logical in my
On Tue, Mar 15, 2016 at 3:29 PM, Andrea Aime
wrote:
> By the way, the usage of "ows" in the caps documents has been ignored for
> so much time that I guess it could
> be put on the discussion table again. I have no strong opinion on the
> matter, to GeoServer wms/wcs/wps/ows
> are all the same (y
On Tue, Mar 15, 2016 at 3:32 PM, Damiano Albani
wrote:
> On Tue, Mar 15, 2016 at 3:19 PM, Andrea Aime > wrote:
>
>>
>> Only because they were developed by different people in different times.
>> That said, the "right" version is almost the WMS one,
>> it should be using "ows", the service named
On Tue, Mar 15, 2016 at 3:19 PM, Andrea Aime
wrote:
>
> Only because they were developed by different people in different times.
> That said, the "right" version is almost the WMS one,
> it should be using "ows", the service named endpoints wms/wfs/wps and so
> on are kept, as far as I know, for
By the way, the usage of "ows" in the caps documents has been ignored for
so much time that I guess it could
be put on the discussion table again. I have no strong opinion on the
matter, to GeoServer wms/wcs/wps/ows
are all the same (you can literally use geoserver/workspace/wms to make a
wfs reque
On Tue, Mar 15, 2016 at 2:38 PM, Damiano Albani
wrote:
> Hello,
>
> Looking at the content of the GetCapabilities response for WMS, I saw
> that Request >> OnlineResource URL follows a different pattern than other
> protocols as WFS and WPS.
>
> For example, compare:
>
> http://host/geoserver/w
Hello,
Looking at the content of the GetCapabilities response for WMS, I saw
that Request >> OnlineResource URL follows a different pattern than other
protocols as WFS and WPS.
For example, compare:
http://host/geoserver/workspace/*ows?SERVICE=WMS&*"/>
http://host/geoserver/workspace/*wfs
