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
* using GOCore
* Fix errors found in docs
* Set the current module in the Literate source
This way, docstrings are resolved respective to where the page is.
* add TGGeometry to docs project
* Update docs/src/api.md
Copy file name to clipboardExpand all lines: GeometryOpsCore/src/types/manifold.jl
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ In GeometryOps (and geodesy more generally), there are three manifolds we care a
16
16
- [`AutoManifold`](@ref): a special manifold that automatically selects the best manifold for the operation when it's executed. Resolves to [`Planar`](@ref), [`Spherical`](@ref), or [`Geodesic`](@ref) depending on the input geometry.
17
17
18
18
Generally, we aim to have `Linear` and `Spherical` be operable everywhere, whereas `Geodesic` will only apply in specific circumstances.
19
-
Currently, those circumstances are [`area`](@ref), [`arclength`](@ref), and [`segmentize`](@ref), but this could be extended with time and https://github.com/JuliaGeo/SphericalGeodesics.jl.
19
+
Currently, those circumstances are [`area`](@ref), `arclength`, and [`segmentize`](@ref), but this could be extended with time and https://github.com/JuliaGeo/SphericalGeodesics.jl.
0 commit comments