Paul Connelly

> I would like to see a complete implementation of this extension in CesiumJS or iTwinJS Most of the rendering pieces are already in place in iTwin.js. I think the...

> How does this extension define the ends of each edge? Do they just end? Are they beveled/rounded? How do they connect to other edges? Beveling and rounding are only...

@kring said: > I would like to see a complete implementation of this extension in CesiumJS or iTwinJS, though, if there isn't one already. It would be useful both as...

> Attachment point stored as a string (ex. "MiddleRight"). This will be related to the shape of the Text Frame. So users can't choose any point on the frame shape...

I lean toward Option 1. It can make sense for a text annotation to be a BIS object. It doesn't make much sense for a leader to be a BIS...

> We should remove either TextBlock.justification or TextAnnotation.Anchor.horizontal. They are redundant Please explain why you consider them redundant. [Anchor point](https://www.itwinjs.org/reference/core-common/annotation/textannotationanchor/) is orthogonal to text justification. > Add a Height property...

> Could these help explain the motivations? Not really. They all specify **what** you want on a technical level, not **why** you (or users) want it, except for a mention...

> in the image below, what value is there in rotating this text around the right edge? > >  Get rid of the extraneous padding on the right-hand side...

> 4. We should remove either TextBlock.justification or TextAnnotation.Anchor.horizontal. They are redundant @Josh-Schifter have we come to a consensus that we **don't** want to do this? > 3. Add text...

> Problems: > > 1. The API key was not propagated. Seems like similar problem that @mdastous-bentley [solved](https://github.com/iTwin/itwinjs-core/blob/master/core/frontend/src/RealityDataSourceCesiumIonAssetImpl.ts) for Cesium ION URLs. > 2. Sub tile URL was not properly...