How to reuse the remote data set machinery for local data sets?

I think that the remote data set are great, in particular because they are donwsample and it is possible to let GMT select the resolution needed for each map.

However, some datasets won’t go to the server (due to lack of license, private/sensitive data, etc).

I wonder how can I do to reuse that machinery (to select the resolution) for datasets on my pc.

I know that I can use the scripts in gmtserver-admin to downsample my grid. But, them I don’t know how to proceed.

Should I put the results in my userdir/server directory and then edit the gmt_data_server.txt and gmt_hash_server.txt files? How should I do it? Editing those files would interfere with the remote data sets?

Is there any better solution?

1 Like

The problem is that those two meta files gets updated every day (if you access a remote file that often) and then any manual edits will be gone. The solutions I see are:

  1. Maintain two separate server subdirectories in .gmt and just have a script that renames one server_saved and the other server. That way you can run that script like “switch_server gmt|mine” and the script will then make active the server directory that goes with it. Downside is that you only would have access to your files until you switch back to the gmt remote data
  2. We would have to make changes to gmt to allow for private server directories and also search those when a user uses @private_relief_12s for instance. This would then be listed perhaps in a private subdirectory with similar structure to server but would never be written to or deleted by GMT. I do not have time to do this now though.

Ok. Many thanks Paul!

The problem is that those two meta files gets updated every day.

I can this turn off with gmt set GMT_DATA_UPDATE_INTERVAL never, right?

Yes you can, I should have mentioned that.

1 Like