Hi Andrea,
sorry for delay, I was in holiday.
If I take the area of use from the site you mentioned (6 38.76, 12 83.92) I
can calculate a bbox as follow:
select st_astext(st_envelope(st_geometryfromtext('LINESTRING(6 38.76, 12
83.92 )', 4326))) and the result is:
POLYGON((6 38.76,6 83.92,12 83.92,12 38.76,6 38.76)).
Now, If I repeat the query on my data with this extent, there are a lot of
data out of it:
select count(*) from database.table_point where not
ST_Contains(st_geometryfromtext('POLYGON((6 38.76,6 83.92,12 83.92,12
38.76,6 38.76))', 4326), st_transform(geom, 4326)) --> 3660763
on the other hand, there are 1447847 inside it.
But, there another strange thing, the bbox of srs from geoserver:
(239323.44497139292 4290144.074117256, 760676.555028607 9320086.206909368)
is different from area of use from the site:
select st_astext(st_transform(st_geometryfromtext('POINT(6 38.76)', 4326),
25832)) --> POINT(239323.444971393 4294418.79680585)
select st_astext(st_transform(st_geometryfromtext('POINT(12 83.92)', 4326),
25832)) --> POINT(535459.483902448 9320086.20690937)
If I use the area of use from geoserver I receive the following results:
select st_astext(st_transform(st_geometryfromtext('POINT(239323.44497139292
4290144.074117256)', 25832), 4326)) --> POINT(6.00161054618446
38.7215301292457)
select st_astext(st_transform(st_geometryfromtext('POINT(760676.555028607
9320086.206909368)', 25832), 4326)) --> POINT(30.0743594610395
83.4965847858297)
and the extent will be POLYGON((6 38.72,6 83.5,30.07 83.5,30.07 38.72,6
38.72))
and the results wiil be:
select count(*) from database.table_point where not
ST_Contains(st_geometryfromtext('POLYGON((6 38.72,6 83.5,30.07 83.5,30.07
38.72,6 38.72))', 4326), st_transform(geom, 4326)) --> 716855
Finally, I am very confused. Where I am wronging?
Thanks a lot,
Matteo.
Matteo Cusmai
On Tue, Oct 31, 2017 at 11:24 AM, Andrea Aime <andrea.a...@geo-solutions.it>
wrote:
> On Tue, Oct 31, 2017 at 10:17 AM, Matteo Cusmai <cusmaimat...@gmail.com>
> wrote:
>
>> Hi all,
>> I am trying to check my data against epsg 25832.
>> Following the steps:
>>
>> 1. get bounds of epsg:25832 in lon, lat (https://epsg.io/25832) -->
>> (-16.1 32.88) (39.65 84.17)
>>
>> I'm quite surprised to see such an extension... its limit is 25 degrees
> west of the central meridian and
> a whopping 55 degrees large, while a UTM is supposed to be only 6 degrees
> large, 3 degrees on
> each side.
>
> This seems to be a bug in epsg.io though, if I check an official
> reference like https://www.epsg-registry.org/
> the "area of use" is reported to be what I expected it to be (too bad the
> blasted web site does not allow
> for a direct link, but see this screenshot:
>
> [image: Inline image 1]
>
> That said, the UTM math should be somewhat stable even so far away from
> the central meridian.
> I would like to see some sample data that can be used to reproduce the
> issue (in a ticket).
>
> Cheers
> Andrea
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> 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
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> 55054 Massarosa
> <https://maps.google.com/?q=Via+di+Montramito+3/A+55054+%C2%A0Massarosa&entry=gmail&source=g>
> (LU)
> phone: +39 0584 962313 <0584%20962313>
> fax: +39 0584 1660272 <0584%20166%200272>
> mob: +39 339 8844549 <339%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.
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
