From filakgang at gmail.com Tue May 6 14:04:36 2025 From: filakgang at gmail.com (Lowell Filak) Date: Tue, 6 May 2025 17:04:36 -0400 Subject: [GeoMoose-users] GeoMoose and WFS In-Reply-To: References: Message-ID: I have a partial fix for the issue involving incompatible coordinate results when using GeoMoose 3.13 and a non-Mapserver WFS. The fix can be implemented by adding the following JS to the index.html file and then calling convertCoordinates as needed. There may be a different fix but I didn't find it. Hopefully this will help those looking to use the latest GM with a WFS back end. -- index.html ... --- --- Select Features template example ... --- > Good day, > Thank you for all the hard work on the new version of GM. > This question involves GM 1.13.1 on Ubuntu 24.04.2 LTS installed using the > gm3-examples-3.13.1.zip and using QGIS Server 3.34.4 as the WMS and WFS > back end. > > The WMS GetMap, GetLegendGraphic and GetFeatureInfo are working correctly. > > I seem to have run into an issue that I need some help resolving with the > WFS requests. > > When adding a QGIS WFS layer to GM 3.13.1 the "Select Features" option does > not work if the map-source type is set to "wfs" but will return results > with the type set to "mapserver-wfs" and the typename set to > "ms:qgis-layer-name". > Using "mapserver-wfs" supplies a working solution for the initial > GetFeature request, although I do see periodic "RequestNotWellFormed" > exception from the server due to the "ms:" prefix. > > My diagnosis could be wrong, but it appears that the "mapserver-wfs" will > trigger an assumed projection of EPSG:4326. > With a type of "wfs" a getCode function is called that may be pointing to a > "projection" library that is not packaged into geomoose.js and > geomoose.min.js which results in an error. > > Unfortunately, the coordinates used in the results template, (for > app.zoomToExtent), seem flipped and projected into EPSG:3857. > > For instance, > Query by point is submitted to the WFS server as EPSG:4326, coordinates > -81.93383567601884 41.02354686335107. > The WFS reply for the feature bounding box is EPSG:4326, coordinates > -81.934173,41.02333098 -81.93359651,41.02375282. > The coordinates returned to the template are > 4566696.315337524,-16915358.3614889,4566743.27435152,-16914901.003045313 > > I can flip the coordinates in the template when making the zoomToExtent > call but have been unsuccessful in forcing zoomToExtent to use EPSG:3857 as > the projection. > > "app.zoomToExtent([-16915358.3614889,4566696.315337524,-16914901.003045313,4566743.27435152],'EPSG:3857')" > > Am I missing or doing something incorrect? > > Thank you for any help. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From flavio.rigolon at gmail.com Wed May 7 09:19:42 2025 From: flavio.rigolon at gmail.com (flavio rigolon) Date: Wed, 7 May 2025 18:19:42 +0200 Subject: [GeoMoose-users] GeoMoose 3.6.2 and Mapserver 8 Message-ID: Hi, when switching from Mapserver 7 to Mapserver 8 with GeoMoose 3.6.2 I noticed that relative references to mapfiles within the mapbook.xml must no longer be written with "./path/to/mapfile.map" but with "path/to/mapfile.map" thus omitting the "./". Initially I always obtain a "msCGILoadMap(): Web application error. CGI variable "map" fails to validate.": it was saying it cannot find the mapfile. Investigating with F12 tool on the browser I've found a "..../path/./to/mapfile.map" call and the problem was there. Indeed in the last demo code and data from GeoMoose site the path description omits the "./". Is this a change due to compatibility with Mapserver 8? I couldn't find it in the documentation, sorry if it's there and I didn't see it. thank in advance for any information flavio -- /"\ ASCII Ribbon Campaign \ / Respect for low technology. X Keep e-mail messages readable by any computer system. / \ Keep it ASCII. From chughes at co.lincoln.or.us Wed May 7 09:49:28 2025 From: chughes at co.lincoln.or.us (Christopher Hughes) Date: Wed, 7 May 2025 16:49:28 +0000 Subject: [GeoMoose-users] GeoMoose 3.6.2 and Mapserver 8 In-Reply-To: References: Message-ID: I don't think this is in the documentation, but it looks like that change was applied to the demo for the reason you mentioned. Update mapbook mapfile paths to avoid './' by klassenjs ? Pull Request #822 ? geomoose/gm3 Chris -- Chris Hughes GIS Analyst Lincoln County GIS Department 880 NE 7th St. l Newport, OR 97365 Tel: (541) 574 1283 ________________________________ From: GeoMoose-users on behalf of flavio rigolon via GeoMoose-users Sent: Wednesday, May 7, 2025 9:19 AM To: GeoMOOSE Users List Subject: [GeoMoose-users] GeoMoose 3.6.2 and Mapserver 8 Hi, when switching from Mapserver 7 to Mapserver 8 with GeoMoose 3.6.2 I noticed that relative references to mapfiles within the mapbook.xml must no longer be written with "./path/to/mapfile.map" but with "path/to/mapfile.map" thus omitting the "./". Initially I always obtain a "msCGILoadMap(): Web application error. CGI variable "map" fails to validate.": it was saying it cannot find the mapfile. Investigating with F12 tool on the browser I've found a "..../path/./to/mapfile.map" call and the problem was there. Indeed in the last demo code and data from GeoMoose site the path description omits the "./". Is this a change due to compatibility with Mapserver 8? I couldn't find it in the documentation, sorry if it's there and I didn't see it. thank in advance for any information flavio -- /"\ ASCII Ribbon Campaign \ / Respect for low technology. X Keep e-mail messages readable by any computer system. / \ Keep it ASCII. _______________________________________________ GeoMoose-users mailing list GeoMoose-users at lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geomoose-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From flavio.rigolon at gmail.com Wed May 7 10:16:34 2025 From: flavio.rigolon at gmail.com (flavio rigolon) Date: Wed, 7 May 2025 19:16:34 +0200 Subject: [GeoMoose-users] GeoMoose 3.6.2 and Mapserver 8 In-Reply-To: References: Message-ID: Many thanks Christopher! I didn't see it. Cheers flavio /"\ ASCII Ribbon Campaign \ / Respect for low technology. X Keep e-mail messages readable by any computer system. / \ Keep it ASCII. Il Mer 7 Mag 2025, 18:49 Christopher Hughes ha scritto: > I don't think this is in the documentation, but it looks like that change > was applied to the demo for the reason you mentioned. > > Update mapbook mapfile paths to avoid './' by klassenjs ? Pull Request > #822 ? geomoose/gm3 > > Chris > > -- > Chris Hughes > > GIS Analyst > Lincoln County GIS Department > 880 NE 7th St > . > l Newport, OR 97365 > Tel: (541) 574 1283 > > ------------------------------ > *From:* GeoMoose-users on behalf > of flavio rigolon via GeoMoose-users > *Sent:* Wednesday, May 7, 2025 9:19 AM > *To:* GeoMOOSE Users List > *Subject:* [GeoMoose-users] GeoMoose 3.6.2 and Mapserver 8 > > Hi, > when switching from Mapserver 7 to Mapserver 8 with GeoMoose 3.6.2 I > noticed that relative references to mapfiles within the mapbook.xml > must no longer be written with "./path/to/mapfile.map" but with > "path/to/mapfile.map" thus omitting the "./". > Initially I always obtain a "msCGILoadMap(): Web application error. > CGI variable "map" fails to validate.": it was saying it cannot find > the mapfile. Investigating with F12 tool on the browser I've found a > "..../path/./to/mapfile.map" call and the problem was there. > Indeed in the last demo code and data from GeoMoose site the path > description omits the "./". Is this a change due to compatibility with > Mapserver 8? > I couldn't find it in the documentation, sorry if it's there and I > didn't see it. > > thank in advance for any information > flavio > > -- > /"\ ASCII Ribbon Campaign > \ / Respect for low technology. > X Keep e-mail messages readable by any computer system. > / \ Keep it ASCII. > _______________________________________________ > GeoMoose-users mailing list > GeoMoose-users at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geomoose-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From filakgang at gmail.com Fri May 23 14:24:11 2025 From: filakgang at gmail.com (Lowell Filak) Date: Fri, 23 May 2025 17:24:11 -0400 Subject: [GeoMoose-users] GM 3 and QGIS Server as WFS Message-ID: Hopefully this will save someone hours in debugging in the future. OpenLayers, and subsequently GeoMoose, expects EPSG:4326 from a WFS server in Lat,Lon format. QGIS Server responds with Lon,Lat. To fix it, edit the index.html to load geomoose.js instead of geomoose.min.js. Edit geomoose.js to change all instances of "flatCoordinates.push(y, x, z)" to "flatCoordinates.push(x, y, z)". The fix is not eloquent but it's a fix. -------------- next part -------------- An HTML attachment was scrubbed... URL: From eadam at co.lincoln.or.us Fri May 23 15:00:11 2025 From: eadam at co.lincoln.or.us (Eli Adam) Date: Fri, 23 May 2025 22:00:11 +0000 Subject: [GeoMoose-users] GM 3 and QGIS Server as WFS In-Reply-To: References: Message-ID: Hi Lowell, Thanks for the info. Sorry to not have emailed sooner, there's a little additional information here, https://github.com/geomoose/gm3/issues/901 Best regards, Eli ________________________________ From: GeoMoose-users on behalf of Lowell Filak via GeoMoose-users Sent: Friday, May 23, 2025 2:24 PM To: geomoose-users at lists.osgeo.org Subject: [GeoMoose-users] GM 3 and QGIS Server as WFS Hopefully this will save someone hours in debugging in the future. OpenLayers, and subsequently GeoMoose, expects EPSG:4326 from a WFS server in Lat,Lon format. QGIS Server responds with Lon,Lat. To fix it, edit the index.html to load geomoose.js instead of geomoose.min.js. Edit geomoose.js to change all instances of "flatCoordinates.push(y, x, z)" to "flatCoordinates.push(x, y, z)". The fix is not eloquent but it's a fix. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chughes at co.lincoln.or.us Tue May 27 14:11:22 2025 From: chughes at co.lincoln.or.us (Christopher Hughes) Date: Tue, 27 May 2025 21:11:22 +0000 Subject: [GeoMoose-users] GM 3 and QGIS Server as WFS In-Reply-To: References: Message-ID: As an aside, instead of editing geomoose.js, you could also make the changes at the source and rebuild the minified javascript (geomoose.js is significantly larger and will take longer for the browser to load). Here's some documentation on how to do that on Windows - Developer Quickstart for Windows ? GeoMoose documentation. It basically involves installing NPM, cloning the geomoose repository, making your changes, and then building the javascript using NPM. Chris -- Chris Hughes GIS Analyst Lincoln County GIS Department 880 NE 7th St. l Newport, OR 97365 Tel: (541) 574 1283 ________________________________ From: GeoMoose-users on behalf of Eli Adam via GeoMoose-users Sent: Friday, May 23, 2025 3:00 PM To: geomoose-users at lists.osgeo.org ; Lowell Filak Subject: Re: [GeoMoose-users] GM 3 and QGIS Server as WFS Hi Lowell, Thanks for the info. Sorry to not have emailed sooner, there's a little additional information here, https://github.com/geomoose/gm3/issues/901 Best regards, Eli ________________________________ From: GeoMoose-users on behalf of Lowell Filak via GeoMoose-users Sent: Friday, May 23, 2025 2:24 PM To: geomoose-users at lists.osgeo.org Subject: [GeoMoose-users] GM 3 and QGIS Server as WFS Hopefully this will save someone hours in debugging in the future. OpenLayers, and subsequently GeoMoose, expects EPSG:4326 from a WFS server in Lat,Lon format. QGIS Server responds with Lon,Lat. To fix it, edit the index.html to load geomoose.js instead of geomoose.min.js. Edit geomoose.js to change all instances of "flatCoordinates.push(y, x, z)" to "flatCoordinates.push(x, y, z)". The fix is not eloquent but it's a fix. -------------- next part -------------- An HTML attachment was scrubbed... URL: