Following from #36 - all graph node/edge TSVs on KG-HUB are stored as tar.gz, so even if we specify URL locations in the config yaml then we still need to have decompressed the tar.gz first.
This may be resolved by including a new key in the config yaml to specify a URL to the node/edge file, then having NEAT retrieve and decompress the file in its run location, updating the node and edge paths in the process.
Following from #36 - all graph node/edge TSVs on KG-HUB are stored as tar.gz, so even if we specify URL locations in the config yaml then we still need to have decompressed the tar.gz first. This may be resolved by including a new key in the config yaml to specify a URL to the node/edge file, then having NEAT retrieve and decompress the file in its run location, updating the node and edge paths in the process.