Foxeye689

Skip to end of metadataGo to start of metadata

1. Wget Command Not Found
2. Install Wget Mac
3. Download And Install Wget Mac
4. Wget For Mac
5. Download And Install Wget Macros

Instructions for how to use the download access script provided by Earthdata Search, which allows users to easily download large numbers of files.

IMPORTANT: The download access script works on Mac, Linux and Windows systems. Windows users will need to a program that emulates a Linux command line, such as Cygwin. Cygwin is free, and can be download here: https://www.cygwin.com/install.html

Step-by-step guide

1. In your Earthdata Login profile, make sure you have authorized the application from which you are downloading data (see How To Pre-authorize an application). There are many similarly named apps. If you aren't sure which one, authorize all apps you think could be relevant to your data. For example, if you are trying to get data from goldsmr5.gesdisc.eosdis.nasa.gov and it's not working, make sure you approve all the apps containing the word 'GESDISC,' just to be sure.
   
   

2. After downloading the script, open Terminal (Mac or Linux) or Cygwin (Windows) and navigate to the folder that contains your script

   The files downloaded by this script will be downloaded to the folder that your script is in. If you want your files downloaded to a specific folder, please make sure to move the script to that folder before executing the script.

3. Next, run the following command to make the script executable:

4. Now that your script is executable, run the script using the following command. (Note: the leading period and forward slash is required.)
   

   
   

5. The script will ask for your Earthdata Login credentials.

   Note: your Earthdata Login and password are case-sensitive, so be sure CAPSLOCK is off.

   When asked for your Username, please enter your Earthdata Login.

   When asked for your Password, please enter your Earthdata Login password. When entering your password, you cannot see your password as you type. This is a Unix convention for security, but it can be confusing.

   After entering your password, be sure to hit the RETURN key.

   
   

6. After entering your password and hitting the RETURN key, the downloads will begin. You should start to see download statuses appear for each link present in the download script.
7. At this point, you should start seeing files downloaded to your computer. The script will terminate once it has attempted to download the files specified in the script.

IF YOU SEE ERROR 'is not recognized as an internal or external command' ON WINDOWS

The download access script works on Windows systems with a program that emulates a Linux command line, such as Cygwin.

If you are a Windows user and you do not have Cygwin, you can download it here: https://www.cygwin.com/install.html

On OS X, there are two ways to get wget and install it. The easiest is to install a package manager and use it to automatically install wget. There is a second method, discussed below, that involves compiling it. Both, however, require that you install Apple’s ‘Command Line Tools’ to use properly. Newer isn’t always better, and the wget command is proof. First released back in 1996, this application is still one of the best download managers on the planet. Whether you want to download a single file, an entire folder, or even mirror an entire website, wget lets you do it with just a few keystrokes.

IF YOU HAVE PROBLEMS WITH THE SCRIPT

To download multiple files, a simple alternative to the script is to use wget as follows:

where myusername is your Earthdata username, mypassword is your Earthdata password, and url_list.txt is a text file with one granule download link per line.
For convenience, wget can pull urls directly out of Earthdata Search's download access script, so the following will also work:

To download a single file, you can use wget as follows:

where url is link for the file you want to download.

Another alternative is to use DownloadThemAll!, an add-in for the Firefox browser. (TIP: By adding .txt to the end of the download script, you can use DownloadThemAll!'s 'import from file' feature to download the links it contains.). DownloadThemAll! is not compatible with Firefox Quantum, so be sure to check your version of Firefox to verify compatibility.

An alternative to DownloadThemAll! is 'Chrono Download Manager,' an extension for the Google Chrome browser that has many of the features of DownThemAll! for Firefox.

IF YOU HAVE CONNECTION FAILURES

Connection failures like 'Operation timed out' or 'No route to host' are an indication that the data provider's server may be temporarily unavailable.

To see a list of known data provider outages, click the alerts button (the little bell icon) in the upper right-hand corner of Earthdata Search.

IF YOU SEE THE ERROR 'curl: option --netrc-file: is unknown'

When running the script, if you get the error

this means the curl command is not recognizing the option --netrc-file.

The --netrc-file option was added in curl version 7.21.5. You can check your version of curl by running the following command:

If your version of curl is less than 7.21.5, you need to update curl.
If you have .netrc already set up with your login credentials, you may be able to get the script to work without updating curl by editing the script and removing the following from the curl command line: --netrc-file '$netrc'

IF YOU DO NOT HAVE WGET

• Windows users can download it at https://eternallybored.org/misc/wget/
• Mac OS X users can install it using Homebrew (https://brew.sh) using the command `brew install wget`
• Additional information on wget is available at https://www.gnu.org/software/wget/faq.html

Wget Command Not Found

IF YOU ARE A WINDOWS USER

• Windows users can download it at https://eternallybored.org/misc/wget/
• Mac OS X users can install it using Homebrew (https://brew.sh) using the command `brew install wget`
• Additional information on wget is available at https://www.gnu.org/software/wget/faq.html

Related articles
How To Access Data With cURL And Wget

Looking to install a package? See Ways to install NuGet packages.

To work with NuGet, as a package consumer or creator, you can use command-line interface (CLI) tools as well as NuGet features in Visual Studio. This article briefly outlines the capabilities of the different tools, how to install them, and their comparative feature availability. To get started using NuGet to consume packages, see Install and use a package (dotnet CLI) and Install and use a package (Visual Studio). To get started creating NuGet packages, see Create and publish a NET Standard package (dotnet CLI) and Create and publish a NET Standard package (Visual Studio).

The MSBuild CLI also provides the ability to restore and create packages, which is primarily useful on build servers. MSBuild is not a general-purpose tool for working with NuGet.

Package Manager Console commands work only within Visual Studio on Windows and do not work within other PowerShell environments.

Visual Studio

Install on Visual Studio 2017 and newer

Starting in Visual Studio 2017, the installer includes the NuGet Package Manager with any workload that employs .NET. To install separately, or to verify that the Package Manager is installed, run the Visual Studio installer and check the option under Individual Components > Code tools > NuGet package manager.

Install on Visual Studio 2015 and older

NuGet Extensions for Visual Studio 2013 and 2015 can be downloaded from https://dist.nuget.org/index.html.

For Visual Studio 2010 and earlier, install the 'NuGet Package Manager for Visual Studio' extension. Note, if you can't see the extension in the first page of search results, try changing the Sort By dropdown to 'Most Downloads', or an alphabetical sort.

CLI tools

You can use either the dotnet CLI or the nuget.exe CLI to support NuGet features in the IDE. The dotnet CLI is installed with some Visual Studio workloads, such as .NET Core. The nuget.exe CLI must be installed separately as described earlier.

The two NuGet CLI tools are dotnet.exe and nuget.exe. See feature availability for a comparison.

• To target .NET Core or .NET Standard, use the dotnet CLI. The dotnet CLI is required for the SDK-style project format, which uses the SDK attribute.
• To target .NET Framework (non-SDK-style project only), use the nuget.exe CLI. If the project is migrated from packages.config to PackageReference, use the dotnet CLI.

dotnet.exe CLI

The .NET Core 2.0 CLI, dotnet.exe, works on all platforms (Windows, Mac, and Linux) and provides core NuGet features such as installing, restoring, and publishing packages. dotnet provides direct integration with .NET Core project files (such as .csproj), which is helpful in most scenarios. dotnet is also built directly for each platform and does not require you to install Mono.

Installation:

• On developer computers, install the .NET Core SDK. Starting in Visual Studio 2017, the dotnet CLI is automatically installed with any .NET Core related workloads.
• For build servers, follow the instructions on Using .NET Core SDK and tools in Continuous Integration.

To learn how to use basic commands with the dotnet CLI, see Install and use packages using the dotnet CLI.

nuget.exe CLI

The nuget.exe CLI, nuget.exe, is the command-line utility for Windows that provides all NuGet capabilities; it can also be run on Mac OSX and Linux using Mono with some limitations.

To learn how to use basic commands with the nuget.exe CLI, see Install and use packages using the nuget.exe CLI.

Installation:

Windows

Note

NuGet.exe 5.0 and later require .NET Framework 4.7.2 or later to execute.

1. Visit nuget.org/downloads and select NuGet 3.3 or higher (2.8.6 is not compatible with Mono). The latest version is always recommended, and 4.1.0+ is required to publish packages to nuget.org.
2. Each download is the nuget.exe file directly. Instruct your browser to save the file to a folder of your choice. The file is not an installer; you won't see anything if you run it directly from the browser.
3. Add the folder where you placed nuget.exe to your PATH environment variable to use the CLI tool from anywhere.

macOS/Linux

Behaviors may vary slightly by OS distribution.

1. Install Mono 4.4.2 or later.

2. Execute the following command at a shell prompt:

3. Create an alias by adding the following script to the appropriate file for your OS (typically ~/.bash_aliases or ~/.bash_profile):

4. Reload the shell. Test the installation by entering nuget with no parameters. NuGet CLI help should display.

Tip

Install Wget Mac

Use nuget update -self on Windows to update an existing nuget.exe to the latest version.

Note

The latest recommended NuGet CLI is always available at https://dist.nuget.org/win-x86-commandline/latest/nuget.exe. For compatibility purposes with older continuous integration systems, a previous URL, https://nuget.org/nuget.exe currently provides the deprecated 2.8.6 CLI tool.

Feature availability

Download And Install Wget Mac

(1) Does not affect project files; use dotnet.exe instead.

(2) Works only with packages.config file and not with solution (.sln) files.

(3) Various advanced package features are available through the CLI only as they aren't represented in the Visual Studio UI tools.

(4) Works with .nuspec files but not with project files.

Upcoming Features

Wget For Mac

If you'd like to preview upcoming NuGet features, install a Visual Studio Preview, which works side-by-side with stable releases of Visual Studio. To report problems or share ideas for previews, open an issue on the NuGet GitHub repository.

Related topics

Download And Install Wget Macros

Developers working on Windows can also explore the NuGet Package Explorer, an open-source, stand-alone tool to visually explore, create, and edit NuGet packages. It's very helpful, for example, to make experimental changes to a package structure without rebuilding the package.