-
Notifications
You must be signed in to change notification settings - Fork 5
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
Jedd/cxpla 55 add required keyword for more geometry types #220
Jedd/cxpla 55 add required keyword for more geometry types #220
Conversation
…ired-keyword-for-more-geometry-types
…ired-keyword-for-more-geometry-types
* fix arcgis units * usings * correct units --------- Co-authored-by: Jedd Morgan <45512892+JR-Morgan@users.noreply.github.com>
ready for review, but until specklesystems/speckle-sharp-sdk#101 is made this can't be merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just 2 super minor things! 🙌🏼
@@ -26,7 +26,8 @@ public IReadOnlyList<Base> Convert(ACG.Multipatch target) | |||
{ | |||
List<Base> converted = new(); | |||
// placeholder, needs to be declared in order to be used in the Ring patch type | |||
SGIS.PolygonGeometry3d polygonGeom = new() { }; | |||
SGIS.PolygonGeometry3d polygonGeom = | |||
new() { units = _contextStack.Current.Document.ActiveCRSoffsetRotation.SpeckleUnitString }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this SpeckleUnitString
computed for every call?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it's being set once, calculated from ACG.SpatialReference
, this Document
is our own ArcGISDocument
class (I presume because we need reference to both the Arcgis Project
, Map
and CRSoffsetRotation
This will need some cleanup with the record
context changes that you and @adamhathcock have worked on. For now I'm tempted to leave as is.
...it/Speckle.Converters.RevitShared/ToSpeckle/TopLevel/TopographyTopLevelConverterToSpeckle.cs
Outdated
Show resolved
Hide resolved
Sdk/Speckle.Connectors.Utils/Instances/InstanceObjectsManager.cs
Outdated
Show resolved
Hide resolved
…ired-keyword-for-more-geometry-types
Connectors updates for specklesystems/speckle-sharp-sdk#101 changes
Changes several conversion functions to comply with using respecting the
required
keyword.importantly, I've made it so we are now setting units on several Revit and ArcGIS (still todo) conversions where previously we were defaulting to Meters erroneously.