And you could step through the code using the Browser's Developer Tools. A good place to set a breakpoint is in wfsGetFeatureQuery in components/map/index.js https://github.com/geomoose/gm3/blob/f9f6e3be5c93b26c62aaa39ecf59c9bfe4d948de/src/gm3/components/map/index.js#L346
I'm still convinced it's related to the SRS of the returned data.... In some of my old test mapbooks I see I have set <param name="srsname" value="EPSG:4326"/> (note the parameter name is "srsname"; I don't recall the significance of that parameter). ---------------------------------------- From: "R. Paul Warriner" <p...@warriner.us> Sent: 5/31/22 7:16 AM To: "geomoose-users@lists.osgeo.org" <geomoose-users@lists.osgeo.org> Subject: Re: [GeoMoose-users] Identify tool using TinyOWS layer TinyOWS 1.2.0 from git. The SQL appears valid, as I get all the correct attributes. Will do some debugging through the browser, and see if I find anything. Thanks, Paul From: Brent Fraser <bfra...@geoanalytic.com> Sent: Monday, May 30, 2022 9:15 PM To: R. Paul Warriner <p...@warriner.us>; geomoose-users@lists.osgeo.org Subject: Re: [GeoMoose-users] Identify tool using TinyOWS layer Some of the things I've done while trying to track down GeoMoose issues are: 1. Use the Developer tools in the browser to examine the network traffic between the browser and the server when doing an Identify. 2. Copy the last SQL command from the TinyOWS log into the SQL tool of pgAdmin and see what response it gives. Which version of TinyOWS are you using?
_______________________________________________ GeoMoose-users mailing list GeoMoose-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geomoose-users
