Last modified by KB on 2025/08/12 11:59

From version 15.1
edited by KB
on 2025/06/30 10:05
Change comment: There is no comment for this version
To version 16.1
edited by KB
on 2025/06/30 10:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -37,11 +37,11 @@
37 37  
38 38  = Applying for an FDSN Network Code =
39 39  
40 -The FDSN requires that each seismic network have a 2-character Network Code assigned to it to differentiate it when shared online. These must be registered from FDSN [[HERE>>https://www.fdsn.org/networks/request/]] or you can ask us to help with this. Ideally you will need a network code before you plan on saving any data as this network code is part of the metadata stored in the file's data.
40 +The FDSN assigns a 2-character Network Code to each seismic network to differentiate them when shared online. Register your Network Code with FDSN [[HERE>>https://www.fdsn.org/networks/request/]]before saving any data ~-~- it will be part of the metadata stored in your network file data.
41 41  
42 -Because the network code is only 2 characters, often they are reused and can only be differentiated by the range of years they are in operation. Thus, it is **CRITICAL** to ensure that you select the correct year range for your experiment, because if your project ends up with data outside of the range assigned to your requested network code then you might be forced to use two separate network codes to accommodate this "spill over". For example, if you are operating a multi-year network with a planned end during 2027, we recommend adding a year of "buffer" to your registration request in the event that your experiment is delayed or extends further than you originally planned, e.g. request a code that spans 2024-2028.
42 +Because the 2-character codes are often reused, networks are also differentiated by the range of years they are in operation. It is therefore **CRITICAL** to register a year range that will accommodate your entire experiment. If you are operating a multi-year network we recommend adding a year to buffer your registration in case of delays or extensions (e.g., for a project planned from Feb 2024 to April 2027, please register 2024-2028). This range can be trimmed when your project has ended.
43 43  
44 -Remember, **//you can always trim the timespan of your network, but don't assume you can add to it!//**
44 +If your project ends up with data outside of the assigned range, and the code has already been reused for another network, you will need an additional code for the "spill over". Remember**//You can always trim the timespan of your network, but you may not be able to add to it!//**
45 45  
46 46  = Accessing your data at AusPass =
47 47