Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rg proj comparison #71

Merged
merged 5 commits into from
Nov 8, 2023
Merged

Rg proj comparison #71

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
fd8f424
Better Wasm support in Cargo.toml
busstoptaktik Aug 31, 2023
069a511
Start rumination #8
busstoptaktik Aug 21, 2023
e945867
stash
busstoptaktik Oct 26, 2023
4773912
stash
busstoptaktik Nov 2, 2023
84ea1e0
Rumination 8 for publication
busstoptaktik Nov 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,9 @@ env_logger = {version="0.10.0"}

[lib]
name = "geodesy"
# Needed for Wasm:
# wasm-pack build --target web --no-default-features --features js
crate-type = ["cdylib", "rlib"]

[features]
js = ["uuid/js"]
Expand All @@ -62,4 +65,10 @@ required-features = ["binary"]
# cargo b --bin kp --features=with_plain,binary

[profile.release]
lto = true
strip = true # Automatically strip symbols from the binary.

[target.wasm32-unknown-unknown.dependencies]
wasm-bindgen = "0.2"
[target.wasm32-unknown-unknown.dev-dependencies]
wasm-bindgen-test = "0.2"
2 changes: 1 addition & 1 deletion ruminations/000-rumination.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,7 @@ ctx.apply(ed50_wgs84, Fwd, data);
Then a user defined operator:

```rust
use geodesy::operator_authoring::*;
use geodesy::authoring::*;

// See examples/03-user-defined-operators.rs for implementation details
pub struct MyNewOperator {
Expand Down
5 changes: 2 additions & 3 deletions ruminations/003-rumination.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,12 +154,11 @@ On the occasion of Knud Poder's 90th birthday in 2015, I wrote a few words about
> /Thomas Knudsen, Danish Geodata Agency
>
>
> [1] Thomas Knudsen, Simon L. Kokkendorff, Karsten E. Engsager (2012): A Vivid Relic Under Rapid Transformation, OSGeo Journal vol. 10, pp. 55-57, URL https://journal.osgeo.org/index.php/journal/article/download/200/167
> [1] Thomas Knudsen, Simon L. Kokkendorff, Karsten E. Engsager (2012): A Vivid Relic Under Rapid Transformation, OSGeo Journal vol. 10, pp. 55-57, URL <https://journal.osgeo.org/index.php/journal/article/download/200/167>
>
> [2] R. König and K. H. Weise (1951): Mathematische Grundlagen der Höheren Geodäsie und Kartographie, Erster Band. Springer, Berlin/Göttingen/Heidelberg, 1951.
>
> [3] L. Krüger (1912): Konforme Abbildung des Erdellipsoids in der Ebene. Neue Folge 52. Royal Prussian Geodetic Institute, Potsdam. URL http://bib.gfz-potsdam.de/pub/digi/krueger2.pdf

> [3] L. Krüger (1912): Konforme Abbildung des Erdellipsoids in der Ebene. Neue Folge 52. Royal Prussian Geodetic Institute, Potsdam. URL <http://bib.gfz-potsdam.de/pub/digi/krueger2.pdf>

### Document History

Expand Down
2 changes: 1 addition & 1 deletion ruminations/004-rumination.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ In a sense, this reflects the modularity of the transformation operator implemen

### Problem #3: The geodetic registry interface ("the resolver")

In PROJ, much automation effort is spent trying to guess the most appropriate transformation betwwen any two CRS. Let's call this effort "resolving" and the contraption implementing that "the resolver".
In PROJ, much automation effort is spent trying to guess the most appropriate transformation between any two CRS. Let's call this effort "resolving" and the contraption implementing that "the resolver".

PROJ is built on the idea that the users should know what system (e.g. represented as an EPSG CRS code) their data are comming from, and which system they want them transformed to. RG on the other hand is built on the much simpler idea, that the users should know which transformation they want to apply.

Expand Down
Loading