Avoid non standard WFS shapefile output

[fergonco]

Basically this means a change in the docs. Currently they make the installation using this option[1], which makes the shapefile output non standard if it contains dates, as it is explained here[2].

Pay also attention to the parameter -Duser.timezone=GMT

[1] -Dorg.geotools.shapefile.datetime=true [2] http://docs.geoserver.org/latest/en/user/tutorials/imagemosaic_timeseries/imagemosaic_timeseries.html#configuration

[alessio-alfonsetti]

Not relevant since we use major mosaic indexes stored at DBMS level.

[fergonco]

I am not using the mosaic indexes stored at DBMS level...

[Damianofds]

Ciao Fernando, Are there use cases where the portal users are allowed to download the data published as shapefile? Furthermore the requested layer should contains a date field to be affected by this issue. I think that this issue should be closed or at least moved to the documentation issue tracker.

[fergonco]

Not the portal users, but directly through the GeoServer. I don't know which data people is loading on GeoServer since it is even used for other purposes other than the portal. So it can potentially contain an date field.

I agree to move it to the docs. Indeed for me is not only a documentation issue but also an issue on the two installations that have been already made in Argentina and Ecuador following this documentation.

[Damianofds]

Ok, but this issue is related to another component of the platform ( geoserver ) not to the portal. Since it is an issue related to a specific geoserver workflow and not to a geoserver bug I think the right place to keep track of this is to write about it in the official user documentation.

[fergonco]

Yeah, sorry, I was quite out of context. I agree to move it to the docs.

[fergonco]

Moved to https://github.com/nfms4redd/documentation/issues/1