There is another page here <https://docs.geoserver.org/latest/en/user/services/wfs/axis_order.html> that provides a breakdown of axis order expectations protocol by protocol. -- Jody Garnett
On Tue, 5 May 2020 at 14:43, Travis Brundage <[email protected]> wrote: > Hi all, > > Thanks for the clarification, that was indeed the issue. You are right, > because my layer expects lon/lat order, where as Andrea points out, the WFS > expects EPSG:4326 to be in lat/lon order - hence the confusion when I > explicitly pass the CRS. Without explicitly passing the CRS parameter, I > need to reorder the coordinates in my case to communicate it properly. > > Cheers, > Travis > > On Tue, May 5, 2020 at 1:35 AM Andrea Aime <[email protected]> > wrote: > >> On Tue, May 5, 2020 at 6:52 AM Travis Brundage <[email protected]> >> wrote: >> >>> The reference documentation >>> <https://docs.geoserver.org/stable/en/user/filter/ecql_reference.html#spatial-predicate> >>> says that it will default to the layer's defined CRS, though my guess is >>> the WFS request is defaulting to the underlying geom's native CRS in >>> PostGIS (which is different). >>> >> >> Nope, not native, it's what we declare in the WFS capabilities. Which, if >> you are using WFS 1.1 or 2.0, means 4326 in lat/lon order, since it uses a >> URN. >> This documentation page explains it better: >> https://docs.geoserver.org/latest/en/user/services/wfs/axis_order.html >> >> Cheers >> Andrea >> >> == >> >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf >> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa >> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 >> http://www.geo-solutions.it http://twitter.com/geosolutions_it >> ------------------------------------------------------- *Con riferimento >> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - >> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni >> circostanza inerente alla presente email (il suo contenuto, gli eventuali >> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i >> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per >> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le >> sarei comunque grato se potesse darmene notizia. This email is intended >> only for the person or entity to which it is addressed and may contain >> information that is privileged, confidential or otherwise protected from >> disclosure. We remind that - as provided by European Regulation 2016/679 >> “GDPR” - copying, dissemination or use of this e-mail or the information >> herein by anyone other than the intended recipient is prohibited. If you >> have received this email by mistake, please notify us immediately by >> telephone or e-mail.* >> > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
