public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Carl Fredrik Forsberg <Carl.Fredrik.Forsberg@ngi.no>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Netcdf error using Generic Mapping Tools
Date: Tue, 14 Jun 2022 11:16:25 +0000	[thread overview]
Message-ID: <OSWP279MB03903E788C03D45783D21FA5D6AA9@OSWP279MB0390.NORP279.PROD.OUTLOOK.COM> (raw)

I have compiled Generic Mapping Tools (GMT; www.generic-mapping-tools.org) version 6.3.0 on Cygwin without any errors using the same workflow as for previous versions.
Previous versions have worked fine. I now get the following errors from GMT when trying to access the accompanying gshhg database of coastal outlines (Netcdf files). I have used the netcdf libraries etc. from the Cygwin depository when compiling GMT.

gshhg_version: cannot open file "/GMT6/gshhg-gmt-2.3.6/binned_border_f.nc" (-101).
gmtget [ERROR]: 1. GSHHG: Found /GMT6/gshhg-gmt-2.3.6/binned_border_f.nc but cannot read it due to wrong permissions
gshhg_version: cannot open file "/GMT6/gmt-6.3.0/share/coast/binned_border_f.nc" (-101).

Permissions are all ok with read and write access. I believe the -101 in brackets is a Netcdf error code indicating a HDF5 error (#define NC_EHDFERR (-101) // Error at HDF5 layer).

Any hints would be appreciated.

Best regards
Carl Fredrik
The confidentiality or integrity of this message can not be guaranteed following transmission on the Internet. The addressee should be aware of this before using the contents of this message.

                 reply	other threads:[~2022-06-14 11:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OSWP279MB03903E788C03D45783D21FA5D6AA9@OSWP279MB0390.NORP279.PROD.OUTLOOK.COM \
    --to=carl.fredrik.forsberg@ngi.no \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).