Introduction
Seismic array observation in Furukawa district is the most dense array network for strong ground-motion observations with a modern remote monitoring system, organized by Kyoto University, Tokyo Institute of Technology, Osaki city office, and aLab Co.Ltd, since September 2011. The details of array system are described in the recent article published in Seismological Research Letters. Observation data for specific earthquake events are available only for an academic research.
User policy
- Users must specify the data resource when users publish a scientific paper, a conference presentation, and any other documents.
- Users must refer to the article published in Seismological Research Letters;
- Users must inform a flaw in the data and system to the administrator before users announce it to the public.
Goto, H., Morikawa, H., Inatani, M., Ogura, Y., Tokue, S., Zhang, X.R. Iwasaki, M., Araki, M., Sawada S. and Zerva, A.: Very dense seismic array observations in Furukawa district, Japan, Seismological Research Letters, Vol.83, No.5, pp.765-774, 2012. PDF, Link
Caution
- Horizontal components of the all data are not directed to exact North and East. Please correct it based on the table in Stations
- Some of the data involves accidental noise due to power supply, data disconnection, and any other reasons. Please confirm the wave shape before the usage.
- Clocks of the sensor are adjusted to the clock signal from a GPS, however some time stamps of the data are not enough accurate. Please be sure to check it before the usase. Up-Down component of the signal may be helpful.
Stations
Station locations and azimuths are listed in a table below. Sensor azimuth is the angle from magnetic North to North component of the sensor. Please correct the horizontal components. Sensors belongs to stations with a sign (*1 opposite) in a remarks column output opposite accelerograms for all three components. Please correct the sign first, and then correct the azimuth for the stations.
Station code | Latitude, Longitude (N,E; degree) | Azimuth (from North) | Start (year/month/day) | Photo | Remarks |
---|---|---|---|---|---|
F01 | 38.5725, 140.9663 | 26 | 2011/09/25 | tgz | |
F02 | 38.5749, 140.9618 | 0 | 2011/09/27 | tgz | |
F03 | 38.5768, 140.9558 | -7 | 2011/09/28 | tgz | |
F04 | 38.5784, 140.9639 | -5 | 2011/09/26 | tgz | |
F05 | 38.5734, 140.9527 | 7 | 2011/09/25 | tgz | |
F06 | 38.5707, 140.9604 | 13 | 2011/09/26 | tgz | |
F07 | 38.5707, 140.9606 | 10 | 2011/10/27 | tgz | |
F08 | 38.5747, 140.9574 | 9 | 2011/10/25 | tgz | observation terminated (-2014/03/09) |
F09 | 38.5775, 140.9586 | 164 | 2011/10/25 | tgz | change sensor azimth (N008E, -2015/04/27) |
F10 | 38.5785, 140.9671 | 13 | 2011/10/26 | tgz | azimuth corrected on 2013/05/06 *1 opposite (2013/07/09-) |
F11 | 38.5818, 140.9586 | 6 | 2011/10/26 | tgz | |
F12 | 38.5773, 140.9574 | 28 | 2011/11/22 | tgz | |
F13 | 38.5818, 140.9519 | -22 | 2011/11/22 | azimuth corrected on 11, Dec. 2012 | |
F14 | 38.5740, 140.9602 | 5 | 2011/11/23 | tgz | observation terminated (-2015/04/05) |
F15 | 38.5610, 140.9572 | 6 | 2011/11/23 | tgz | |
F16 | 38.5722, 140.9711 | 25 | 2011/11/25 | tgz | |
F17 | 38.5810, 140.9625 | 1 | 2011/11/24 | ||
F18 | 38.5737, 140.9642 | 108 | 2011/12/21 | ||
F19 | 38.5754, 140.9538 | -2 | 2011/12/23 | ||
F20 | 38.5778, 140.9549 | 0 | 2012/02/26 | tgz | *1 opposite |
F21 | 38.5868, 140.9718 | 36 | 2012/02/28 | *1 opposite | |
F22 | 38.5752, 140.9592 | 26 | 2012/02/27 | tgz | *1 opposite |
F23 | 38.5754, 140.9629 | 36 | 2012/02/28 | tgz | *1 opposite |
F24 | 38.5803, 140.9536 | 25 | 2012/05/12 | tgz | |
F25 | 38.5794, 140.9663 | 16 | 2012/07/31 | tgz | |
F26 | 38.5827, 140.9743 | 36 | 2012/08/01 | tgz | |
F27 | 38.5722, 140.9618 | 15 | 2012/08/01 | tgz | |
F28 | 38.5814, 140.9730 | 34 | 2012/08/02 | tgz | |
F29 | 38.5829, 140.9738 | 34 | 2012/08/03 | observation terminated (-2015/04/05) | |
F30 | 38.5919, 140.9618 | 42 | 2012/08/04 | tgz | observation terminated (-2015/04/06) |
F31 | 38.5705, 140.9736 | 14 | 2012/10/28 | tgz | *1 opposite (2015/04/05-) |
F32 | 38.5841, 140.9734 | 30 | 2012/10/28 | tgz | |
F33 | 38.5779, 140.9577 | 25 | 2012/10/29 | tgz | *1 opposite (2013/11/06-) time correction is not ensured (2013/09/07-2013/11/06) |
F34 | 38.5807, 140.9767 | 2 | 2012/10/29 | tgz | observation terminated (-2014/08/20) |
F35 | 38.5731, 140.9669 | 18 | 2013/01/21 | tgz | |
F36 | 38.5883, 140.9556 | 42 | 2013/03/21 | tgz | |
F37 | 38.5695, 140.9650 | 12 | 2015/08/18 | *1 opposite |
File Format
File name consists of trigered time (YYYYMMDDhhmm) and station code (Fxx), are connected with under bar. The trigered time is represented by JST (GMT+9). For example, 201203272001_F01.dat means a data for station F01 at 20:01 on 27, Mar. 2012.
Data file is ASCII containing 3 columns, which are the data on East-West, North-South, and Up-Down components, respectively. East, North and Up are the positive direction, excepting the sensor indicated (*1 opposite) in the above table. Notice that the horizontal components are not exact East-West and North-South components. Unit is gal (cm/s/s) and all sampling rates are fixed to be 100Hz.
Event Data
triger time [GMT+9] (YYYY/MM/DD hh:mm) | average PGA (gal) | number ofavailable stations |
---|