meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tectonicwaters:2013:1113_working_with_plate_velocities_in_gplates [2020/12/29 22:33] – ↷ Page moved and renamed from tectonicwaters:2020:1229_working_with_plate_velocities_in_gplates to tectonicwaters:2013:1113_working_with_plate_velocities_in_gplates christian | tectonicwaters:2013:1113_working_with_plate_velocities_in_gplates [2020/12/29 23:07] (current) – christian | ||
---|---|---|---|
Line 8: | Line 8: | ||
GPlates v1.3 can display and extract plate velocities. Depending on your work, you might have different requirements for these domains, plus there are a few pitfalls on the way. Currently, there are two three ways to create velocity domains in GPlates: | GPlates v1.3 can display and extract plate velocities. Depending on your work, you might have different requirements for these domains, plus there are a few pitfalls on the way. Currently, there are two three ways to create velocity domains in GPlates: | ||
- | - Create a global set of points at regular spacing which stay fixed absolute and the plates move across them. This method will report velocities of whatever plate will be on top of these points. This method is generally used when working with global models and when one wants to export boundary conditions for global geodynamic modelling (the CitcomS and Terra mesh generation options). Use < | + | - Create a global set of points at regular spacing which stay fixed absolute and the plates move across them. This method will report velocities of whatever plate will be on top of these points. This method is generally used when working with global models and when one wants to export boundary conditions for global geodynamic modelling (the CitcomS and Terra mesh generation options). Use < |
- | + | - Alternatively, | |
- | - Alternatively, | + | - Use [[https:// |
- | - Use QGIS and | + | |
One important thing to know is that GPlates utilises layers for different types of data, so here's a little digression and some background info. This layer business is much like GIS software has vector and raster layers, and other layers which are the result of some computations/ | One important thing to know is that GPlates utilises layers for different types of data, so here's a little digression and some background info. This layer business is much like GIS software has vector and raster layers, and other layers which are the result of some computations/ | ||
- | * < | + | * < |
- | * ReconstructedGeometries: | + | * <color #b5e61d>ReconstructedGeometries</ |
- | * Co-registration: | + | * <color #ff7f27>Co-registration</ |
- | * Calculated velocity fields: Another one of of those layers where the layer=feature collection equation breaks down. Here we load a point feature collection and combine it with other data such as topological polygons or static polygons to compute velocities. | + | * <color #99d9ea>Calculated velocity fields</ |
- | * Resolved topologial networks: This (brown) layer type is similar to the topological geometries but creates triangulated networks used for deformation. | + | * <color #efe4B0>Resolved topologial networks</ |
- | * Resolved topological geometries: Topologically closed polygons are created from the combination of a rotation file (ReconstructionTree) and a feature layer (ReconstructedGeometries). | + | * <color #c8bfe7>Resolved topological geometries</ |
- | * Reconstructed Raster: Raster data gets loaded into the red layer type. | + | * <color #ed1c24>Reconstructed Raster</ |
- | * 3D scalar field: Volume-rendering of scalar fields as, for example, from seismic tomography | + | * <color #22b14c>3D scalar field</ |
Line 33: | Line 32: | ||
- Create a global velocity domain layer using (1) from above or create your velocity points using method 2 or 3 from above. | - Create a global velocity domain layer using (1) from above or create your velocity points using method 2 or 3 from above. | ||
- | - Once you have created the velocity domain layer using option (1), GPlates will automatically load a new feature layer with the name of velocity point layer as you specified. If you have used the " | + | - Once you have created the velocity domain layer using option (1), GPlates will automatically load a new feature layer with the name of velocity point layer as you specified. If you have used the " |
+ | - The next thing you need is either a static polygon feature collection set or a topologically closed polygon feature collection and of course a rotation model loaded. The next steps will illustrate why. | ||
+ | - Only if you have created your point velocity domain layer manually): | ||
+ | - The key now is to connect the Velocity layer with other feature data. This can be a global polygon data set or a set of static polygons. Open the aqua-colored layer by clicking the little triangle on the left and under the " | ||
+ | - In the case that you are using global velocity domain points and polygons, make sure that in the " | ||
+ | - Once you have connected your surface domains with your velocity domains, you should see velocity vectors displayed in the main window. The settings for the vector display can be altered in the layer dialogue. {{ : | ||
+ | - If needed these vectors can be exported using the < | ||
~~DISCUSSION~~ | ~~DISCUSSION~~ | ||