[mapserver-users] WFS GeoJSON Output Missing numberMatched

2019-06-05 Thread Seth G
Hi all, I'm currently working on a front-end grid that requests features via WFS 2.0 and loads them using OpenLayers. OpenLayers 4 doesn't support parsing of GML3 used by WFS 2.0, but I can return features as GeoJSON by setting the output format as follows: OUTPUTFORMAT NAME "geojs

Re: [mapserver-users] WFS GeoJSON Output Missing numberMatched

2019-06-05 Thread Seth G
Thanks Even for both suggestions. Using resultType=hits and caching the result for the duration of the session could be an option for read-only layers (and would likely speed things up as setting "wfs_compute_number_matched" is not recommended for performance reasons). Editable layers would re

Re: [mapserver-users] WFS GeoJSON Output Missing numberMatched

2019-06-05 Thread Even Rouault
On mercredi 5 juin 2019 23:43:22 CEST Seth G wrote: > Hi all, > > I'm currently working on a front-end grid that requests features via WFS 2.0 > and loads them using OpenLayers. OpenLayers 4 doesn't support parsing of > GML3 used by WFS 2.0, but I can return features as GeoJSON by setting the > ou

Re: [mapserver-users] WFS GeoJSON Output Missing numberMatched

2019-06-07 Thread Julian Hollingbery
sing from the GeoJSON output. Any ideas or hints appreciated, Seth -- web:http://geographika.co.uk twitter: @geographika ------------------ Message: 3 Date: Thu, 06 Jun 2019 00:39:03 +0200 From: "Seth G" To: "Even Rouault" , mapserver-users@lists.osge

Re: [mapserver-users] WFS GeoJSON Output Missing numberMatched

2019-06-07 Thread Seth G
eep asking until > you get a page with zero features? > > Regards, > Julian > > -Oprindelig meddelelse- > Date: Wed, 05 Jun 2019 23:43:22 +0200 > From: "Seth G" > To: mapserver-users@lists.osgeo.org > Subject: [mapserver-users] WFS GeoJSON Out