Thank you very much for the data. However, the file (sst.nc) you sent had 1D coordinates. These kinds of coordinates are okay in GeoServer: lat_1D: float32 lat(y) lon_1D: float32 lon(x)
The latitudes and longitudes in a 2D NetCDF data have 2D shapes, and they depend on both the x and y axis. They are problematic in GeoServer, although in the documentations <https://docs.geoserver.org/stable/en/user/extensions/netcdf/netcdf.html#two-dimensional-coordinate-variables> it is mentioned that they can be handled): lat_2D: float32 lat(x,y) lon_2D: float32 lon(x,y) On Thu, May 4, 2023 at 5:09 PM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > On Thu, May 4, 2023 at 3:09 PM Amirhossein Nikfal <ah.nik...@gmail.com> > wrote: > >> Well actually in the documentation >> <https://docs.geoserver.org/stable/en/user/extensions/netcdf/netcdf.html#two-dimensional-coordinate-variables> >> it has been mentioned that GeoServer can handle NetCDF data with 2D >> coordinates (latitudes/longitudes). >> > > A scalar variable with lat and lon? Sure, it's supported. > When you said a 2D variable, I understood you wanted a vector-type > variable (not sure if NetCDF even supports it, TBH). > > >> I just want a sample NetCDF data with 2D coordinates to test it. >> > > This tiny NetCDF used for the NetCDF module tests should do the trick: > > https://github.com/geoserver/geoserver/raw/main/src/extension/netcdf/src/test/resources/org/geoserver/netcdf/test-data/sst.nc > > Regards > 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-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