Skip to Content
Last modified by KB on 2025/08/12 11:59
From version 9.1
edited by robert
on 2025/06/20 13:41
Change comment: There is no comment for this version
To version 10.1
edited by robert
on 2025/06/20 13:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -34,10 +34,12 @@
34 34  
35 35  = Applying for an FDSN Network Code =
36 36  
37 -Each seismic network needs its own 2-character Network Code to help differentiate it. 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.
37 +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.
38 38  
39 -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 your originally requested network code then you might be forced to use two separate network codes. If you are operating a multi-year network with a planned end of, say, 2027, we recommend adding a year of "buffer" to your registration request e.g. request a code from 2024-2028. Remember, **//you can always trim the timespan of your network, but don't assume you can add to it!//**
39 +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.
40 40  
41 +Remember, **//you can always trim the timespan of your network, but don't assume you can add to it!//**
42 +
41 41  = Accessing your data at AusPass =
42 42  
43 43  See [[HERE>>http://auspass.edu.au/xwiki/bin/view/Data/Tutorials/]] for tips and advice on using python and ObsPy to access our server.