Hello All,
I am seeing something that I’m not sure about.
A GFI request to a layer through Geoserver with:
I’m using geoserver 2.7.2 on Ubuntu 14.04 with postgres 9.3.
Does anybody know why this massive response time difference would be?
Thanks,
Toby
Hi
El 20 jul 2016, a las 06:57, Tobias Reinicke <ramotswa@anonymised.com> escribió:
- A shapefile store and info_format application/json = ~ 3000ms !!!
Yes I’ve seen that performance issue with a Shapefile in the Sinusoidal projection.
I’ve found this related issue
https://osgeo-org.atlassian.net/browse/GEOS-6923
and, as one comment says, setting ‘-DGEOSERVER_GEOJSON_LEGACY_CRS=true’ fixed the performance of JSON requests.
The issue is marked as fixed so I’m not sure why it was happening. May it’s something that must be fixed per projection.
Hope this workaround helps you in the meanwhile.
Cheers
Yes, very good. That has solved that performance problem.
My projection is EPSG:27700 which is most definitely part of the official EPSG database, so unsure if that fix has helped much.
Anyway, option added and all working fine.
Thanks for your help,
Toby
On 20 July 2016 at 15:17, Diego Nieto Cid <dnietoc@anonymised.com> wrote:
Hi
El 20 jul 2016, a las 06:57, Tobias Reinicke <ramotswa@anonymised.com> escribió:
- A shapefile store and info_format application/json = ~ 3000ms !!!
Yes I’ve seen that performance issue with a Shapefile in the Sinusoidal projection.
I’ve found this related issue
https://osgeo-org.atlassian.net/browse/GEOS-6923
and, as one comment says, setting ‘-DGEOSERVER_GEOJSON_LEGACY_CRS=true’ fixed the performance of JSON requests.
The issue is marked as fixed so I’m not sure why it was happening. May it’s something that must be fixed per projection.
Hope this workaround helps you in the meanwhile.
Cheers
On Wed, Jul 20, 2016 at 4:17 PM, Diego Nieto Cid <dnietoc@anonymised.com> wrote:
The issue is marked as fixed so I'm not sure why it was happening. May
it's something that must be fixed per projection.
Not really. The fix just tries to leverage an eventual EPSG code baked into
the projection, but it won't work for
shapefiles generated by ESRI software, that normally do not contain any
EPSG code.
That said, if the projection handling is set to "force declared" then
GeoServer should be forcing in a projection
with a proper code, wondering if the shapefile in question is using the
"leave native" instead of "force declared"
Cheers
Andrea
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
*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.
-------------------------------------------------------
Hi list,
Despite the setting of a proxy URL in Geoserver's global configuration,
the geowebcache tiled layers interface still points out to wrong URLs
(things in 127.0.0.1 actually) for preview, seed/truncate links. Is this
a known bug of do I have to set something more up to get a correct
behavior ?
Best regards
Guillaume
Thanks Andrea,
Yes it was on “leave native”. Changing that to “force declared” (and undoing the tomcat java option) also solves the problem.
Do you happen to know how to specify “force declared” on a shapefile when loading it via curl?
Thanks,
Toby
On 20 July 2016 at 16:23, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Wed, Jul 20, 2016 at 4:17 PM, Diego Nieto Cid <dnietoc@anonymised.com> wrote:
The issue is marked as fixed so I’m not sure why it was happening. May it’s something that must be fixed per projection.
Not really. The fix just tries to leverage an eventual EPSG code baked into the projection, but it won’t work for
shapefiles generated by ESRI software, that normally do not contain any EPSG code.
That said, if the projection handling is set to “force declared” then GeoServer should be forcing in a projection
with a proper code, wondering if the shapefile in question is using the “leave native” instead of “force declared”
Cheers
Andrea
–
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
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.
Hi Tobias,
I don’t know off the top of my head, but you can always make a second curl call in PUT mode
to force the desired handling
Cheers
Andrea
On Fri, Jul 22, 2016 at 10:28 AM, Tobias Reinicke <ramotswa@anonymised.com> wrote:
Thanks Andrea,
Yes it was on “leave native”. Changing that to “force declared” (and undoing the tomcat java option) also solves the problem.
Do you happen to know how to specify “force declared” on a shapefile when loading it via curl?Thanks,
Toby
–
On 20 July 2016 at 16:23, Andrea Aime <andrea.aime@anonymised.com107…> wrote:
On Wed, Jul 20, 2016 at 4:17 PM, Diego Nieto Cid <dnietoc@anonymised.com> wrote:
The issue is marked as fixed so I’m not sure why it was happening. May it’s something that must be fixed per projection.
Not really. The fix just tries to leverage an eventual EPSG code baked into the projection, but it won’t work for
shapefiles generated by ESRI software, that normally do not contain any EPSG code.
That said, if the projection handling is set to “force declared” then GeoServer should be forcing in a projection
with a proper code, wondering if the shapefile in question is using the “leave native” instead of “force declared”
Cheers
Andrea
–
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
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.
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
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.
I also have the same issue.
I may have found the problem in the code and I am itching to submit a patch, but I have not touched Java in more than 10 years and I am not familiar with this codebase. I reported the issue instead: https://osgeo-org.atlassian.net/browse/GEOS-7653
Problem description:
Geoserver tiled layers preview points to http://127.0.0.1:8080/geoserver/gwc/… even though I have set "Proxy Base URL" correctly. Plain layers previews work just fine.
Simple workaround:
Replace the http://127.0.0.1:8080/geoserver in the browser address bar with whatever your actual url is. It works for me. The service seems to have no problem, it's just the inconvenience of the interface link pointing to a wrong address.
Related Issues:
I have only found https://osgeo-org.atlassian.net/browse/GEOS-4930, which concerns the layer preview (not the tile layer preview). It seems even at the time (Mar 2013) it was not a real bug but was due to geoserver being run under something other than Tomcat.
Best,
Daniel
Em 22/07/2016 04:40, Guillaume Sueur escreveu:
Hi list,
Despite the setting of a proxy URL in Geoserver's global configuration,
the geowebcache tiled layers interface still points out to wrong URLs
(things in 127.0.0.1 actually) for preview, seed/truncate links. Is this
a known bug of do I have to set something more up to get a correct
behavior ?Best regards
Guillaume
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users