Thanks again. Could you please help what to look for in the code of the UI?
Is SRS bounds stored in the SRS definition? Could it be that EPSG:23700 SRS
definition is not correct?
Laszlo
> On 2018. Apr 19., at 8:33, Andrea Aime <andrea.a...@geo-solutions.it> wrote:
>
> On Thu, Apr 19, 2018 at 6:45 AM, László Németh <nlaszlo1...@gmail.com
> <mailto:nlaszlo1...@gmail.com>> wrote:
> Hi Andrea,
>
> Thank you for your answer. I did some tests.
>
> 1. Deleted all workspaces in the workspaces configuration except the tested
> one.
> 2. Tried downloading Layer preview in KML for the problematic layer -> I get
> the error.
> 3. Deleted the layer and recreated as new. Geoserver did figure our the
> Native SRS based on DB info. If I use “compute from data” I get 0,0,-1-1,
> since the table is empty, so I used “compute from SRS” and I get
> -180,-90,180,90.
>
> This seems wrong, the native bbox should be native. If your data is in
> EPSG:23700 the bound coordinates should be too. I guess the UI is confused by
> the "reproject native to declared" setting, but I'm not sure,
> I did not work on adding the "compute from SRS" functionality.
>
> 4. Tried downloading Layer preview in KML for the problematic layer -> SUCCESS
> 5. Diffed the two featuretype XML files and the only difference I see that
> the one with the error has a line: <crs class="projected">EPSG:23700</crs> in
> the nativeboundingbox XML section.
>
> I attached the two XMLs. Removing the line and inserting <crs>EPSG:4326</crs>
> instead solved the problem on other problematic layers as well. Could you
> please clarify why?
>
> I don't know, my guess is that it's working by accident.
> Here is a sample from a working layer that I have locally, in a projected crs
> (but mind the projected coordinates here):
>
> <nativeBoundingBox>
> <minx>-840901.150827375</minx>
> <maxx>872858.801962177</maxx>
> <miny>2966776.48464754</miny>
> <maxy>5029485.2911404</maxy>
> <crs class="projected">EPSG:32654</crs>
> </nativeBoundingBox>
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
> <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://www.geo-solutions.it/>
> http://twitter.com/geosolutions_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
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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
