Re: [Geoserver-devel] Removing ASCII grid output format from WCS?

2023-06-12 Thread Andrea Aime 
Hi Richard,
mind, we are talking about the ability to produce a ASCII Grid in WCS
output,
not about the ability to read one and create a layer out of it.

Cheers
Andrea

On Mon, Jun 12, 2023 at 6:56 PM Richard Duivenvoorde 
wrote:

> FYI:
>
> I've had users which because of the simplicity to create them (when you
> use Fortran als programming language...), used them to create time series
> for (dispersion) models.
> So that could be an argument?
>
> I've had a  lot of fun setting these up for Geoserver...
> (so I would not vote for complete code removal, unless I was the only user
> for ascii grids :-))
>
> (now moving to netcdf...)
>
> Regards,
>
> Richard Duivenvoorde
>
>
> On 6/12/23 17:44, Andrea Aime wrote:
> > Hi all,
> > with this mail I want to discuss the eventual removal of the ASCII grid
> > output format from the WCS codebase.
> >
> > The output format produces the classic ESRI ASCII grid, a text based
> export format suitable only for single banded raster data.
> > I was discussing with Simone about it, and we are skeptical about its
> current usefulness:
> >
> >   * Limited functionality, due to single band support
> >   * Inefficient format, and inefficient implementation (dumps to file
> first, streams out later, inviting timeouts)
> >   * Difficult to discover MIME,  it's reported as "application/x-gzip"
> along the output formats
> >   * Unaware of significant usage in the wild
> >   * The GML grid output format provides a better alternative, still
> human readable, but human readable and can be streamed
> >
> > If you disagree, we'd like to hear why.
> > If you agree, what option should we follow? Two ideas:
> >
> >   * Simple code removal, not worth spending extra effort
> >   * Migration to community module, to provide soft landing for those
> that might have been using it
> >
> > Thoughts?
> >
> > Cheers
> > Andrea
> >
> > ==
> > GeoServer Professional Services from the experts!
> >
> > Visit http://bit.ly/gs-services-us for
> more information.
> > ==
> >
> > Ing. Andrea Aime
> > @geowolf
> > Technical Lead
> >
> > GeoSolutions Group
> > phone: +39 0584 962313
> >
> > fax: +39 0584 1660272
> >
> > mob:   +39  339 8844549
> >
> >
> > https://www.geosolutionsgroup.com/ 
> >
> > 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-devel mailing list
> > Geoserver-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>

-- 

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

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,

Re: [Geoserver-devel] Removing ASCII grid output format from WCS?

2023-06-12 Thread Richard Duivenvoorde via Geoserver-devel 

FYI:

I've had users which because of the simplicity to create them (when you use 
Fortran als programming language...), used them to create time series for 
(dispersion) models.
So that could be an argument?

I've had a  lot of fun setting these up for Geoserver...
(so I would not vote for complete code removal, unless I was the only user for 
ascii grids :-))

(now moving to netcdf...)

Regards,

Richard Duivenvoorde


On 6/12/23 17:44, Andrea Aime wrote:

Hi all,
with this mail I want to discuss the eventual removal of the ASCII grid
output format from the WCS codebase.

The output format produces the classic ESRI ASCII grid, a text based export 
format suitable only for single banded raster data.
I was discussing with Simone about it, and we are skeptical about its current 
usefulness:

  * Limited functionality, due to single band support
  * Inefficient format, and inefficient implementation (dumps to file first, 
streams out later, inviting timeouts)
  * Difficult to discover MIME,  it's reported as "application/x-gzip" along 
the output formats
  * Unaware of significant usage in the wild
  * The GML grid output format provides a better alternative, still human 
readable, but human readable and can be streamed

If you disagree, we'd like to hear why.
If you agree, what option should we follow? Two ideas:

  * Simple code removal, not worth spending extra effort
  * Migration to community module, to provide soft landing for those that might 
have been using it

Thoughts?

Cheers
Andrea

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more 
information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549


https://www.geosolutionsgroup.com/ 

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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel




___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Removing ASCII grid output format from WCS?

2023-06-12 Thread Simone Giannecchini 
I would go for the hard removal.
We need to concentrate our resources on things that matter and I don't
think anyhow would commit suicide over the remova of Ascii Grid format from
GeoServer.

Regards,
Simone Giannecchini
==
Online training classes for GeoNode, GeoServer and MapStore from the
experts!
Visit https://www.geosolutionsgroup.com/professional-training/ for more
information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director GeoSolutions Italy
President GeoSolutions USA

phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39  333 8128928
US: +1 (845) 547-7905

http://www.geosolutionsgroup.com
http://twitter.com/geosolutions_it

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


On Mon, Jun 12, 2023 at 6:39 PM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:

> Hi all,
> with this mail I want to discuss the eventual removal of the ASCII grid
> output format from the WCS codebase.
>
> The output format produces the classic ESRI ASCII grid, a text based
> export format suitable only for single banded raster data.
> I was discussing with Simone about it, and we are skeptical about its
> current usefulness:
>
>- Limited functionality, due to single band support
>- Inefficient format, and inefficient implementation (dumps to file
>first, streams out later, inviting timeouts)
>- Difficult to discover MIME,  it's reported as "application/x-gzip"
>along the output formats
>- Unaware of significant usage in the wild
>- The GML grid output format provides a better alternative, still
>human readable, but human readable and can be streamed
>
> If you disagree, we'd like to hear why.
> If you agree, what option should we follow? Two ideas:
>
>- Simple code removal, not worth spending extra effort
>- Migration to community module, to provide soft landing for those
>that might have been using it
>
> Thoughts?
>
> Cheers
> Andrea
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> 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-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Removing ASCII grid output format from WCS?

2023-06-12 Thread Andrea Aime 
Hi all,
with this mail I want to discuss the eventual removal of the ASCII grid
output format from the WCS codebase.

The output format produces the classic ESRI ASCII grid, a text based export
format suitable only for single banded raster data.
I was discussing with Simone about it, and we are skeptical about its
current usefulness:

   - Limited functionality, due to single band support
   - Inefficient format, and inefficient implementation (dumps to file
   first, streams out later, inviting timeouts)
   - Difficult to discover MIME,  it's reported as "application/x-gzip"
   along the output formats
   - Unaware of significant usage in the wild
   - The GML grid output format provides a better alternative, still human
   readable, but human readable and can be streamed

If you disagree, we'd like to hear why.
If you agree, what option should we follow? Two ideas:

   - Simple code removal, not worth spending extra effort
   - Migration to community module, to provide soft landing for those that
   might have been using it

Thoughts?

Cheers
Andrea

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] GS 2.22.4, GT 28.4 and GWC 1.22.3 release cycle will start this Friday

2023-06-12 Thread Peter Smythe 
Good day developers

If you have any fixes that you want included in the upcoming 2.22.4
GeoServer, 1.22.3 GeoWebCache or 28.4 GeoTools releases, please make sure
you have backported them and updated the fix version in the ticket before
Friday afternoon (UTC) which is when Jody and I plan to start the next
release cycle.

Thank you

Peter

___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-11024) metadata: add datetime field type to feature catalog

2023-06-12 Thread Niels Charlier (JIRA) via Geoserver-devel 
Niels Charlier ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1d2c4019-de4e-4624-8b27-2486941601cf
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZTRmNDRjMzNmNWJhNDg1NDkwYjg1YmI5NGUxZjRhYTciLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-11024?atlOrigin=eyJpIjoiZTRmNDRjMzNmNWJhNDg1NDkwYjg1YmI5NGUxZjRhYTciLCJwIjoiaiJ9
 ) GEOS-11024 ( 
https://osgeo-org.atlassian.net/browse/GEOS-11024?atlOrigin=eyJpIjoiZTRmNDRjMzNmNWJhNDg1NDkwYjg1YmI5NGUxZjRhYTciLCJwIjoiaiJ9
 ) metadata: add datetime field type to feature catalog ( 
https://osgeo-org.atlassian.net/browse/GEOS-11024?atlOrigin=eyJpIjoiZTRmNDRjMzNmNWJhNDg1NDkwYjg1YmI5NGUxZjRhYTciLCJwIjoiaiJ9
 )

Issue Type: Bug Assignee: Niels Charlier ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1d2c4019-de4e-4624-8b27-2486941601cf
 ) Created: 12/Jun/23 11:59 AM Priority: Medium Reporter: Niels Charlier ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A1d2c4019-de4e-4624-8b27-2486941601cf
 )

In recent versions of geoserver, if you include metadata extension but you 
don’t have a metadata.properties file then geoserver doesn’t start up.

( 
https://osgeo-org.atlassian.net/browse/GEOS-11024#add-comment?atlOrigin=eyJpIjoiZTRmNDRjMzNmNWJhNDg1NDkwYjg1YmI5NGUxZjRhYTciLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-11024#add-comment?atlOrigin=eyJpIjoiZTRmNDRjMzNmNWJhNDg1NDkwYjg1YmI5NGUxZjRhYTciLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100225- 
sha1:956085d )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel