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.

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

Update h_schema_300.rst #456

Merged
merged 1 commit into from
Oct 16, 2024
Merged
Changes from all commits
Commits
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
5 changes: 4 additions & 1 deletion source/h_schema_300.rst
Original file line number Diff line number Diff line change
Expand Up @@ -185,11 +185,14 @@ General changes
- All tables that have a geometry (in the new schema) also have a code, display name, and tags.

- Instead of using latitude/longtitude coordinates (WGS84, EPSG:4326) to define geometries, the data uses a local, projected coordinate system (set by model_settings.epsg_code). This has several benefits:

- Measurements can be done in meters instead of degrees

- Spatial schematisation checks no longer need to project the data before performing the check, making them faster and in some cases more accurate

- The data as it appears on the map canvas in the 3Di Modeller Interface is exactly the same as what is used by 3Di. This is expected to fix some hard-to-solve issues with 2D boundary conditions not being located at the correct location, even though they seem to be exactly in the right location on the map.
- It simplifies the routines used by 3Di to convert schematisation data to 3Di models, by eliminating the need to reproject the data to a projected CRS.

- It simplifies the routines used by 3Di to convert schematisation data to 3Di models, by eliminating the need to reproject the data to a projected CRS.

Tags
^^^^
Expand Down
Loading