GNSS DEVICE WITH PROXIMITY SENSOR FOR INITIATING DATA COLLECTION

Abstract

A graphics-aided geodesic device is provided. The device includes an antenna for receiving position data from a plurality of satellites and a receiver coupled to the antenna. The device further includes orientation circuitry for obtaining orientation data. The orientation data represents an orientation of the apparatus with respect to a plane parallel with a horizon. The device further includes positioning circuitry for determining the position of the point of interest based at least on the position data and the orientation data. A function of the graphics-aided geodesic device may be activated in response to a distance sensor detecting that an object is within a threshold distance from the device.

Description

BACKGROUND

1. Field

The present disclosure relates generally to geodesy and precise positioning of a handheld geodesic device.

2. Related Art

Geodesists commonly use satellite positioning devices, such as Global Navigation Satellite System (GNSS) devices, to determine the location of a point of interest anywhere on, or in the vicinity of, the Earth. Often, these points of interest are located at remote destinations which are difficult to access. Thus, compact, easy to carry positioning devices are desired.

Typically, to properly measure the position of a given point using a GNSS-based device, the GNSS antenna must be positioned directly above the point of interest with the antenna ground plane parallel to the ground. To position a GNSS device in such a manner, external hardware is commonly used. For example, a tripod may be used to properly position the GNSS antenna directly over the point of interest. In another example, a pole may be used to hang a GNSS antenna above the point of interest, allowing the antenna to swing until settling into a position where the antenna ground plane is parallel to the ground. While both external hardware devices allow the user to “level” the antenna, such devices are bulky and difficult to carry. Thus, even as positioning devices become more compact, they all suffer from the drawback of requiring additional bulky positioning equipment.

Recently, GNSS-based devices have become increasingly complex as additional measurement technologies have been incorporated. (See, e.g., U.S. Pat. No. 6,947,820B2, “Construction machine control system” and U.S. Pat. No. 5,471,218, “Integrated terrestrial survey and satellite positioning system.”) For example, in addition to an antenna and a receiver, many GNSS devices may include distance meters, electronic compasses, or video cameras. However, even as current GNSS-based devices include such sensors, none allow a user to position the device without the use of external hardware.

Therefore, a geodesic device capable of measuring position without the use of additional positioning equipment is desired.

BRIEF SUMMARY

Embodiments of the present disclosure are directed to a GNSS device. The device includes a distance sensor for measuring a distance between the device and an object. In response to the distance measured by the distance sensor being less than a threshold distance, a function of the GNSS device may be performed. The function may include determining a position of a point of interest, recording an image or video generated by a camera, selecting an option displayed on the GNSS device, or the like.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary graphics-aided geodesic device viewed from various angles.

FIG. 2A illustrates an exemplary view of the orientation of the components of a graphics-aided geodesic device.

FIG. 2B illustrates another exemplary view of the orientation of the components of a graphics-aided geodesic device.

FIG. 2C illustrates yet another exemplary view of the orientation of the components of a graphics-aided geodesic device.

FIG. 3 illustrates an exemplary logic diagram showing the relationships between the various components of a graphics-aided geodesic device.

FIG. 4 illustrates an exemplary view of the display screen of a graphics-aided geodesic device including elements used for positioning the device.

FIG. 5 illustrates another exemplary view of the display screen of a graphics-aided geodesic device oriented horizontally and above a point of interest.

FIG. 6A illustrates an exemplary process for measuring position using a graphics-aided geodesic device.

FIG. 6B illustrates another exemplary process for measuring position using a graphics-aided geodesic device.

FIG. 7 illustrates the intersection of four cones and the common point of intersection between them.

FIG. 8A illustrates an exemplary process for measuring a position using a graphics-aided geodesic device.

FIG. 8B illustrates another exemplary process for measuring a position using a graphics-aided geodesic device.

FIG. 9 illustrates an exemplary process for activating a function of a GNSS device.

FIG. 10 illustrates a typical computing system that may be employed to implement some or all processing functionality in certain embodiments.

DETAILED DESCRIPTION

The following description is presented to enable a person of ordinary skill in the art to make and use the various embodiments. Descriptions of specific devices, techniques, and applications are provided only as examples. Various modifications to the examples described herein will be readily apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other examples and applications without departing from the spirit and scope of the various embodiments. Thus, the various embodiments are not intended to be limited to the examples described herein and shown, but are to be accorded the scope consistent with the claims.

Various embodiments are described below relating to a handheld graphics-aided geodesic device. The device may include various sensors, such as a camera, distance sensor, and horizon sensors. A display element may also be included for assisting a user to position the device without the aid of external positioning equipment (e.g., a tripod or pole).

FIG. 1 illustrates an exemplary graphics-aided geodesic device 100 viewed from various angles. Graphics-aided geodesic device 100 is shown contained within camera housing 105. Camera housing 105 allows the user to hold graphics-aided geodesic device 100 as one would hold a typical camera. In one example, the device may include GNSS antenna 110 which may receive signals transmitted by a plurality of GNSS satellites and used by graphics-aided geodesic device 100 to determine position. In one example, GNSS antenna may receive signals transmitted by at least 4 GNSS satellites. In the example shown by FIG. 1, GNSS antenna 110 is located on the top side of graphics-aided geodesic device 100.

Graphics-aided geodesic device 100 may further include a GNSS receiver (not shown) for converting the signal received by GNSS antenna 110 into Earth-based coordinates, for example, World Geodetic System 84 (WGS84), Earth-Centered Earth Fixed (ECEF), local east, north, up coordinates (ENU), and the like. Such receivers are well-known by those of ordinary skill in the art and any such device may be used.

Graphics-aided geodesic device 100 may further include “measure” button 120 to cause the device to perform a position measurement. In one example, this button may be similar to that of a conventional camera. However, instead of taking a photograph, “measure” button 120 may cause graphics-aided geodesic device 100 to perform a position measurement as described in greater detail below. In the example shown by FIG. 1, “measure” button 120 is located on the top side of graphics-aided geodesic device 100.

Graphics-aided geodesic device 100 may further include display 130 for displaying information to assist the user in positioning the device. Display 130 may be any electronic display such as a projection display, a liquid crystal (LCD) display, light emitting diode (LED) display, a plasma display, and the like. Such display devices are well-known by those of ordinary skill in the art and any such device may be used. In the example shown by FIG. 1, display 130 is located on the back side of graphics-aided geodesic device 100.

Graphics-aided geodesic device 100 may further include camera 140 for recording still images or video. Such recording devices are well-known by those of ordinary skill in the art and any such device may be used. In the example illustrated by FIG. 1, camera 140 is located on the bottom side of graphics-aided geodesic device 100. A more detailed description of the positioning of camera 140 will be provided below with respect to FIGS. 2A-C. In one example, display 130 may be used to display the out put of camera 140. Thus, when held upright, display 130 displays a view of the ground located below graphics-aided geodesic device 100.

Graphics-aided geodesic device 100 may further include horizon sensors (not shown) for determining the orientation of the device. The horizon sensors may be any type of horizon sensor, such as an inclinometer, accelerometer, and the like. Such horizon sensors are well-known by those of ordinary skill in the art and any such device may be used. In one example, a representation of the output of the horizon sensors may be displayed using display 130. A more detailed description of display 130 is provided below. Horizon sensors 215 and 216 are illustrated in FIGS. 2A-2C and FIG. 3.

The horizon sensors 215 and 216, by determining the inclination of the geodesic device 100, allow a CPU to compensate for errors resulting from the mis-leveling of the geodesic device 100. A user taking a position measurement may position the geodesic device 100 so that it is not level with respect to a plane parallel to the horizon. However, the CPU 360 (FIG. 3) of the geodesic device 100, receiving orientation data from the horizon sensors 215 and 216, can compensate the position determination as long as the inclination of the geodesic device 100 is below an inclination threshold. In this way, the orientation data, indicating the orientation of the GNSS antenna 110, may be used by the CPU 360 to correct for errors in the position data received by the GNSS antenna 360. (The position determination and compensation by the CPU 360 is generally discussed below). For example, a geodesic device 100 may be configured to have an inclination error of 15 degrees. As such, if the inclination of the geodesic device 100 is between 0 to 15 degrees with respect to a plane parallel to the horizon, the CPU 360 will determine the position of the point of interest.

Furthermore, the horizon sensors 215 and 216 determining the inclination of the geodesic device 100 with respect to a plane parallel with the horizon may be used to determine when the CPU 360 of the geodesic device 100 determines the position of a point of interest. The horizon sensors 215 and 216 measure the inclination of the geodesic device 100 with respect to a plane parallel to the horizon. The CPU 360 automatically begins determining the position of a point of interest when the inclination of the geodesic device 100 enters a predetermined inclination range. The CPU 360 continues determining position of the point of interest as long as the inclination of the geodesic device 100 is within the predetermined inclination range. If the inclination is measured to be outside the predetermined inclination range, the CPU 360 suspends determining the position of the point of interest. For example, the user of the geodesic device 100 may indicate that a position measurement should be taken at an inclination of 0 to 15 degrees from a plane parallel with the horizon. When the user holding the geodesic device 100 positions the geodesic device at 5 degrees, the position measurement by the CPU 360 starts automatically. Similarly, when the user tilts the geodesic device 100 so the inclination is no longer within the range of 0 to 15 degrees, the CPU 360 suspends the position measurement. In other words, the user may set a predetermined inclination range at which the CPU 360 will initiate the position measurement. Thus, by measuring the inclination of the geodesic device 100 during positioning by the user, the position measurement by the CPU 360 starts and stops depending on the positioning and orientation of the geodesic device 100. In this way, the user does not need to activate the position determination by depressing a start and stop key, for example. Moreover, the user does not need to search for a start or stop button to take a position measurement when environmental conditions, such as bright sunlight and darkness, may make it challenging for the user to find specific soft keys or hard buttons, respectively.

Moreover, if the horizon sensors 215 and 216 determines the inclination to be more than a predetermined threshold inclination, the CPU 360 deactivates buttons and touch display screen so that they do not respond to user actuation input or inadvertently activated. The CPU 360 deactivates, or locks, the function of buttons and the touch screen when the horizon sensors 215 and 216 determine the geodesic device 100 is inclined more than a predetermined threshold inclination. In one example, the buttons and display screen of the geodesic device 100 locks when the horizon sensors 215 and 216 determines the inclination of the geodesic device 100 is more than 30 degrees.

Graphics-aided geodesic device 100 may further include distance sensor 150 to measure a linear distance. Distance sensor 150 may use any range-finding technology, such as sonar, laser, radar, and the like. Such distance sensors are well-known by those of ordinary skill in the art and any such device may be used. In the example illustrated by FIG. 1, distance sensor 150 is located on the bottom side of graphics-aided geodesic device 100.

FIGS. 2A-C illustrate exemplary views of graphics-aided geodesic device 100 and the orientation of its components from various angles. FIG. 2A shows a side view of graphics-aided geodesic device 100 with arrows 201 and 202 indicating the top/bottom and front/back of the device, respectively. FIG. 2B shows graphics-aided geodesic device 100 viewed from the back with arrows 203 and 204 indicating the top/bottom and left/right side of the device, respectively. FIG. 2C shows a bottom view of graphics-aided geodesic device 100 with arrows 205 and 206 indicating the right/left side and front/back of the device, respectively.

In the examples illustrated by FIGS. 2A-C, camera housing 105 contains antenna 110, horizon sensors 215 and 216, distance sensor 150, and camera 140. The orientation of the components will be described herein with the use of vectors which indicate a direction in space. For instance, antenna 110 has an antenna ground plane defined by antenna phase center 211 and two ground plane vectors 212 and 213. In one example, ground plane vectors 212 and 213 are parallel or substantially parallel to the local horizon. Camera 140 has optical center 241 located along camera optical axis 242. Camera optical axis 242 passes through antenna phase center 211 and is orthogonal or substantially orthogonal to ground plane vectors 212 and 213. Distance sensor 150 has distance sensor main axis (measuring direction) 251 which is parallel or substantially parallel to camera optical axis 242. Horizon sensors 215 and 216 have orthogonal or substantially orthogonal measurement vectors 217 and 218 which create a plane parallel or substantially parallel to the antenna ground plane defined by ground plane vectors 212 and 213. It should be appreciated that in a real-world application, the components of graphics-aided geodesic device 100 may not be positioned exactly as described above. For instance, due to manufacturing imperfections, the orientations of certain components may not be parallel or orthogonal to the other components as designed. The tolerances for the orientations of the various components depend on the desired precision of the resulting position measurement.

FIG. 3 illustrates an exemplary logic diagram showing the relationships between the various components of graphics-aided geodesic device 100. In one example, GNSS antenna 110 may send position data received from GNSS satellites to GNSS receiver 315. GNSS receiver 315 may convert the received GNSS satellite signals into Earth-based coordinates, such as WGS84, ECEF, ENU, and the like. GNSS receiver 315 may further send the coordinates to CPU 360 for processing along with distance data from distance sensor 150, pitch data from pitch horizon sensor 215, roll data from roll horizon sensor 216, a measure command from “measure” button 120, and image data from video camera 140. CPU 360 processes the data as will be described in greater detail below and provides display data to be displayed on display 130.

FIG. 4 illustrates an exemplary view 400 of display 130 for positioning graphics-aided geodesic device 100. In one example, display 130 may display the output of camera 140. In this example, the display of the output of camera 140 includes point of interest marker 440. As shown in FIG. 4, point of interest marker 440 is a small circular object identifying a particular location on the ground. In the examples provided herein, we assume that the location to be measured is located on the ground and that the point of interest is identifiable by a visible marker (e.g., point of interest marker 440). The marker may be any object having a small height value. For instance, an “X” painted on ground or a circular piece of colored paper placed on the point of interest may serve as point of interest marker 440.

In another example, display 130 may further include virtual linear bubble levels 410 and 420 corresponding to the roll and pitch of graphics-aided geodesic device 100, respectively. Virtual linear bubble levels 410 and 420 may include virtual bubbles 411 and 421 which identify the amount and direction of roll and pitch of graphics-aided geodesic device 100. Virtual linear bubble levels 410 and 420 and virtual bubbles 411 and 421 may be generated by CPU 360 and overlaid on the actual image output of camera 140. In one example, positioning of virtual bubbles 411 and 421 in the middle of virtual linear bubble levels 410 and 420 indicate that the device is positioned “horizontally.” As used herein, “horizontally” refers to the orientation whereby the antenna ground plane is parallel to the local horizon.

In one example, data from horizon sensors 215 and 216 may be used to generate the linear bubble levels 410 and 420. For instance, sensor data from horizon sensors 215 and 216 may be sent to CPU 360 which may convert a scaled sensor measurement into a bubble coordinate within virtual linear bubble levels 410 and 420. CPU 360 may then cause the display on display 130 of virtual bubbles 411 and 421 appropriately placed within virtual linear bubble levels 410 and 420. Thus, virtual linear bubble levels 410 and 420 may act like traditional bubble levels, with virtual bubbles 411 and 421 moving in response to tilting and rolling of graphics-aided geodesic device 400. For example, if graphics-aided geodesic device 100 is tilted forward, bubble 420 may move downwards within virtual linear bubble level 420. Additionally, if graphics-aided geodesic device 100 is rolled to the left, virtual bubble 411 may move to the right within virtual linear bubble level 410. However, since virtual linear bubble levels 410 and 420 are generated by CPU 360, movement of virtual bubbles 411 and 421 may be programmed to move in any direction in response to movement of graphics-aided geodesic device 100.

In another example, display 130 may further include planar bubble level 425. Planar bubble level 425 represents a combination of virtual linear bubble levels 410 and 420 (e.g., placed at the intersection of the bubbles within the linear levels) and may be generated by combining measurements of two orthogonal horizon sensors (e.g., horizon sensors 215 and 216). For instance, scaled measurements of horizon sensors 215 and 216 may be converted by CPU 360 into X and Y coordinates on display 130. In one example, measurements from horizon sensor 215 may be used to generate the X coordinate and measurements from horizon sensor 216 may be used to generate the Y coordinate of planar bubble level 425.

As shown in FIG. 4, display 130 may further include central crosshair 450. In one example, central crosshair 450 may be placed in the center of display 130. In another example, the location of central crosshair 450 may represent the point in display 130 corresponding to the view of camera 140 along optical axis 242. In yet another example, placement of planar bubble level 425 within central crosshair 450 may correspond to graphics-aided geodesic device 100 being positioned horizontally. Central crosshair 450 may be drawn on the screen of display 130 or may be electronically displayed to display 130.

Display 130 may be used to aid the user in positioning graphics-aided geodesic device 100 over a point of interest by providing feedback regarding the placement and orientation of the device. For instance, the camera output portion of display 130 provides information to the user regarding the placement of graphics-aided geodesic device 100 with respect to objects on the ground. Additionally, virtual linear bubble levels 410 and 420 provide information to the user regarding the orientation of graphics-aided geodesic device 100 with respect to the horizon. Using at least one of the two types of output displayed on display 130, the user may properly position graphics-aided geodesic device 100 without the use of external positioning equipment.

In the example illustrated by FIG. 4, both point of interest marker 440 and planar bubble level 425 are shown as off-center from central crosshair 450. This indicates that optical axis 242 of camera 140 is not pointed directly at the point of interest and that the device is not positioned horizontally. If the user wishes to position the device horizontally above a particular point on the ground, the user must center both planar bubble level 425 and point of interest marker 440 within central crosshair 450 as shown in FIG. 5.

FIG. 5 illustrates another exemplary view 500 of display 130. In this example, virtual linear bubble levels 410 and 420 are shown with their respective bubbles centered, indicating that the device is horizontal. As such, planar bubble level 425 is also centered within central crosshair 450. Additionally, in this example, point of interest marker 440 is shown as centered within central crosshair 450. This indicates that optical axis 242 of camera 140 is pointing towards point of interest marker 440. Thus, in the example shown by FIG. 5, graphics-aided geodesic device 100 is positioned horizontally above point of interest marker 440.

As discussed above with respect to FIG. 2, antenna phase center 211 may be located along optical axis 242. This means that in the example shown by FIG. 5, antenna phase center 211 is also located directly above point of interest marker 440. Thus, the only difference between the position of antenna phase center 211 and point of interest marker 440 is a vertical component equal to the vertical distance between point of interest marker 440 and antenna phase center 211. In this example, the position of point of interest marker 440 may be calculated using the following equation:

{right arrow over (P)}={right arrow over (P)} _dev −{right arrow over (n)}(D_in+D_out)  (1)

Where:

{right arrow over (P)}_x—Calculated position of the point of interest.

{right arrow over (P)}_dev—Measured GNSS position of the device antenna phase center.

{right arrow over (n)}—Unit vector orthogonal to the ground.

D_in—Vertical distance between antenna phase center 211 and the zero measurement point of distance sensor 150.

D_out—Distance measured by distance sensor 150 from the sensor's zero measurement point to an object along distance sensor main axis 251.

As shown above, {right arrow over (P)}_x of equation (1) represents the calculated position of the point of interest. {right arrow over (P)}_dev represents the position of antenna phase center 211 determined by graphics-aided geodesic device 100. {right arrow over (n)} represents a unit vector pointing in a direction orthogonal to the ground. D_in represents the vertical distance between antenna phase center 211 and the zero measurement point of distance sensor 150. The zero measurement point of distance sensor 150 is the point in space for which distance sensor 150 is configured to return a zero value and may be located either inside or outside of graphics-aided geodesic device 100. Thus, D_in is a constant value that is specific to each graphics-aided geodesic device 100. Finally, D_out represents the distance measured by distance sensor 150 from the sensor's zero measurement point to an object along distance sensor main axis 251. Therefore, {right arrow over (P)}_x is calculated by taking the position measured by graphics-aided geodesic device 100 and subtracting a vertical distance equal to the distance measured by distance sensor 150 plus the distance between antenna phase center 211 and the zero measurement point of distance sensor 150.

It should be appreciated that the coordinates used in equation (1) may be expressed in any coordinate system. For example, the above described equation may be applicable to any Cartesian coordinate system and the measurement results may be converted to any Earth-based coordinates, such as WGS84, ECEF, ENU, and the like. Such conversion methods are well-known by those of ordinary skill in the art.

FIG. 6A illustrates exemplary process 600 for measuring a position using graphics-aided geodesic device 100. At block 610 the user positions graphics-aided geodesic device 100 horizontally above the point of interest as described with respect to FIG. 5. At block 620, the user presses “measure” button 120 while graphics-aided geodesic device 100 is positioned horizontally above the point of interest. At block 630, graphics-aided geodesic device 100 records the position data from receiver 315 and the distance measured by distance sensor 150. At block 640, CPU 360 of graphics-aided geodesic device 100 calculates the position of the point of interest using equation (1) and the values recorded at block 630.

FIG. 6B illustrates another exemplary process 601 similar to exemplary process 600 for measuring a position using graphics-aided geodesic device 100. The main difference between exemplary processes 600 and 601 is that in exemplary process 601, the user is not required to press “measure” button 120. The process begins at block 650, which is similar to block 610. At block 660, graphics-aided geodesic device 100 detects that the device is positioned horizontally above the point of interest. In one example, this may be accomplished by detecting that both planar bubble 425 and point of interest marker 440 are centered within central crosshair 450.

In one particular example, graphics-aided geodesic device 100 may determine that planar bubble 425 is centered on central crosshair 450 by comparing the horizon sensor data which has been converted into X-Y coordinates with the display coordinates located at central crosshair 450. Additionally, graphics-aided geodesic device 100 may determine that point of interest marker 440 is centered on central crosshair 450 by utilizing an image recognition program for identifying point of interest marker 440 and determining its location within display 130. This may require that point of interest marker 440 conform to some predefined standard. For instance, point of interest marker 440 may be required to be a particular color or shape in order to be identified by the image recognition program of graphics-aided geodesic device 100. Such recognition algorithms are well-known by those of ordinary skill in the art and any such algorithm may be used in graphics-aided geodesic device 100.

Thus, in one example, when graphics-aided geodesic device 100 determines that planar bubble 425 and point of interest marker 440 are centered within central crosshair 450, the device may proceed to block 670. In another example, block 660 may only require that the distance between central crosshair 450 and planar bubble 425 and the distance between central crosshair 450 and point of interest marker 440 fall below a predefined distance threshold before proceeding to block 670. Blocks 670 and 680 are similar to blocks 630 and 640 of FIG. 6A.

Calculation of the Intersection Point of Multiple Cones

The examples provided in FIGS. 6A and 6B require that the device be positioned at least substantially horizontal and substantially above the point of interest. Since the user is not expected to perfectly orient the device, graphics-aided geodesic device 100 may allow a deviation in the angle and position. For instance, in one example, a deviation of 2 degrees from horizontal and 4 mm from the point of interest may be acceptable. However, it should be appreciated that other tolerances may be used depending on the desired application. The variations described below allow graphics-aided geodesic device 100 to perform position measurements without having to be positioned as required in the examples provided in FIGS. 6A and 6B. The following variations are based on two supplementary techniques: calculation of the camera pointing vector deviation and calculation of the intersection point of multiple cones.

The latter technique is based on the principal that the intersection region of two cone surfaces is an ellipse, the intersection region of three cones is a pair of points, and the intersection region of four cones is a single point. Thus, if graphics-aided geodesic device 100 generates four different cones, each cone containing point of interest marker 440 somewhere on its surface, the position of point of interest marker 440 may be determined FIG. 7 illustrates the intersection of four cones and the point 710 shared among them. The process of generating each cone will be described in greater detail below. It should be appreciated that four cones is the minimum number of cones needed to identify a common point. Additional cones may be used to increase the precision of the intersection point technique.

Calculation of the Camera Pointing Vector Deviation

To generate the cones described above, the following parameters may be determined: the position of the cone apex, the orientation of the cone axis, and the angle between the cone axis and the cone surface. Using these parameters to generate a mathematical representation of a cone is well-known and understood by those of ordinary skill in the art. For example, the mathematical representation of the cone may be generated using the methods described in Appendix C. In one example, determining the angle between the cone axis and the cone surface may be accomplished by calculating the camera pointing vector deviation.

Calculating the camera pointing vector deviation is based on the principle that each pixel of the image taken by camera 140 and displayed on display 130 represents an angle from the camera optical axis 242. For example, the pixel at the center of display 130 may represent optical axis 242, while a pixel 5 pixels to the right of center may represent a particular angle to the right of optical axis 242. By knowing the pixel coordinates of an object on the image of camera 140, the direction to this object from camera optical axis 242 may be calculated using equation (2) below. For use with graphics-aided geodesic device 100, it is sufficient to know the angle between the pointing vector and camera optical axis 242, where the pointing vector represents the vector from camera optical center 241 to the point of interest. For a perfect central projection camera, this angle value may be approximated as a linear function of the pixel distance from the center of the display and may be modeled using the following equation:

α_pnt=kd  (2)

Where:

α_pnt—The angle between the pointing vector and camera optical axis 242.

k—Calibration coefficient, determined by the camera effective focal length.

d—Pixel distance between the center of the frame and the point of interest.

As shown above, α_pnt of equation (2) represents the angle between the pointing vector and optical axis 242. k represents a calibration coefficient which is determined by the camera effective focal length. This value is a constant value specific to each camera model. d represents the pixel distance, in pixels, between the center of display 130 (central crosshair 450) and point of interest marker 440. Thus, the angle between the pointing vector and optical axis 242 is equal to the product of the camera calibration coefficient and the number of pixels between central crosshair 450 and point of interest marker 440.

Equation (2) only applies to perfect central projection cameras. However, real cameras require that barrel distortion be taken into account. In most practical cases, it would be sufficient to consider distortion as a projection of a spherical surface to a tangent plane. Thus, a corrected pixel distance must be calculated and used in place of d in equation (2). The following equation may be used to find the corrected pixel distance:

$\begin{array}{cc}{d}_{\mathrm{corr}}=d\frac{r}{\sqrt{r^2-d^2}}& \left(3\right)\end{array}$

Where:

d_corr—Corrected pixel distance between the center of the screen and the point of interest. This value replaces d in equation (2).

d—Pixel distance between the center of the frame and the point of interest (same as in equation (2)).

r—Calibration parameter representing the projected sphere radius in relative pixels units.

As shown above, d_corr of equation (3) represents the corrected pixel distance between the center of the screen and the point of interest taking into consideration the barrel distortion of the camera. d represents the pixel distance, in pixels, between the center of the frame (central crosshair 450) and point of interest marker 440. r represents the calibration parameter representing the projected sphere radius in relative pixels units. This value takes into consideration all internal lens distortions and is a constant value specific to each camera. Thus, to take into consideration the barrel distortion, the corrected pixel distance (d_corr) calculated in equation (3) should be used in place of d in equation (2).

Using equations (2) and (3), the angle between the cone axis and the cone surface may be calculated. As discussed above, the angle between the cone axis and the cone surface is one of the parameters used to generate a cone. Specifically, if given the position of the apex of the cone, the orientation of the cone axis, and the angle between the cone axis and the cone surface, one of ordinary skill in the art would understand how to generate an equation representing the cone. Processes for determining the other recited parameters are described in greater detail below.

FIG. 8A illustrates an exemplary process 800 for measuring a position using graphics-aided geodesic device 100 and the intersection point of multiple cones technique. At block 810, the process begins with the user positioning graphics-aided geodesic device 100 horizontally with point of interest marker 440 in the field of view of display 130. At block 815, graphics-aided geodesic device 100 detects a measurement condition. In one example, the measurement condition may be receiving a “measure” command in response to the user pressing “measure” button 120. This is similar to block 620 of FIG. 6A. In another example, the measurement condition may be that the distance between central crosshair 450 and planar bubble 425 falls below a predefined distance threshold. This is similar to block 660 of FIG. 6B. Upon detection of a measurement condition, the process moves to block 820. At block 820, graphics-aided geodesic device 100 records data from the sensors. For example, position data may be recorded from GNSS receiver 315, pitch and roll data may be recorded from horizon sensors 215 and 216, and image data may be recorded from video camera 140. At block 825, CPU 360 uses the position data, pitch and roll data, and image data to generate a cone. Since the device has been positioned horizontally or at least substantially horizontal, the apex of the cone is the position of camera optical center 241, the cone axis is optical axis 242 which is orthogonal to the ground, and the angle between the cone axis and the cone surface is the angle between the pointing vector to point of interest marker 440 and optical axis 242 calculated using equations (2) and (3). At block 830, CPU 360 determines whether four intersecting cones have been generated. If there are less than four intersecting cones, the process returns to block 810. However, if there are at least four intersecting cones, the process moves to block 835. At block 835, CPU 360 of graphics-aided geodesic device 100 calculates the intersection point of the multiple cones. Calculation of the intersection point of the multiple cones results in a set of nonlinear equations that may be solved with a variety of numerical schemes, such as Newton, quasi-Newton, and Gauss-Newton methods. Such methods are well-known and understood by those of ordinary skill in the art. For example, the equations may be solved using the methods described in Appendices A and B.

FIG. 8B illustrates another exemplary process 801 for measuring a position using graphics-aided geodesic device 100 and the intersection point of multiple cones technique. This process differs from that of FIG. 8A in that the device need not be positioned horizontally. However, point of interest marker 440 must be centered within a predefined threshold distance from central crosshair 450. At block 840, the process begins with the user pointing optical axis 242 of graphics-aided geodesic device 100 towards point of interest marker 440. At block 845, graphics-aided geodesic device 100 detects a measurement condition. In one example, the measurement condition may be receiving a “measure” command in response to the user pressing “measure” button 120. This is similar to block 620 of FIG. 6A. In another example, the measurement condition may be that the distance between point of interest marker 440 and center crosshair 450 falls below a predefined distance threshold. This is similar to block 660 of FIG. 6B. Upon detection of a measurement condition, the process moves to block 850. At block 850, graphics-aided geodesic device 100 records data from the sensors. For example, position data may be recorded from GNSS receiver 315, pitch and roll data may be recorded from horizon sensors 215 and 216, and image data may be recorded from video camera 140. At block 855, CPU 360 uses the position data, pitch and roll data, and image data to generate a cone as described above. Since the device may not be positioned horizontally, the apex of the cone coincides with GNSS antenna phase center 211, the cone axis is a line passing through GNSS antenna phase center 211 and orthogonal to the ground, and the angle between the cone axis and the cone surface is the total vertical deviation angle given by horizon sensors 215 and 216. At block 860, CPU 360 determines whether four intersecting cones have been generated. If there are less than four intersecting cones, the process returns to block 840. However, if there are at least four intersecting cones, the process moves to block 865. At block 865, CPU 360 of graphics-aided geodesic device 100 calculates the intersection point of the multiple cones using the methods described above.

For the exemplary processes illustrated by FIGS. 8A and 8B, the generated cones are similar to those illustrated in FIG. 7. The apex of each cone is located at either camera optical center 241 or antenna phase center 211, with the base of the cone projecting away from graphics-aided geodesic device 100 towards the ground.

In one example, when calculating the position of a point of interest using the processes illustrated by FIGS. 8A and 8B, the greater the distance between the apexes of the four cones, the greater the precision of the resulting calculated position.

FIG. 9 illustrates an exemplary process 900 for activating a function of a GNSS device using a distance sensor. In some examples, process 900 may be performed using graphics-aided geodesic device 100. At block 910, a distance to an object may be measured. In some examples, a distance sensor similar or identical to distance sensor 150 of the GNSS device may be used to measure the distance to the object. The distance sensor may be positioned anywhere on the GNSS device to measure a distance from the GNSS device in any desired direction. For example, the distance sensor may be positioned on the same side of the GNSS device as a display (e.g., display 130) of the device to measure a distance between the display and an object. In other examples, the distance sensor may be positioned on the bottom of the device in a manner similar to that of distance sensor 150 to measure a distance between an object and the bottom of the device.

At block 920, it may be determined by a processor of the GNSS device whether the distance measured at block 910 is less than a threshold distance. The threshold distance may be selected to be any desired distance. For example, the threshold distance may be one foot. If it is determined that the distance measured at block 910 is not less than the threshold distance, the process may return to block 910. If, however, the distance measured at block 910 is determined to be less than the threshold distance at block 920, the process may proceed to block 930.

At block 930, a function of the GNSS device may be activated in response to determining that the distance measured at block 910 is less than the threshold distance at block 920. The function of the GNSS device may be any default or user-selected function of the device. Non-limiting examples of the functions that may be activated at block 930 include initiating data collection from the sensors of the GNSS device (e.g., for position determination), capturing an image using a camera (e.g., camera 140), begin recording video using a camera (e.g., camera 140), and selecting an option of a menu displayed on the GNSS device. It should be appreciated that any other function of the GNSS device may be activated at block 930 with the distance sensor acting as a virtual button for activating that function.

In some examples, the state of the GNSS device may be used to select the function to be performed. For example, if the GNSS device is in a position determination mode, the function may include determining a position of interest. If the device is in an image capturing mode, the function may include recording an image or video from a camera of the device. If the device is displaying a menu or selectable option to the user, the function may include selecting an item of the menu or selecting the selectable option.

In some examples, the function may be performed once at block 930 in response to determining that the distance to the object is less than the threshold distance at block 920. In other examples, the function may continue to be performed until the measured distance to the object is determined to no longer be less than the threshold distance. In yet other examples, the function may begin to be performed at block 930 and may continue to be performed for a threshold duration or for a threshold number of times. In other examples, the function may begin to be performed at block 930 and may continue to be performed until it is determined that the measured distance to the object is greater than the threshold distance and then returns to be less than the threshold distance (e.g., representing an object being brought near the device to active the function, being pulled away from the device, and then being brought near the device again to deactivate the function).

For example, the function to be activated at block 930 may include recording position data from the receiver of the GNSS device and using the position data to determine the position of the receiver or other point of interest. In some examples, a single position determination may be performed at block 930. In other examples, position determinations may continue to be made until the detected distance to the object is determined to no longer be less than the threshold distance. In yet other examples, position determinations may begin to be performed at block 930 and may continue for a threshold duration or for a threshold number of measurements. In other examples, the position determinations may begin to be performed at block 930 and may continue to be performed until it is determined that the measured distance to the object is greater than the threshold distance and then returns to be less than the threshold distance.

Using process 900, a function of the GNSS device may be activated without the user having to contact the device. For example, the user may mount the GNSS device in a desired position and may activate the position determination function of the device by placing his/her hand within the threshold distance from the GNSS device. This allows the user to cause the GNSS device to determine a position of a point of interest without contacting the device (e.g., without having to press a button on the device). This advantageously prevents misalignment of the GNSS device that could otherwise occur if the user was required to press a button of the device.

FIG. 10 illustrates an exemplary computing system 1000 that may be employed to implement processing functionality for various aspects of the current technology (e.g., as a geodesic device, receiver, CPU 360, activity data logic/database, combinations thereof, and the like.). Those skilled in the relevant art will also recognize how to implement the current technology using other computer systems or architectures. Computing system 1000 may represent, for example, a user device such as a desktop, mobile phone, geodesic device, and so on as may be desirable or appropriate for a given application or environment. Computing system 1000 can include one or more processors, such as a processor 1004. Processor 1004 can be implemented using a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control logic. In this example, processor 1004 is connected to a bus 1002 or other communication medium.

Computing system 1000 can also include a main memory 1008, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by processor 1004. Main memory 1008 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1004. Computing system 1000 may likewise include a read only memory (“ROM”) or other static storage device coupled to bus 1002 for storing static information and instructions for processor 1004.

The computing system 1000 may also include information storage mechanism 1010, which may include, for example, a media drive 1012 and a removable storage interface 1020. The media drive 1012 may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a CD or DVD drive (R or RW), or other removable or fixed media drive. Storage media 1018 may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive 1014. As these examples illustrate, the storage media 1018 may include a computer-readable storage medium having stored therein particular computer software or data.

In alternative embodiments, information storage mechanism 1010 may include other similar instrumentalities for allowing computer programs or other instructions or data to be loaded into computing system 1000. Such instrumentalities may include, for example, a removable storage unit 1022 and an interface 1020, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units 1022 and interfaces 1020 that allow software and data to be transferred from the removable storage unit 1018 to computing system 1000.

Computing system 1000 can also include a communications interface 1024. Communications interface 1024 can be used to allow software and data to be transferred between computing system 1000 and external devices. Examples of communications interface 1024 can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a USB port), a PCMCIA slot and card, etc. Software and data transferred via communications interface 1024 are in the form of signals which can be electronic, electromagnetic, optical, or other signals capable of being received by communications interface 1024. These signals are provided to communications interface 1024 via a channel 1028. This channel 1028 may carry signals and may be implemented using a wireless medium, wire or cable, fiber optics, or other communications medium. Some examples of a channel include a phone line, a cellular phone link, an RF link, a network interface, a local or wide area network, and other communications channels.

In this document, the terms “computer program product” and “computer-readable storage medium” may be used generally to refer to media such as, for example, memory 1008, storage device 1018, or storage unit 1022. These and other forms of computer-readable media may be involved in providing one or more sequences of one or more instructions to processor 1004 for execution. Such instructions, generally referred to as “computer program code” (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system 1000 to perform features or functions of embodiments of the current technology.

In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into computing system 1000 using, for example, removable storage drive 1014, drive 1012 or communications interface 1024. The control logic (in this example, software instructions or computer program code), when executed by the processor 1004, causes the processor 1004 to perform the functions of the technology as described herein.

It will be appreciated that, for clarity purposes, the above description has described embodiments with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processors or domains may be used. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather the feature may be equally applicable to other claim categories, as appropriate.

Although a feature may appear to be described in connection with a particular embodiment, one skilled in the art would recognize that various features of the described embodiments may be combined. Moreover, aspects described in connection with an embodiment may stand alone.

APPENDIX A

Unconstrained Minimization Methods

• • Let:
    • Rⁿ be n-dimensional Euclidean space, x=(x₁, x₂, . . . , x_n)^TεRⁿ, where vectors are columns and the symbol ^T denotes transpose;
    • ∥x∥=√{square root over (x₁²+x₂²+ . . . +x_n²)} be an Euclidean norm of the vector
    • x=(X₁, x₂, . . . , x_n)^TεRⁿ;
    • x, y=x^T y=y^T x be the scalar product of two vectors;

$\frac{\partial f\left(x\right)}{\partial x}$

• • •  be the vector of first partial derivatives of the continuously differentiable function ƒ(x), or the gradient vector;

$\frac{{\partial }^2f\left(x\right)}{\partial x^2}$

• • •  be the matrix of second partial derivatives of the twice continuously differentiable function ƒ(x), or the Hesse matrix;
    • R^n×n be the space of square n×n matrices;
    • I be the identity matrix.
  • The sequence {x^(k)}, k=0,1, . . . , starting with initial approximation x⁽⁰⁾, generated by the following equation

$\begin{array}{cc}{x}^{\left(k\right)}=x^{\left(k-1\right)}-{\lambda }^{\left(k\right)}B^{\left(k\right)}\frac{\partial f\left(x^{\left(k-1\right)}\right)}{\partial x}& \left(\mathrm{A1}\right)\end{array}$

• • which satisfies the minimization property

ƒ(x^(k))<ƒ(x^(k-1))< . . . <ƒ(x⁽⁰⁾)  (A2)

• • if the matrix B^(k)εR^n×n is positive definite and the step length λ^(k) is specially chosen. Methods for calculation of the step length are described, for example, in P. E. Gill, W. Murray, M. H. Wright (1980), Practical Optimization, Academic Press, 1981 pp. 100-102, which is incorporated herein by reference. Robust and practically proven methods include calculating the first number in the sequence

$\left\{{\lambda }_i=\frac{1}{2^i}\right\},i=0,1,2,\dots ,$

• •  satisfying the inequality

$\begin{array}{cc}f\left(x^{\left(k-1\right)}-{\lambda }_ip^{\left(k\right)}\right)-f\left(x^{\left(k-1\right)}\right)<{\mathrm{\mu \lambda }}_i〈p^{\left(k\right)},\frac{\partial f\left(x^{\left(k-1\right)}\right)}{\partial x}〉,\mathrm{where}& \left(\mathrm{A3}\right)\\ p^{\left(k\right)}=-B^{\left(k\right)}\frac{\partial f\left(x^{\left(k-1\right)}\right)}{\partial x},& \left(\mathrm{A4}\right)\end{array}$

• • is the search (or descent) direction vector, and μ is an arbitrary number in the range 0<μ≦0.5. In one example, the value μ=0.01 may be used.
  • The sequence {x^(k)} generated according to the expression (A1) minimizes the function ƒ(x) as shown in inequalities (A2). Thus, the equation (A1) recursively generates the minimizing sequence for any positively definite matrices chosen. The convergence properties of the sequence depend on the choice of the positive definite matrix B^(k). The following are methods that may be used to select the positive definite matrix B^(k) and calculate the equation (A1):
• 1) If B^(k)=I, the equation (A1) may be calculated using the gradient or steepest descent method. The method is known to be linearly convergent.
• 2) If

$B^{\left(k\right)}={\left(\frac{{\partial }^2f\left(x^k\right)}{\partial x^2}\right)}^{-1},$

•  the equation (A1) maybe calculated using the Newton method. The method is quadratic convergent in the neighborhood of the local minimum point where the Hesse matrix is positive definite.
• 3) The iteratively calculated matrices B^(k) may be updated according to the Broyden-Fletcher-Goldfarb-Shanno (BFGS) or Davidon-Fletcher-Powell (DFP) schemes as described, for example, in P. E. Gill, W. Murray, M. H. Wright (1980), Practical Optimization, Academic Press, 1981, pp. 116-127, which is incorporated herein by reference. The BFGS and DFP schemes form the Quasi-Newton family of methods which are known to be super-linearly convergent. These methods are practically as fast as Newton methods, but do not demand calculation of the Hesse matrix. In applications where the Hesse matrix is easily calculated, like in the present application, Newton methods are preferable.

APPENDIX B

Sum of Squares Minimization Methods

Let us consider a particular case of the function ƒ(x) subject to minimization. Let the function ƒ(x) be the sum of squares of m functions φ_i(x):

$\begin{array}{cc}f\left(x\right)=\frac{1}{2}\sum _{i=1}^m{\left[{\varphi }_i\left(x\right)\right]}^2& \left(\mathrm{A5}\right)\end{array}$

Solution of the redundant (if n) set of nonlinear equations

$\begin{array}{cc}{\varphi }_1\left(x\right)=0,{\varphi }_2\left(x\right)=0,\dots {\varphi }_m\left(x\right)=0,& \left(\mathrm{A6}\right)\end{array}$

is often reduced to the minimization problem

ƒ(x)→min  (A7)

Any of the methods 1)-3) described above can be applied to the problem (A7). To apply the Newton method, the expressions for the gradient vector and Hesse matrix are needed. The following equations express them through gradients and Hesse matrices of the functions φ_i(x):

$\begin{array}{cc}\frac{\partial f\left(x\right)}{\partial x}=\sum _{i=1}^m{\varphi }_i\left(x\right)\frac{\partial {\varphi }_i\left(x\right)}{\partial x},& \left(\mathrm{A8}\right)\\ \frac{{\partial }^2f\left(x\right)}{\partial x^2}=\sum _{i=1}^m{\frac{\partial {\varphi }_i\left(x\right)}{\partial x}\left[\frac{\partial {\varphi }_i\left(x\right)}{\partial x}\right]}^T+\sum _{i=1}^m{\varphi }_i\left(x\right)\frac{{\partial }^2{\varphi }_i\left(x\right)}{\partial x^2}& \left(\mathrm{A9}\right)\end{array}$

If the system (A6) is feasible, the values φ_i(x) vanish as the minimizing sequence {x^(k)} converges to the solution. Even if the system (A6) is ‘almost’ feasible, the values φ_i(x) can be neglected in the expression for the Hesse matrix (A9). We arrive at the formulation of the fourth method:

• 4) If

$B^{\left(k\right)}=\sum _{i=1}^m{\frac{\partial {\varphi }_i\left(x\right)}{\partial x}\left[\frac{\partial {\varphi }_i\left(x\right)}{\partial x}\right]}^T,$

•  the equation (A1) maybe calculated using the Gauss-Newton method, for example, as described in P. E. Gill, W. Murray, M. H. Wright (1980), Practical Optimization, Academic Press, 1981, pp. 134-136, which is incorporated herein by reference.

APPENDIX C

Let the cone C, in three dimensional space be defined by its apex α_iεR³, central axis hεR³, common for all m cones, and the angle δ between the axis and the generating line. The vector h is a unit vector aligned with the gravity vector. The equation of the cone C_i takes the form:

$\begin{array}{cc}\frac{〈h,x-a_i〉}{hx-a_i}=\cos \delta .& \left(\mathrm{A10}\right)\end{array}$

Let us denote α=cos δ. Then taking into account that the vector h is a unit vector, we arrive at the following equation

h,x−a _i −α∥x−a _i∥=0  (A11)

The point xεR³ belongs to the surface of the cone C_i if and only if it satisfies the equation (A11). The problem of determining the intersection of cones is reduced to the solution of the problem (A6) with φ_i(x)=h,x−a_i−α_i∥x−a_i∥. The problem is then reduced to the problems (A5) and (A7), which in turn, can be solved by any of the methods 1)-4) described above. To apply, for example, the Newton method, we need to calculate the gradient and Hesse matrix (A8) and (A9), respectively. To complete the description, we derive expressions for

$\frac{\partial {\varphi }_i\left(x\right)}{\partial x}\mathrm{and}\frac{{\partial }^2{\varphi }_i\left(x\right)}{\partial x^2}$

needed for calculations (A8) and (A9):

$\frac{\partial {\varphi }_i\left(x\right)}{\partial x}=h-\frac{{\alpha }_i}{x-a_i}\left(x-a_i\right),\frac{{\partial }^2{\varphi }_i\left(x\right)}{\partial x^2}=\frac{{\alpha }_i}{x-a_i}\left(\frac{1}{{x-a_i}^2}\left(x-a_i\right){\left(x-a_i\right)}^T-I\right).$

Claims

1. A computer-implemented method for operating a Global Navigation Satellite System (GNSS) device, the method comprising: measuring, using a distance sensor of the GNSS device, a distance to an object;determining whether the measured distance is less than a threshold distance; andin response to determining that the measured distance is less than the threshold distance, determining a position of a point of interest based on position data received from a GNSS receiver of the GNSS device.

2. The computer-implemented method of claim 1, wherein determining the position of a point of interest consists of determining the position once.

3. The computer-implemented method of claim 1, wherein determining the position of a point of interest comprises determining the position at least a threshold number of times.

4. The computer-implemented method of claim 1, wherein determining the position of a point of interest comprises determining the position for at least a threshold duration.

5. The computer-implemented method of claim 1, wherein determining the position of the point of interest comprises continuing to determine the position of the point of interest until: determining that the measured distance is not less than the threshold distance; andafter determining that the measured distance is not less than the threshold distance, determining that the measured distance is less than the threshold distance.

6. The computer-implemented method of claim 1, wherein determining the position of the point of interest further comprises recording an image generated by a camera of the GNSS device.

7. The computer-implemented method of claim 1, wherein determining the position of the point of interest further comprises recording a video generated by a camera of the GNSS device.

8. The computer-implemented method of claim 1, wherein determining the position of the point of interest is also in response to a state of the GNSS device.

9. The computer-implemented method of claim 1, wherein determining the position of the point of interest comprises: continuing to determine the position of the point of interest while the measured distance to the object is determined to be less than the threshold distance.

10. The computer-implemented method of claim 1, wherein determining the position of the point of interest comprises: continuing to until determining that the measured distance to the object is not less than the threshold distance.

11. A GNSS device comprising: a distance sensor configured to measure a distance to an object; anda processor coupled to the distance sensor and configured to: receive distance data from the distance sensor representative of the measured distance to the object;determine whether the measured distance is less than a threshold distance; andin response to determining that the measured distance is less than the threshold distance, determining a position of a point of interest based on position data received from a GNSS receiver of the GNSS device.

12. The GNSS device of claim 11, wherein determining the position of a point of interest consists of determining the position once.

13. The GNSS device of claim 11, wherein determining the position of a point of interest comprises determining the position at least a threshold number of times.

14. The GNSS device of claim 11, wherein determining the position of a point of interest comprises determining the position for at least a threshold duration.

15. The GNSS device of claim 11, wherein determining the position of the point of interest comprises continuing to determine the position of the point of interest until: determining that the measured distance is not less than the threshold distance; andafter determining that the measured distance is not less than the threshold distance, determining that the measured distance is less than the threshold distance.

16. The GNSS device of claim 11, wherein determining the position of the point of interest further comprises recording an image generated by a camera of the GNSS device.

17. The GNSS device of claim 11, wherein determining the position of the point of interest further comprises recording a video generated by a camera of the GNSS device.

18. The GNSS device of claim 11, wherein determining the position of the point of interest is also in response to a state of the GNSS device.

19. The GNSS device of claim 11, wherein determining the position of the point of interest comprises: continuing to determine the position of the point of interest while the measured distance to the object is determined to be less than the threshold distance.

20. The GNSS device of claim 11, wherein determining the position of the point of interest comprises: continuing to until determining that the measured distance to the object is not less than the threshold distance.