flatfile
The query below returns 500 entries for the default set of tables for sites with VS30 less than 300 m/s.
https://gmdatabase.org/flatfile?limit=500&vs30<300This one returns data from the response_spectra and intensity_measure tables for all motions with pga_rotd50 between 0.1 and 0.2 g.
https://gmdatabase.org/flatfile?limit=500&tables=response_spectra,intensity_measure,time_series_metadata&rotd50_pga=0.1-0.2Let's say we want to retrieve, a range of spectral periods, fill all null fields with “-999”, and sort the values in descending order of PGA? We would then do this.
https://www.uclageo.com/gm_database/api/index.php/flatfile?format=html&limit=500&tables=event,event_type,network,station,site,motion,time_series_metadata,intensity_measure,response_spectra&vs30=0-300&components=rotd50&pga_rotd50=0.1-0.2&period=0.01-5&fill_null=-999&sortby=pga_rotd50&order=DESC
or (since these are the default flatfile tables)
https://www.uclageo.com/gm_database/api/index.php/flatfile?format=html&limit=500&vs30=0-300&components=rotd50&pga_rotd50=0.1-0.2&period=0.01-5&fill_null=-999&sortby=pga_rotd50&order=DESC
We could go on and on like this all day because there are so many different possibilities here. I think you get the picture though because that last one was pretty complicated. Feel free to reach out to us if you have any questions about forming these URLs.