eida / eida-portal Goto Github PK

Add following buttons that remove / invert selection of elements based on provided coordinates (also via map bounding box):

1. Events tab
   1. Remove selected events within coordinates
   2. Invert selection of events within coordinates
2. Stations tab
   1. Remove selected stations within coordinates
   2. Invert selection of stations within coordinates

[ x ] Use Routing Web Service to get stationd data
[ x ] Add network start/end year
[ x ] Add station stream codes

A query for network Z3 - (2015) on the Stations tab returns stations from the Aegean deployment in 2005. Additionally, I would add a sort before inserting the list of networks with two opt group tags: temporary, permanent.

Federator should not be used before it is commissioned. Some alternatives could be:

• ObsPy
• fdsnws_fetch

The P/Pdiff and S/Sdiff time window selection methods are not implemented.

Add network start/end year in the backend service providing station list
Or:
Make use of network+station service in the station.service.ts

Drop-downs holding a lot of elements (Networks, Stations) are pretty slow.
The solution could be to add a virtual scroll functionality, so dynamically render only those elements which at certain point should be visible on the screen.

The P/Pdiff and S/Sdiff time window selection methods are not implemented.

Add a dropdown to select between network, station, channel and response response levels.

When "download" button is hit, the "save file" popup is shown when data is already downloaded and packaged, which might take some time and no progress notification is given to the user.

Give a popup with an overview of selected criteria.

Add a functionality to popup a notification instead of just logging the output to console.

1. On the frontend side - get selected network code and station code
2. Query the backend to get the list of available stream codes ordered based on availability

Network start year value is crucial for referencing to the original network (used across the board, from filtered drop-downs to URL builders). This concerns both front and back end.

• Update backend sync_networks to retrieve xml ipv text and add network start year in the station info

• Event based request requires event + station selection - it will download and pack files per event (one pack with files for given event, preferably event id as pack name).
• Station based request does not require event selection - it just downloads data based on station + stream + time window selection (only allowed in relative time window selection method).

In the map.component.ts the coordinate extraction and conversion needs to be made right.

In the stations tab, it is possible to deselect station without removing it from the set. Skipped stations are included in the request anyway. Probably the same applies for events!

It is not supported (yet) when selecting stations by region or by events.