Tag: GNSS

  • UAVs, high-accuracy GNSS: Red-hot, right-now tech

    By Eric Gakstatter

    It’s been a few months since I’ve published a GSS Monthly newsletter column. What a busy few months it has been. It’s been all about UAVs, high-precision GNSS projects and GIS, with some conferences and workshops sprinkled in between. High-accuracy GNSS technology and UAV technology are hot trends— red hot.

    UAVs: Prosumer and mapping on a slope

    Obviously, consumer UAVs have exploded in the mainstream consumer electronics market during the past five years. Since the FAA began requiring UAVs to be registered in late 2015, far more UAVs have been registered (~700,000 to date) with the FAA than manned aircraft (~320,000).

    In fact, the number of registered UAVs aircraft eclipsed registered manned aircraft more than a year ago! The FAA reported that at any one point during the day, there are ~7,000 manned aircraft flying in the U.S. airspace. That begs the question, how many UAVs are flying above our heads at any one point in time? No one can answer that question.

    On the coattails of consumer UAVs in mainstream America is the use of UAVs in the USA’s commercial world. Since the FAA opened the floodgates in August 2016 to allow almost anyone to fly UAVs for business ($150 and answer 42 out of 60 questions correctly), lots and lots of companies are buying inexpensive “prosumer” UAVs and extracting tremendous value from them.

    Prosumer electronics is equipment and software targeted at the consumer market but also good enough to be used for business. The UAV market is a perfect example of this. DJI, by far the biggest UAV manufacturer in the world at $1B+ in annual revenue, targets the mainstream consumer market and sells a huge number of low-, medium- and high-end UAVs to businesses. Think about it: You can buy a DJI Phantom 4 Pro at your local Apple Store and the next day be generating one-foot elevation contours on a project site!

    Following is an example of a papermill I flew a few weeks ago. I flew it in less than one hour (50 acres), generated an orthophoto with 2.4-cm/pixel resolution and a digital elevation model (DEM) with 4.79-cm/pixel resolution.

    Figure 1 - 2.4cm/pixel resolution orthophoto - 50 acres
    Figure 1.  2.4-cm/pixel resolution orthophoto, 50 acres.
    Figure 2 -DEM with 4.79cm/pixel resolution of the same flight
    Figure 2.  DEM with 4.79-cm/pixel resolution of the same flight.
    Figure 3- Zoomed in image of the same DEM
    Figure 3.  Zoomed-in image of the same DEM.

    The detailed data above, generated from a $1,500 UAV, is clearly outstanding. By the way, the purpose of the project was to determine the volume of the various stockpiles, which I’ve not computed yet. But if the volume calcs are close enough to the traditional terrestrial-based measuring methods, the UAV return on investment (ROI) argument will be hard to beat.

    It takes ~14 hours each month to measure all the stockpiles on this site using traditional terrestrial measurement tools. Also, the measurements must be taken on the weekend when the site activity is minimal. It took less than one hour to fly the entire site, and I flew it twice (one time west-east direction at 80/80 overlap and one time north-south at 70/70 overlap) to make sure I had enough data. I mean, seriously, I drove 1.5 hours to the site. Why not spend another 20 minutes to fly it in a perpendicular direction?

    To date, I’ve only flown relatively flat sites such as construction sites, agricultural fields, and industrial sites. That was until a couple of weeks ago. While I’ve become pretty comfortable at flying open and relatively flat sites over the past 18 months, I’ve not ventured into flying a site with a lot of elevation changes and tree canopy. I finally did that earlier this month, and it was both challenging and rewarding. There are a few problems on sites with major elevation changes and tall tree canopy:

    A. Maintaining visual line of sight (VLOS) as required by the FAA.

    B. Flying in such a manner that the image-processing software has good quality data to work with so you can generate the products you need.

    The mission planning/control software plays a very important roll in this process. Well, it always does, but it really does in this case. Typically, the mission planning/control folks want you to fly at a consistent height above the ground so your overlap is consistent. This is very difficult to accomplish if you’re flying a site with a lot of elevation change. In that case, they typically tell you to launch from the highest (or nearly the highest) elevation point and fly at that elevation.

    The problem this causes is that you could end up flying 500, 600 or 700 feet above ground level (AGL). For example, if you are flying a site with 500 feet of elevation change and you instruct the mission planning/control software to fly at 350 feet AGL, at some point in the project the UAV will be at 850 feet AGL. That can be a problem from both a regulatory standpoint (FAA allows UAV flights up to 400 feet AGL) and an image-processing standpoint.

    Fortunately, the mission planning/control software I use just introduced a Terrain Awareness feature. It uses SRTM (Shuttle Radar Topography Mission) elevation data. Granted, it’s 30-meter pixel elevation data, so each elevation block is 30 meters x 30 meters, so I really wondered if the resolution was high enough. The site I was going to fly was only 60 acres in size and had 550 feet of elevation change. Note that the trees on the site had already been harvested, so the land was relatively clear. There’s about a 550-foot difference from the projected launch point (purple dot) to the northern and western end of the site. Following is the mission plan for the site I was planning to fly.

    Figure 4- 60-acre site with ~550 feet of elevation change
    Figure 4. 60-acre site with ~550 feet of elevation change.

    To give you an idea of the slope, the solid red lines in the following image are 100-foot elevation contour lines. The green triangle is the projected UAV launch point. This was a great launch point because I could see the entire site and maintain VLOS.

    Figure 5- Site topo with projected UAV launch point
    Figure 5.  Site topo with projected UAV launch point.

    I chose to fly the mission at 300 feet AGL. I figured it would be high enough if there was some “slop” in the SRTM elevation model. Still, I was concerned about the resolution of the SRTM data because at 300 feet AGL, my UAV would be flying below the launch elevation due to the extreme elevation slope on the site. Remember, the Terrain Awareness feature of the mission planning/control software is based on the SRTM elevation data, and not based on any sensors in the UAV itself — if the SRTM elevation data was incorrect, my UAV might crash into the ground.

    Following is the SRTM elevation data along with the flight path data displayed in the mission planning/control software.

    Figure 6 - The projected UAV flight path based on the SRTM elevation data
    Figure 6.  The projected UAV flight path based on the SRTM elevation data.

    The moment of truth came when I launched the UAV from the start point (purple dot) and watched it rise to 300 feet AGL to start its mission. The first few swaths were uneventful. After that, it started to fly into the canyon, following the terrain as programmed, then rise up from the canyon during each pass. It was a thing of beauty to watch.

    Unfortunately, about 70% of the way through the mission, it started raining, so we called it quits. However, we proved that at least on the four sites I flew that day, the SRTM data and Terrain Awareness feature were effective in collecting data in steep-slope environments. Following is the 2.69-cm/pixel orthophoto generated from the flight. Note the tracks where the logging rigs pulled the logs up the steep slope.

    Figure 7 - 2.69cm/pixel resolution orthophoto
    Figure 7.  2.69-cm/pixel resolution orthophoto.

    Following is a zoomed-in view of the UAV launch site.

    Figure 8 - Zoomed in view of the orthophoto
    Figure 8.  Zoomed-in view of the orthophoto.

    Following is an image of the 5.37-cm/pixel DEM generated from the flight data. Notice the logging tracks.

    Figure 9 - 5.7cm/pixel image of the DEM generated from the flight data
    Figure 9.   5.7-cm/pixel image of the DEM generated from the flight data.

    Following is a zoomed in view of the 5.37-cm/pixel DEM image.

    Figure 10 - Zoomed in 5.37cm DEM image of UAV launch point
    Figure 10.  Zoomed-in 5.37-cm DEM image of UAV launch point.

    The mission was successful in proving that SRTM elevation data was sufficient enough to fly a mission with a dynamic AGL. It handled the steep slopes by maintaining a sufficient AGL elevation as I hoped it would despite only having 30-meter x 30-meter block elevation resolution. The image processing software seemed to like the UAV data, as you can see from the results above. I didn’t have to spend any additional processing time over and above what I usually spend in order to generate these products.

    I did experience a hiccup with the mission planning/control software running on my iPad Mini 2. It turns out that the Terrain Awareness feature in my mission planning/control software requires some extra CPU horsepower — the software overpowered my iPad Mini and crashed once during a mission. The UAV kept flying its intended course as instructed, but it stopped taking photos when the software crashed, so I brought it back to the launch point.

    After visiting the software vendor’s website, it became clear to me that it’s probably time to upgrade my iPad Mini to the latest model to keep up with the new features being implemented in the software.

    A Quick Note on High-Accuracy GNSS

    In March, I attended the Hawaii GIS conference and decided to perform some benchmark testing on a survey mark using WAAS and a high-accuracy GNSS receiver.

    My goal was two-fold.

    1. See how WAAS is behaving in Hawaii. WAAS in Hawaii is an anomaly because it’s far away from the Continental U.S. (CONUS) where all the WAAS reference stations are located (there’s one in Honolulu, but that’s it). In other words, Hawaii is the most challenging place for WAAS accuracy in North America.
    2. See how many GNSS satellites I could track and use in Hawaii.

    Holy moly, was I surprised at how good it was. I’ve tested WAAS in Hawaii several times in the past many years. The last time I tested it was in 2013 and the GNSS receiver I used (GPS + GLONASS) achieved a steady 80-cm accuracy. That was pretty darned good for WAAS in Hawaii at that time.

    I packed up some receivers and hiked about 4 miles to a survey mark I could find in Honolulu. I was a great survey mark for testing because it was on the sidewalk of a quiet residential street. Following is a photo of the survey mark.

    Figure 11 - PID DK4162 survey mark in Honolulu
    Figure 11. PID DK4162 survey mark in Honolulu.

    I set up on the survey mark and then looked at the satellites the receiver was tracking. I wanted to know how many GPS, GLONASS, Galileo and BeiDou satellites were being used. Following is a screen shot.

    Figure 12 - Total number of GNSS satellites being used – 23
    Figure 12.  Total number of GNSS satellites being used – 23.

    Twenty-three GNSS satellites being used! Are you kidding me? This is more than double the number of GPS satellites being used. This illustrates the power of four-constellation GNSS that is only going to continue to get better over the next several years.

    What surprised me the most was the number of Galileo satellites being used, and this was before two Galileo satellites were declared healthy in late May.

    My next test was to evaluate WAAS accuracy. Who cares how many satellites the receiver is using if the accuracy isn’t improved? I plumbed the receiver antenna on the survey mark and plotted ~7 minutes of data.

    Figure 13- Accuracy plot compared to the DK4162 survey mark coordinates
    Figure 13. Accuracy plot compared to the DK4162 survey mark coordinates.

    Yep, that’s about 30-cm accuracy over a 7-minute period. That’s better by a factor of two compared to the accuracy I saw in 2013. Sure, WAAS has improved somewhat, and maybe the ionosphere was particularly happy that day, but I have to believe that the additional GNSS satellites contributed the most to the improvement in accuracy. In the next few months, I’m going to be performing more tests with WAAS and RTK on my GNSS test course near my office. I’ll keep you posted on the results of those tests.

    The Esri International User Conference – July 10-14

    As usual, I’ll be attending the largest gathering of GIS professionals in the U.S. next month, the Esri International User Conference. 16,000 of our colleagues will descend upon San Diego to share, network and enjoy the spatialness that we have for one another.

    If you’re interested, I’m giving a couple of presentations at the Esri UC:

    • Tuesday (July 11), 08:30 a.m., Room 28B (subject to change)

    Paper Title: An Efficient, Accuracy Mobile GIS Workflow using RTK GNSS

    Session Title: Mobile Data Collection

    This is cool project I worked on with WaterOne, a large water utility, to design a real-time, high-accuracy GNSS workflow in the Esri environment. They are collecting data at the centimeter level for mapping their above-ground assets as well as new construction using tablet computers and RTK GNSS receivers.

    • Thursday (July 13), 8:30 a.m., Room 29C (subject to change)

    Paper Title: UAV (drone) applications for water utilities

    Session Title: Applied GIS: Three Unique Examples

    This is some groundbreaking work I’ve done with American Water on using UAV technology for mapping and inspection. We did a lot of experimenting during the proof-of-concept phase to figure out what applications are practical and which aren’t.

    Thanks, and see you next time.

    Follow me on Twitter at https://twitter.com/GPSGIS_Eric

    All Provided by Eric Gakstatter

  • Handbook on GNSS published by Springer

    Handbook on GNSS published by Springer

    The Springer Handbook of Global Navigation Satellite Systems is now available.

    Described as “A state-of-the-art description of GNSS as a key technology for science and society at large,” the 1,327-page tome is edited by Peter J.G. Teunissen and Oliver Montenbruck.

    Teunissen is a professor of Geodesy and Satellite Navigation at Curtin University, Australia, and Delft University of Technology (TU Delft), the Netherlands.

    Montenbruck is head of the GNSS Technology and Navigation Group at the DLR’s German Space Operations Center, Oberpfaffenhofen, and chair of the Multi-GNSS Working Group of the International GNSS Service, as well as being a GPS World contributor and recipient of the GPS World Leadership Award.

    Exhaustive Reference. The handbook presents a complete and rigorous overview of the fundamentals, methods and applications of the multidisciplinary field of GNSS, providing an exhaustive, one-stop reference work and a state-of-the-art description of GNSS as a key technology for science and society at large.

    All global and regional satellite navigation systems, in operation and under development (GPS, GLONASS, Galileo, BeiDou, QZSS, IRNSS/NAVIC, SBAS), are examined in detail. The functional principles of receivers and antennas, as well as the advanced algorithms and models for GNSS parameter estimation, are rigorously discussed.

    The book covers the broad and diverse range of land, marine, air and space applications, from everyday GNSS to high-precision scientific applications and provides detailed descriptions of the most widely used GNSS format standards, covering receiver formats as well as IGS product and meta-data formats.

    The full coverage of the field of GNSS is presented in seven parts, from its fundamentals, through the treatment of global and regional navigation satellite systems, of receivers and antennas, and of algorithms and models, up to the broad and diverse range of applications in the areas of positioning and navigation, surveying, geodesy and geodynamics, and remote sensing and timing.

    Each chapter is written by international experts and amply illustrated with figures and photographs, making the book an invaluable resource for scientists, engineers, students and institutions alike.

    Learn more at the publisher website.

  • Altair markets narrowband cellular chipset with integrated GNSS

    Altair markets narrowband cellular chipset with integrated GNSS

    LTE chipset maker Altair Semiconductor has demonstrated GNSS functionality integrated in its new ALT1250 narrowband CAT-M1 and NB1 (NB-IoT) chipset.

    In addition to GNSS functionality, the ALT1250’s extreme level of integration eliminates the need for most external components required to design a cellular Internet of Things (IoT) module.

    Its GNSS capability was demonstrated June 13  at the Sierra Wireless Innovation Summit being held at the Paris Novotel Tour Eiffel in Paris, France.

    Approximately the size of a shirt button and less than 100 mm2 in size, an ALT1250 module features support for both Release 13 standards — CAT-M1 and NB1, and includes a wideband RF front-end supporting unlimited combinations of LTE bands within a single hardware design, a multi-layered and hardware-based security framework, an internal application MCU subsystem and packaging that enables standard, low-cost PCB manufacturing.

    “Location determination is essential in many IoT applications — including asset tracking, vehicle monitoring and wearable devices. Satellite positioning is the most accurate method for doing that,” said Eran Eshed, co-founder and vice president of marketing for Altair. “Integrating GNSS functionality in the ALT1250 significantly reduces the overall cost of IoT solutions while offering state-of-the-art, low-power satellite positioning capabilities in a miniature package. The market is responding well to it.

    “We called the ALT1250 a game-changer when we announced it several months ago — integrated GNSS is one of a large set of groundbreaking innovations offered by this chip.”

     

  • Inertial performance: Enhanced tightly coupled dead reckoning

    Inertial performance: Enhanced tightly coupled dead reckoning

    Exploring IMU specifications and correlating them to performance of a final product can be daunting, as differences between MEMS sensors are not always apparent. This article presents achievable performances in fusion technology across a range of IMUs among the best in their respective performance categories. 

    The number of available options in inertial navigation systems (INS) has grown substantially over the last several years. Major advances have been made not only in inertial measurement unit (IMU) technology, but also in the ability to exploit sensor information to its fullest extent. In both cases, the largest impact can be seen in the micro-electrical-mechanical systems (MEMS) sensors. MEMS sensors are typically much smaller, lower power and less expensive than traditional IMUs. The net result of these improvements is a proliferation of INS systems at much lower cost than were previously available and, therefore, greatly increased accessibility to technology that has historically seen limited deployment. Selecting the appropriate sensor and fusion solution for a particular application can be very challenging due to the large and confusing spectrum of solutions.

    The IMUs will be examined in the context of new enhancements to sensor fusion algorithms such as the use of INS profiles. The concept of INS profiles applies environment specific constraints to improve performance in certain types of vehicles, or motion profiles. External sensors such as odometers and dual antenna operation can also aid the solution considerably, but will be unused in this analysis except for occasional comparisons. These external aiding sensors are extremely helpful in many cases and are available to use with a proprietary tightly coupled GNSS+INS solution called SPAN, but this paper seeks to evaluate what performance can be achieved without such aids.

    Real-world test results will be examined using a selection of IMUs with the latest SPAN algorithms to illustrate what kind of performance can be achieved with different sensors in difficult conditions. Despite their major advances over the past few years, there are many challenges involved with utilizing MEMS technology to provide a robust navigation solution, particularly during limited GNSS availability or low dynamics. The measurement error characteristics of these devices have improved dramatically, but are still much larger and more difficult to estimate than traditional sensors. Advancements in SPAN sensor fusion algorithms have enabled these smaller sensors to achieve remarkable performance, especially in applications where environmental conditions allow for additional constraints to be applied.

    This testing focuses on the land profile, meaning the constraints applied to a fixed-axle vehicle. The test scenarios were selected in such a way as to provide results for ideal, poor and completely denied GNSS coverage.

    INS Profiles

    GNSS and IMU sensors are only one part of the overall INS system performance. The sensor fusion algorithms used to exploit the available sensor data to its utmost capability are equally as important. In this regard, several improvements have been made to the SPAN INS algorithms to enhance performance under a variety of scenarios.

    The largest addition to the SPAN product line is the introduction of INS profiles. That is, environment- and vehicle-specific modeling constraints can be utilized to enhance the filter performance. For example, the land profile, which will be examined in depth in this article, is intended for use with ground vehicles that cannot move laterally. The assumptions introduced for land vehicles, however, are not necessarily valid for different forms of movement, such as those experienced by a helicopter. Therefore, profiles have been implemented via command, and controlled as required by the user, allowing for maximum performance depending on the application at hand.

    The land profile is analogous to what has historically been identified as dead reckoning. It is a method that uses a priori knowledge of typical land vehicle motion to help constrain the INS error growth. In other words, it makes assumptions on how land vehicles move to simplify inertial navigation from a six-degree-of-freedom system to something closer to a distance/bearing calculation. The land profile takes the concept of dead reckoning, models it as an update type into the inertial filter and adds a few additional enhancements.

    Velocity Constraints / Dead Reckoning. Amongst other optimizations, the land profile enables velocity constraints based on the assumption of acceptable vehicle dynamics. This includes limiting the cross track and vertical velocities of the vehicle. Of all the enhancements, this is the one most colloquially referred to as dead reckoning.

    In its simplest form, dead reckoning is the propagation of a position without any external input. In this forum, external input generally refers to GNSS satellites. Without external input, dead reckoning is inherently dependent on assumptions of velocity and heading to propagate the position. These solutions have evolved by integrating inertial and directional sensors to provide more local input and improve the solution propagation. This also is not a perfect method, however, as inertial sensors have their own errors that grow exponentially over time. The land profile velocity constraints explain the bulk of optimizations SPAN has made to enable dead-reckoning performance in extended GNSS outage conditions.

    Explaining the velocity updates involves using the current INS attitude (  ); the vehicle attitude (  ) is estimated by applying the measured or estimated IMU body to vehicle direction cosine (  ). From this, the pitch and azimuth for the vehicle is estimated.Using the magnitude of the measured INS velocity in conjunction with the derived vehicle orientation, the vehicle velocity is computed, allowing the expected vertical velocity and cross-track to be constrained.

    A velocity vector update is then applied to the inertial filter to constrain error growth. The effects of this method are expected to be most apparent in extended GNSS outage conditions when the INS solution must propagate with no external update information.

    Phase Windup Attitude Updates. Some applications are inherently difficult for inertial sensors due to the fact that these systems are reliant on measuring accelerations and rotations in order to observe IMU errors. When traveling at a constant bearing and speed, separating IMU errors from measurements becomes challenging, so any application that does not provide meaningful dynamics is more demanding on inertial navigation algorithms. This type of condition commonly appears in applications such as machine control, agriculture and mining.

    Gravity is a strong and fairly well known acceleration signal, so the real difficulty in this type of environment is managing the attitude, and especially azimuth, errors. Attitude parameters become difficult to observe when the system experiences insignificant rotation rates about its vertical axis.

    External inputs can be used for providing input during low dynamic conditions when rotational observations are weaker. These are particularly helpful in constraining angular errors and include the same types used to assist in initial alignment: dual antenna GNSS heading, magnetometers, etc. However, as the goal of this testing is to demonstrate the achievable performance from a single antenna GNSS system, this type of external aid was specifically omitted.

    Utilizing a patented technique for determining relative yaw from phase windup, the system is able to distinguish between true system rotation and unmodeled IMU errors during times of limited motion. This is a novel way to extract additional information out of existing sensors rather than adding more equipment and complexity.

    The phase windup update is used to constrain azimuth error growth during low dynamic conditions that are typically not favorable to inertial navigation. However, it does require uninterrupted GNSS tracking and is therefore applicable only in GNSS benign environments. This approach is expected to show the greatest benefit in low dynamic conditions and be directly attributable to azimuth accuracy, but only in conditions where GNSS availability is relatively secure.

    Equipment and Test Setup

    We paired OEM-grade GNSS receiver cards with a selection of IMUs in different performance categories. Since the OEM GNSS platform is capable of tracking all GNSS constellations and frequencies, we configured each receiver to use triple frequency, quad-constellation RTK positioning. The receivers were coupled with a wideband antenna capable of tracking GPS L1/L2/L5, GLONASS L1/L2, BeiDou B1/B2 and Galileo E1/E5b signals.

    Three IMUs were tested: an entry-level MEMS IMU (UUT1), a tactical-grade MEMS IMU (UUT2) and a high-performance fiber-optic gyro-based IMU (UUT3).

    All GNSS receivers and IMUs were set up in a single test vehicle and collected simultaneously for all scenarios. IMUs were mounted together on a rigid frame, and all receivers ran the same firmware build that were connected to the same antenna.

    The tests were conducted using a single GNSS antenna with no additional augmentation sources, such as distance measurement instrument (DMI) or wheel sensor. These are extremely helpful in aiding the solution, but as previously mentioned, this testing seeks to demonstrate the possible performance without the benefit of additional aiding sources. Dependence on aiding sources is a very important distinction when comparing such systems.

    The GNSS positioning mode used was RTK via an NTRIP feed from a single base station with baselines between 5–30 kilometers. This was done to try to minimize GNSS positioning differences between the three systems. L-band correction signals were not tracked, and PPP positioning modes were not enabled.

    A basic setup diagram of each system under test can be seen in Figure 1.

    FIGURE 1. Equipment set-up (not to scale).

     

    Test Scenarios

    Four test scenarios will be examined using all the equipment and algorithms described above. They are: urban canyon, low dynamics, parking garage and extended GNSS outage.

    The urban canyon test is designed to show the performance of the system in restricted GNSS conditions. The challenge to this scenario is to maintain a high-accuracy solution when GNSS positioning becomes intermittent or even unavailable.

    The low dynamics test is intended to illustrate the benefits of the land profile, and specifically the phase windup azimuth updates in maintaining the azimuth accuracy.

    The parking garage test will show the efficacy of the velocity constraint models over the different IMU classes as the extended outage provides no external information to the INS filter whatsoever. Again, no other aiding sources were used.

    Urban Canyon Test. The urban canyon environment has been and remains one of the strongest arguments in favor of using GNSS/INS fusion in a navigation solution. Because urban canyons are common, densely populated and, of course, a demanding GNSS environment, they represent both an important and challenging location to provide a reliable navigation solution. Typically, they contain major signal obstructions, strong reflectors and complete blockages (depending on the city). For this reason, they provide an excellent use case for INS bridging to maintain stability of the solution.

    During most urban canyon environments, it is typically rare to incur total GNSS outages of more than 30 seconds. Therefore, this scenario examines the stability of the solution in continuously degraded, but not generally absent, GNSS. In this case, the coupling technique of the inertial algorithms rather than quality of the IMU dominates achievable position accuracy.

    The receiver platform is capable of tracking all GNSS constellations and frequencies. This provides a significant benefit to test scenarios, such as the urban canyon, where the amount of visible sky is significantly restricted. In this case, the more satellites that are observable, the more the tightly coupled architecture can exploit the partial GNSS information.

    Though position accuracy between IMUs is less apparent in this condition, attitude results remain separated by IMU quality, which is a major consideration for some mapping applications such as those using lidar or other sensors where a distance/bearing calculation must be done for distant targets.

    Test data for this scenario was collected in downtown Calgary, Canada. The trajectory (Figure 2) includes several overhead bridges for brief total outages and some very dense urban conditions.

    FIGURE 2. Urban canyon test trajectory.

    Table 1 shows the RMS error results of the three systems running both the default and land profiles. The first thing to notice is that the errors are differentiated by IMU category, though the differences are fairly small in the position domain thanks to the tightly coupled architecture. However, because GNSS information is partially available, the differences seen in activating the land profile are fairly modest, especially as the IMU performance rises.

    TABLE 1. RTK RMS errors for urban canyon.

    As the clearest benefits of the land profile are seen on the entry-level MEMS IMU (UUT1), these will be explored graphically in Figures 3 and 4. Figure 3 shows the position domain, and the RMS differences can be seen in a few cases where the default mode errors increased faster than the land profile. An example of this divergence is most obvious around the 1500-second mark of the test during periods GNSS is most heavily blocked.

    Low Dynamics Test. The low dynamics test is designed to emulate conditions experienced by machine control, agriculture and mining applications. In this situation, GNSS availability is generally not the limiting factor and can be used to control the low frequency position and velocity errors of the INS system. The difficulty is managing the attitude, especially azimuth, errors because attitude parameters are very hard to observe without significant rotations or accelerations (Figures 5 and 6).

    The low dynamics test was collected in an open-sky environment and consisted of traveling in a straight line on a rural road for roughly 2 km at an average speed of 10–15 km/h.

    As this type of scenario provides little physical impetus, the azimuth and gyroscope biases are not observable. The reason for this is due to the use of the first-order differential equations to estimate the navigation system errors. Essentially, the differential equations define how the position, velocity and attitude errors change (grow) over time based on each other and the IMU errors. The observability of a particular update is tied to additional states through the off-diagonal elements of the derived transition matrix with the accelerations and rotations experienced by the system.

    The overall RMS solution errors for RTK are provided in Table 2. As evident by the results presented, the position and velocity errors are clearly constrained by the continuous RTK-level GNSS position regardless of whether the land profile is enabled or not. The real differentiator in the land profile is the attitude performance due to the use of phase windup as a constraint. Moreover, the attitude improvements are certainly tied to IMU quality.

    TABLE 2. RTK RMS errors for low dynamics.
    TABLE 3. RTK RMS errors, parking garage (500s).

    UUT1 exhibited a noticeable improvement in the attitude performance, while the higher performance IMUs did not. This is not entirely unexpected as the precision of the phase windup is lower than that of the higher grade IMUs.

    Looking at the data graphically, Figure 7 shows the effect of land profile on positioning performance in this scenario. The two solutions are indistinguishable on the plot, and are all within standard RTK-level error bounds as was indicated in the RMS table.

    Figure 7 shows the attitude accuracy with and without the land profile enabled. Again, the largest gains are seen on the entry-level UUT1, so this is the graphic shown below. This shows how the error peaks of the azimuth estimates are constrained. All the sharp corrections in each plot correspond to the vehicle turning around at the end of each 2-Km line and illustrates how much more powerful a rotation observation can be in azimuth accuracy overall.

    FIGURE 7. UUT1 attitude error (std vs. land).

    Parking Garage Test. This test was carried out at the Calgary International Airport and was selected to show the INS solution degradation during extended complete GNSS outages. The test consisted of an initialization period in open sky conditions to allow the SPAN filter time to properly converge, followed by a 500-second period within the parking garage. During the interval within the parking garage there were no GNSS measurements available.

    Figure 8 provides a trajectory of the test environment. The time spent inside the parking structure is evident on the center bottom of the image.

    FIGURE 8. Parking garage test trajectory.

    Unlike urban canyon environments that contain partial GNSS information, this exhibits an extended period of complete GNSS outage. During this type of scenario, the IMU specifications become much more significant. IMU errors directly translate to the duration the solution can propagate before the accumulated low-frequency errors of the IMU grow to unacceptable levels. System performance during the outage degrades according to the system errors at the time of the outage and the system noise. The velocity errors increase linearly as a function of attitude and accelerometer bias errors. The attitude errors will increase linearly as a function of the unmodeled gyro bias error. The position error is a quadratic function of accelerometer bias and attitude errors.

    Position results from each IMU are shown for UUT 1 in Figure 9. This plot shows the error with the land profile on and off. Without the land profile, the second-order position degradation in an unconstrained system is clearly visible.

    FIGURE 9. UUT1 position error (std vs. land ).

    By enabling the land profile, the filter constrains IMU errors by utilizing a velocity model for wheeled vehicles. With the constraints, the position errors are startlingly reduced for UUT1 and then progressively less impactful as the IMU quality increases in UUT2 and UUT3, respectively. This makes sense as the IMU error growth is progressively smaller in those IMUs, so the effect of mitigating them is also reduced.

    Extended GNSS Outage Test. An extension of the parking garage test is to evaluate the performance in a much longer outage. Instead of 10 minutes, an outage of one hour was tested. Also, due to the extremely long GNSS outage bridging, the effects of adding a DMI sensor (odometer) will also be explored as they are able to be used as a major additional aiding source.

    Table 4. Percent error / distance traveled over 1-hour GNSS outage.

    The most common measure of dead-reckoning performance is error over distance traveled (EDT). Due to the very long duration outages in this test, the errors will be reported in error over distance traveled to conform to the typical reporting method. This test was conducted in a mixture of highways and suburban streets with an average speed of 65 Km/h, incorporating a moderate amount of dynamics.

    This effect can be seen over the duration of the entire outage as well in Figure 9. In this case, the points are the RMS error over several tests. and the light background shroud represents the one-sigma confidence as time progresses. The confidence increases over time as the overall distance traveled also increases.

    FIGURE 10. Land profile EDT with and without DMI aid over 1-hour GNSS outage.

    Results and Conclusions

    In testing a range of IMUs in some challenging scenarios, this paper has sought to illustrate what kind of performance is achievable using each kind of system. An added complexity is looking at what effect certain inertial constraint algorithms have on this solution.

    Although low-cost MEMs IMUs are continuing to greatly improve in quality and stability, the end application is still highly correlated to the overall performance of a selected INS system. For a great many applications, the MEMS devices in combination with a robust inertial filter can meet requirements and provide excellent value. However, some applications continue to require higher end sensors, and possibly post-processing to meet their needs.

    The ability of SPAN to utilize partial GNSS measurements such as pseudorange, delta phase and vehicle constraints means even low-cost MEMs are capable of providing a robust solution in challenging GNSS conditions. However, this tightly coupled integration is limited in cases where GNSS is completely denied or when in low dynamic conditions.

    INS profiles using velocity constraints, phase windup and robust alignment routines have been shown to provide substantial aid to the INS solution in tough conditions, such as GNSS denied or low dynamics. These improvements were shown to exhibit greater impact as the IMU sensor precision decreases. These abilities, in conjunction with the existing tightly coupled architecture of SPAN and the ever-increasing accuracy of MEMS, IMUs indicate that robust GNSS/INS solutions will continue to proliferate at lower cost targets. However, very precise applications such as mapping will continue to rely on higher quality sensors to meet strict accuracy requirements.

    ACKNOWLEDGMENTS

    The authors thank Trevor Condon and Patrick Casiano of NovAtel for collecting and helping to process the data presented in this article, and to Sheena Dixon for her tireless editing.

    Manufacturers

    NovAtel SPAN technology on the NovAtel OEM7 receiver is the testing and development platform for this research. NovAtel OEM7700 GNSS receiver cards and a NovAtel wideband Pinwheel antenna were employed. The inertial units under test were an Epson G320 (low-power, small-size MEMS IMU); Litef μIMU-IC (larger tactical-grade performance IMU still based on MEMS sensors); and a Litef ISA-100C (near navigation-grade IMU using fiber-optic gyros (FOG). Although all are excellent performers in their class and capable of providing a navigation-quality solution, the intent is to show the potential limitations that might arise due to the intended application.


    RYAN DIXON is the chief engineer of the SPAN product line at NovAtel Inc., leading a highly skilled team in the development of GNSS augmentation technology. He holds a BSc. in geomatics engineering from the University of Calgary.

    MICHAEL BOBYE is a principal geomatics engineer at NovAtel and has participated in a variety of research projects since joining in 1999. Bobye holds a BSC. in geomatics engineering from the University of Calgary.

  • Sokkia introduces field-to-office GeoPro software

    Sokkia introduces field-to-office GeoPro software

    Sokkia has introduced a pair of software solutions for its total stations, robotics and GNSS rover systems — GeoPro Field and GeoPro Office.

    Sokkia GeoPro Field software.

    GeoPro Field provides a graphical user interface designed to collect field measurements for land surveying and construction activities.

    “End-users needing a field tool to collect and import measurement data into design and drafting software will find GeoPro Field to be a fast and accurate method that will increase productivity with CAD functionality in the field,” said Ray Kerwin, director of global surveying products. “A key to GeoPro Field is its compatibility with various software workflows — point files are easily exported to third-party software.”

    Sokkia GeoPro Office software.

    Sokkia GeoPro Office is the office-processing complement to the field software — designed to clean, process, and analyze field data into its easiest-to-use form. “Users will immediately see the benefit in time saved, when compared to a variety of traditional manual methods,” Kerwin said.

    The office software can also be expanded with an optional 3D and road design module, for further versatility to design roads with the processed field measurements.

    “The Sokkia GeoPro Field and Office have user-friendly graphical interfaces, with simple in-field functions and office workflows. The user can get to work quickly due to the intuitive interface and simplicity of operation without the need for advanced training,” Kerwin said.

  • Galileo provides healthy signals 97.33 percent of the time

    Galileo provides healthy signals 97.33 percent of the time

    Europe’s Galileo satellite navigation system has undergone its first performance report since it started work at the end of last year, and it passed with flying colors, said the European Space Agency.

    The European GNSS Agency, GSA, through its GNSS Service Centre, has published the first of its regular quarterly performance reports on Galileo. This European GNSS (Galileo) Initial Services Open Service report, now available online, covers the first three months of 2017 and documents the good performance of Galileo Initial Services to date.

    The report shows the 11 satellites then operating in the Galileo constellation were able to provide healthy signals 97.33 percent of the time on a per satellite basis, with a ranging accuracy better than 1.07 m and disseminating global UTC time within its signal to within 30 billionths of a second on a 95 percentile monthly basis.

    “Galileo Initial Services were declared by the European Commission on 15 December 2016,” said Joerg Hahn of ESA’s Galileo System Office.

    “It was thanks to the tremendous effort of ESA’s Galileo team working closely together with colleagues from the commission and GSA that this milestone could be achieved: the key pillars for reaching are the currently deployed Galileo satellites in combination with the global Galileo ground segment infrastructure, defined and implemented by the ESA team with their respective industry partners.”

    The Initial Service performance levels achieved by the system are monitored using two complementary monitoring platforms: the Time and Geodetic Validation Facility, an independent precision time-measuring system accurate to a billionth of a second — using an ensemble of atomic clocks located at ESA’s ESTEC technical centre in Noordwijk, the Netherlands — and the Galileo System Evaluation Equipment, GALSEE, based in Rome.

    The steadily declining Signal in Space Ranging Error (SISE) of the Galileo constellation from 2014 to the present.

    In the future, the independent monitoring of the services will be carried out by GSA’s Galileo Reference Centre, currently taking shape beside ESTEC in Noordwijk. The results for the first quarter of 2017 show the measured performances are generally far better than the minimum performance levels identified in the Service Definition Documents.

    “Looking back over the ranging accuracy of the Galileo constellation from the time of the very first positioning fix in 2014 to the present, the overall performance trend for the Open Service is very positive,” Joerg said.

    “It has reached values of less than 1 m in recent months, being already competitive with other satellite navigation systems.

    “The high-quality ranging service enables user level positioning with a typical accuracy of around 3 m on the ground and 5 m in altitude during periods when four satellites are visible. With the limited infrastructure so far deployed, current horizontal position fixes can be achieved during more than 80 percent of the time with accuracies better than 10 meters.

    “This user level performance is expected to improve with the launch of more satellites making the provided Galileo services more accurate, more available and more robust for end users.”

  • Google updates progress on Android GNSS measurements

    Google updates progress on Android GNSS measurements

    Nearly a year ago, Google debuted GPS measurements in Android.

    “Since then, we’ve made a lot of progress,” Steve Malkos, Google technical program manager, told GPS World.

    Frank van Diggelen and Mohammed Khider joined Malkos in hosting a half-day tutorial at ION GNSS+ 2016 in September that detailed how to access and use GPS measurements from Android devices.

    “We (Google) launched a new website around our efforts with GNSS Measurements that has the latest updates about all things GNSS, such as supported devices, collection tools and analysis tools,” Malkos said.

    The Android GNSS Analysis Tool shows how users can select and run the analysis on a per-satellite basis. This tool now supports multi-constellation and dual frequency (L1 and L5) by default. (Credit: Google)
    The Android GNSS Analysis Tool shows how users can select and run the analysis on a per-satellite basis. This tool now supports multi-constellation and dual frequency (L1 and L5) by default. (Credit: Google)

    Also, many devices releasing this year will support multi-constellation raw GNSS measurements for the first time. The Phone section on Google’s website shows the latest phones that support multi-constellation measurements. “Google also has launched a device with this capability, one of the first in the world,” Malkos said.

    Android O, the next version of Android, will include new GNSS measurement features, such as true multi-constellation support with GNSS measurements (API supported constellations include GPS, SBAS, GLONASS, QZSS, BeiDou and Galileo), measurement support on multiple frequencies (including L1 and L5) and reported AGC (accumulated gain control) jamming detector.

    This plot shows the generated output from the Android GNSS Analysis Tool: Signals strengths for the top four satellites per constellation, Skyplots, C/N0 plots, clock continuity or discontinuity, WLS output, PRR and PRR residuals. (Credit: Google)
    This plot shows the generated output from the Android GNSS Analysis Tool: Signals strengths for the top four satellites per constellation, Skyplots, C/N0 plots, clock continuity or discontinuity, WLS output, PRR and PRR residuals. (Credit: Google)

    Google hosts ION GNSS tutorial

    Google is hosting a full-day tutorial, “Raw GNSS Measurements from Android Phones,” at ION GNSS+ 2017, which will be held Sept. 25–29 in Portland, Oregon.

    The interactive course covers:

    • The Android Software Stack. Learn how GNSS measurement data flows through the Android software stack. Google will also show attendees where to find the definitions of the different data structures and identify which ones are available at the Application layer.
    • Updates to Android O. Preview the new GPS-related changes that are slated for Android O.
    • Description of the available data. Review the data that is accessible in Android, the definitions of the different types of GNSS measurements, their physical meaning and how to use them for analysis and location.
    • Using the data. Collect GNSS measurements outside and download the data from a provided test device to do some processing. Google will provide software tools that allow participants to log data from an Android Nougat or Android O device, view the raw measurements, and complete basic measurement analysis and position computation.
    • Examples. Finally, Google will give those who attend specific examples of research projects and applications that users can develop with the tools and knowledge obtained in the class, such as how to build a GNSS data analysis app or how to build a crowd-sourced jammer detector.

    To help the Android Measurements team tailor this tutorial to your needs, fill out this form with additional items you’d like covered in the class.

  • Road navigation using multiple dissimilar environmental features

    Look Around

    Road Navigation Using Multiple Dissimilar Environmental Features

    New navigation paradigms combining GNSS and inertial with additional sensors can increase overall reliability and power robust road navigation. A feasibility study tests a barometer, a magnetometer and a camera looking at road signs, and concludes that such sensors examining environmental features can supply the necessary context for frequently traveled or shared routes.

    By Debbie Walter, Paul D. Groves, Bob Mason, Joe Harrison, Joe Woodward and Paul Wright

    Where a robust and reliable position solution is required, it is necessary to combine GNSS with other technologies. Dead-reckoning is only suitable for bridging short outages. For robustness against longer GNSS outages, alternative position fixing techniques are needed. Radio-based signals have been excluded from this study as they are either not yet mature or are, like GNSS, susceptible to jamming, though they may still play a part in the final navigation solution.

    For land navigation in particular, a new approach is therefore needed. Environmental features provide a potential source of location information. These include buildings or parts thereof, signs, roads, rivers, terrain height, sounds, smells and even variations in the magnetic and gravitational fields. Visual navigation technologies are being developed and are likely to be complementary to the feature-matching discussed in this article; however, they will not be directly discussed. The environmental features will be integrated with dead reckoning to provide robust positioning.

    The overall solution is to place hardware within a batch of vehicles, comprising multiple sensors, including a GNSS receiver and sensors for dead reckoning. Road map matching could also be included. During normal usage, the GNSS receiver is used for positioning and a database is updated with the feature information from all the sensors accompanied by location stamps from the GNSS-based position solution.

    As the multiple vehicles travel around an area, the database is built up for these routes. In the event that the GNSS receiver does not receive sufficient signals to maintain an accurate position, the database is called upon for navigation by environmental feature matching. In this scenario, the sensors continue to take measurements and, by combining the knowledge of the last known location, dead reckoning and the sensor’s outputs, the positioning algorithm draws upon the database to estimate a positioning solution. This method is shown in Figure 1 and Figure 2.

    This navigation system relies upon the roads being travelled on a regular basis so that the “maps” created from the sensor’s outputs are kept up to date and therefore valid. The most likely users of this technology would be fleets of vehicles that can share the mapping information. To focus on a typical system, use in emergency vehicles was considered. Knowing your position is vital in an emergency vehicle, and a system that incorporates a back-up to GNSS would be advantageous. The motivation for maintaining a continuous positioning solution is that, when moving within a complex environment, it is necessary to maintain the integrity of the current position. In emergency situations, delays are not acceptable and integrity is vital. There will be no point in time when the vehicle can be delayed to obtain a position fix.

    Although this system will be designed with emergency service vehicles such as ambulances and police cars in mind, it could also be used in wider applications such as fleet management and tracking devices. Ultimately, crowd sourcing or cooperative techniques could be used to pool information from different vehicles equipped with the system. With a very large number of vehicles maintaining the feature database, the system could adapt to changes in the environment very quickly.

    To reliably achieve meters-level positioning across a range of different challenging environments, a paradigm shift is needed. We need to use as much information as we can cost-effectively obtain from many different sources in order to determine the best possible navigation solution in terms of both accuracy and reliability.

    This new approach to navigation and real-time positioning in challenging environments requires many new lines of research to be pursued.

    ROAD EXPERIMENT

    A set of sensors with a GNSS receiver were attached to a car and driven in closed loops around Stoke-on-Trent on multiple road types over multiple days. The loops were repeated three times on each day on four road types and then repeated over three consecutive days. The sensors used can be seen in Table 1.

    Table 1. Sensors used in the road experiments.

    The accelerometer, air quality sensor, barometer, dust sensor, light sensors and microphone interfaced with an Arduino microprocessor which outputted the signals from the sensors to a laptop. The Arduino sensors had a data rate of 20 measurements per second. There was an individual accelerometer (attached to the axel of the vehicle) for use in identifying road texture. There are also accelerometers that form part of the inertial measurement unit (IMU), and these were used for dead reckoning.

    The onset of movement as recorded from the IMU was used to assist in identifying the beginning of each circuit. During the car journeys, there were two experimenters, one to drive the car and another to monitor the sensors. There were 5–10 minutes between each round; during this time, the sensors would be turned off and then restarted. The equipment was designed for the outputs of the sensors to be post-processed.

    The four classes of road were suburban, urban, rural and high-speed road. The route taken and a view from Google Street View showing the general type of landscape traveled through is shown in Figure 3.

    A road experiment travelled the routes, using GPS receivers with the Arduino, video camera and the IMU so that GPS time could be used as a constant for the various sensors.

    WHOLE ROUTE ANALYSIS

    The outputs from the sensors were evaluated initially for their cross correlation over the whole route. This process assessed whether the data from different runs over the same terrain were similar and thus had a high cross correlation. This is vital for this map-building method of navigation. This section deals only with sensors that produce continuous output. The next section discusses discrete features.

    Cross-Correlation Coefficients. The correlation coefficient (see online version of this article for derivation equations) is used to calculate the cross-correlation of two rounds of sensor data. The cross correalation coefficient is a normalized value. If a signal is correlated with itself, at zero offset (autocorrelation) this would give a value of 1; entirely uncorrelated data gives 0. Signals 180° out of phase would give a correlation value of –1.

    The cross-correlation coefficients are shown in Table 2 for all of the sensors. It shows the coefficients for the four different road types using combinations of rounds (round 1 and 2, round 2 and 3 and round 1 and 3 for each three days) from the same days and the average of the coefficients for all the combinations. The sensors with higher coefficients are discussed in more detail in the following subsections. Road signs do not have cross-correlation coefficients; they are treated differently as this is a discrete measurement.

    Accelerometer. The magnitude of the acceleration from a accelerometer triad was used in this experiment as a method of measuring road texture. A zoomed-in section of the acceleration as recorded from the accelerometer against the distance traveled can be seen in Figure 4.

    Figure 4. Profile from accelerometer attached to axle.

    It is difficult to see similarities in the output from the different rounds, although the accelerometer can show movement from stationary to driving and this was used to initialize the sensor outputs from the XSens IMU. This is shown in Figure 5 at 44s.

    Figure 5. Accelerometer data showing vehicle setting off.

    Barometer. The barometer measures height change of the vehicle. This sensor consistently produced the highest cross-correlation coefficient, shown in Figure 6.

    Figure 6. Comparison of height profile over 3 days with minimums set to zero.

    Magnetometer. The magnetometer produced data with distinct spikes caused by various magnetic anomalies in the environment being travelled through. This can be seen in Figure 7 for the high-speed road.

    Figure 7. Vertical axis magnetic field profile for a high-speed road.

    Figure 8 is a zoomed-in section of the magnetometer data from the high-speed road in Figure 7. It shows correlation with an offset of approximately 44m between round 1 and round 3. This is mostly due to synchronization errors between the magnetometer counter and the GNSS receiver clock. This is the reason a second run of the road experiment was completed.

    Figure 8. Zoomed-in section of the vertical axis magnetic field experienced on a high-speed road.

    Microphone. The microphone was able to pick up clear signals when the vehicle was stationary, and the signal seems to be dependent on the speed of the vehicle. Figure 9 shows the profile from the microphone.

    Figure 9. Profile from microphone attached to axle.

    It may be possible to combine this data with the accelerometer or odometer data to develop a clearer picture of what sound is resulting directly from the road surface and what is speed related, although this still may not result in a useful feature for this study.

    Thermometer. Temperature can vary particularly in a rural environment, seen in Figure 10. Similarities are not consistent across environments as seen from cross-correlation values in Table 2 and are likely to change with the seasons and due to weather conditions.

    Figure 10. Temperature profile for rural roads.

    Light Sensor. Four light sensors were used in the experiment: upwards, forwards, left and right facing. Figure 11 shows the data from the upward-facing sensor on the high-speed road. There are distinct events where the light level drops. Many of these instances correspond to gantries (bridge -like structures spanning highways displaying speed limits and other information). These features could be treated as discrete, whereby the sharp dips in light level would be treated as momentary events. Some of the information would be lost in treating the ambient light as discrete, but it would make the feature more robust against changing light levels due to shadowing or cloud cover.

    If light is treated as a continuous feature, it can be seen in Table 2 that the cross correlation was inconsistent. This is partly due to the effects of changing light conditions. On the days with direct sunlight, the light sensor would reach its maximum intensity and be saturated. This can be seen in Figure 11, and this affects the cross-correlation coefficient calculated.

    Table 2. Cross-correlation coefficients for sensor outputs for the four road types.
    Figure 11. The upward-facing light sensor profile for the high-speed road in second experiment day two.

    Feature outcome. Thermometer data has been discounted as although it gave a cross-correlation coefficient of about 0.5 for the rural route, the other routes had lower cross-correlation values. Similarly, the microphone data had moderate success in high speed and rural environments but not in the other two routes. Therefore it will not be taken forward to the next phase although it could be used in the future if further processing was carried out on the data. As with the microphone, the light sensor had cross-correlation values greater than 0.5 in the rural and urban environments but had lower values in the other two. The success of this sensor is more reliant on the weather conditions than the environment type. At the current point this will not be brought forward to the next stage.

    The accelerometer (used to measure road texture) showed no correlation with cross-correlation coefficients of approximately zero (between 0.0 and 0.3). It was useful for use in dead reckoning, but does not illustrate road texture.

    The magnetometer and barometer showed the greatest potential for positioning with the highest cross-correlation values consistent over all the environments. These sensors are taken forward into phase 3.

    DISCRETE FEATURES

    A discrete feature is one where there are environmental events that occur at one position but can repeat multiple times along a route. The discrete feature can either be Boolean (an event occurs or does not) or it can be descriptive (different possible events or the strength of the event). Examples of discrete features include lamp posts, speed humps and shop signage.

    In this paper, the discrete feature that will be discussed will be street signs, although the techniques used are applicable to many discrete features. How the signs are identified will also not be discussed in detail in this paper; instead, focus will be on how a sequence of discrete features is used show consistency across a route.

    SCANNING METHOD

    This section will look at scanning one round to find the region that best matches a region from a different round. Figure 12 illustrates this technique.

    Figure 12. Diagram showing the principle used to scan for best match to a pre-set region.

    The test data is scanned through the reference data. Cross-correlation coefficients are calculated as the test data is scanned through. The aim is to locate the position of the test data using the reference data for which the position is already known. The output of this exercise gives a cross-correlation profile (cross correlation as a function of position).

    This profile can be treated similarly to a probability density distribution of position (although they are not the same) and so gives an idea of the probability of the position at each point in the test data.

    Results. Two rounds from the suburban route are shown in this section as an example of the results achieved with the scanning method. Figure 13 and Figure 14 show the cross-correlation profiles for magnetic field and height for day 3 rounds 1 and 2 on the suburban route respectively. The test data region chosen is centered at 1.6 km into the route. The test data region size was 125 m for 4.5 km reference data.

    It can be seen that the magnetic field has a number of peaks along the route. The peak with the highest cross-correlation coefficient is at the 1.6-km point (which is the correct position). For the height figure, there are many broad peaks at similar cross-correlation values approximately 700 m apart. The height peaks are broader than the magnetic peaks because the terrain height changes more slowly than the magnetic field.

    Ambiguities, Dead Reckoning. The two graphs in Figure 13 and Figure 14 show that there are ambiguities present in both of the features. The majority of the features will have some ambiguities along a route, and so it is important to develop a technique that could mitigate them. One way ambiguities could be mitigated is by using the information available from dead reckoning. The dead-reckoning solution will have a specific position error (which grows with time), and the ambiguities from the features can be reduced by only considering the candidate position within the dead reckoning position uncertainty bounds.

    COMBINING FEATURES

    The quality of position information that can be extracted from a particular feature type varies with location. Thus, a better position solution can be obtained if higher weighting is attributed to higher quality features. Factors that will need to be considered include the precision of position that can be extracted from a feature, the level of ambiguity (Are there multiple candidate positions?) and the reliability (how much measurements vary unpredictably with time).

    There are multiple ways to combine the scores from different features. Initially, there is the decision as to when in the position estimation process to combine the features. There are two ways to do this: Either combine the scores for each feature, or combine the position estimates for each sensor. The following subsections will describe a number of ways of combining the scores before estimating the position. It will be noted if these techniques could also be used to combine position estimates.

    Equal Weighting. A simple combination technique is for each feature score to have equal weighting. The equal weighting used earlier took the two scores and found the average. This way, no single feature will dominate the navigation solution. As the feature scores are not probabilities, the values are not self-weighting, therefore it cannot be presumed that that equal weighting would always provide an optimal position estimation.

    Test Data Weighting. This method takes a set of experimental data and empirically determines the weighting coefficients based on the best position solution in this test dataset. The test data would be used to maximize the score of the combined features using weighting at the correct position. This would have the benefit of using real data to determine the weighting, but its strength is based on how representative the test dataset is to the environments that the car will travel in.

    Environment Weighting. This would detect the environmental context and use this to select an appropriate set of weights. For example, the presence of many Wi-Fi sources would suggest a suburban or urban environment, while a vehicle speed of 31m/s (70 mph/113  km/h) would suggest that the vehicle is likely to be on a highway. Based on this knowledge, it would possible to use a specific weighting coefficient set is developed for that environmental context.

    Cross-Correlation Weighting. This weights each feature according to the characteristics of the cross-correlation coefficients profile obtained using the scanning method described earlier. This enables the weighing to adapt to the quality of the data. Figure 15 shows traits of a set of peaks that affect the confidence in the highest peak being the correct position.

    Figure 15. Weighting nomenclature of actual position shown as blue dotted line.

    Taking the uncertainty in the current position, only peaks that, for example, fall within 3 standard deviations would be evaluated. The characteristics of the tallest peaks compared with the others would be used to determine a measure of confidence for that feature.

    There will be more confidence in the tallest peak (h0) if there is a greater difference between its height and that of the other peaks within the uncertainty range (h1, 2, 3). In Table 3 this is height.

    Table 3. Cross-correlation profile weighting showing average distance from true position of the vehicle and the percentage of times the weighted scanning technique calculated the position within 100 m.

    The next factor is the number of peaks within the uncertainty range (No. Peaks). The more peaks, the less confidence that the correct peak has been chosen as the position estimate.

    The average cross-correlation coefficient within the uncertainty region (γ) would affect the confidence in the estimated position. If the average coefficient value (Av. CC) was similar to that of the highest peak, this suggests insufficient variation in the data being analyzed from that feature.

    Finally, the standard deviation could be used. Calculating how many standard deviation (Std Dev) the highest peak was from the mean could provide a weighting value.

    Each of these characteristics was looked at separately and compared against the benchmark of equal weighting using the scanning method comparing multiple pairs of rounds on different routes. It can be seen in Table 3 that the standard deviation from the mean provided the best weighting outcomes. To optimize the weighting algorithm, it may be that using a combination of these profile characteristics would provide the best position estimation.

    Figure 16 and Figure 17 show examples of cross-correlation profiles; they show high and low confidence respectively. Figure 16 is the cross correlation of data from day three, rounds two and three, on suburban roads. It has a few spaced out peaks over the full profile, and one of the peaks is clearly higher than the others. Figure 17 is the cross correlation of data from day two, round three, and day three, round three, from the high-speed road. It has many similar height peaks all around the value of 0.5.

    Figure 16. Good cross correlation profile; few spaced out peaks with one higher than all other peaks.
    Figure 17. Poor cross correlation profile; many low similar height peaks.

    CONCLUSION

    Environmental features have sufficient variability spatially and stability temporally for a database of features to be developed to create a map of the environment. This supports the hypothesis that it is feasible to map a space and then create a feature-mapping and navigation algorithm using a combination of environmental feature sensors, a GNSS receiver and sensors for dead reckoning.

    FUTURE WORK

    The next step of the project is to develop a feature-matching, mapping and navigation algorithm that incorporates inputs from the multiple sensors, a GNSS receiver, map-matching and sensors for dead reckoning. The algorithm will run collecting sensor data while GNSS receiver data is available, and store this in a database along with location stamps until called upon in times of GNSS receiver signal disturbance. The data from the road experiments will be used for a test database in developing the navigation system.

    ACKNOWLEDGMENTS

    Debbie Walter is funded by Engin-eering and Physical Sciences Research Council (EPSRC) and Terrafix ltd.

    The authors thank Paul Neesham for a method of manually recording street signs seen in video footage and Juliusz Romaniuk of Terrafix for advice and creating hardware that contained the sensors’ carrier frequencies.


    DEBBIE WALTER is a Ph.D. student at University College London in the Engineering Faculty’s Space Geodesy and Navigation Laboratory, and a software engineer at u-blox.

    PAUL GROVES is a lecturer at UCL, where he leads a program of research into robust positioning and navigation. He holds a Ph.D. in physics from the University of Oxford.

    BOB MASON is chief scientific officer and director of Terrafix Limited, holding a Ph.D. in communications and neuroscience from Keele University.

    JOE HARRISON is principal radio frequency design engineer at Terrafix Ltd.

    JOE WOODWARD is a software design engineer at Terrafix Ltd.

    PAUL WRIGHT is a development engineer with Terrafix Ltd., with doctoral degrees in physics and electronics.

  • ESA: Space debris enters ‘more feared exponential trend’

    ESA: Space debris enters ‘more feared exponential trend’

    Space Debris: Artist’s impression based on density data, shown at an exaggerated size to make objects visible. Image: ESA
    Space Debris: Artist’s impression based on density data, shown at an exaggerated size to make objects visible.
    Image: ESA

    In April, the European Space Agency (ESA) hosted the 7th European Conference on Space Debris at ESA’s Satellite Control Centre in Darmstadt, Germany. There, international experts discussed ways to head off the threat of space junk.

    ESA estimates there are roughly 5,000 objects larger than 1 meter, 20,000 objects over 10 centimeters and 750,000 “flying bullets” of around one centimeter.

    Risks of a collision are statistically remote, but “The growth in the number of fragments has deviated from the linear trend in the past and has entered into the more feared exponential trend,” warns Holger Krag, in charge of ESA’s space debris office.

    Many of the objects are traveling at enormous speed, up to 56,000 kilometers per hour, giving them the potential explosive force of a hand grenade on impact, said ESA experts.

    In the U.S., more than 16,000 objects are tracked and cataloged daily by crews in the Joint Space Operations Center at Vandenberg Air Force Base. Only 1,100 of the tracked items are functional spacecraft, including GPS satellites.

    Dealing with existing debris will call for innovative solutions — the purpose of the four-day summit, held every four years since 1993.

    “It’s clear to us that the issue of space debris is serious,” Jan Woerner, ESA chief, told the conference. “No country can stand or act alone.”

  • Panasonic collaborates with u-blox on RTK GNSS tablet

    Panasonic collaborates with u-blox on RTK GNSS tablet

    Panasonic Corporation, in collaboration with u-blox, has launched a tablet-using centimeter-level RTK GNSS technology.

    Toughpad, the newly born version of Panasonic’s professional grade notebooks family, is specifically designed for precision agriculture, machine control and robotic guidance applications in harsh environments and conditions. Embedded in the tablet is a u-blox NEO-M8 GNSS receiver module delivering high integrity and precision in demanding applications world-wide.

    The Toughpad FZ uses a u-blox NEO-M8 GNSS receiver module.
    The Toughpad FZ uses a u-blox NEO-M8 GNSS receiver module. Photo: Panasonic

    First successfully tested for collecting snow in Hokkaido, the Toughpad tablet uses Panasonic’s own satellite positioning technology combining a satellite radio receiver module, wireless WAN, and a single band real-time kinematic (RTK) GNSS receiver connected to an external antenna. The system enables high-precision positioning down to centimeter level in open sky conditions.

    “We needed a high quality, reliable and robust GNSS module for this tablet designed to be used in rugged environments,”  said Tetsuya Sakamoto, general manager, mobile solutions business division, development center at Panasonic Corporation. “The NEO-M8 from u-blox was therefore the right choice.”

    “It was very exciting to collaborate with a market leader such as Panasonic in developing a product that would guarantee precise positioning for a wide range of professional applications,” said Tesshu Naka, country manager at u-blox Japan. “This implementation will support the global expansion of the high precision market where u-blox is a key player.”

    Toughpad was first launched in Japan.

  • Autonomous vehicles drive innovation in the GNSS industry

    The May issue of GPS World carries these three expert opinions on the question: How are autonomous vehicles and V2V technologies driving innovation within the GNSS industry?

    Chaminda Basnyake
    Chaminda Basnyake

    Chaminda Basnyake
    Principal Engineer, Market Development,
    Locata Corporation

    We still have technical and cost versus performance challenges to meet the PNT needs of V2V and AV. Positioning and even timing expectations in deep urban areas are still not met reliably. As a result, ad hoc methods such as HD map-based nav — methods that work but are not scalable — have emerged. Innovations to deal with multipath, signal visibility and geometry are critical. Solutions that enable real-time mapping will be essential for scalable AV deployment.

     

     

    Curtis Hay
    Curtis Hay

    Curtis Hay
    Technical Fellow, GPS & Maps,
    General Motors

    Four key areas the commercial GNSS industry is pursuing include: low-cost, high-volume dual-frequency chipsets; broadly available PPP and network RTK corrections delivered either through mobile IP or satellite; precise maps for highways, urban centers and trunk roads that achieve 10-cm localization relative to WGS-84; and improved integrity monitoring and fault detection. The National Highway Transportation and Safety Administration also released a proposed rule-making with tight standards for GNSS performance: 1.5 meters, 1-sigma confidence.

    Jonathan Auld
    Jonathan Auld

    Jonathan Auld
    Director, Safety Critical Systems,
    NovAtel

    Unlike traditional GNSS applications, automotive positioning requires high-precision accuracy at extremely low cost and size. Most importantly, this performance must be achieved with high reliability while operating in the toughest environments.  Solving this positioning challenge is driving innovation in the system engineering of multi-frequency receivers and antennas along with extending performance through sensor fusion with lower cost devices.  Additionally, there is significant work in the area of safety and integrity for land-based applications.

    Here’s a preview of the V2V countdown article from the May issue, introduced by Chaminda Basnyake, an engineer at Locata Corporation:

    The U.S. Department of Transportation (USDOT) released a Notice of Proposed Rulemaking (NPRM) in December 2016 for the deployment of Dedicated Short Range Communications (DSRC)-based vehicle-to-vehicle (V2V) safety applications as part of the connected vehicles (CV) and automated vehicles (AV) initiative. If all goes well, this mean a V2V deployment mandate for new passenger vehicles likely starting in 2021 and reaching all new vehicles within 2–3 years.

    Standards required for V2V deployment were published in 2016 or before, including the V2V Minimum Performance Requirements SAE 2945/1, leading the way for commercial product development. The USDOT, which has been the catalyst behind V2V industry R&D starting from the automaker collaboration CAMP (Crash Avoidance Metrix Partnership) in 2001, is conducting CV Pilot programs in New York, Wyoming and Florida. These offer the opportunity for state DOTs, vendors and all other stakeholders to test the technology in real-life scenarios.
    Automotive OEMs have been developing this technology for more than a decade, and the NPRM is the beginning of a race toward integrating V2V to production vehicles. Deploying V2V technology requires the close cooperation of OEMs, their suppliers and many other stakeholders.

    This article captures the views of major players in the CV marketplace on expected deployment timelines, remaining challenges such as reliable positioning technology, integration with existing systems, and the implications on AV technology.

  • System of Systems: Brexit may oust UK from Galileo work

    Brexit May Oust U.K. from Galileo Work

    Participation of the United Kingdom space industry in Galileo may be in doubt as negotiations get underway on details of the U.K. withdrawal from the European Union (EU).

    European Commission officials signaled that they want to rely solely on producers within the European Union for the block’s major programs, citing security concerns such as the possible acquisition of a U.K. contractor by a company from a non-EU country such as China.

    In particular, officials are concerned about protecting the heavily encrypted, jam-resistant Public Regulated Service capability designed for government use that is reserved for EU member states and where U.K. industry has had a significant role.

    Surrey Satellite Technology Ltd., based in Guildford, England, but a subsidiary of France-based Airbus, built 22 navigation payloads for Europe’s Galileo satellite fleet.

    Other companies with U.K. interests that could be affected include Qinetiq, CGI, Airbus and Scisys.


    Galileo SAR Service Launched

    Galileo’s Search And Rescue (SAR) service became officially operational with a public launch on April 6, as part of the COSPAS-SARSAT network for detecting and locating emergency beacons activated by aircraft, ships and hikers. According to the European Commission, Galileo SAR will help reduce the detection delay of a distress signal from up to several hours to 10 minutes.

    At sea, this makes SAR rescue operations easier thanks to a narrowed search box, since the vessel in distress has less time to drift. On land, acquisition of a precise position enables rescue teams to more quickly reach the operation zone and assist the victims. In the air, Galileo contributes to fulfilling International Civil Aviation Organization (ICAO) requirements for implementing the next-generation emergency management system Global Aeronautical Distress and Safety System (GADSS).

    SAR transponders on Galileo satellites can pick up signals emitted from 406-MHz distress beacons anywhere in the service coverage area and transmit this information to the dedicated ground stations, the Medium-Earth Orbit Local User Terminals (MEOLUTs). The SAR/Galileo infrastructure is interoperable with GPS and GLONASS SAR transponders.
    Once the beacon is located by the MEOLUTs, the location data is sent to the COSPAS-SARSAT mission control center, which distributes it to the relevant rescue centers. These then coordinate the required rescue efforts.

    Galileo provides a ground segment coverage of 40 million square kilometers over Europe as a contribution to MEOSAR global coverage. Galileo SAR service is one of the three services launched in December 2016 with the Initial Services. The SAR service represented 1 percent of total Galileo program costs, but should result in thousands of lives being saved, said the European Commission.


    Pile of Studies Produced Not a Lot

    Gen. Shelton
    Headshot: Gen. Shelton

    Testifying before a joint hearing of the House Homeland Security Committee and House Armed Services strategic forces subcommittee on March 29, Retired Gen. William Shelton, the former head of Air Force Space Command, warned that the U.S. needs to take action to protect GPS very soon.

    He cited demonstrated ability by the Chinese government in 2007 to destroy a satellite in orbit, and improved signal jamming and cyber attack capabilities against ground control systems. The U.S. is unprepared to meet those threats, he said.

    “Here we are 10 years later and we don’t really have a lot to show but a pile of studies,” Shelton said. “We’ve been part of this ‘one more study’ kind of attitude. ‘Well, that may not be the perfect answer, so let’s just do one more study’ and meanwhile time marches on. Satellites have fixed lifetimes, and you need to plan for the death of the satellite. A decision not to move forward is a de facto decision to maintain the status quo with no protection.”

    Shelton stated that space research and development is at a 30-year low, with 15–40 percent of R&D funds taken by management services and technical assistance rather than actual research and development.

    “The executive branch and the legislative branch could get together and agree on a strategy and a way forward and then execute … I don’t see any other way. There has to be some broad agreement here in the whole of government as we move forward.”


    June Launch in japan for QZSS Michibiki 2

    QZSS’s second satellite is scheduled for launch in June. Once completed, the Quasi-Zenith Satellite System will be a satellite augmentation system for GPS over Japan and other parts of the Pacific region.

    Michibiki 2 will be launched by the Japan Aerospace Exploration Agency (JAXA), with a launch window planned for June 1–30. The system’s first Michibiki satellite was launched in September 2010.


    OCX Back on Track

    OCX, the next-generation ground control system for GPS, is back on track following a 2016 government contract breach that prompted the Air Force to work with Raytheon to revise OCX’s budget and schedule, according to the company.

    Raytheon implemented a series of corrective actions through 2015 and 2016 to get the delayed program on a firm timeframe for completion. Coding on OCX was about 80 percent complete in late March, according to the company.

    Raytheon completed a re-baselining on OCX in March, setting up a new timeline for completion. Current delivery for the full system is planned for December 2020.

    DevOps. The OCX team reduced development cycle times to create more efficient software development by using a commercial best practice called DevOps, which adds more automation into coding and testing, and breaks coding down into units rather than focusing on the need to finish the complete system all at once.

    A subset of OCX, the Launch and Checkout System for GPS satellites is undergoing testing at Schriever Air Force Base in Colorado. Raytheon expects to complete testing and deliver the system by late September or early October.


    EGNOS Refreshes

    The geosynchrous Earth-orbit (GEO) satellites broadcasting EGNOS messages changed in March. PRN 123 was introduced in the operational platform, and PRN 136 was moved from the operational platform to the test platform.

    Regional aviation in the dense European air traffic system is a key market segment for EGNOS, according to Gian Gherardo Calini, the European GNSS Agency’s head of market development. More than 440 EGNOS-based approaches are available at nearly 220 airports across Europe. These figures are expected to dramatically increase in the coming years.

    A proposal from the European Aviation Safety Agency recommends that air ANSPs and aerodrome operators implement Performance Based Navigation (PBN) approach procedures with vertical guidance (APV), such as EGNOS LPVs, at all non-precision instrument runway ends by 2020.


    Second GPS III Launch Contracted

    The U.S. Air Force has awarded a second GPS III satellite launch contract to SpaceX.

    According to the $96.5 million agreement, the company will provide GPS III launch vehicle production, mission integration, launch operations, spaceflight worthiness and mission-unique activities. Work is expected to be complete by April 30, 2019.

    An earlier SpaceX launch contract, worth $82.7 million, calls for orbiting a GPS satellite aboard a Falcon 9 rocket in May 2018.