You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/man/Tutorial_Basic.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,10 +204,10 @@ In creating this image, I used the `Clip` tool of Paraview to only show topograp
204
204
### 4. Cartesian data
205
205
As you can see, the curvature or the Earth is taken into account here. Yet, for many applications it is more convenient to work in Cartesian coordinates (kilometers) rather then in geographic coordinates.
206
206
`GeophysicalModelGenerator` has a number of tools for this.
207
-
First we need do define a `ProjectionPoint` around which we project the data
207
+
First we need do define a `projectionPoint` around which we project the data
Copy file name to clipboardExpand all lines: docs/src/man/Tutorial_LaPalma.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ In order to create model setups, it is helpful to first transfer the data to Car
65
65
This requires us to first determine a *projection point*, that is fixed. Often, it is helpful to use the center of the topography for this. In the present example, we will center the model around La Palma itself:
66
66
67
67
```julia
68
-
proj =ProjectionPoint(Lon=-17.84, Lat=28.56)
68
+
proj =projectionPoint(Lon=-17.84, Lat=28.56)
69
69
```
70
70
71
71
Once this is done you can convert the topographic data to the cartesian reference frame
So far, the subducting part of the slab was always straight. We can also create a curved slab by using the `AddSlab!` function. This uses a parametric representation of the slab and is a bit more involved than the `AddBox!` function.
228
+
So far, the subducting part of the slab was always straight. We can also create a curved slab by using the `addSlab!` function. This uses a parametric representation of the slab and is a bit more involved than the `addBox!` function.
Next, we should define a `Trench` structure, which contains info about the trench which goes in 3D from `Start` - `End` coordinates (`x`,`y`)-coordinates respectively. As we are dealing with a 2D model, we set the `y`-coordinates to -100.0 and 100.0 respectively.
@@ -251,7 +251,7 @@ Add them to the `CartData` dataset:
Lets start with defining the horizontal part of the overriding plate. Note that we define this twice with different thickness to deal with the bending subduction area:
The main data structure used in GeophysicalModelGenerator.jl is `GeoData`, which contains info about the `longitude`,`latitude`, and `depth` of a data set, as well as several data sets itself.
4
-
We also provide a `UTMData`, which is essentially the same but with UTM coordinates, and a `CartData` structure, which has Cartesian coordinates in kilometers (as used in many geodynamic codes). If one wishes to transfer `GeoData` to `CartData`, one needs to provide a `ProjectionPoint`.
4
+
We also provide a `UTMData`, which is essentially the same but with UTM coordinates, and a `CartData` structure, which has Cartesian coordinates in kilometers (as used in many geodynamic codes). If one wishes to transfer `GeoData` to `CartData`, one needs to provide a `projectionPoint`.
5
5
For plotting, we transfer this into the `ParaviewData` structure, which has cartesian coordinates centered around the center of the Earth. We employ the `wgs84` reference ellipsoid as provided by the [Geodesy.jl](https://github.com/JuliaGeo/Geodesy.jl) package to perform this transformation.
Copy file name to clipboardExpand all lines: docs/src/man/projection.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Typically, you load a dataset by reading it into julia and either generating a `
4
4
5
5
If you write the data to `Paraview`, it is internally converted to a Paraview structure (which involves `x,y,z` Cartesian Earth-Centered-Earth-Fixed (ECEF) coordinates using the `wgs84` ellipsoid).
6
6
7
-
Yet, if you do geodynamic calculations the chances are that the geodynamic code does not operate in spherical coordinates, but rather use cartesian ones. In that case you should transfer your data to the `CartData` structure, which requires you to specify a `ProjectionPoint` that is a point on the map that will later have the coordinates `(0,0)` in the `CartData` structure.
7
+
Yet, if you do geodynamic calculations the chances are that the geodynamic code does not operate in spherical coordinates, but rather use cartesian ones. In that case you should transfer your data to the `CartData` structure, which requires you to specify a `projectionPoint` that is a point on the map that will later have the coordinates `(0,0)` in the `CartData` structure.
8
8
9
9
10
10
#### 1. Converting
@@ -41,8 +41,8 @@ As the area is large, it covers a range of `UTM` zones (and every point has a UT
41
41
Yet, what we could do instead is show all data with respect to a single UTM zone. For this, we have to select a point around which we project (in this case more or less in the center):
Copy file name to clipboardExpand all lines: docs/src/man/visualise.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,8 +36,8 @@ Which will look like:
36
36
37
37
This is an example where we used `GeoData` to visualize results. Alternatively, we can also visualize results in km (often more useful for numerical modelling setups). For `Visualize` to work with this, we however need orthogonal cartesian data, which can be obtained by projecting both the data.
0 commit comments