Data Help with Data Submission of Data Custom Data Request

GAGE Custom Data Request

Most users will find the data they need from the GAGE Facility via our various data access methods, for example GPS/GNSS Data Access Methods. Some data are only available via special request. Use the form on this page for these custom data requests. (For support of large scale projects, such as field deployments, or long-term sustained data activities or proposal development, use the Request Support form.)

Custom data requests are custom in the sense that they are for data that would not otherwise be collected and archived by the GAGE Facility, such as:

  • GPS/GNSS high rate (i.e. 1- or 5-Hz rate)
  • borehole strain (i.e. processed 1-Hz rate)
  • borehole seismic (i.e. 200-Hz rate)
  • surface laser strain (i.e. processed 1-Hz rate)

or for data that are in a category not currently available from the GAGE Facility operated by EarthScope Consortium. Custom data requests are intended to be small scale in both space and time, i.e. for a limited set of stations within a limited period of time. See the Requirements below.

Custom data requests are supported on a best-effort basis, subject to personnel and resource constraints, and are prioritized by project funding/affiliation in the following order from high to low: (1) NSF-EAR, NSF-PLR and NASA-SENH; (2) NSF-other, government partners (USGS, NASA-other) and general community research and education; (3) commercial and all others. Custom data requests related to geophysical events (e.g. earthquakes) are always supported at the highest priority.


  1. All non-event response custom data requests must be submitted at least five business days prior to the data start date in order to be considered.
  2. Currently, we have a limit of 50 stations per custom data request. Once a request for 50 stations is fulfilled, a user may request 50 more stations, i.e., please do not submit multiple requests totalling more than 50 stations.
  3. High-rate data requests, e.g., 5Hz data, should include date/time extents limited to only the hours (time ranges) of interest and should not include extraneous data, e.g., requesting a full 24 hours of data when only 3 hours are needed for that day, even when multiple time ranges are needed for a given day. Limiting the amount of requested data will allow us to fulfill requests faster than if additional, high-rate GNSS data are needlessly requested.

To reduce spam, please answer the following question:
How many letters are in the word GAGE?:


Last modified: 2024-01-08  11:26:51  America/Denver