Re: [mapserver-users] WFS OUTPUTFORMATs and PROPERTYNAME

[Seth G]

Thanks Jukka and Even for the quick replies and suggestions. 
It looks like the issue relates to the MSSQL driver used by the layers I'm 
testing with - apologies I jumped to the conclusion it wasn't implemented for 
OUTPUTFORMATs. 

Findings are as follows:

- The output is correct when I use GML output and the MSSQL driver (which I 
believe defaults to OUTPUTFORMAT=text/xml) - PROPERTYNAME correctly limits 
which fields are in the GML/XML. 
- For any other format PROPERTYNAME is ignored and all gml_include_items are 
returned. This includes Shapefile, Spatialite, and CSV (the same SQL is run on 
the database in both cases)
- Performance on the exports is very slow for Spatialite. I get one of these 
calls for every feature in the layer: "msMSSQL2008LayerGetShape called for 
shapeindex = 816457", and it takes 161.799s
- Shapefile also produces the msMSSQL2008LayerGetShape calls but runs in 26.595s
- Adding  =1 works correctly in all cases, but the time to produce 
the exports is almost identical to a full export

All tests were carried out on the command line on a Windows server. I'm using 
MS 7.04.

Seth


--
web:http://geographika.co.uk
twitter: @geographika

On Mon, Jul 2, 2018, at 9:25 PM, Even Rouault wrote:
> On lundi 2 juillet 2018 20:55:11 CEST Seth G wrote:
> > Hi all,
> > 
> > A question on WFS GetFeature requests and the OUTPUTFORMAT type.
> > 
> > All fields specified in gml_include_items are returned when creating non-GML
> > outputs such as Shapefile and GeoJSON even when setting the PROPERTYNAME
> > parameter in the request to reduce which fields should be added to the
> > output. The docs at
> > http://mapserver.org/output/ogr_output.html#layer-metadata note you can use
> >  gml_include_items but makes no mention they can't be overridden with
> > PROPERTYNAME .
> > 
> > As OUTPUT format is an extension to WFS
> > (http://mapserver.org/ogc/wfs_server.html#mapserver-wfs-extensions) is this
> > logic by design?
> > 
> > Maybe a note should be added to
> > http://mapserver.org/ogc/wfs_server.html#to-do-items-and-known-limitations
> > ?
> 
> Seth,
> 
> From a quick test, I don't see a difference in behaviour between OGR output 
> and native GML one, based on msautotest wfs_ogr.map
> 
> $ mapserv 
> QUERY_STRING="map=wfs_ogr.map=WFS=1.1.0=GetFeature=popplace=CSV=NAME=1"
> Content-Disposition: attachment; filename=result.csv
> Content-Type: text/csv
> 
> WKT,NAME
> "POINT (2281604.25 340848.9375)","""Tignish"
> 
> 
> $ mapserv 
> QUERY_STRING="map=wfs_ogr.map=WFS=1.1.0=GetFeature=popplace=NAME=1"
> Content-Type: text/xml; subtype=gml/3.1.1; charset=UTF-8
> 
> 
> xmlns:ms="http://mapserver.gis.umn.edu/mapserver;
>xmlns:gml="http://www.opengis.net/gml;
>xmlns:wfs="http://www.opengis.net/wfs;
>xmlns:ogc="http://www.opengis.net/ogc;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver http://
> localhost/path/to/wfs_simple?
> SERVICE=WFSVERSION=1.1.0REQUEST=DescribeFeatureTypeTYPENAME=popplaceOUTPUTFORMAT=text/
> xml;%20subtype=gml/3.1.1  http://www.opengis.net/wfs http://
> schemas.opengis.net/wfs/1.1.0/wfs.xsd">
>   
>   
>   2281604.25 
> 340848.937500
>   2281604.25 
> 340848.937500
>   
>   
> 
>   
> Tignish
>   
> 
> 
> 
> Even
> 
> -- 
> Spatialys - Geospatial professional services
> http://www.spatialys.com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] [Geomoose-users] OSGeo Local (TCMUG) Meeting schedule.

[Basques, Bob (CI-StPaul)]

All,

We had a nice turnout at the last meeting, even snuck in a couple of guests too.

The next meeting is scheduled for:

 Jul 11th.
 Location : BlackStack Brewing.
Time: 4:30

See you there.

bobb




An inventor is simply a fellow who doesn’t take his education too seriously.
—Charles F. Kettering

___
Geomoose-users mailing list
geomoose-us...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geomoose-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WMS DescribeLayer: MapServer requires WIDTH and HEIGHT params?

[Edward Mac Gillavry]

Hi Jonathan,


Thanks for pointing me to the Demo MapServer. That instance works as expected 
without the WIDTH and HEIGHT params. We're seeing the erroneous behaviour on 
both a MapServer 7.0.4 and a MapServer 7.0.7 instance. Don't see anything in 
the release notes / changelogs that would indicate changes to that part of the 
code either...


Tried 
http://demo.mapserver.org/cgi-bin/wms?SERVICE=WMS=1.3.0=DescribeLayer=country_bounds_version=1.1.0
 as well just to see whether vector or raster makes a difference, but the Demo 
MapServer behaves alright.

>From https://github.com/mapserver/mapserver/issues/1157 I learned that I 
>should be adding the "ows_onlineresource" keyword to the metadata section. 
>Will report back if that resolves the issue...

Cheers,

Edward





From: mapserver-users  on behalf of 
Jonathan Moules 
Sent: Monday, July 2, 2018 10:02 PM
To: mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] WMS DescribeLayer: MapServer requires WIDTH and 
HEIGHT params?


Hi Edward,


They don't seem to be required on the Demo MapServer (which is MapServer 
version 7.0.6):

http://demo.mapserver.org/cgi-bin/wms_landsat?request=DescribeLayer=WMS=1.3.0_version=1.1.0=WMS_raster


For SLD 1.1.0, looking at the spec, Table 1 and 2 both list the "Parameters in 
DescribeLayer operation request". The required ones (beyond the standard 
service/request/version) are:
layers, sld_version

There are no others, either mandatory or optional.


The SLD 1.0 spec is less clear about what's going on, but when I changed the 
sld_version=1.0.0, Mapserver excepted telling me only 1.1.0 is supported.


Hope that helps in some way,

Cheers,

Jonathan

On 2018-07-02 16:35, Edward Mac Gillavry wrote:

Dear list,


We're currently investigating an error message we get from the WMS service when 
we execute a DescribeLayer request. It appears MapServer requires WIDTH and 
HEIGHT parameters to be present:


https://github.com/mapserver/mapserver/blob/branch-7-0/mapwms.c#L1705


However, according to the SLD specs, these are NOT required:


http://portal.opengeospatial.org/files/?artifact_id=22364


Am I interpreting the code or SLD spec incorrectly? Or should I go ahead and 
remove these checks and provide a PR?


Many thanks,


Edward




___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WMS DescribeLayer: MapServer requires WIDTH and HEIGHT params?

[Jonathan Moules]

Hi Edward,


They don't seem to be required on the Demo MapServer (which is MapServer 
version 7.0.6):


http://demo.mapserver.org/cgi-bin/wms_landsat?request=DescribeLayer=WMS=1.3.0_version=1.1.0=WMS_raster


For SLD 1.1.0, looking at the spec, Table 1 and 2 both list the 
"Parameters in DescribeLayer operation request". The required ones 
(beyond the standard service/request/version) are:

layers, sld_version

There are no others, either mandatory or optional.


The SLD 1.0 spec is less clear about what's going on, but when I changed 
the sld_version=1.0.0, Mapserver excepted telling me only 1.1.0 is 
supported.



Hope that helps in some way,

Cheers,

Jonathan


On 2018-07-02 16:35, Edward Mac Gillavry wrote:


Dear list,


We're currently investigating an error message we get from the WMS 
service when we execute a DescribeLayer request. It appears MapServer 
requires WIDTH and HEIGHT parameters to be present:



https://github.com/mapserver/mapserver/blob/branch-7-0/mapwms.c#L1705


However, according to the SLD specs, these are NOT required:


http://portal.opengeospatial.org/files/?artifact_id=22364


Am I interpreting the code or SLD spec incorrectly? Or should I go 
ahead and remove these checks and provide a PR?



Many thanks,


Edward




___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users


___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS OUTPUTFORMATs and PROPERTYNAME

[Rahkonen Jukka (MML)]

Hi,

Do you get what you want with GML output? Have you tried if using 
ows_include_items would make any difference? And how do those attributes appear 
in the DescribeFeatureType? Attributes which are "not null" must appear in the 
response by WFS standard.

-Jukka Rahkonen- 


-Alkuperäinen viesti-
Lähettäjä: mapserver-users [mailto:mapserver-users-boun...@lists.osgeo.org] 
Puolesta Seth G
Lähetetty: 2. heinäkuuta 2018 21:55
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: [mapserver-users] WFS OUTPUTFORMATs and PROPERTYNAME

Hi all,

A question on WFS GetFeature requests and the OUTPUTFORMAT type. 

All fields specified in gml_include_items are returned when creating non-GML 
outputs such as Shapefile and GeoJSON even when setting the PROPERTYNAME 
parameter in the request to reduce which fields should be added to the output. 
The docs at http://mapserver.org/output/ogr_output.html#layer-metadata note you 
can use  gml_include_items but makes no mention they can't be overridden with 
PROPERTYNAME . 

As OUTPUT format is an extension to WFS 
(http://mapserver.org/ogc/wfs_server.html#mapserver-wfs-extensions) is this 
logic by design?

Maybe a note should be added to 
http://mapserver.org/ogc/wfs_server.html#to-do-items-and-known-limitations ?

Regards,

Seth

--
web:http://geographika.co.uk
twitter: @geographika
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WFS OUTPUTFORMATs and PROPERTYNAME

[Seth G]

Hi all,

A question on WFS GetFeature requests and the OUTPUTFORMAT type. 

All fields specified in gml_include_items are returned when creating non-GML 
outputs such as Shapefile and GeoJSON even when setting the PROPERTYNAME 
parameter in the request to reduce which fields should be added to the output. 
The docs at http://mapserver.org/output/ogr_output.html#layer-metadata note you 
can use  gml_include_items but makes no mention they can't be overridden with 
PROPERTYNAME . 

As OUTPUT format is an extension to WFS 
(http://mapserver.org/ogc/wfs_server.html#mapserver-wfs-extensions) is this 
logic by design?

Maybe a note should be added to 
http://mapserver.org/ogc/wfs_server.html#to-do-items-and-known-limitations ?

Regards,

Seth

--
web:http://geographika.co.uk
twitter: @geographika
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WMS DescribeLayer: MapServer requires WIDTH and HEIGHT params?

[Edward Mac Gillavry]

Dear list,


We're currently investigating an error message we get from the WMS service when 
we execute a DescribeLayer request. It appears MapServer requires WIDTH and 
HEIGHT parameters to be present:


https://github.com/mapserver/mapserver/blob/branch-7-0/mapwms.c#L1705


However, according to the SLD specs, these are NOT required:


http://portal.opengeospatial.org/files/?artifact_id=22364


Am I interpreting the code or SLD spec incorrectly? Or should I go ahead and 
remove these checks and provide a PR?


Many thanks,


Edward

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users