Re: [Geoserver-users] Geoserver 2.17.0 - load layers catalog once start

[Andrea Aime]

On Mon, Dec 21, 2020 at 10:42 PM Tiago Vieira  wrote:

> Hi,
>
> When i startup geoserver, it goes up quickly, but the problem is when the
> application makes the first WMS or WFS request, it takes a while to load.
>
> Or another example to reproduce:
> - Start geoserver
> - Login on geoserver web interface
> - Click Layer Preview
>
> At this point, it will start to send a connection per layer to database to
> get the metadata.
>
> Is it possible to load the layers catalog once geoserver is up?
>

That's what already happens today, the catalog is fully loaded in memory
(unless you're
usign the jdbcconfig community extension).

However, when producing the capabilities,
extra work needs to be done, like getting the full list of EPSG codes,
connecting
the databases, and the like. There is no way to warm up that part yet.
Code changes or funding to add a flag that does that are both welcomed

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


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] reorder static gpkg by geohash for faster reads?

[Andrea Aime]

On Fri, Jan 8, 2021 at 4:42 AM Russell Grew <
russell.g...@douglaspartners.com.au> wrote:

> All,
>
>
>
> I quite enjoyed the two OGC Testbed 16 videos prepared by GeoSolutions
> Group.
>
>
>
> https://www.youtube.com/watch?v=hc81tlFMDbA
>

Thanks!


>
>
> I have a few large (5+ GB) geopackage files hosted read only by GeoServer.
> They could be shapefiles but I went with geopackage to do something
> progressive, and avoid the 2 GB limit which some software has.
>

In our experience GeoHash sorting helped greatly on the 200GB GeoPackage,
and only in a smaller amount
on the 10GB ZoomStack package, where the generalized table extension had a
far greater effect*.
Your case might vary, depends a lot on the number of records (the more
records, the more the effect is visible)
and the type of disks (less visible on SSDs unless the size of the package
is huge, more visible on spinning disks... I'm guessing
network mounted disks also benefit).


>  Following Andre’s talk I wonder if I should attempt to reorder the data
> in these files by geohash. To help it load faster.
>
>
>
> Is my understanding correct? Does anyone know of any tools to enable this?
>

I had to build the machinery from scratch in Java. Thinking out loud, if
you want to use something else,
maybe you can dump the data in postgresql, add the geohash column, and
create a view that returns data sorted by geohash by default.
Then use ogr2ogr to dump a geopackage from the view, that hopefully retains
the right record order.


> Perhaps I could use GeoServer 2.19 RC hosting my current files and then
> dump them with gs:GeoPackage? If this is the way forward any advice on how
> to tell it what layer I want to dump would be great. The WPS I have looked
> at before all had vector layer process input boxes.
>

I've attached a request sorting by GeoHash against the ZoomStack data set,
hopefully you can
use it as a reference to build your request. If you try it out, let us know
how the results perform.

Cheers
Andrea

*: As a note, GeoServer has been extended to produce the packages with the
new extensions, but has not
ability to read them (the read part was in a different Testbed component,
developed by another company).
That said, the existing work on the write side would help develop the read
portion quicker.

== 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.*

http://www.opengis.net/wps/1.0.0; xmlns="http://www.opengis.net/wps/1.0.0; xmlns:gml="http://www.opengis.net/gml; xmlns:ogc="http://www.opengis.net/ogc; xmlns:ows="http://www.opengis.net/ows/1.1; xmlns:wcs="http://www.opengis.net/wcs/1.1.1; xmlns:wfs="http://www.opengis.net/wfs; xmlns:xlink="http://www.w3.org/1999/xlink; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; version="1.0.0" service="WPS" xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd;>
   gs:GeoPackage
   
  
 contents
 

   

 
  
   
   
  
 geopackage
  
   


___
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

Re: [Geoserver-users] WCS - subsetting y-axis of EPSG:3857

[Andrea Aime]

Hi,
could you please share the full stack trace?

In general it's not a great idea to store data in a visualization CRS such
as EPSG:3857, as it introduces
significant data resampling. As a result, it's a use case that's not very
well covered by the existing codebase
(of course it could be improved, funding permitting).

Cheers
Andrea

On Sun, Jan 3, 2021 at 3:24 AM FANGER Lorenz via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hi
>
>
>
> I'm having an ImageMosaic datastore with images georeferenced in EPSG:3857
> placed at BBOX(-5,-5200,8200,10) far away from a pole...
>
>
>
> If I try to get Coverages over WCS Version 2.0.1 I get errors like
> "org.geotools.referencing.operation.projection.ProjectionException:
> Latitude 90°00.0S is too close to a pole. Latitude 90°00.0S is
> too close to a pole." as soon as I request coverages with a Y-Subset of >90
> resp. <-90
>
>
>
> This means the following URL is working perfectly:
>
>
> http://localhost/geoserver/wcs?service=WCS=2.0.1=GetCoverage=XYZ_xyz=X(10,8000)=Y(-80,80)=http://www.opengis.net/def/crs/EPSG/0/3857
> and if I replace Y(-80,80) with Y(-90,90) or even larger numbers I get the
> above mentioned errors.
>
>
>
> Any Idea? Thanks and br
>
>
>
> *Lorenz Fanger*
>
>
> ___
> 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
>


-- 

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 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


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] reorder static gpkg by geohash for faster reads?

[Russell Grew]

All,

I quite enjoyed the two OGC Testbed 16 videos prepared by GeoSolutions Group.

https://www.youtube.com/watch?v=hc81tlFMDbA

I have a few large (5+ GB) geopackage files hosted read only by GeoServer. They 
could be shapefiles but I went with geopackage to do something progressive, and 
avoid the 2 GB limit which some software has.

Following Andre's talk I wonder if I should attempt to reorder the data in 
these files by geohash. To help it load faster.

Is my understanding correct? Does anyone know of any tools to enable this?

Perhaps I could use GeoServer 2.19 RC hosting my current files and then dump 
them with gs:GeoPackage? If this is the way forward any advice on how to tell 
it what layer I want to dump would be great. The WPS I have looked at before 
all had vector layer process input boxes.

Thanks.
___
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

Re: [Geoserver-users] WFS insert transaction has a bug.

[Nuno Oliveira]

Hi,
strange behavior indeed, that is to say, I'm not sure at 100% that the WFS
transaction queries you are sending are correct, an example from the WFS
1.1.0 specification:


http://www.someserver.com/myns; xmlns:gml="http://www.opengis.net/gml;
xmlns:ogc="http://www.opengis.net/ogc; xmlns:wfs="http://www.opengis.net/wfs;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="
http://www.someserver.com/myns http://www.someserver.com/wfs/cwwfs.cgi?
request=describefeaturetypetypename=InWaterA_1M.xsd
http://www.opengis.net/wfs ../wfs/1.1.0/WFS.xsd">
  

  
http://www.opengis.net/gml/srs/epsg.xml#63266405;>
  

  -98.54 24.26 ...
  

  
  150
  ABCDE
  152
  250
  111

  


I would recommend to give it a try (if not already done) using GeoServer
WFS strict mode

and see if GeoServer complains about them, if not then feel free to fill a
bug report.

Best regards,
Nuno Oliveira


On Tue, Jan 5, 2021 at 8:22 AM feyzullah yıldız <
ahmet.feyzullah.yil...@gmail.com> wrote:

>
>- Geoserver version: 2.14.1 and 2.18.0.
>- My store is Postgis.
>- Those are my tables, there is no relation on database level
>
> create table example_table(
> id serial primary key,
> name varchar(100),
> geom geometry(Point, 4326)
> );create table name(
> id serial primary key,
> key varchar(100)
> );
>
> I executed this sql query, then I just published example_table. here is my 
> insert transaction.
>
>
>xmlns:wfs="http://www.opengis.net/wfs;
>   xmlns:topp="http://www.openplans.org/topp;
>   xmlns:gml="http://www.opengis.net/gml;
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://www.opengis.net/wfs 
> http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd 
> http://www.openplans.org/topp 
> http://localhost:8080/geoserver/wfs/DescribeFeatureType?typename=feyzullah_test:example_table;>
>   
> 
>   isim
>   
> http://www.opengis.net/gml/srs/epsg.xml#4326;>
>   29,41
> 
>   
> 
>   
>
>
>- Then It is inserted successfully.
>- I published the other layer called name
>- Then I executed the same transaction XML again and I got an error.
>The error says: value too long for type character varying(100). but is
>not that long. Here is the what GeoServer generated for insert query
>
> INSERT INTO "public"."example_table" ( "name","geom" )VALUES 
> ('SimpleFeatureImpl:name=[SimpleFeatureImpl.Attribute: key id=fid-55948f24_176ad551553_-7fb5>=null]',
> ST_GeomFromText('POINT (29 41)', 4326)
> )
>
>
>- When I unpublish the layer called name, this error is not firing. We
>have had an app in production for over 2 years, this was not happening
>until we realized this error. This error is not happening in the update
>transaction.
>- So, if we have a table like foo and another layer has a column
>called foo we cannot execute insert transaction successfully.
>
> ___
> 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
>


-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:  +39 0584 1660272

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