No, just construct a 3D geometry as your query filter, not a 3d box. select count(*) from "3dfloor" where geom &&& ST_Makeline(ST_MakePoint(0,0,0), ST_MakePoint(1000000,1000000,1));
I would imagine that should work fine and dodge this little nastiness. P On Thu, Jan 19, 2017 at 5:14 AM, Andrea Aime <andrea.a...@geo-solutions.it> wrote: > On Wed, Jan 18, 2017 at 5:13 PM, Rémi Cura <remi.c...@gmail.com> wrote: > >> Hey, >> I can't test right now, >> but : >> - you have the same srid for object and bbox right? >> > > Err... the box3d does not seem to have a srid, nor I could find a way to > assign one. > > >> - I remember Sandro discussing this case >> > > I searched in postgis-users before sending and again now, but could not > find any. > I've now searched in postgis-devel and found a thread you started on the > topic instead: > http://osgeo-org.1560.x6.nabble.com/BOX3D-strange-behaviour-td5251231.html > > So... it seems that the z gets dropped eh? I see a pull request to fix it > but it seems it has > been closed and the associated ticket marked as "wont' fix": > https://trac.osgeo.org/postgis/ticket/3466 > > Soo... should I do 2d filtering using && and then do the z filtering using > ST_Zmin/ST_ZMax? > > 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 <+39%200584%20962313> > fax: +39 0584 1660272 <+39%200584%20166%200272> > mob: +39 339 8844549 <+39%20339%20884%204549> > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > ------------------------------------------------------- > > _______________________________________________ > postgis-users mailing list > postgis-users@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/postgis-users >
_______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/postgis-users