GETDAP(1)

🦋 GETDAP(1) 🦋

okay bestie, buckle up — this is the getdap page from the User Manuals section, and it's literally the test driver for the libdap library. she's a whole vibe and she's here to make DAP servers talk. ✨

---

✨ NAME ✨

getdap — test driver for the libdap library

like. that's her. that's the whole job. 💅

---

🌸 SYNOPSIS 🌸

getdap [-idaDxXBvVkzsM] [-c expr ] [-m num ] [-p x.y ] url ...

getdap [-VvksM] file ...

two whole forms, no cap. pick your fighter. 🫶

---

💖 DESCRIPTION 💖

form one: the URL era 👑

In the first form of the command, you dereference the URL and perform the requested operations. This includes routing the returned information through the DAP processing library (parsing the returned objects, et c.).

but here's the tea: if none of a, d, or D are used with a URL, then the DAP library routines are NOT used and the URL's contents are dumped to standard output. periodt. no library, just vibes.

form two: the file era 📁

In the second form of the command, assume the files are DataDDS objects (stored in files or read from pipes) and process them as if -D were given.

⚠️ in this case the information must contain valid MIME header in order to be processed. no header, no processing, i don't make the rules.

---

🎀 OPTIONS 🎀

okay this is the part where it gets good. every single flag, accounted for, not a single one left on read:

• -i — For each URL, get the server version. like a little "hey bestie what version are you running" check-in 💌
• -d — For each URL, get the the DDS. (yes the original says "the the", i'm not fixing her, she's iconic as-is)
• -a — For each URL, get the the DAS.
• -D — For each URL, get the the DataDDS.
• -x — For each URL, get the DDX object. Does not get data. just the object, nothing more, we're being minimal here.
• -X — Request a DataDDX from the server (the DAP4 data response). DAP4 girlies rise up 🔥
• -B — Build a DDX in getdap using the DDS and DAS. DIY energy, we love to see it.
• -v — Verbose output. she talks. a lot. we respect it.
• -V — Version of this client; see 'i' for server version. (client version vs server version, know the difference iykyk)
• -c expr — expr is a constraint expression. Used with -D/X. You can use a '?' for the CE also. 👑
• -k — Keep temporary files created by libdap. not me hoarding temp files... actually yes me, on purpose, with a flag.
• -m num — Request the same URL num times. spam that endpoint bestie 🫶
• -z — Ask the server to compress data. zip zip hooray ✨
• -s — Print Sequences using numbered rows. cute, numbered, organized, we stan.
• -M — Assume data read from a file has no MIME headers (the default is to assume the headers are present). so -M = "no headers here, don't come for me"
• -p x.y — Set DAP protocol to x.y. choose your era. 🌈

---

🦋 FILES 🦋

• ~/.dodsrc — The .dodsrc file contains various parameters that affect the runtime behavior for DAP clients. See dodsrc(5) for further details.

it's giving config file main character energy and honestly? deserved.

---

🌈 ENVIRONMENT 🌈

• DODS_CONF — Specifies an alternate file or directory for the .dodsrc file.

when you wanna be ✨different✨ and put your config somewhere else, this is the flag-adjacent env var for you.

---

💀 DIAGNOSTICS 💀

Various self-explanitory messages may be issued on stderr.

(that's literally all it says. spelling of "self-explanitory" is theirs, i'm keeping it, it's a heritage moment.)

---

🙈 BUGS 🙈

• The command name should have been chosen more carefully to reflect its purpose. 💀 okay drag her a little bit i guess
• The dodsrc man page needs to be written.

no cap these are the actual documented bugs. we love an honest queen.

---

⭐ AUTHOR ⭐

James Gallagher <jgallagher at opendap.org>

---

💜 SEE ALSO 💜

• dodsrc(5)

---

and that's the whole page bestie, you ate that. this one's from Linux, dated December 2011, and she's the GETDAP(1) page of the User Manuals — go forth and test your drivers, mwah 🎀💖