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 7.1
edited by robert
on 2025/06/17 16:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,15 +18,15 @@
18 18  
19 19  The recommended process is:
20 20  
21 -~1. Check availability
21 +~1. Check availability;
22 22  
23 -2. Review the terms and conditions: [[ANSIR: Terms and Conditions>>https://www.auscope.org.au/ansir-terms]]
23 +2. Review the terms and conditions: [[ANSIR: Terms and Conditions>>https://www.auscope.org.au/ansir-terms]].  ;
24 24  
25 -3. Review the application form: [[ANSIR: Application Form>>https://www.auscope.org.au/ansir-application-form]]
25 +3. Review the application form: [[ANSIR: Application Form>>https://www.auscope.org.au/ansir-application-form]] ;
26 26  
27 -4. Contact our Scientific Coordinator to schedule a consultation
27 +4. Contact our Scientific Coordinator to schedule a consultation;
28 28  
29 -5. Submit your application
29 +5. Submit your application.
30 30  
31 31  = Metadata =
32 32  
... ... @@ -34,10 +34,8 @@
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 +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. 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 may 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!//**
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!//**
40 -
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.