Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
R
Rugged
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Orekit
Rugged
Commits
569db8c6
Commit
569db8c6
authored
3 years ago
by
Luc Maisonobe
Browse files
Options
Downloads
Patches
Plain Diff
Javadoc.
parent
6c2c1ee1
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Pipeline
#1598
passed
3 years ago
Stage: verify
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/main/java/org/orekit/rugged/raster/Tile.java
+13
-1
13 additions, 1 deletion
src/main/java/org/orekit/rugged/raster/Tile.java
with
13 additions
and
1 deletion
src/main/java/org/orekit/rugged/raster/Tile.java
+
13
−
1
View file @
569db8c6
...
...
@@ -256,7 +256,19 @@ public interface Tile extends UpdatableTile {
double
interpolateElevation
(
double
latitude
,
double
longitude
);
/** Find the intersection of a line-of-sight and a Digital Elevation Model cell.
* @param p point on the line
* <p>
* Beware that for continuity reasons, the point argument in {@code cellIntersection} is normalized
* with respect to other points used by the caller. This implies that the longitude may be
* outside of the [-π ; +π] interval (or the [0 ; 2π] interval, depending on the DEM). In particular,
* when a Line Of Sight crosses the antimeridian at ±π longitude, the library may call the
* {@code cellIntersection} method with a point having a longitude of -π-ε to ensure this continuity.
* As tiles are stored with longitude clipped to a some DEM specific interval (either [-π ; +π] or [0 ; 2π]),
* implementations MUST take care to clip the input point back to the tile interval using
* {@link org.hipparchus.util.MathUtils#normalizeAngle(double, double) MathUtils.normalizeAngle(p.getLongitude(),
* someLongitudeWithinTheTile)}. The output point normalization should also be made consistent with
* the current tile.
* </p>
* @param p point on the line (beware its longitude is <em>not</em> normalized with respect to tile)
* @param los line-of-sight, in the topocentric frame (East, North, Zenith) of the point,
* scaled to match radians in the horizontal plane and meters along the vertical axis
* @param latitudeIndex latitude index of the Digital Elevation Model cell
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment