CesiumGS / CesiumGS/cesium

entity using other local reference frame than ENU?

Open
#6,041 2 comments 0 reactions 0 assignees View on GitHub
category - entity type - enhancement
Dominant language
JavaScript
Stars
15.7k
Forks
3.9k
Avg merge
4d 6h
Merged PRs (30d)
34

Description

Hello,
after seeing this [post](https://groups.google.com/forum/#!searchin/cesium-dev/enu|sort:date/cesium-dev/WiI0xn7BgBI/SBocZp_ADgAJ) and after seeing that ``entity.computeModelMatrix`` is now public (see [here](https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/DataSources/Entity.js#L596-L618)), do you think it's a good feature to make the the default ``Transforms.eastNorthUpToFixedFrame`` in line [613](https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/DataSources/Entity.js#L613) more versatile and use an other transform?

Contributor guide

Open the contributing guide

Research direction

Start with Source/DataSources/Entity.js, especially entity.computeModelMatrix and the Transforms.eastNorthUpToFixedFrame call around line 613. Read the linked discussion to determine which alternative local reference frames are needed and how callers would select them. Done means the supported transform behavior and its API are defined and validated by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.