Here is the English translation of the provided text:
We have prepared an API for extracting data. The specifications are as follows:
URL
https://kyoto-soundscape.sakura.ne.jp/api.php
Method 1
Specify the ID using either GET or POST method.
The data is output in JSON format.
Please find the ID from the list of locations on a separate page.
You can extract data from only one location at a time.
e.g. https://kyoto-soundscape.sakura.ne.jp/api.php?id=0001
Method 2
Specifying “all” for the ID allows you to retrieve all data in JSON format.
e.g. https://kyoto-soundscape.sakura.ne.jp/api.php?id=all
Data storage locations
https://kyoto-soundscape.sakura.ne.jp/db/data
https://kyoto-soundscape.sakura.ne.jp/db/thumbs
Thumbnail image filenames are not recorded in the database. Please generate filenames each time you retrieve them. As of August 2024, sizes “s” (vertical side 480 pixels) and “m” (1080 pixels) are stored. The filenames are formatted as “s_filename.jpg” and “m_filename.jpg” respectively.
How to retrieve a file
If data with id 0001 is retrieved, the file name and URL will be as follows.
| id | 0001 |
| File name of the original data | https://kyoto-soundscape.sakura.ne.jp/db/data/0001_Ava01_Raw.wav |
| Stereo data file name | https://kyoto-soundscape.sakura.ne.jp/db/data/Str_0001_Ava01.wav |
| Binaural data file name | https://kyoto-soundscape.sakura.ne.jp/db/data/Bnr_0001_Ava01.wav |
| File name of the panoramic photo | https://kyoto-soundscape.sakura.ne.jp/db/data/0001_Ava01.jpg |
| Thumbnail s size file name | https://kyoto-soundscape.sakura.ne.jp/db/thumbs/s_0001_Ava01.jpg |
| Thumbnail m size file name | https://kyoto-soundscape.sakura.ne.jp/db/thumbs/m_0001_Ava01.jpg |
Return value list
| id | Short ID (4 digits) |
| data_id | Long ID (short ID_block name point ID) |
| db | Noise value at recording |
| impression | Impressions of the recording location by the recorder |
| raw | File name of the original data |
| stereo | File name of the file that was cut out and made into stereo data |
| binaural | File name of the file that was cut out and converted to binaural data |
| photo | File name of the panoramic photo |
| spot | location ID |
| EW | Street name in east-west direction |
| NS | Street name in north-south direction |
| longitude | Longitude on Google Maps of the recorded location |
| latitude | Latitude on Google Maps of the recorded location |
| map | Google Map URL |
| Photo_lon | Longitude as indicated in the EXIF data of the photo |
| Photo_lat | Latitude as indicated in the EXIF data of the photo |
| distance(m) | Distance between the latitude and longitude on the map and the latitude and longitude in the EXIF data |
| Photo_alt | Altitude as indicated in the EXIF data of the photo |
| Photo_taken | Date and time the photo was taken as indicated in the photo’s EXIF data |
| Raw_taken | Creation date and time of the original data |
| Raw_metadata | List of metadata included in the original data |
| Time_lag | Time difference between the creation date and time of the original data and the date and time of the EXIF data |
| Street_EN | English translations of street names |
| Imp_EN | English translation of impressions |
About Location ID
The geographical IDs were assigned street names in the east-west direction in aiueo order, and the north-south direction was represented by numbers, starting from the north. The long IDs were converted to romanized characters (e.g. “na18” was converted to na18). (However, only the “a” line has va, vi, vu, ve, and vo to align the number of digits.（v = vowel）。
revision history
- 2024.04.14：API Release
- 2024.08.27：Create thumbnail data and add description
- 2024.09.10 : English translation added