#Python rf toolbox software

GISMO: Data download, processing and visulization software written in Matlab.SeisIO.jl: Data download, processing and visulization software written in Julia.

#Python rf toolbox manual

Chinese manual (better) | Zhigang Peng’s tutorial | IRIS’s manual | An intro video.

SAC: Seismic Analysis Code, the most commonly used seismic data processing software | Request.

fetch_NOISE: Download daily seismograms from the IRIS-DMC.

fetch_Events: Download event data from IRIS-DMC.

AusPass’s examples: Access AusPass data with ObsPy.

EIDA’s examples: using direct HTTP requests and ObsPy FDSN Client.ObsPy Teaching Material: Workshops / Posters / Presentations.Live Jupyter Notebooks for Seismology: Workshops - ORFEUS_lisbon_2017_EIDA_webservices.Retrieving Data from Data Centers: e.g., FDSN Web Services & IRIS Web Services.

ObsPy: Data download, processing and visulization software written in Python.

SOD: a very powerful seismic data request tool | Chinese tutorial | SeisMan’s recipes | coreman’s recipes.

jweed: Data request client written in Java.

IRIS Wilber 3: A web GUI to request waveform data of individual seismic events | Chinese note.

BREQ_FAST: Seismic data request by sending email | Chinese note.

ROVER: A command line tool to robustly retrieve geophysical timeseries data from data centers.

#Python rf toolbox archive

PH5WS: provide PH5 data and metadata | Accessing PH5 Archive with FetchData | wiki.MUSTANG: data quality analysis services.FDSNWS: Chinese note of IRIS Fetch scripts.There's an example of a fully fleshed out Python toolbox here, though it doesn't cover your exact case (it'd be difficult to cover every case in the doc).Īlso, check out recent presentations on creating toolboxes here, where parts of this topic are covered (haven't watched this one in a while, it might not cover your exact use case but might provide some more insights).Seismic Data Downloading and Processing Data Request Tools The reason GPLayer doesn't have a data filter type is because GPLayer is for any Layer (which includes tables, raster, etc.) and GPFeatureLayer is explicitly only the subset of Layers with features (Feature Class, Shapefile). You can safely omit the line = 'Featureclass'.Īlso note that you won't be able to do the same with the GPLayer data type. Note that the default filter type for GPFeatureLayer is 'Featureclass', so there is actually no need to explicitly specify this as in the example below. You can then choose a 'Featureclass' filter type. You can accomplish what you are trying to do more concisely by changing dataType to 'GPFeatureLayer'. *Edit* JohannesLinder beat me to this solution while I was writing this out =D. Set this to an empty list and your code works for me. There is a bug in your code at line 28, where you did not set polylist to any value. Poly_list = # list only polygon feature layers

#Python rf toolbox validation code

The validation code works just fine, but every time I run it, it yields the somewhat cryptic error 000820: The parameters need repair. It also seems like 'parameters' and 'messages' behave as magic arcpy variables that don't need to be expressly instantiated I'm having trouble finding explicit guidance/documentation on that.Įither way, could someone who has done this take a look at my code and help me understand why it's failing? I can't find any good examples anywhere of what a fully, completed toolbox with validation and source code should look like. Unfortunately, programming python toolboxes is not very well documented by Esri.