A location node can be added to a scene using a coordinate.
+
+
Its scale and position should not be adjusted, as these are used for scene
+layout purposes. To adjust the scale and position of items within a node,
+you can add them to a child node and adjust them there
Parameter to raise or lower the label’s rendering position relative to the node’s actual project location.
+The default value of 1.1 places the label at a pleasing height above the node.
+To draw the label exactly on the true location, use a value of 0. To draw it below the true location,
+use a negative value.
Note: we repeat code from LocationNode‘s implementation of this function. Is this because of the use of SCNTransaction
+to wrap the changes? It’s legal to nest the calls, should consider this if any more changes to
+LocationNode’s implementation are needed.
A location node can be added to a scene using a coordinate.
+
+
Its scale and position should not be adjusted, as these are used for scene
+layout purposes. To adjust the scale and position of items within a node,
+you can add them to a child node and adjust them there
Whether the location of the node has been confirmed.
+This is automatically set to true when you create a node using a location.
+Otherwise, this is false, and becomes true once the user moves 100m away from the node,
+except when the locationEstimateMethod is set to use Core Location data only,
+as then it becomes true immediately.
Whether a node’s position should be adjusted on an ongoing basis
+based on its given location.
+This only occurs when a node’s location is within 100m of the user.
+Adjustment doesn’t apply to nodes without a confirmed location.
+When this is set to false, the result is a smoother appearance.
+When this is set to true, this means a node may appear to jump around
+as the user’s location estimates update,
+but the position is generally more accurate.
+Defaults to true.
Whether a node’s position and scale should be updated automatically on a continual basis.
+This should only be set to false if you plan to manually update position and scale
+at regular intervals. You can do this with SceneLocationView‘s updatePositionOfLocationNode.
Whether the node should be scaled relative to its distance from the camera
+Default value (false) scales it to visually appear at the same size no matter the distance
+Setting to true causes annotation nodes to scale like a regular node
+Scaling relative to distance may be useful with local navigation-based uses
+For landmarks in the distance, the default is correct
Whether the node should appear at the same altitude of the user
+May be useful when you don’t know the real altitude of the node
+When set to true, the node will stay at the same altitude of the user
Converts distance from meters to SCNKit rendering order
+Constant multiplier eliminates flicker caused by slight distance variations
+Nodes with greater rendering orders are rendered last
Creates a PolylineNode from the provided polyline, altitude (which is assumed to be uniform
+for all of the points) and an optional SCNBox to use as a prototype for the location boxes.
The best estimation of location that has been taken
+This takes into account horizontal accuracy, and the time at which the estimation was taken
+favouring the most accurate, and then the most recent result.
+This doesn’t indicate where the user currently is.
orientationTracking: Informs the SceneLocationView to use Device Orientation tracking only.
+Useful when your nodes are all CLLocation based, and are not synced to real world planes
+See Apple’s documentation
+
worldTracking: Informs the SceneLocationView to use a World Tracking Configuration.
+Useful when you have nodes that attach themselves to real world planes
+See Apple’s documentation
Addresses Issue #196 -
+Delegate issue when assigned to self (no location nodes render). If the user
+tries to set the delegate, perform an assertionFailure and tell them to set the arViewDelegate instead.
If you wish to receive delegate ARSCNViewDelegate events, use this instead of the delegate property.
+The delegate property is reserved for this class itself and trying to set it will result in an assertionFailure
+and in production, things just won’t work as you expect.
Only to be overrided if you plan on manually setting True North.
+When true, sets up the scene to face what the device considers to be True North.
+This can be inaccurate, hence the option to override it.
+The functions for altering True North can be used irrespective of this value,
+but if the scene is oriented to true north, it will update without warning,
+thus affecting your alterations.
+The initial value of this property is respected.
iOS can be inaccurate when setting true north
+The scene is oriented to true north, and will update its heading when it gets a more accurate reading
+You can disable this through setting the
+These functions provide manual overriding of the scene heading,
+if you have a more precise idea of where True North is
+The goal is for the True North orientation problems to be resolved
+At which point these functions would no longer be useful
+Moves the scene heading clockwise by 1 degree
+Intended for correctional purposes
Upon being added, a node’s location, locationConfirmed and position may be modified and should not be changed externally.
+Silently fails and returns without adding the node to the scene if any of currentScenePosition,
+sceneLocationManager.currentLocation, or sceneNode is nil.
Silently fails and returns without adding the node unlesslocation is not nil and locationConfirmed is true.
+Upon being added, a node’s position will be modified internally and should not be changed externally.
+location will not be modified, but taken as accurate.
Adds routes to the scene and lets you specify the geometry prototype for the box.
+Note: You can provide your own SCNBox prototype to base the direction nodes from.
Adds polylines to the scene and lets you specify the geometry prototype for the box.
+Note: You can provide your own SCNBox prototype to base the direction nodes from.
Adds polylines to the scene and lets you specify the geometry prototype for the box.
+Note: You can provide your own SCNBox prototype to base the direction nodes from.
orientationTracking: Informs the SceneLocationView to use Device Orientation tracking only.
+Useful when your nodes are all CLLocation based, and are not synced to real world planes
+See Apple’s documentation
+
worldTracking: Informs the SceneLocationView to use a World Tracking Configuration.
+Useful when you have nodes that attach themselves to real world planes
+See Apple’s documentation
A set of schemes that can be used to scale a LocationNode.
+
+
Values:
+
+
+
normal: The default way of scaling, Hardcoded value out to 3000 meters, and then 0.75 that factor beyond 3000 m.
+
tiered (threshold, scale): Return 1.0 at distance up to threshold meters, or scale beyond.
+
doubleTiered (firstThreshold, firstCale, secondThreshold, secondScale): A way of scaling everything
+beyond 2 specific distances at two specific scales.
+
linear (threshold): linearly scales an object based on its distance.
+
linearBuffer (threshold, buffer): linearly scales an object based on its distance as long as it is
+further than the buffer distance, otherwise it just returns 100% scale.
A set of schemes that can be used to scale a LocationNode.
+
+
Values:
+
+
+
normal: The default way of scaling, Hardcoded value out to 3000 meters, and then 0.75 that factor beyond 3000 m.
+
tiered (threshold, scale): Return 1.0 at distance up to threshold meters, or scale beyond.
+
doubleTiered (firstThreshold, firstCale, secondThreshold, secondScale): A way of scaling everything
+beyond 2 specific distances at two specific scales.
+
linear (threshold): linearly scales an object based on its distance.
+
linearBuffer (threshold, buffer): linearly scales an object based on its distance as long as it is
+further than the buffer distance, otherwise it just returns 100% scale.
Returns a closure to compute appropriate scale factor based on the current value of self (a ScalingSchee).
+The closure accepts two parameters and returns the scale factor to apply to an AnnotationNode.
Translates distance in meters between two locations.
+Returns the result as the distance in latitude and distance in longitude.
+The approximation used here gives reasonable accuracy out to a radius of 50 km except at high latitudes.
+TODO: rewrite .translation(toLocation:) to improve the accuracy. See unit test notes.
Bearing from self to another point. Returns bearing in +/- degrees from north
+This function uses the haversine formula to compute a geodesic (great circle), assuming a spherical earth.
+Note that, especially at high latitudes and with relatively distant points, a.bearing(between: b)
+is not necessarily 180 degrees opposite to b.bearing(between: a).
Overlapping nodes require unique renderingOrder values to avoid flicker
+This method will select random values if you don’t care which node is in front of the other,
+or you can specify a particular z-order value
+Note: rendering order will be changed later based on distance from camera
After a node’s location is initially set based on current location,
+it is later confirmed once the user moves far enough away from it.
+This update uses location data collected since the node was placed to give a more accurate location.
This explicit definition is needed because the free init function is marked fileprivate by default,
+so LocationTranslation isn’t available to client apps.
A location node can be added to a scene using a coordinate.
+
+
Its scale and position should not be adjusted, as these are used for scene
+layout purposes. To adjust the scale and position of items within a node,
+you can add them to a child node and adjust them there
Parameter to raise or lower the label’s rendering position relative to the node’s actual project location.
+The default value of 1.1 places the label at a pleasing height above the node.
+To draw the label exactly on the true location, use a value of 0. To draw it below the true location,
+use a negative value.
Note: we repeat code from LocationNode‘s implementation of this function. Is this because of the use of SCNTransaction
+to wrap the changes? It’s legal to nest the calls, should consider this if any more changes to
+LocationNode’s implementation are needed.
A location node can be added to a scene using a coordinate.
+
+
Its scale and position should not be adjusted, as these are used for scene
+layout purposes. To adjust the scale and position of items within a node,
+you can add them to a child node and adjust them there
Whether the location of the node has been confirmed.
+This is automatically set to true when you create a node using a location.
+Otherwise, this is false, and becomes true once the user moves 100m away from the node,
+except when the locationEstimateMethod is set to use Core Location data only,
+as then it becomes true immediately.
Whether a node’s position should be adjusted on an ongoing basis
+based on its given location.
+This only occurs when a node’s location is within 100m of the user.
+Adjustment doesn’t apply to nodes without a confirmed location.
+When this is set to false, the result is a smoother appearance.
+When this is set to true, this means a node may appear to jump around
+as the user’s location estimates update,
+but the position is generally more accurate.
+Defaults to true.
Whether a node’s position and scale should be updated automatically on a continual basis.
+This should only be set to false if you plan to manually update position and scale
+at regular intervals. You can do this with SceneLocationView‘s updatePositionOfLocationNode.
Whether the node should be scaled relative to its distance from the camera
+Default value (false) scales it to visually appear at the same size no matter the distance
+Setting to true causes annotation nodes to scale like a regular node
+Scaling relative to distance may be useful with local navigation-based uses
+For landmarks in the distance, the default is correct
Whether the node should appear at the same altitude of the user
+May be useful when you don’t know the real altitude of the node
+When set to true, the node will stay at the same altitude of the user
Converts distance from meters to SCNKit rendering order
+Constant multiplier eliminates flicker caused by slight distance variations
+Nodes with greater rendering orders are rendered last
Creates a PolylineNode from the provided polyline, altitude (which is assumed to be uniform
+for all of the points) and an optional SCNBox to use as a prototype for the location boxes.
The best estimation of location that has been taken
+This takes into account horizontal accuracy, and the time at which the estimation was taken
+favouring the most accurate, and then the most recent result.
+This doesn’t indicate where the user currently is.
orientationTracking: Informs the SceneLocationView to use Device Orientation tracking only.
+Useful when your nodes are all CLLocation based, and are not synced to real world planes
+See Apple’s documentation
+
worldTracking: Informs the SceneLocationView to use a World Tracking Configuration.
+Useful when you have nodes that attach themselves to real world planes
+See Apple’s documentation
Addresses Issue #196 -
+Delegate issue when assigned to self (no location nodes render). If the user
+tries to set the delegate, perform an assertionFailure and tell them to set the arViewDelegate instead.
If you wish to receive delegate ARSCNViewDelegate events, use this instead of the delegate property.
+The delegate property is reserved for this class itself and trying to set it will result in an assertionFailure
+and in production, things just won’t work as you expect.
Only to be overrided if you plan on manually setting True North.
+When true, sets up the scene to face what the device considers to be True North.
+This can be inaccurate, hence the option to override it.
+The functions for altering True North can be used irrespective of this value,
+but if the scene is oriented to true north, it will update without warning,
+thus affecting your alterations.
+The initial value of this property is respected.
iOS can be inaccurate when setting true north
+The scene is oriented to true north, and will update its heading when it gets a more accurate reading
+You can disable this through setting the
+These functions provide manual overriding of the scene heading,
+if you have a more precise idea of where True North is
+The goal is for the True North orientation problems to be resolved
+At which point these functions would no longer be useful
+Moves the scene heading clockwise by 1 degree
+Intended for correctional purposes
Upon being added, a node’s location, locationConfirmed and position may be modified and should not be changed externally.
+Silently fails and returns without adding the node to the scene if any of currentScenePosition,
+sceneLocationManager.currentLocation, or sceneNode is nil.
Silently fails and returns without adding the node unlesslocation is not nil and locationConfirmed is true.
+Upon being added, a node’s position will be modified internally and should not be changed externally.
+location will not be modified, but taken as accurate.
Adds routes to the scene and lets you specify the geometry prototype for the box.
+Note: You can provide your own SCNBox prototype to base the direction nodes from.
Adds polylines to the scene and lets you specify the geometry prototype for the box.
+Note: You can provide your own SCNBox prototype to base the direction nodes from.
Adds polylines to the scene and lets you specify the geometry prototype for the box.
+Note: You can provide your own SCNBox prototype to base the direction nodes from.
orientationTracking: Informs the SceneLocationView to use Device Orientation tracking only.
+Useful when your nodes are all CLLocation based, and are not synced to real world planes
+See Apple’s documentation
+
worldTracking: Informs the SceneLocationView to use a World Tracking Configuration.
+Useful when you have nodes that attach themselves to real world planes
+See Apple’s documentation
A set of schemes that can be used to scale a LocationNode.
+
+
Values:
+
+
+
normal: The default way of scaling, Hardcoded value out to 3000 meters, and then 0.75 that factor beyond 3000 m.
+
tiered (threshold, scale): Return 1.0 at distance up to threshold meters, or scale beyond.
+
doubleTiered (firstThreshold, firstCale, secondThreshold, secondScale): A way of scaling everything
+beyond 2 specific distances at two specific scales.
+
linear (threshold): linearly scales an object based on its distance.
+
linearBuffer (threshold, buffer): linearly scales an object based on its distance as long as it is
+further than the buffer distance, otherwise it just returns 100% scale.
A set of schemes that can be used to scale a LocationNode.
+
+
Values:
+
+
+
normal: The default way of scaling, Hardcoded value out to 3000 meters, and then 0.75 that factor beyond 3000 m.
+
tiered (threshold, scale): Return 1.0 at distance up to threshold meters, or scale beyond.
+
doubleTiered (firstThreshold, firstCale, secondThreshold, secondScale): A way of scaling everything
+beyond 2 specific distances at two specific scales.
+
linear (threshold): linearly scales an object based on its distance.
+
linearBuffer (threshold, buffer): linearly scales an object based on its distance as long as it is
+further than the buffer distance, otherwise it just returns 100% scale.
Returns a closure to compute appropriate scale factor based on the current value of self (a ScalingSchee).
+The closure accepts two parameters and returns the scale factor to apply to an AnnotationNode.
Translates distance in meters between two locations.
+Returns the result as the distance in latitude and distance in longitude.
+The approximation used here gives reasonable accuracy out to a radius of 50 km except at high latitudes.
+TODO: rewrite .translation(toLocation:) to improve the accuracy. See unit test notes.
Bearing from self to another point. Returns bearing in +/- degrees from north
+This function uses the haversine formula to compute a geodesic (great circle), assuming a spherical earth.
+Note that, especially at high latitudes and with relatively distant points, a.bearing(between: b)
+is not necessarily 180 degrees opposite to b.bearing(between: a).
Overlapping nodes require unique renderingOrder values to avoid flicker
+This method will select random values if you don’t care which node is in front of the other,
+or you can specify a particular z-order value
+Note: rendering order will be changed later based on distance from camera
After a node’s location is initially set based on current location,
+it is later confirmed once the user moves far enough away from it.
+This update uses location data collected since the node was placed to give a more accurate location.
This explicit definition is needed because the free init function is marked fileprivate by default,
+so LocationTranslation isn’t available to client apps.
ARKit: Uses camera and motion data to map out the local world as you move around.
+
+
CoreLocation: Uses wifi and GPS data to determine your global location, with a low degree of accuracy.
+
+
ARKit + CoreLocation: Combines the high accuracy of AR with the scale of GPS data.
+
+
+
+
The potential for combining these technologies is huge, with so many potential applications across many different areas. This library comes with two major features:
+
+
+
Allow items to be placed within the AR world using real-world coordinates.
+
Dramatically improved location accuracy, using recent location data points combined with knowledge about movement through the AR world.
+
+
+
The improved location accuracy is currently in an “experimental” phase, but could be the most important component.
+
+
Because there’s still work to be done there, and in other areas, this project will best be served by an open community, more than what GitHub Issues would allow us. So I’m opening up a Slack group that anyone can join, to discuss the library, improvements to it, and their own work.
You should call sceneLocationView.run() whenever it’s in focus, and sceneLocationView.pause() if it’s interrupted, such as by moving to a different view or by leaving the app.
After we’ve called run(), we can add our coordinate. ARCL comes with a class called LocationNode - an object within the 3D scene which has a real-world location along with a few other properties which allow it to be displayed appropriately within the world. LocationNode is a subclass of SceneKit’s SCNNode, and can also be subclassed further. For this example we’re going to use a subclass called LocationAnnotationNode, which we use to display a 2D image within the world, which always faces us:
LocationAnnotationNode can also be initialized using a UIView. Internally, the UIView is converted into UIImage, so you cannot update the content dynamically.
+However, this methods allows you to easily show complex layout as POI.
+
letcoordinate=CLLocationCoordinate2D(latitude:51.504571,longitude:-0.019717)
+letlocation=CLLocation(coordinate:coordinate,altitude:300)
+letview=UIView()// or a custom UIView subclass
+
+letannotationNode=LocationAnnotationNode(location:location,view:view)
+
+
+
It can also be initialized with CALayer. You can use this when you want to update the contents live.
+
letcoordinate=CLLocationCoordinate2D(latitude:51.504571,longitude:-0.019717)
+letlocation=CLLocation(coordinate:coordinate,altitude:300)
+letlayer=CALayer()// or a custom CALayer subclass
+
+letannotationNode=LocationAnnotationNode(location:location,layer:layer)
+
+
+
By default, the image you set should always appear at the size it was given, for example if you give a 100x100 image, it would appear at 100x100 on the screen. This means distant annotation nodes can always be seen at the same size as nearby ones. If you’d rather they scale relative to their distance, you can set LocationAnnotationNode’s scaleRelativeToDistance to true.
There are two ways to add a location node to a scene - using addLocationNodeWithConfirmedLocation, or addLocationNodeForCurrentPosition, which positions it to be in the same position as the device, within the world, and then gives it a coordinate.
+
+
So that’s it. If you set the frame of your sceneLocationView, you should now see the pin hovering above Canary Wharf.
+
+
In order to get a notification when a node is touched in the sceneLocationView, you need to conform to LNTouchDelegate in the ViewController class.
+
+
The annotationNodeTouched(node: AnnotationNode) gives you access to node that was touched on the screen. AnnotationNode is a subclass of SCNNode with two extra properties: image: UIImage? and view: UIView?. Either of these properties will be filled in based on how the LocationAnnotationNode was initialized (using the constructor that takes UIImage or UIView).
+
+
The locationNodeTouched(node: LocationNode) gives you instead access to the nodes created from a PolyNode (e.g. the rendered directions of a MKRoute).
+
classViewController:UIViewController,LNTouchDelegate{
+
+ overridefuncviewDidLoad(){
+ super.viewDidLoad()
+ //...
+ self.sceneLocationView.locationNodeTouchDelegate=self
+ //...
+ }
+
+ funcannotationNodeTouched(node:AnnotationNode){
+ // Do stuffs with the node instance
+
+ // node could have either node.view or node.image
+ ifletnodeView=node.view{
+ // Do stuffs with the nodeView
+ // ...
+ }
+ ifletnodeImage=node.image{
+ // Do stuffs with the nodeImage
+ // ...
+ }
+ }
+
+ funclocationNodeTouched(node:LocationNode){
+ guardletname=node.tagelse{return}
+ guardletselectedNode=node.childNodes.first(where:{$0.geometryisSCNBox})else{return}
+
+ // Interact with the selected node
+ }
+
+}
+
+
Additional features
+
+
The library and demo come with a bunch of additional features for configuration. It’s all fully documented to be sure to have a look around.
+
+
SceneLocationView is a subclass of ARSCNView. Note that while this gives you full access to ARSCNView to use it in other ways, you should not set the delegate to another class. If you need to use delegate features then you should subclass SceneLocationView.
+
True North calibration
+
+
One issue which I haven’t personally been able to overcome is that the iPhone’s True North calibration currently has an accuracy of 15º at best. This is fine for maps navigation, but when placing things on top of the AR world, it starts to become a problem.
+
+
I’m confident that this issue can be overcome by using various AR techniques - it’s one area I think can really benefit from a shared effort.
+
+
To improve this currently, I’ve added some functions to the library that allow adjusting the north point:
+
+
+
sceneLocationView.moveSceneHeadingClockwise
+
sceneLocationView.moveSceneHeadingAntiClockwise
+
sceneLocationView.resetSceneHeading
+
+
+
You should use these by setting sceneLocationView.useTrueNorth to false, and then pointing the device in the general direction of north before beginning, so it’s reasonably close. With useTrueNorth set to true (default), it would continually adjust as it gets a better sense of north.
+
+
Within the demo app, there’s a disabled property called adjustNorthByTappingSidesOfScreen, which accesses these functions, and, once enabled, allows tapping on the left and right of the screen to adjust the scene heading.
+
+
My recommendation would be to fine a nearby landmark which is directly True North from your location, place an object there using a coordinate, and then use the moveSceneHeading functions to adjust the scene until it lines up.
+
Improved Location Accuracy
+
+
CoreLocation can deliver location updates anywhere from every 1-15 seconds, with accuracies which vary from 150m down to 4m. Occasionally, you’ll receive a far more accurate reading, like 4m or 8m, before returning to more inaccurate readings. At the same time, AR uses motion and camera data to create a map of the local world.
+
+
A user may receive a location reading accurate to 4m, then they walk 10m north and receive another location reading accurate to 65m. This 65m-accurate reading is the best that CoreLocation can offer, but knowing the user’s position within the AR scene when they got that 4m reading, and the fact that they’ve walked 10m north through the scene since then, we can translate that data to give them a new coordinate with about 4m of accuracy. This is accurate up to about 100m.
I mentioned this was experimental - currently, ARKit occasionally gets confused as the user is walking through a scene, and may change their position inaccurately. This issue also seems to affect the “euler angles”, or directional information about the device, so after a short distance it may think you’re walking in a different direction.
+
+
While Apple can improve ARKit over time, I think there are improvements we can make to avoid those issues, such as recognising when it happens and working to correct it, and by comparing location data with our supposed location to determine if we’ve moved outside a possible bounds.
+
Location Algorithm Improvements
+
+
There are further optimisations to determining a user’s location which can be made.
+
+
For example, one technique could be to look at recent location data, translate each data point using the user’s travel since then, and use the overlap between the data points to more narrowly determine the user’s possible location.
We have some Milestones and Issues related to them - anyone is welcome to discuss and contribute to them. Pull requests are welcomed. You can discuss new features/enhancements/bugs either by adding a new Issue or via the Slack community.
+
Thanks
+
+
Library created by @AndrewProjDent, but a community effort from here on.
+
+
Available as open source under the terms of the MIT License.
This explicit definition is needed because the free init function is marked fileprivate by default,","parent_name":"LocationTranslation"},"Structs/ARKit_CoreLocation.html#/s:4ARCL18ARKit_CoreLocationV4textSSvp":{"name":"text","abstract":"
After a node’s location is initially set based on current location,","parent_name":"SceneLocationViewDelegate"},"Protocols/SceneLocationViewDelegate.html#/s:4ARCL25SceneLocationViewDelegateP08didSetupB4Node05scenecD00iH0yAA0bcD0C_So7SCNNodeCtF":{"name":"didSetupSceneNode(sceneLocationView:sceneNode:)","abstract":"
Calculates distance between vectors","parent_name":"SCNVector3"},"Extensions/SCNNode.html#/s:So7SCNNodeC4ARCLE13removeFlicker18withRenderingOrderySi_tF":{"name":"removeFlicker(withRenderingOrder:)","abstract":"
Overlapping nodes require unique renderingOrder values to avoid flicker","parent_name":"SCNNode"},"Extensions/SCNNode.html#/s:So7SCNNodeC4ARCLE8axesNode12quiverLength0E9ThicknessAB12CoreGraphics7CGFloatV_AItFZ":{"name":"axesNode(quiverLength:quiverThickness:)","abstract":"
Returns a node similar to the one displayed when an ARSCNView‘s .debugOptions includes .showWorldOrigin
Returns a new CLLocationCoordinate2D at the given bearing and distance from the original point.","parent_name":"CLLocationCoordinate2D"},"Extensions/CLLocationCoordinate2D.html#/s:So22CLLocationCoordinate2DV4ARCLE17earthRadiusMetersSdyF":{"name":"earthRadiusMeters()","abstract":"
Return the WGS-84 radius of the earth, in meters, at the given point.
Translates distance in meters between two locations.","parent_name":"CLLocation"},"Extensions/CLLocation.html#/s:So10CLLocationC4ARCLE18translatedLocation4withAbC0D11TranslationV_tF":{"name":"translatedLocation(with:)","abstract":"
TODO: rewrite .translatedLocation(with:) to improve the accuracy. See unit test notes.
Bearing from self to another point. Returns bearing in +/- degrees from north","parent_name":"CLLocation"},"Extensions/CLLocation.html#/s:So10CLLocationC4ARCLE14approxMidpoint2toA2B_tF":{"name":"approxMidpoint(to:)","abstract":"
Returns the midpoint between two locations","parent_name":"CLLocation"},"Extensions/CLLocation.html#/s:So10CLLocationC4ARCLE8debugLogSSvp":{"name":"debugLog","abstract":"
Returns a closure to compute appropriate scale factor based on the current value of self (a ScalingSchee).","parent_name":"ScalingScheme"},"Enums/LocationEstimateMethod.html#/s:4ARCL22LocationEstimateMethodO04coreB8DataOnlyyA2CmF":{"name":"coreLocationDataOnly","abstract":"
Only uses Core Location data.","parent_name":"LocationEstimateMethod"},"Enums/LocationEstimateMethod.html#/s:4ARCL22LocationEstimateMethodO012mostRelevantC0yA2CmF":{"name":"mostRelevantEstimate","abstract":"
Combines knowledge about movement through the AR world with","parent_name":"LocationEstimateMethod"},"Enums/LocationEstimateMethod.html":{"name":"LocationEstimateMethod","abstract":"
Different methods which can be used when determining locations (such as the user’s location).
The limit to the scene, in terms of what data is considered reasonably accurate.","parent_name":"SceneLocationView"},"Classes/SceneLocationView/ARTrackingType.html":{"name":"ARTrackingType","abstract":"
If you wish to receive delegate ARSCNViewDelegate events, use this instead of the delegate property.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC22locationEstimateMethodAA0cfG0Ovp":{"name":"locationEstimateMethod","abstract":"
The method to use for determining locations.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC12showAxesNodeSbvp":{"name":"showAxesNode","abstract":"
When set to true, displays an axes node at the start of the scene
Only to be overrided if you plan on manually setting True North.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC17showFeaturePointsSbvp":{"name":"showFeaturePoints","abstract":"
Whether debugging feature points should be displayed.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC07currentB8PositionSo10SCNVector3VSgvp":{"name":"currentScenePosition","abstract":"
This initializer allows you to specify the type of tracking configuration (defaults to world tracking) as well as","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/c:@M@ARCL@objc(cs)SceneLocationView(im)initWithFrame:options:":{"name":"init(frame:options:)","abstract":"
iOS can be inaccurate when setting true north","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC04moveB20HeadingAntiClockwiseyyF":{"name":"moveSceneHeadingAntiClockwise()","abstract":"
Moves the scene heading anti-clockwise by 1 degree","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC03addC22NodeForCurrentPosition08locationF0yAA0cF0C_tF":{"name":"addLocationNodeForCurrentPosition(locationNode:)","abstract":"
Upon being added, a node’s location, locationConfirmed and position may be modified and should not be changed externally.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC03addC23NodesForCurrentPosition08locationF0ySayAA0C4NodeCG_tF":{"name":"addLocationNodesForCurrentPosition(locationNodes:)","abstract":"
Silently fails and returns without adding the node unlesslocation is not nil and locationConfirmed is true.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/c:@CM@ARCL@objc(cs)SceneLocationView(im)sceneLocationViewTouchedWithSender:":{"name":"sceneLocationViewTouched(sender:)","abstract":"
Adds routes to the scene and lets you specify the geometry prototype for the box.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC9addRoutes9polylines0012altitude_wBf10boxBuilderySayAA14AttributedTypeVySo10MKPolylineCGG_SdSo6SCNBoxC12CoreGraphics7CGFloatVcSgtF":{"name":"addRoutes(polylines:Δaltitude:boxBuilder:)","abstract":"
Adds polylines to the scene and lets you specify the geometry prototype for the box.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC12removeRoutes6routesySaySo7MKRouteCG_tF":{"name":"removeRoutes(routes:)","abstract":"
Adds polylines to the scene and lets you specify the geometry prototype for the box.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC15removePolylines9polylinesySaySo10MKPolylineCG_tF":{"name":"removePolylines(polylines:)","abstract":"
Creates a PolylineNode from the provided polyline, altitude (which is assumed to be uniform","parent_name":"PolylineNode"},"Classes/PolylineNode.html#/c:@M@ARCL@objc(cs)PolylineNode(im)initWithCoder:":{"name":"init(coder:)","abstract":"
Whether the location of the node has been confirmed.","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC017continuallyAdjustC23PositionWhenWithinRangeSbvp":{"name":"continuallyAdjustNodePositionWhenWithinRange","abstract":"
Whether a node’s position should be adjusted on an ongoing basis","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC33continuallyUpdatePositionAndScaleSbvp":{"name":"continuallyUpdatePositionAndScale","abstract":"
Whether a node’s position and scale should be updated automatically on a continual basis.","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC23scaleRelativeToDistanceSbvp":{"name":"scaleRelativeToDistance","abstract":"
Whether the node should be scaled relative to its distance from the camera","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC14ignoreAltitudeSbvp":{"name":"ignoreAltitude","abstract":"
Whether the node should appear at the same altitude of the user","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC13scalingSchemeAA07ScalingE0Ovp":{"name":"scalingScheme","abstract":"
See LocationAnnotationNode‘s override of this function. Because it doesn’t invoke super’s version, any changes","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC14renderingOrder12fromDistanceSiSd_tF":{"name":"renderingOrder(fromDistance:)","abstract":"
Converts distance from meters to SCNKit rendering order","parent_name":"LocationNode"},"Classes/AnnotationNode.html#/s:4ARCL14AnnotationNodeC4viewSo6UIViewCSgvp":{"name":"view","abstract":"
Subnodes and adjustments should be applied to this subnode","parent_name":"LocationAnnotationNode"},"Classes/LocationAnnotationNode.html#/s:4ARCL22LocationAnnotationNodeC32annotationHeightAdjustmentFactorSdvp":{"name":"annotationHeightAdjustmentFactor","abstract":"
Parameter to raise or lower the label’s rendering position relative to the node’s actual project location.","parent_name":"LocationAnnotationNode"},"Classes/LocationAnnotationNode.html#/s:4ARCL22LocationAnnotationNodeC8location5imageACSo10CLLocationCSg_So7UIImageCtcfc":{"name":"init(location:image:)","abstract":"
Note: we repeat code from LocationNode‘s implementation of this function. Is this because of the use of SCNTransaction","parent_name":"LocationAnnotationNode"},"Classes/SceneLocationManager.html#/s:4ARCL20SceneLocationManagerC05sceneC8DelegateAA0bcdF0_pSgvp":{"name":"sceneLocationDelegate","abstract":"
The best estimation of location that has been taken","parent_name":"SceneLocationManager"},"Classes/SceneLocationManager.html#/s:4ARCL20SceneLocationManagerC07currentC0So10CLLocationCSgvp":{"name":"currentLocation","abstract":"
ARKit: Uses camera and motion data to map out the local world as you move around.
+
+
CoreLocation: Uses wifi and GPS data to determine your global location, with a low degree of accuracy.
+
+
ARKit + CoreLocation: Combines the high accuracy of AR with the scale of GPS data.
+
+
+
+
The potential for combining these technologies is huge, with so many potential applications across many different areas. This library comes with two major features:
+
+
+
Allow items to be placed within the AR world using real-world coordinates.
+
Dramatically improved location accuracy, using recent location data points combined with knowledge about movement through the AR world.
+
+
+
The improved location accuracy is currently in an “experimental” phase, but could be the most important component.
+
+
Because there’s still work to be done there, and in other areas, this project will best be served by an open community, more than what GitHub Issues would allow us. So I’m opening up a Slack group that anyone can join, to discuss the library, improvements to it, and their own work.
You should call sceneLocationView.run() whenever it’s in focus, and sceneLocationView.pause() if it’s interrupted, such as by moving to a different view or by leaving the app.
After we’ve called run(), we can add our coordinate. ARCL comes with a class called LocationNode - an object within the 3D scene which has a real-world location along with a few other properties which allow it to be displayed appropriately within the world. LocationNode is a subclass of SceneKit’s SCNNode, and can also be subclassed further. For this example we’re going to use a subclass called LocationAnnotationNode, which we use to display a 2D image within the world, which always faces us:
LocationAnnotationNode can also be initialized using a UIView. Internally, the UIView is converted into UIImage, so you cannot update the content dynamically.
+However, this methods allows you to easily show complex layout as POI.
+
letcoordinate=CLLocationCoordinate2D(latitude:51.504571,longitude:-0.019717)
+letlocation=CLLocation(coordinate:coordinate,altitude:300)
+letview=UIView()// or a custom UIView subclass
+
+letannotationNode=LocationAnnotationNode(location:location,view:view)
+
+
+
It can also be initialized with CALayer. You can use this when you want to update the contents live.
+
letcoordinate=CLLocationCoordinate2D(latitude:51.504571,longitude:-0.019717)
+letlocation=CLLocation(coordinate:coordinate,altitude:300)
+letlayer=CALayer()// or a custom CALayer subclass
+
+letannotationNode=LocationAnnotationNode(location:location,layer:layer)
+
+
+
By default, the image you set should always appear at the size it was given, for example if you give a 100x100 image, it would appear at 100x100 on the screen. This means distant annotation nodes can always be seen at the same size as nearby ones. If you’d rather they scale relative to their distance, you can set LocationAnnotationNode’s scaleRelativeToDistance to true.
There are two ways to add a location node to a scene - using addLocationNodeWithConfirmedLocation, or addLocationNodeForCurrentPosition, which positions it to be in the same position as the device, within the world, and then gives it a coordinate.
+
+
So that’s it. If you set the frame of your sceneLocationView, you should now see the pin hovering above Canary Wharf.
+
+
In order to get a notification when a node is touched in the sceneLocationView, you need to conform to LNTouchDelegate in the ViewController class.
+
+
The annotationNodeTouched(node: AnnotationNode) gives you access to node that was touched on the screen. AnnotationNode is a subclass of SCNNode with two extra properties: image: UIImage? and view: UIView?. Either of these properties will be filled in based on how the LocationAnnotationNode was initialized (using the constructor that takes UIImage or UIView).
+
+
The locationNodeTouched(node: LocationNode) gives you instead access to the nodes created from a PolyNode (e.g. the rendered directions of a MKRoute).
+
classViewController:UIViewController,LNTouchDelegate{
+
+ overridefuncviewDidLoad(){
+ super.viewDidLoad()
+ //...
+ self.sceneLocationView.locationNodeTouchDelegate=self
+ //...
+ }
+
+ funcannotationNodeTouched(node:AnnotationNode){
+ // Do stuffs with the node instance
+
+ // node could have either node.view or node.image
+ ifletnodeView=node.view{
+ // Do stuffs with the nodeView
+ // ...
+ }
+ ifletnodeImage=node.image{
+ // Do stuffs with the nodeImage
+ // ...
+ }
+ }
+
+ funclocationNodeTouched(node:LocationNode){
+ guardletname=node.tagelse{return}
+ guardletselectedNode=node.childNodes.first(where:{$0.geometryisSCNBox})else{return}
+
+ // Interact with the selected node
+ }
+
+}
+
+
Additional features
+
+
The library and demo come with a bunch of additional features for configuration. It’s all fully documented to be sure to have a look around.
+
+
SceneLocationView is a subclass of ARSCNView. Note that while this gives you full access to ARSCNView to use it in other ways, you should not set the delegate to another class. If you need to use delegate features then you should subclass SceneLocationView.
+
True North calibration
+
+
One issue which I haven’t personally been able to overcome is that the iPhone’s True North calibration currently has an accuracy of 15º at best. This is fine for maps navigation, but when placing things on top of the AR world, it starts to become a problem.
+
+
I’m confident that this issue can be overcome by using various AR techniques - it’s one area I think can really benefit from a shared effort.
+
+
To improve this currently, I’ve added some functions to the library that allow adjusting the north point:
+
+
+
sceneLocationView.moveSceneHeadingClockwise
+
sceneLocationView.moveSceneHeadingAntiClockwise
+
sceneLocationView.resetSceneHeading
+
+
+
You should use these by setting sceneLocationView.useTrueNorth to false, and then pointing the device in the general direction of north before beginning, so it’s reasonably close. With useTrueNorth set to true (default), it would continually adjust as it gets a better sense of north.
+
+
Within the demo app, there’s a disabled property called adjustNorthByTappingSidesOfScreen, which accesses these functions, and, once enabled, allows tapping on the left and right of the screen to adjust the scene heading.
+
+
My recommendation would be to fine a nearby landmark which is directly True North from your location, place an object there using a coordinate, and then use the moveSceneHeading functions to adjust the scene until it lines up.
+
Improved Location Accuracy
+
+
CoreLocation can deliver location updates anywhere from every 1-15 seconds, with accuracies which vary from 150m down to 4m. Occasionally, you’ll receive a far more accurate reading, like 4m or 8m, before returning to more inaccurate readings. At the same time, AR uses motion and camera data to create a map of the local world.
+
+
A user may receive a location reading accurate to 4m, then they walk 10m north and receive another location reading accurate to 65m. This 65m-accurate reading is the best that CoreLocation can offer, but knowing the user’s position within the AR scene when they got that 4m reading, and the fact that they’ve walked 10m north through the scene since then, we can translate that data to give them a new coordinate with about 4m of accuracy. This is accurate up to about 100m.
I mentioned this was experimental - currently, ARKit occasionally gets confused as the user is walking through a scene, and may change their position inaccurately. This issue also seems to affect the “euler angles”, or directional information about the device, so after a short distance it may think you’re walking in a different direction.
+
+
While Apple can improve ARKit over time, I think there are improvements we can make to avoid those issues, such as recognising when it happens and working to correct it, and by comparing location data with our supposed location to determine if we’ve moved outside a possible bounds.
+
Location Algorithm Improvements
+
+
There are further optimisations to determining a user’s location which can be made.
+
+
For example, one technique could be to look at recent location data, translate each data point using the user’s travel since then, and use the overlap between the data points to more narrowly determine the user’s possible location.
We have some Milestones and Issues related to them - anyone is welcome to discuss and contribute to them. Pull requests are welcomed. You can discuss new features/enhancements/bugs either by adding a new Issue or via the Slack community.
+
Thanks
+
+
Library created by @AndrewProjDent, but a community effort from here on.
+
+
Available as open source under the terms of the MIT License.
This explicit definition is needed because the free init function is marked fileprivate by default,","parent_name":"LocationTranslation"},"Structs/ARKit_CoreLocation.html#/s:4ARCL18ARKit_CoreLocationV4textSSvp":{"name":"text","abstract":"
After a node’s location is initially set based on current location,","parent_name":"SceneLocationViewDelegate"},"Protocols/SceneLocationViewDelegate.html#/s:4ARCL25SceneLocationViewDelegateP08didSetupB4Node05scenecD00iH0yAA0bcD0C_So7SCNNodeCtF":{"name":"didSetupSceneNode(sceneLocationView:sceneNode:)","abstract":"
Calculates distance between vectors","parent_name":"SCNVector3"},"Extensions/SCNNode.html#/s:So7SCNNodeC4ARCLE13removeFlicker18withRenderingOrderySi_tF":{"name":"removeFlicker(withRenderingOrder:)","abstract":"
Overlapping nodes require unique renderingOrder values to avoid flicker","parent_name":"SCNNode"},"Extensions/SCNNode.html#/s:So7SCNNodeC4ARCLE8axesNode12quiverLength0E9ThicknessAB12CoreGraphics7CGFloatV_AItFZ":{"name":"axesNode(quiverLength:quiverThickness:)","abstract":"
Returns a node similar to the one displayed when an ARSCNView‘s .debugOptions includes .showWorldOrigin
Returns a new CLLocationCoordinate2D at the given bearing and distance from the original point.","parent_name":"CLLocationCoordinate2D"},"Extensions/CLLocationCoordinate2D.html#/s:So22CLLocationCoordinate2DV4ARCLE17earthRadiusMetersSdyF":{"name":"earthRadiusMeters()","abstract":"
Return the WGS-84 radius of the earth, in meters, at the given point.
Translates distance in meters between two locations.","parent_name":"CLLocation"},"Extensions/CLLocation.html#/s:So10CLLocationC4ARCLE18translatedLocation4withAbC0D11TranslationV_tF":{"name":"translatedLocation(with:)","abstract":"
TODO: rewrite .translatedLocation(with:) to improve the accuracy. See unit test notes.
Bearing from self to another point. Returns bearing in +/- degrees from north","parent_name":"CLLocation"},"Extensions/CLLocation.html#/s:So10CLLocationC4ARCLE14approxMidpoint2toA2B_tF":{"name":"approxMidpoint(to:)","abstract":"
Returns the midpoint between two locations","parent_name":"CLLocation"},"Extensions/CLLocation.html#/s:So10CLLocationC4ARCLE8debugLogSSvp":{"name":"debugLog","abstract":"
Returns a closure to compute appropriate scale factor based on the current value of self (a ScalingSchee).","parent_name":"ScalingScheme"},"Enums/LocationEstimateMethod.html#/s:4ARCL22LocationEstimateMethodO04coreB8DataOnlyyA2CmF":{"name":"coreLocationDataOnly","abstract":"
Only uses Core Location data.","parent_name":"LocationEstimateMethod"},"Enums/LocationEstimateMethod.html#/s:4ARCL22LocationEstimateMethodO012mostRelevantC0yA2CmF":{"name":"mostRelevantEstimate","abstract":"
Combines knowledge about movement through the AR world with","parent_name":"LocationEstimateMethod"},"Enums/LocationEstimateMethod.html":{"name":"LocationEstimateMethod","abstract":"
Different methods which can be used when determining locations (such as the user’s location).
The limit to the scene, in terms of what data is considered reasonably accurate.","parent_name":"SceneLocationView"},"Classes/SceneLocationView/ARTrackingType.html":{"name":"ARTrackingType","abstract":"
If you wish to receive delegate ARSCNViewDelegate events, use this instead of the delegate property.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC22locationEstimateMethodAA0cfG0Ovp":{"name":"locationEstimateMethod","abstract":"
The method to use for determining locations.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC12showAxesNodeSbvp":{"name":"showAxesNode","abstract":"
When set to true, displays an axes node at the start of the scene
Only to be overrided if you plan on manually setting True North.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC17showFeaturePointsSbvp":{"name":"showFeaturePoints","abstract":"
Whether debugging feature points should be displayed.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC07currentB8PositionSo10SCNVector3VSgvp":{"name":"currentScenePosition","abstract":"
This initializer allows you to specify the type of tracking configuration (defaults to world tracking) as well as","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/c:@M@ARCL@objc(cs)SceneLocationView(im)initWithFrame:options:":{"name":"init(frame:options:)","abstract":"
iOS can be inaccurate when setting true north","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC04moveB20HeadingAntiClockwiseyyF":{"name":"moveSceneHeadingAntiClockwise()","abstract":"
Moves the scene heading anti-clockwise by 1 degree","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC03addC22NodeForCurrentPosition08locationF0yAA0cF0C_tF":{"name":"addLocationNodeForCurrentPosition(locationNode:)","abstract":"
Upon being added, a node’s location, locationConfirmed and position may be modified and should not be changed externally.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC03addC23NodesForCurrentPosition08locationF0ySayAA0C4NodeCG_tF":{"name":"addLocationNodesForCurrentPosition(locationNodes:)","abstract":"
Silently fails and returns without adding the node unlesslocation is not nil and locationConfirmed is true.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/c:@CM@ARCL@objc(cs)SceneLocationView(im)sceneLocationViewTouchedWithSender:":{"name":"sceneLocationViewTouched(sender:)","abstract":"
Adds routes to the scene and lets you specify the geometry prototype for the box.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC9addRoutes9polylines0012altitude_wBf10boxBuilderySayAA14AttributedTypeVySo10MKPolylineCGG_SdSo6SCNBoxC12CoreGraphics7CGFloatVcSgtF":{"name":"addRoutes(polylines:Δaltitude:boxBuilder:)","abstract":"
Adds polylines to the scene and lets you specify the geometry prototype for the box.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC12removeRoutes6routesySaySo7MKRouteCG_tF":{"name":"removeRoutes(routes:)","abstract":"
Adds polylines to the scene and lets you specify the geometry prototype for the box.","parent_name":"SceneLocationView"},"Classes/SceneLocationView.html#/s:4ARCL17SceneLocationViewC15removePolylines9polylinesySaySo10MKPolylineCG_tF":{"name":"removePolylines(polylines:)","abstract":"
Creates a PolylineNode from the provided polyline, altitude (which is assumed to be uniform","parent_name":"PolylineNode"},"Classes/PolylineNode.html#/c:@M@ARCL@objc(cs)PolylineNode(im)initWithCoder:":{"name":"init(coder:)","abstract":"
Whether the location of the node has been confirmed.","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC017continuallyAdjustC23PositionWhenWithinRangeSbvp":{"name":"continuallyAdjustNodePositionWhenWithinRange","abstract":"
Whether a node’s position should be adjusted on an ongoing basis","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC33continuallyUpdatePositionAndScaleSbvp":{"name":"continuallyUpdatePositionAndScale","abstract":"
Whether a node’s position and scale should be updated automatically on a continual basis.","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC23scaleRelativeToDistanceSbvp":{"name":"scaleRelativeToDistance","abstract":"
Whether the node should be scaled relative to its distance from the camera","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC14ignoreAltitudeSbvp":{"name":"ignoreAltitude","abstract":"
Whether the node should appear at the same altitude of the user","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC13scalingSchemeAA07ScalingE0Ovp":{"name":"scalingScheme","abstract":"
See LocationAnnotationNode‘s override of this function. Because it doesn’t invoke super’s version, any changes","parent_name":"LocationNode"},"Classes/LocationNode.html#/s:4ARCL12LocationNodeC14renderingOrder12fromDistanceSiSd_tF":{"name":"renderingOrder(fromDistance:)","abstract":"
Converts distance from meters to SCNKit rendering order","parent_name":"LocationNode"},"Classes/AnnotationNode.html#/s:4ARCL14AnnotationNodeC4viewSo6UIViewCSgvp":{"name":"view","abstract":"
Subnodes and adjustments should be applied to this subnode","parent_name":"LocationAnnotationNode"},"Classes/LocationAnnotationNode.html#/s:4ARCL22LocationAnnotationNodeC32annotationHeightAdjustmentFactorSdvp":{"name":"annotationHeightAdjustmentFactor","abstract":"
Parameter to raise or lower the label’s rendering position relative to the node’s actual project location.","parent_name":"LocationAnnotationNode"},"Classes/LocationAnnotationNode.html#/s:4ARCL22LocationAnnotationNodeC8location5imageACSo10CLLocationCSg_So7UIImageCtcfc":{"name":"init(location:image:)","abstract":"
Note: we repeat code from LocationNode‘s implementation of this function. Is this because of the use of SCNTransaction","parent_name":"LocationAnnotationNode"},"Classes/SceneLocationManager.html#/s:4ARCL20SceneLocationManagerC05sceneC8DelegateAA0bcdF0_pSgvp":{"name":"sceneLocationDelegate","abstract":"
The best estimation of location that has been taken","parent_name":"SceneLocationManager"},"Classes/SceneLocationManager.html#/s:4ARCL20SceneLocationManagerC07currentC0So10CLLocationCSgvp":{"name":"currentLocation","abstract":"
View on GitHub
+ Classes Reference
+ 
View on GitHub
+ AnnotationNode Class Reference
+ 
View on GitHub
+ ARTrackingType Enumeration Reference
+ 
+ 
+ 
+ 
+ 
