Category: Applications

  • Launchpad: RTK modules, inertial sensors

    Launchpad: RTK modules, inertial sensors

    OEM

    RTK and Heading Module

    Positioning and attitude determination

    Image: Unicore
    Image: Unicore

    The UM442 can simultaneously track GPS, BDS, GLONASS and Galileo. It also supports SBAS and QZSS. It uses Uncore’s new-generation Nebulas II chip and UGypsophila real-time kinematic (RTK) algorithm. Based on high-performance data-sharing technology and the simplified operation system of the Nebulas II chip, the UGypsophila RTK algorithm dramatically optimizes matrix processing, enabling the UM442 to track more satellites and shorten the initialization time to 5 seconds.

    Unicore Communications, www.unicorecomm.com

    Inertial sensors

    Designed for dynamic inclination and positioning

    Image: Lord Sensing
    Image: Lord Sensing

    The MV5-AR inertial sensors are designed for off-highway and military vehicles, marine and mobile robot applications, and the autonomous vehicle market. The rugged, compact sensors use LORD’s fifth-generation high-performance industrial-grade solid-state six-degrees-of-freedom (6-DOF) micro-electromechanical accelerometer and gyro inertial sensor technology. Successfully deployed on ground robots and heavy machinery, applications also include autosteer and terrain compensation; dynamic incline detection (roll, pitch, rotation); vehicle stability and leveling; platform control, alignment and stabilization; operator feedback; and precision navigation. The compact and rugged reinforced housing is fully sealed for immersion and pressure wash. Each sensor is calibrated and temperature compensated.

    LORD Sensing Microstrain, microstrain.com

    BeiDou upgrade

    GNSS simulators ready for 2020

    Spirent's GSS7000 test system. (Image: Spirent)
    Spirent’s GSS7000 test system. (Image: Spirent)

    BeiDou Phase 3 signals are now available on Spirent GNSS RF constellation simulators GSS7000 and GSS9000 — existing users can obtain the software upgrade by contacting Spirent. Phase 3 of the Chinese BeiDou system will extend its coverage from Asia to the entire world, providing receiver developers and integrators with additional GNSS signals to make positioning, navigation and timing systems more accurate, and help to support new applications, such as autonomous vehicles. Customers can test their designs before the system is fully operational in 2020.

    Spirent Communications, www.spirent.com

    High-precision module

    Based on u-blox F9 technology

    Image: u-blox
    Image: u-blox

    The ZED-F9P multi-band GNSS module has integrated multi-band real-time kinematic (RTK) technology for machine control, ground robotic vehicles and high-precision unmanned aerial vehicles applications. It measures 22 x 17 x 2.4 millimeters and uses technology from the u‑blox F9 platform to deliver robust high-precision positioning performance in seconds. The ZED-F9P is a mass-market multi-band receiver that concurrently uses GNSS signals from all four GNSS constellations (GPS, GLONASS, Galileo and BeiDou). Combining GNSS signals from multiple frequency bands (L1/L2/L5) and RTK technology lets the ZED‑F9P achieve centimeter-level accuracy in seconds.

    u-blox, u-blox.com

    Chip-scale atomic clock

    Ready for space

    Image: Microsemi
    Image: Microsemi

    The SA.45s Commercial Space Chip-Scale Atomic Clock (CSAC) is a commercially available radiation-tolerant CSAC suitable for low Earth orbit (LEO) applications. The device provides the accuracy and stability of atomic clock technology while achieving significant breakthroughs in reduced size, weight and power consumption. It provides excellent drift performance and built-in 1 pulse per second (PPS) input for GPS disciplining, making the device well-suited for holdover applications. Commercial and research space applications include satellite timing and frequency control; satellite cross linking; assured position, navigation and timing; and Earth observation.

    Microsemi, microsemi.com


    SURVEY & MAPPING

    Radio modem

    For heavy-duty RTK applications

    Image: Harxon
    Image: Harxon

    The long-range, power-efficient eRadio is designed to support high-precision GNSS real-time kinematic (RTK) applications in surveying and precision agriculture. It is enabled with intelligent serial baud rate identification for different RTK devices. It can automatically identify RTK serial baud rate with a radio data cable and provide a plug-and-play form for easy connection between the eRadio and RTK. With its high transmitting power (5-35 Watts), transmission data can be up to 19200 bps/s over a connection distance of 50–80 kilometers. It can work as either a base or repeater with other Harxon radio modems in challenging environments.

    Harxon, harxon.com

    GNSS receiver

    Wireless communication with any Android or Windows terminal

    Image: SXblue/Geneq
    Image: SXblue/Geneq

    The SXblue Premier GNSS receiver is available in a submetric version (GNSS) or centimetric version (RTK). It is equipped with Pacific Crest Maxwell 6 Trimble technology with BD910 (GNSS version) and BD930 (RTK version) OEM boards, delivering 220 channels to acquire and track GNSS signals from all constellations in view. It makes effective use of GPS, GLONASS, Galileo, BeiDou, QZSS and SBAS signals for precise positioning.

    SXblue, www.sxbluegps.com

    Smart antennas

    With integrated Atlas L-band

    Image: Hemisphere GNSS
    Image: Hemisphere GNSS

    The single-frequency, multi-GNSS Vector V123 and V133 all-in-one smart antennas are multi-GNSS compass systems using GPS, GLONASS, BeiDou, Galileo and QZSS for simultaneous tracking for heading, position, heave, pitch and roll. Both support NMEA 0183 and NMEA 2000. The V123 and V133 thrive in radar/ARPA, AIS, ECDIS, side-scan survey, multi- and single-beam surveys, dredging and general navigation applications.

    Hemisphere GNSS, hemispheregnss.com


    TRANSPORTATION

    Mobile GPS tracker

    For tracking vehicles, assets and people

    Images: Trak4
    Images: Trak4

    The Trak4 provides GPS tracking with cell-trilateration fallback. Ping rates can be selected from every two minutes to once a day, with email and text alerts provided for geozone entry and exit or if the high-capacity rechargable battery is low (the battery runs up to 12 months on a single charge.) The Trak4 is designed for tracking vehicles, assets and inventory; it can also be used to track people such as the elderly. Indoor/outdoor weatherproofing allows “anywhere” mounting.

    Trak-4, trak-4.com

    Multi-GNSS antennas

    For positive train control

    Image: PCTEL
    Image: PCTEL

    PCTEL’s multi-GNSS L1/L2/L5 antennas combine aerospace-level precision with global satellite compatibility in a highly durable package. They enable critical applications including vehicular automation, 5G network timing synchronization and Positive Train Control (PTC) systems. The antennas increase the accuracy of timing and location information by providing simultaneous access to multiple GNSS signals across multiple frequency bands. The antennas support all relevant GPS, GLONASS, BeiDou and Galileo frequencies with excellent multipath mitigation and high out-of-band rejection for greater signal clarity. Their robust AAR and IP67-compliant design makes them suitable for years of use on railways and in other harsh real-world environments.

    PCTEL, pctel.com

    Off-Road GPS

    New range for walking and cycling

    Image: Ordnance Survey
    Image: Ordnance Survey

    Four new GPS handhelds are designed for off-road use, with safety in mind. All four of the OS GPS models have a built-in SIM card with access to the SeeMe subscription-based service and its safety features. With I.C.E (In Case of Emergency), users can send emergency alerts with exact coordinates to family and friends directly from the OS GPS. Live Tracking enables the user to be locatable at all times, sharing location and performance data with up to 20 friends in real time. Aventura, the most advanced navigation device, can be used in all weather conditions.

    Ordnance Survey, ordnancesurvey.co.uk

    Fleet management

    Real-time GPS fleet tracking

    Image: Zubie
    Image: Zubie

    Zubie Fleet Connect provides real-time GPS fleet tracking, driver check-in and performance reports, and vehicle health alerts. The monitoring and reporting service lets managers of fleets from 2 to 5,000 vehicles optimize business on the road. Wi-Fi connection to the cloud delivers important information about the health and performance of the vehicle, enhancing driver safety. Zubie also works with large enterprises to develop custom data flows and access driving data that can be used to analyze driving patterns, spot geographical trends in activity, or improve fleet asset management based on vehicle wear and tear.

    Zubie, zubie.com

    Multi-sensor payload

    Utility inspections with manned helicopters

    Image: Sharper Shape
    Image: Sharper Shape

    The Heliscope 2.0 provides onboard data collection with speed, efficiency and productivity improvements for the utility inspection industry. It provides a solution for operations over greater distances or in harsher environments than drones can accommodate The system integrates multiple sensor systems into a single, lightweight helicopter payload, capable of simultaneously collecting a range of data types required for utility maintenance and vegetation management inspections. Deployment enables optimized inspection and maintenance schedules, offering potential cost savings in those operational activities by as much as 50 percent. The Heliscope 2.0 has flexible mounting configurations and the ability to adapt for mounting on many different helicopter types.

    Sharper Shape, sharpershape.com


    UAV

    Survey system

    Accurate, quick aerial surveys

    Image: Aibot
    Image: Aibot

    Based on DJI’s M600 Pro platform, the Leica Aibot system is designed to rapidly and autonomously enable digitizing of critical infrastructure. It enables users to get a complete data set quickly with a user-friendly interface. Using Leica Infinity for point-cloud, digital surface model and orthophoto generation enables surveyors to process and visualize aerial data. For construction projects, Aibot provides access to critical information to perform volume calculations and monitor site progress. Users can see high-definition imagery and 3D mapping of the site and document progress. The UAV data can be combined with other survey technologies such as GPS for a more complete set of information.

    Leica Geosystems, leica-geosystems.com

    UAV antenna

    GPS L1/L2 + GLONASS G1/G2

    Image: Tallysman
    Image: Tallysman

    Two lightweight, compact antennas are designed for UAVs with a low aerodynamic profile. Antenna model TW1829 is for original equipment manufacturers (OEMs), and model TW8829 is a housed version. Accutenna technology provides high-level rejection of multipath signals, a phase linear response and tight phase-center variations. Pre-filters prevent saturation of the front-end low noise amplifier by strong near frequency and harmonic signals.

    Tallysman, www.tallysman.com

    GNSS Antenna

    Multi-GNSS, multi-frequency four-heliX UAV antenna

    Image: Hemisphere GNSS
    Image: Hemisphere GNSS

    The HA32 high-performance antenna supports GPS, GLONASS, Galileo, BeiDou and Hemisphere’s Atlas L-band correction service. It is designed for UAVs, geographic information systems (GIS), surveying, real-time kinematic (RTK) and other applications requiring high-precision positioning and navigation. The HA32 is built on a proprietary four-helix antenna technology that provides superior filtering and anti-jamming performance with features such as a low noise figure of 2.0 dB (typical) and up to 30-dB gain (typical). Suitable for most outdoor and harsh operating environments, the HA32 antenna is sealed in a durable and ruggedized IP67-rated. The lightweight (40 g, typical), compact form factor (40 x 75 mm) makes it resistant to wind when on UAVs.

    Hemisphere GNSS, hemispheregnss.com

  • The surveyor and artificial intelligence: A look ahead

    In the not-too-distant future, the following scenario may take place.

    Image: Stockvault
    Image: Stockvault

    A corporation owns an improved property in a large metropolitan city and has decided to sell it to a prospective buyer. Through a series of electronic messages and high-tech operations, the seller, buyer, their respective counsels, lending institutions and a title company are provided with documentation stating the condition of the site along with holograms and 3D digital models worthy of a science-fiction movie. In a matter of minutes, the deal is closed with monies and titles silently swapping places out in the ether.

    Behind the scenes, the surveyor is a big part of this transaction. But how will the operation of the land title survey look in the future? Like everything else, artificial intelligence (A.I.) and blockchain technology will play a substantial role in surveying. I don’t profess to be the next Carnac the Magnificent, but it could look like this…

    HOW IT ALL STARTS

    The seller contacts their corporate attorneys to begin the contractual process. Requirements for the sale include acceptable and insurable conditions of the site and a clean title policy from a title insurance company, so the latest land title survey requirements will be held for site and title review. Once the seller and buyer are committed to a sale of the subject property, a blockchain is established in a transactional database to track every step of the sale.

    Image: GSA
    Image: GSA

    The attorney will consult with “Sheldon,” an artificial intelligence system built by a leading e-commerce company and designed to assist with business-to-business commerce. Sheldon will be used to secure the services of a land surveyor for the transaction. By researching available consultants based upon the information for the parcel contained within the blockchain, Sheldon contacts firms that could meet the criteria for this part of the transaction.

    Once an appropriate firm is chosen by Sheldon, the data for the survey within the blockchain is uploaded to “Thomas,” a digital assistant designed specifically for surveyors. Thomas works with Sheldon and the blockchain to formalize an agreement, secure the necessary insurance requirements, and finalize a payment schedule for services.

    ENTER THE SURVEYOR

    Once the project is secured, Thomas creates a project file, downloads current satellite images, GIS data (including parcel, building and utility information), and recorded documents for the subject parcel. Among the information is parcel data for the project site. This data is based upon historical land surveys and converted into an accurate dataset in which most of the property and land corners are now included in the GIS database. All corners within the database have been installed or upgraded to contain an RFID chip imbedded within the top of the marker.

    Image: NOAA
    Image: NOAA

    These GIS databases also take advantage of ongoing advancements of the North American Terrestrial Reference Frame of 2022 (NATRF2022). Beyond the initial implementation, the National Geodetic Survey has incorporated additional precision gained by improved L5 satellite reception and other nations’ satellite constellations in sub-centimeter location with most survey-grade receivers. Thomas compiles all site data into a comprehensive package for submission to the surveyor.

    Because of the advancements with instrumentation and sensors in locating improvements both above and below the surface of the ground, the latest land title survey standard has moved all optional Table A items into required information to be provided on the plat. The standard also now requires a drainage analysis to be prepared to determine how the subject property relates to the adjacent parcels.

    Thomas reviews the current backlog of project managers and assigns/transmits the project to the first available team. The chosen survey project manager receives the project information and creates an Ethereum blockchain file to work with the master blockchain and begin the survey process. By creating additional survey programming working in conjunction with the project blockchain, all parties involved in the transaction can monitor progress every step of the way.

    The first responsibility of the survey PM is to work with Thomas to evaluate the existing data available for the project location. Current conditions from satellite imagery, improvement and utility information from existing governmental GIS databases, and parcel/easement information from recorded document sources are used to determine flight paths for UAVs utilizing multiple sensors, avoiding substantial obstacles. This process will also establish areas to be surveyed/verified by mobile methods where aerial data cannot be obtained.

    All available information is processed by Thomas to establish the most efficient routes and methods of data collection for the parcel through software designed to compile and review spatial datasets. This software is specifically designed to review existing information for potential conflicts in flight and on-the-ground obstacles. Once completed, a flight plan for the UAV and route plan for the autonomous mobile vehicle will be reported with missed areas identified for manual data collection.

    FIELD WORK ON STEROIDS

    When the time arrives for field work to begin, a technician is dispatched in an autonomous electric truck pre-programmed to go directly to the site. The truck is loaded with various survey-grade instruments and equipment (all GNSS equipped): vertical take-off fixed wing and multi-rotor UAVs (both with lidar, photo, hyper-spectral, and GPR sensors), an autonomous mobile ground robot (with GPR/lidar sensors), and an RFID reader for boundary location.

    The technician works with the equipment through a universal tablet computer controlling both aerial and ground data collection simultaneously, depicting the progress of the work in real time. This gives the technician time to locate the boundary points with the handheld GNSS receiver/RFID reader to verify the limits of the property.

    Once the autonomous work is finished, the technician processes the data on site, and software compares collection coverage versus the initial site review. When processing is complete, the technician will utilize a handheld GNSS receiver with lidar sensor to obtain remote areas not collected by the other methods.

    The remaining data is compiled with autonomous data and re-analyzed for overall coverage and approved by the software for completeness. Once the computer determines everything has been collected, the technician checks the complete box and leaves the site.

    OFFICE WORK AND WRAP-UP

    The final field data is uploaded to cloud servers as the technician leaves the site and the survey PM is notified by electronic message of the field task completion. Thomas, the digital surveying assistant, takes the lead and begins the final processing. The data is reviewed for completeness, parsed for any anomalies within the downloads, and compiled into one database for building a 3D model of the site.

    Photo and lidar data are compared for accuracy, utilities are verified against existing records and easements, and building characteristics are matched against governmental records for zoning code compliance.

     

    Once this analysis is complete, the final drafting takes place to create the final deliverable. While the data within the model contains attributes of each entity, labels are placed interactively throughout the site to help depict the site information. This model is also suitable for use by architects and planners to utilize in their B.I.M. design programs, so the quality in the modeling output is top notch.

    The final deliverable contains an overall report documenting site conditions, drainage characteristics and physical conditions of various entities. This report will also detail potential site encroachments, possible drainage issues, and zoning/parking red flags. Thomas will report back to the survey PM that all final checks have been made and deliverables made for submittal to the client, leaving only the final transmittal left to do.

    Once the deliverable is received by the client, Sheldon (the B2B automated assistant) recognizes the delivery and begins the process of payment to the surveyor. With standardized surveys, automated assistant/analyzation systems, and trackable processes through blockchain, the client gets a quality product at a market rate in an acceptable timeframe and the surveyor gets paid in a reasonable period.

    THEN WE ALL WOKE UP TO REALITY…

    Maybe this fictional situation for land surveyors won’t be a reality in my lifetime, but I’m not willing to bet against it. I look back at my short 30+ year career and still marvel at the technological advancements yet I acknowledge we are still turning a corner in computing power (see May’s column). I remember the introduction of laser scanners and lidar sensors as future data-collector saviors, gathering multitudes of precise and accurate data much faster than any mortal. Now we have UAVs that can soar above us with little interference and provide images and data at a reasonable cost, so technology does benefit us.

    But what about data that is automated to the point it is beyond the control of the surveyor? And what does this do to our shrinking surveying workforce?

    Some may say it is a godsend on both accounts. I personally won’t turn out a product or survey in which I don’t have a good understanding of what the data represents or how it was collected; that violates a code of ethics of practicing beyond my expertise. I also don’t think automation will eliminate our technicians, but the surveying profession will need to provide adequate training for our next generation.

    “I’M SORRY, DAVE. I’M AFRAID I CAN’T DO THAT.”

    We live in a world in which so many things are automated (Alexa, Siri and “Hey, Google”) to assist us with even the most mundane of tasks. Amazon recently introduced a store where the customer doesn’t stop at a cashier; just grab the items off the shelf and walk out. Apple introduced its latest iPhone that opens by recognizing your face. Automation is here to stay, whether we like it or not.

    Image: MGM
    Image: MGM

    An article by the Pew Research Center (“Automation is Everyday Life“) described in detail the amount of anxiety that automation instilled in Americans. Many felt that while there are opportunities to increase productivity and profitability in many sectors, that will be offset by lost jobs replaced by automation. Others were also troubled by automation becoming more prevalent in medical treatment of senior citizens.

    For many, the thought of automation isn’t nearly as scary as the concept of “artificial intelligence.” While most of the processes involve machine learning (ML) and refining results based upon increasing datasets, computing power is increasing and introducing new methods including “deep learning.” The algorithms being produced by deep learning through neural networks are making smarter decisions as they use larger and more complicated datasets.

    From a June article for The Atlantic, Henry Kissinger (yes, that Henry Kissinger) offered these thoughts on A.I.:

    Henry Kissinger (Photo: The Atlantic)
    Henry Kissinger (Photo: The Atlantic)

    Ultimately, the term artificial intelligence may be a misnomer. To be sure, these machines can solve complex, seemingly abstract problems that had previously yielded only to human cognition. But what they do uniquely is not thinking as heretofore conceived and experienced. Rather, it is unprecedented memorization and computation. Because of its inherent superiority in these fields, AI is likely to win any game assigned to it. But for our purposes as humans, the games are not only about winning; they are about thinking. By treating a mathematical process as if it were a thought process, and either trying to mimic that process ourselves or merely accepting the results, we are in danger of losing the capacity that has been the essence of human cognition. (June 2018)

    He also makes a strong statement that the United States needs to develop a national vision for AI like other countries (i.e. China, Russia, India) to stay competitive in computing power.

    TRANSLATING ARTIFICIAL INTELLIGENCE INTO SURVEYING

    The point of this discussion wasn’t to be “doom and gloom” of technology. I look forward to enjoying many of the advancements of AI and blockchain advancements. Many of the advantages of both technologies have not been brought to the surveying forefront yet, but it will only be a matter of time.

    My one big fear to automation attempting to overtake and regulate some functions of surveying leads back to boundary determination and the increasing use of holding technology/mathematics over monumentation, hence Kissinger’s comment regarding human cognition. The rules of construction will always hold true in my boundary analysis until there is a time and place where all parcels (original and retracement) are created in a mathematical vacuum.

    I also don’t see a timeframe yet that reduces the amount of measurement error between survey practitioners utilizing differing methods and technologies. Survey equipment manufacturers are still refining ways to get more precision from their GNSS receivers, yet still put them on a pole with a bullseye bubble that needs constant checking. Even tribrachs and total stations aren’t checked as often as recommended, but we always seem willing to argue over who measures better.

    Until we get more consistent in our overall measuring as a profession, I’ll hold off on worrying about artificial intelligence taking over.

    In the meantime, let’s back off calling a corner monument off by 0.03’ just yet. Let’s hope that when A.I. does become more prevalent, the surveying profession will have its collective heads wrapped around our own intellect as well.

  • Innovation: Instantaneous centimeter-level multi-frequency precise point positioning

    Innovation: Instantaneous centimeter-level multi-frequency precise point positioning

    More Is Better

    The technique of precise point positioning (PPP) is making inroads in the positioning industry. However, one issue hampering its more widespread adoption is the convergence time required for the carrier-phase ambiguities to be fully resolved so that the 10-centimeter-accuracy threshold can be surpassed. By using a multi-system, multi-carrier-frequency approach, instantaneous centimeter-level PPP can be achieved.

    Innovation Insights with Richard Langley
    Innovation Insights with Richard Langley

    CARRIER PHASE. It’s one of the two main measurement types or observables used by all GNSS receivers. Fundamentally, it is the instantaneous phase of a GNSS signal’s carrier, an electromagnetic wave of fixed amplitude and frequency (when transmitted), which is (optionally) modulated by a ranging code and a navigation message. It’s measured in radians, degrees or cycles and can be converted to a biased measure of the range between the receiver and satellite antennas by multiplying the value in cycles by the wavelength of the carrier in meters. The other GNSS observable is the phase of the ranging code. Initially measured in code chips or units of time, it is converted to a biased measure of the receiver-satellite range by multiplying it by the speed of light. This value is then typically called the code measurement or the pseudorange. The carrier phase is much more precise than the pseudorange by something like a factor of 100. So, while pseudoranges can be measured to a precision of tens of centimeters, carrier phases can be measured to millimeters or better.

    Most GNSS receivers use pseudorange measurements to determine their position. In fact, this is the standard approach to satellite-based positioning that was introduced by GPS in the 1970s. While carrier-phase measurements, or rather their time-rate-of-change, are used for precise velocity determination, it wasn’t originally recognized that carrier-phase measurements could be used for position determination, too. The problem with the carrier phase as a measure of the range is that it has an initially unknown and potentially huge bias. This is because when a receiver starts tracking a signal’s carrier, it doesn’t know the exact number of cycles of the carrier wave stretching all the way from the satellite to the receiver. Hence, carrier-phase measurements are ambiguous as a result of this initial bias. If this ambiguity can be resolved, then carrier-phase measurements can be used for very precise positioning — positioning at the centimeter level or even better.

    Over the years, various techniques have been developed to use carrier-phase measurements for positioning, most notably in differential positioning where one or more reference stations are used to position a user receiver or rover. But the technique of precise point positioning, which only requires direct uncombined measurements from the user receiver, is being actively developed and is making inroads in the positioning industry. However, one continuing issue hampering its more widespread adoption is the convergence time required for the carrier-phase ambiguities to be fully resolved so that the 10-centimeter-accuracy threshold can be surpassed. Research by the authors of this month’s article shows that by using a multi-system, multi-carrier-frequency approach, instantaneous centimeter-level PPP can be achieved. They call their technique Optimal Estimation using Uncombined Four-frequency Signals or OEUFS for short. Those of us who remember a smattering of our high-school French will agree that it is quite an eggceptional technique.


    Instantaneous centimeter-level positioning used to be synonymous with the single-baseline real-time kinematic (RTK) technique. The rover was constrained to be within a few kilometers of the base station to ensure that errors would remain spatially correlated. Modeling error sources using a regional network of stations later allowed users to retain this level of accuracy within the area of network coverage. A global network of reference stations enabled the determination of precise satellite orbit and clock products, paving the way for precise point positioning (PPP).

    Global centimeter-level accuracy can be achieved with PPP, at the cost of a long convergence time, often measured in hours. An additional layer of corrections, including satellite code (pseudorange) and carrier-phase biases, has enabled PPP with ambiguity resolution (PPP-AR). While an improvement in convergence time can be obtained, PPP-AR still cannot compete with RTK or network RTK in terms of time to first fix. Only by providing precise atmospheric information to PPP users, in the form of zenith tropospheric and slant ionospheric delays, can instantaneous centimeter-level accuracy be obtained. This approach led to a unification of PPP and RTK, often referred to as PPP-RTK. This scalable approach has allowed PPP users to obtain accurate positioning globally, while achieving rapid convergence when located within the regional reference network boundaries.

    The modernization of GNSS includes satellites transmitting signals on multiple frequencies. The 12 GPS Block IIF satellites currently in orbit already broadcast the L5 signal, and all Galileo and BeiDou satellites launched so far have triple-frequency capabilities. In November 2017, the BeiDou constellation began a new phase of its development with the launch of the Beidou-3S satellites offering new signals compatible with the GPS L1/L5 bands. In March 2018, the European Union decided to open its Commercial Service (CS), offering at no cost the signal and correction stream for the “CS high accuracy” service. As a result, the E6 signal is now available on 14 satellites and can be tracked by modern GNSS receivers. FIGURE 1 depicts the frequency plan of the open GNSS signals, including these last evolutions, as of May 2018.

    FIGURE 1. GNSS open signals (as of May 2018). (Image: authors)
    FIGURE 1. GNSS open signals (as of May 2018). (Image: authors)

    With three or more frequencies, a series of widelane ambiguities can be resolved in a cascading scheme. These unambiguous widelane signals can be used to form an ionosphere-free phase measurement with lower noise than code measurements, but typically still at the decimeter level. The availability of the Galileo E6 signal provides a significant step forward for PPP-AR, permitting instantaneous convergence. As a result of frequency separation, unambiguous widelane signals have low noise characteristics, which further benefits the resolution of the whole set of ambiguities. The strategy used in our study is a generalization of the widelaning technique, based on uncombined observations, which we describe as Optimal Estimation using Uncombined Four-frequency Signals (OEUFS).

    We explain how instantaneous centimeter-level PPP is achieved by first analyzing the precision of the ambiguity and range parameters in the single-satellite case. The network estimation of the uncombined Galileo phase biases is then described, followed by epoch-by-epoch and 5-minute PPP solutions based on OEUFS.

    SINGLE-SATELLITE PROCESSING

    To get a first grasp of the benefits of using four frequencies, we first look into single-satellite data. The aim of this analysis is twofold: first, to evaluate the ability of fixing linear combinations of ambiguities and, second, to determine the resulting precision of the unbiased range estimate once these ambiguities are fixed.

    Uncombined observations on four Galileo frequencies (E1, E5a, E5b and E6) are used to model an ionosphere-free range, a slant ionospheric delay, and four carrier-phase ambiguities. It should be noted that measurements on a fifth frequency (E5) are available but, due to the proximity of E5 with respect to E5a and E5b, its impact was found to be almost negligible. We will, therefore, restrict ourselves to the four-frequency case. Only two code observations are included in the model — in this case E1 and E5a — since adding other frequencies would require the estimation of differential code biases. Thus, for single-epoch processing, additional code measurements would not usefully contribute to the solution. Observable standard deviations are set to 3 millimeters and 30 centimeters for carrier phase and code, respectively. An analysis using a zero-length baseline revealed that weak correlations do exist between signals, and multipath effects could further increase this correlation. Although taking into consideration correlations among observations would lead to a more realistic covariance matrix, these correlations were neglected in producing the results shown in this article. This is justified by the fact that correlation coefficients are usually not available, especially for real-time processing.

    The above-mentioned model was inverted in a least-squares adjustment to perform covariance analysis. While the Least‐squares AMBiguity Decorrelation Adjustment (LAMBDA) method can be used for the identification of optimal linear combinations of ambiguities, the classic widelane ambiguities were found to perform equally well and were used in our work to simplify the exposition. When no ambiguities are fixed, the quality of the solution is driven by the noise on the code observations. TABLE 1 shows that, in this case, the receiver-satellite range parameter can be estimated with a precision of 0.776 meters. This value can be translated into a 3D-position precision by using the position dilution of precision (PDOP) factor. As a rule of thumb, if the PDOP for all satellites in view is equal to 1, the resulting 3D precision should be around 78 centimeters.

    TABLE 1. Precision of parameters in the Galileo four-frequency (E1, E5a, E5b, E6) single-satellite case.

    Even though the range is not very precise, forming the E5a-E5b widelane ambiguity from the estimated uncombined ambiguities gives a precision of 0.034 cycles, which can be reliably fixed due to the very long wavelength of the signal (9.77 meters). Adding this constraint to the system allows us to estimate the E5b-E6 widelane ambiguity with a standard deviation of 0.041 cycles (although it could also have been fixed initially). Interestingly, fixing both extra-widelane ambiguities does not significantly improve the precision of the range information derived from a single satellite. Nevertheless, due to correlations among ambiguity parameters, a precision of 0.183 cycles is now obtained for the E1-E5a widelane, an improvement of approximately 35 percent over the initial estimate.

    While the E1-E5a ambiguity is not sufficiently precise for reliable instantaneous fixing based on single-satellite data from one epoch, using the geometric information from several satellites will enable single-epoch ambiguity resolution for three widelane ambiguities per satellite, as we show in the following sections. Assuming for the moment that ambiguity resolution was indeed successful on all three widelanes, Table 1 indicates that the range parameter can now be estimated with a standard deviation of 19 centimeters, a substantial improvement over the initial 78-centimeter precision. Recalling the PDOP factor introduced above, instantaneous 3D position precision at the 20-centimeter mark should then be possible with good geometry.

    Including all available measurements in the model necessarily leads to the best performance. Still, TABLE 2 presents the conditional precision of parameters in three-frequency configurations. The precision for the widelane ambiguity is conditioned on first fixing the extra-widelane ambiguity, while that for the range assumes fixed extra-widelane and widelane ambiguities. The table highlights that frequency spacing plays a key role in the system performance. After fixing two widelane ambiguities, the Galileo E1-E5a-E5b configuration provides a range with a standard deviation of approximately 42 centimeters. The E1-E5a-E6 configuration is the best option, with a precision of the range parameter equal to the four-frequency case. In other words, the contribution of the E5b signal is almost negligible once the E5a-E6 ambiguity, having a wavelength of 2.93 meters, is resolved. For comparison purposes, the values for GPS are included and show that Galileo has the potential for significantly more precise instantaneous positioning.

    TABLE 2. Conditional precision of parameters for three-frequency single-satellite configurations.

    NETWORK SOLUTION

    To demonstrate the concept of four-frequency ambiguity resolution for PPP, a phase-bias network solution for the Galileo constellation must be generated. Our solution is based on the precise satellite orbit and clock corrections produced by the Centre National d’Études Spatiales (CNES) as a part of the International GNSS Service (IGS) Multi-GNSS Experiment (MGEX). These products contain satellite clock corrections at a 30-second interval, as well as widelane biases allowing for GPS ambiguity resolution in the L1 and L2 frequency bands. For this reason, the following analysis considers both GPS and Galileo constellations.

    Consistent processing of multi-frequency and multi-modulation signals requires code-bias corrections. The differential code-bias products from the German Aerospace Center (DLR), including the Galileo E6 signals, are used. Ambiguity resolution for Galileo can only be enabled with corresponding phase biases for all frequencies. To this date, the main contributors to the IGS for E6-compatible receivers are Natural Resources Canada (NRCan), CNES and Geoscience Australia. Since a global network of ground receivers tracking all four Galileo frequencies is not yet available, our solution is computed from a regional, but wide-area, network in Australia. The network consists of six reference stations with multi-system, multi-frequency receivers as depicted with red triangles in FIGURE 2. (Station CEDU is not included in the network solution because it is used later as a rover for PPP testing.) Measurements collected at a 30-second interval are retrieved from the Crustal Dynamics Data Information System (CDDIS) data archive. For the purpose of our demonstration, data from April 1, 2018, from 13:45:00 to 14:35:00 GPS Time is selected. During this period, five Galileo satellites were continuously tracked by the Australian stations, allowing the computation of a Galileo-only solution.

    The phase-bias solution is a generalization in the multi-frequency case of the well-known widelane/narrowlane GPS scheme. The first step consists of resolving all integer ambiguities in the network. As we deal with four frequencies, it is required to fix four ambiguities, or their combinations, per satellite-station pass. The first three combinations used for this study are the widelanes defined from E5a-E1, E5b-E1 and E6-E1. Their ambiguities are solved, as for the dual-frequency GPS case, thanks to the Melbourne-Wübbena combination. Then, one remaining integer ambiguity (here, E1) is solved by forming the ionosphere-free phase combination between E1 and E5a (with the corresponding widelane ambiguity already resolved as an integer value). The second step aims at recovering the uncombined phase biases from the estimated linear combinations of biases. By a simple system inversion, it is possible to reconstruct the phase biases on each frequency.

    FIGURE 2. Stations used to generate the Galileo phase-bias solution are represented by red triangles, while the PPP user is represented by a black square. (Image: authors)
    FIGURE 2. Stations used to generate the Galileo phase-bias solution are represented by red triangles, while the PPP user is represented by a black square. (Image: authors)

    FIGURE 3 shows the estimated biases for each frequency over the study period. The values were shifted by an integer number of the carrier wavelength for plotting purposes. The uncombined biases obtained are relatively stable, although they vary by a few centimeters over this one-hour period. These fluctuations are correlated among frequencies due to the transformation from linear combinations to uncombined biases. It should be understood that the resulting biases are not true phase biases, but rather biases to be applied to the carrier-phase observations.

    FIGURE 3. Estimated Galileo phase biases for the four frequency bands over the study period. (Image: authors)
    FIGURE 3. Estimated Galileo phase biases for the four frequency bands over the study period. (Image: authors)

    PRECISE POINT POSITIONING

    We assessed the impact of using four frequencies transmitted by Galileo (E1, E5a, E5b and E6) on positioning performance by using station CEDU in Australia (see Figure 2). It is equipped with a multi-frequency receiver collecting multi-GNSS observations at 30-second intervals. Position estimates are derived from the PPP methodology using the satellite orbit and clock corrections, along with the carrier-phase and code biases, described in the previous section.

    We computed three different solutions:

    1. a GPS-only solution;
    2. a Galileo-only solution; and
    3. a GPS and Galileo combined solution.

    For all solutions, all error sources affecting observations are modeled, including relativistic and wind-up effects, solid Earth tides and ocean loading. The a priori tropospheric zenith delay (TZD) is computed using the Vienna Mapping Function 1 (VMF1) grids, while a priori ionospheric delays are obtained from a global ionospheric map (GIM) generated at the Center for Orbit Determination in Europe (CODE). The eccentricity between the satellite antenna phase centers and the satellite center of mass is obtained from the latest version of the IGS ANTEX file, which includes frequency-dependent phase-center offsets and variations for Galileo. Since there are no Galileo-specific ground-antenna calibrations available, GPS values are used as approximations.

    In all cases, we processed uncombined observations corresponding to the OEUFS strategy. For GPS, the L1C and L2W carrier-phase observations are used, along with the C1W and C2W code observations. For Galileo, the L1C, L5Q, L6C and L7Q carrier phases are used, with identical modulations for code measurements. Note that this signal identification uses the RINEX 3 conventions where, for Galileo, the L5 and L7 signals correspond to those in the E5a and E5b bands, respectively. Carrier-phase observations are given a standard deviation of 2 millimeters at zenith, while code observations are deweighted by a factor of 100. An elevation-angle-dependent weighting strategy also assigns lesser weight to satellites closer to the local horizon. Therefore, the value of 3 millimeters used in the single-satellite analysis above corresponds to a satellite tracked at an elevation angle of approximately 40 degrees.

    The PPP filter includes states for the three position components, one receiver clock parameter per satellite system, inter-frequency code biases, one phase-bias parameter per frequency, a residual TZD, a residual slant ionospheric delay per satellite and carrier-phase ambiguities. To confirm the theoretical analysis from a previous section, the empirical single-epoch ambiguity-fixing success rate is first evaluated using a bootstrapping algorithm. The full vector of estimated float ambiguities is first decorrelated using the LAMBDA method, and all ambiguities having a success rate larger than 99 percent are fixed to integers. FIGURE 4 shows the number of fixed ambiguities for each solution.

    FIGURE 4. Number of fixed ambiguities using a bootstrapping approach for independent, single-epoch, solutions. Number of frequencies in parentheses. (Image: authors)
    FIGURE 4. Number of fixed ambiguities using a bootstrapping approach for independent, single-epoch, solutions. Number of frequencies in parentheses. (Image: authors)

    Not surprisingly, the dual-frequency GPS solution is incapable of reliably fixing ambiguities within a single epoch. During this time period, five Galileo satellites are tracked. If we first consider all four frequencies from Galileo, and use the ambiguities on one satellite to provide the datum, then a total of 16 ambiguities are being estimated in the PPP filter, 12 of which are considered widelanes. Figure 4 confirms that using correlations introduced by the geometry allows instantaneous fixing of all widelane ambiguities for Galileo for most epochs. Adding GPS to the Galileo solution makes Galileo widelane fixing more reliable, but does not allow fixing of additional ambiguities. The three-frequency (E1, E5a and E6) Galileo configuration also enables instantaneous fixing of all eight widelane ambiguities, since the inclusion of E5b brings minimal additional information.

    In all subsequent solutions, ambiguity estimation is performed using a more sophisticated method referred to as the best integer equivariant (BIE) approach. Because it is expected that not all ambiguities can be fixed simultaneously, a partial ambiguity resolution scheme is required. The BIE method fulfills this criterion by computing a weighted average of integer vectors. The outcome is a constrained ambiguity vector whose entries take either integer or float values. The key point of this approach is that the BIE float estimates can be improved by the averaging process with respect to the least-squares float estimates. Furthermore, by exploiting the correlations contained in the ambiguity covariance matrix, this method can effectively fix linear combinations of ambiguities. Therefore, we are not explicitly forming widelane ambiguities, but rather optimal linear combinations of ambiguities are fixed through the BIE averaging process. This strategy is implemented using the LAMBDA method to decorrelate ambiguities. Even though the BIE estimates are independent of the decorrelation, this step improves the computational efficiency of the approach.

    As we explained in the previous sections, positioning with fixed widelane ambiguities can potentially allow for instantaneous precise positioning. FIGURE 5 demonstrates the epoch-by-epoch position estimates for the three solutions. As the strategy implies, the filter is entirely reset between epochs, and each point in the time series is independently determined. As expected, instantaneous ambiguity resolution with GPS alone is not feasible. Although the external information provided by the GIM is beneficial in reducing the errors, the root-mean-square (RMS) error is at the decimeter level for all components (see TABLE 3).

    FIGURE 5. Instantaneous (epoch by epoch) PPP-AR solutions for GPS only, Galileo only and GPS and Galileo combined. Number of frequencies in parentheses. (Image: authors)
    FIGURE 5. Instantaneous (epoch by epoch) PPP-AR solutions for GPS only, Galileo only and GPS and Galileo combined. Number of frequencies in parentheses. (Image: authors)
    TABLE 3. RMS errors for each instantaneous PPP-AR solution (meters).

    The Galileo-only solution offers a substantial improvement in the horizontal components. These results are explained by the ambiguity-resolved widelane signals providing precise range estimates. It should be noted that only five Galileo satellites are visible during this period with a PDOP slightly exceeding a value of 3. When the full constellation of satellites will be in orbit, even better results could be obtained from a Galileo-only solution. The three-frequency (E1, E5a, E6) Galileo solution offers almost identical position estimates and is not shown here for conciseness. Combining GPS and Galileo yields the best solution with centimeter-level instantaneous positioning (refer to Table 3). For several epochs, a fully converged position is even obtained within a single epoch.

    While the RMS errors of the combined GPS + Galileo solution is at the centimeter level, individual epochs can still exhibit decimeter-level errors. To demonstrate the convergence capabilities of the OEUFS strategy, we computed 5-minute PPP sessions. Even though the station is stationary, we added a large amount of process noise to the position states to simulate kinematic processing. FIGURE 6 shows the results of all 10 sessions: horizontal convergence to a few centimeters could be achieved within two epochs in all but one session.

    FIGURE 6. Independent 5-minute kinematic PPP solutions using GPS and Galileo. Each trace represents a different session. (Image: authors)
    FIGURE 6. Independent 5-minute kinematic PPP solutions using GPS and Galileo. Each trace represents a different session. (Image: authors)

    CONCLUSION

    We have shown that GNSS modernization is a key component for reducing the convergence time of PPP solutions. Combining multiple constellations strengthens the geometry, and using multiple frequencies allows for improved ambiguity resolution performance. In particular, tracking of the E6 Galileo commercial service signal turns out to be particularly beneficial in terms of instantaneous positioning capabilities. We demonstrated that ambiguities can be instantaneously resolved on Galileo satellites, leading to a range estimate approximately four times better than that provided using code measurements. With good satellite geometry, these frequencies can enable instantaneous 3D positioning with an accuracy of around 20 centimeters. Combining Galileo and GPS allows for single-epoch centimeter-level PPP solutions and full convergence within a few epochs.

    We expect that the robustness and accuracy of the OEUFS strategy will improve in the future, with an increasing number of multi-frequency satellites and ground stations. Specifically, the additional frequencies provided by BeiDou and the Quasi-Zenith Satellite System will enhance the geometry of the solution and will further expedite convergence. Within a few years, instantaneous PPP might very well become a practical alternative to RTK for a wide range of applications.

    ACKNOWLEDGMENTS

    The authors acknowledge Geoscience Australia for making publicly available modernized GNSS data, as well as Paul Collins from NRCan for the review of our manuscript and technical advice. This article is published as NRCan Contribution 20180102.

    MANUFACTURER

    All of the stations used for the tests described in this article have PolaRx5 reference receivers manufactured by Septentrio (www.septentrio.com).


    DENIS LAURICHESSE is a member of the Navigation Systems Department at CNES in Toulouse, France. He has been in charge of the DIOGENE GPS orbital navigation filter, and is now involved in navigation algorithms for GNSS. He is in charge of the CNES IGS real-time analysis center. Laurichesse was the co-recipient of the 2009 Institute of Navigation Burka Award for his work on phase ambiguity resolution.

    SIMON BANVILLE is a senior geodetic engineer with the Canadian Geodetic Survey of NRCan, Ottawa, Canada, working on PPP. He obtained his Ph.D. degree in 2014 from the Department of Geodesy and Geomatics Engineering at the University of New Brunswick, under the supervision of Richard B. Langley. He is the recipient of the Institute of Navigation 2014 Parkinson Award.

    FURTHER READING

    •  Precise Point Positioning

    Where Are We Now, and Where Are We Going?: Examining Precise Point Positioning Now and in the Future” by S. Bisnath, J. Aggrey, G. Seepersad and M. Gill in GPS World, Vol. 29, No. 3, March 2018, pp. 41–48.

    “Precise Point Positioning” by J. Kouba, F. Lahaye and P. Tétreault, Chapter 25 in Springer Handbook of Global Navigation Satellite Systems, edited by P.J.G. Teunissen and O. Montenbruck, published by Springer International Publishing AG, Cham, Switzerland, 2017.

    •  Multi-GNSS Experiment

    “The Multi-GNSS Experiment (MGEX) of the International GNSS Service (IGS) – Achievements, Prospects and Challenges” by O. Montenbruck, P. Steigenberger, L. Prange, Z. Deng, Q. Zhao, F. Perosanz, I. Romero, C. Noll, A. Stürze, G. Weber, R. Schmid, K. MacLeod and S. Schaer in Advances in Space Research, Vol. 59, No. 7, April 2017, pp. 1671–1697, doi: 10.1016/j.asr.2017.01.011.

    Getting a Grip on Multi-GNSS: The International GNSS Service MGEX Campaign” by O. Montenbruck, C. Rizos, R. Weber, G. Weber, R. Neilan and U. Hugentobler in GPS World, Vol. 24, No. 7, July 2013, pp. 44–49.

    •  PPP Carrier-Phase Ambiguity Resolution and Convergence

    Carrier-phase Ambiguity Resolution: Handling the Biases for Improved Triple-frequency PPP Convergence” by D. Laurichesse in GPS World, Vol. 26, No. 4, April 2015, pp. 49-54.

    “Zero-difference GPS Ambiguity Resolution at CNES–CLS IGS Analysis Center by S. Loyer, F. Perosanz, F. Mercier, H. Capdeville, and J.C. Marty in Journal of Geodesy, Vol. 86, No. 11, Nov. 2012, pp. 991–1003, doi: 10.1007/s00190-012-0559-2.

    “Undifferenced GPS Ambiguity Resolution Using the Decoupled Clock Model and Ambiguity Datum Fixing” by P. Collins, S. Bisnath, F. Lahaye and P. Héroux in Navigation, Vol. 57, No. 2, Summer 2010, pp. 123–135, doi: 10.1002/j.2161-4296.2010.tb01772.x.

    •  Leastsquares AMBiguity Decorrelation Adjustment (LAMBDA)

    “Carrier Phase Integer Ambiguity Resolution” by P.J.G. Teunissen, Chapter 23 in Springer Handbook of Global Navigation Satellite Systems, edited by P.J.G. Teunissen and O. Montenbruck, published by Springer International Publishing AG, Cham, Switzerland, 2017.

    “Theory of Integer Equivariant Estimation with Application to GNSS” by P.J.G. Teunissen in Journal of Geodesy, Vol. 77, No. 7-8, Oct. 2003, pp. 402–410, doi: 10.1007/s00190-003-0344-3.

    A New Way to Fix Carrier-phase Ambiguities” by P.J.G. Teunissen, P.J. de Jonge, and C.C.J.M. Tiberius in GPS World, Vol. 6, No. 4, April 1995, pp. 58–61.

  • How to achieve 1-meter accuracy in Android

    How to achieve 1-meter accuracy in Android

    Recent changes in hardware and standards make one-meter accuracy possible, in some cases as soon as this year. The transcript of a talk given to Android developers earlier this year, this article gives a short overview of location in smartphones, introduces Wi-Fi round-trip time technology and standards, and then explains the Wi-Fi application programming interfaces.

    By Frank van Diggelen, Roy Want and Wei Wang, Android Location, Google

    Image: GPS World; outdoor, Andriy Solovyov/Shutterstock.com; indoor, Rade Kovac/Shutterstock.com
    Image: GPS World; outdoor, Andriy Solovyov/Shutterstock.com; indoor, Rade Kovac/Shutterstock.com

    It’s a great time for location applications because technology hardware standards and Android application programming interfaces (APIs) are all evolving simultaneously to enable an improved location accuracy that has not previously been possible when using smartphones.

    Eventually, this means high accuracy for everyone, but we want to take you under the hood of location because we want to give you the opportunity to get a head start on the future. We also want to highlight the need to protect and respect the user. The more people who use location, the more careful we and you have to be. We will highlight where you must get user permissions and we’ll close with some guidelines for making great location apps.

    Where are we today with indoor location accuracy? If you’ve noticed that your phone seems to be more accurate when you’re inside shopping malls and office blocks than it was a few years ago, you’re not imagining it. With each release of the fused location provider, we have had steady improvement of the Android algorithms and machine learning for Wi-Fi locations.

    There continues to be improvement, and you’ll see indoor accuracy of better than 10 meters, but round-trip time (RTT) is the technology that will take us to the one-meter level.

    Meanwhile, what about GPS? In terms of GPS accuracy in the open sky, there has not been much change in the last few years. If you’re outside and can see the open sky, the GPS accuracy from your phone is about five meters, and that’s been constant for a while. But with raw GNSS measurements from the phones, this can now improve, and with changes in satellite and receiver hardware, the improvements can be dramatic.

    Everyone’s familiar with the blue dot, but to get the blue dot you need a location provider, and to get location you need measurements — specifically, range measurements from Wi-Fi access points or from GPS satellites. We’ll show you how one-meter measurement accuracy can be made available in smartphones. The key technologies are Wi-Fi RTT, GPS dual-frequency and carrier phase measurements.

    If you want to wait a year or two, this will find its way into the worldwide ecosystem and the Android fused location provider API, but we want to give you a chance for a one- to two-year lead by taking accurate measurements and turning them into accurate location. We want to work with you to accelerate development and bring the present closer to the future.

    You might wonder, why do I need better location accuracy anyway? Let’s look at two instances where existing apps could use much better location accuracy.

    For indoor routing or navigation of the kind that you’re used to in your cars, you need much better accuracy than you have outdoors: you need one-meter accuracy, because indoor features like cubes or aisles are only a few meters wide. Even for the most loved outdoor applications such as map directions and finding alternate routes in traffic, we could benefit from higher accuracy than we have now.

    For example, when you came here this morning in a car, you probably had your arrival time estimated using the average speed of the traffic. What you really want is the traffic speed in the lane that you’re in, so that you could ask, how much faster would it be if I took the carpool lane instead? There are, of course, many other use cases and we’ll mention a few. But the important thing is that we are sure that you will have many more ideas than we have, and that’s the beauty of the open Android ecosystem.

    Wi-Fi Round-Trip Time

    Wi-Fi RTT ranging and indoor position estimation is based on making measurements of the time of flight of RF signals, and can be used to estimate your indoor position to an accuracy of one to two meters.

    Before we get into the details of Wi-Fi RTT, we want to tell you how we currently calculate an indoor location. At this time, we use Wi-Fi received signal strength indication (RSSI). Basically, we can calculate distance as a function of signal strength. Figure 1, with the access point in the center, shows a heat map of the signal strength around a Wi-Fi access point (AP).

    Figure 1.  Wi-Fi receive signal strength indication (RSSI) non-isotropic signal propagation. (Image: Frank van Diggelen, Roy Want and Wei Wang)
    Figure 2. Wi-Fi RTT principles, basic concept. (Image: authors)
    Figure 2. Wi-Fi RTT principles, basic concept.(Image: Frank van Diggelen, Roy Want and Wei Wang)
    Figure 3. Wi-Fi RTT principles in practice. (Image: authors)
    Figure 3. Wi-Fi RTT principles in practice. (Image: authors)

    The green is the strongest signal, near the AP and the red is the weakest, measured toward the edges. I’ve placed two phones on this diagram at the transition between the weak and the strong. Notice that the phone on the right is further away from the access point than the phone on the left. The signal strength can therefore vary at the same distance, which unfortunately makes it very hard to make accurate range measurements based on this type of measurement. There are lots of algorithms and tricks that can be used to improve this, but the greatest improvement can be achieved using a new Wi-Fi technology.

    That’s where Wi-Fi RTT comes into play. It uses time-of-flight instead of signal strength. It measures the time it takes to send a Wi-Fi RF packet from an access point to a phone and back again. Because radio signals travel at the same speed as visible light, if we multiply the total round-trip time of a Wi-Fi packet by the speed of light and divide by two, we get distance, and therefore the range from the phone to the access point. That’s the basic principle.

    If you want to use several ranges to nearby access points to calculate your position, we have to use a process called multi-lateration. The key thing to think about here is that the more ranges you have, the more accurate the position you can estimate. If you can use at least four ranges, then we think you can achieve a location accuracy of about one to two meters in most buildings.

    Why are we telling you about Wi-Fi RTT today? Why not last year or before? Because 2018 is the year of Wi-Fi RTT in Android. We are releasing a public API in Android P based on the IEEE 802.11mc ranging protocol. Furthermore, we’re also integrating aspects of this protocol into the fused location provider, which is the main location API that developers use to put a blue dot on a map. So, in the near future, any time there are RTT access points in the vicinity of a phone, the estimated position accuracy will be greater.

    History. The 802.11 standard was ratified in December 2016, and in early 2017 the Wi-Fi Alliance started an interop program for silicon vendors to make sure the chips followed the protocol. That’s when we started doing a lot of work to validate its operation and understand how it could be integrated into Android. By the fall of this year, we will release the public API so that you can all have access to this capability and can build your own applications around the technology.

    Principles of Wi-Fi RTT Operation

    The ranging process starts with a standard Wi-Fi scan. The phone discovers the access points that are nearby, and, based on certain bits in information elements (IEs) contained in the Wi-Fi beacons and the probe responses, we can figure out which of those access points are RTT-capable, and the phone can choose one of them to range to. It starts by making a request to the access point; as a result, the access point will start a ping-pong protocol in response. The ping sent to the phone is called a fine timing measurement (FTM) packet, and the pong sent back to the access point is an acknowledgment of that packet.

    The arrival and departure time stamps are recorded at each end of the transaction, but for the phone to calculate the total round-trip time, it needs to have all four of those times. So the access point sends one more packet to the phone, and this third message contains the missing times. The phone then simply calculates the round-trip time by subtracting the time stamps from the AP, and subtracting its own packet turnaround timestamps. The difference between these times leaves just the packet time-of-flight. We multiply this by the speed of light to get distance, and divide by two to get the range that we are trying to measure.

    Now, it turns out if you execute this process multiple times, you will in fact get more accuracy, and so that’s what the protocol allows for, enabling a burst of FTM packets. We’re typically doing a burst of about eight of these of these transactions and, as a consequence, the system can calculate ranging statistics, such as the mean and the variance. This allows us to more accurately plot a position on a map, and knowing the accuracy also allows us to more easily calculate a trajectory.

    Now that you have ranges, how do you get a position? One way, similar to GPS positioning, is you take four ranges to four separate access points; if those ranges were accurate, they would define four circles that would intersect at a single point. In practice, because of error in each range, a maximum likelihood position is calculated using a least squares multilateration algorithm.

    You can then further refine this position by repeating the process, particularly as the phone moves, and then calculate trajectory using filtering techniques, such as Kalman filtering, to optimize the estimate.

    Like any new technology, there are challenges, and we’ve experienced some of these early on. What we find is that sometimes there is a constant range calibration offset that may be as much as half a meter. Sometimes you also see multipath effects where a packet on the non-line-of-sight path from the access point to the phone is received rather than on the line-of-sight path, making the range appear longer. That problem can be solved by the vendor using something called antenna diversity, but all of these issues are related to algorithms, which the vendors are improving.

    Basically, we need to go through a sort of teething process to get rid of these bugs, and Google can help in this process by providing reference platforms and reference applications. Vendors can then calibrate their own platforms before you guys even get to use them, which will be the ideal situation.

    We’ve assumed that as early adopters you want to start using this API, but as we move into the relatively near future, we expect you to just use the Fused Location Provider because we’re going to be integrating the RTT capability into it. At the moment, the Fused Location Provider uses GPS (when it’s available), cell-tower signal strength and Wi-Fi RSSI, and fuses all this with the onboard sensors: inertial navigation from the accelerometer, gyro and compass. Now we’re adding Wi-Fi RTT into that mix, and it will increase the accuracy of the Fused Location Provider whenever RTT-capable access points are available nearby.

    One other thing to remember is that if you are calculating the Wi-Fi RTT position yourself, you also had to know the position of the access points. In the Fused Location Provider, we will calculate those positions for you automatically: we’ll crowd-source those positions so you won’t have to worry about that, and it will make life a lot easier for you to write applications.

    RTT APIs

    Let’s walk you through the RTT APIs in P to see how you can add RTT in your own application. As we mentioned, RTT measures the round-trip time between two Wi-Fi devices so both your mobile phone and your access points need to support the 802.11mc protocol. As you saw, RTT can give you very fine location estimates down to one-meter accuracy, so your application needs to declare the ACCESS_FINE_LOCATION permission. Of course, both location and Wi-Fi scanning need to be enabled on the mobile device.

    How do you know whether your mobile phone supports RTT? In P, we added a new system feature called FEATURE_WIFI_RTT so you can simply check whether this returns true on your mobile device. Our pixel phones running P DP2, and above, will support RTT. How do you know whether your access points support RTT? As usual, you will need to do a Wi-Fi scan and get a list of Wi-Fi scan results. Then iterate through the scan results and check for each scan result whether the method is80211mcRepsonder() returns true. This will tell you whether the access points support RTT.

    After you get a list of RTT-enabled APs, simply add them to the ScanRequest Builder to build a scan request. RTT is carried out by the WiFiRTTManager, which you can get access to by getting the system service WIFI_RTT_RANGING_SERVICE. Now we’re ready to start RTT ranging by sending the RTT request to the RTTManager with a ranging result callback. Usually RTT takes only a few hundreds of milliseconds, and when it finishes, you will get a list of information including the status — an RTT may fail, the MAC address — which AP you have just ranged, and most importantly, the distance between the mobile phone and the access point.

    Here is the list of information you can get from RTT ranging results: the distance, the distance standard deviation, which is the standard deviation from multiple ranges in multiple FTMs, and the number of attempted FTM measurements and number of successful measurements. The ratio of successful measurements over attempted measurements will give you an idea of how good the Wi-Fi environment is for RTT ranging.

    We mentioned all Pixel devices support RTT. How about access points? We are beginning to see access points supporting the 11mc protocol in production. We are also very excited to let you know Google Wi-Fi will soon support the 11mc protocol. By the end of this year, off-the-shelf Google Wi-Fi will have RTT enabled by default. Worldwide, we’re also beginning to see the deployment of RTT APs. South Korea is actually leading the deployment of RTT APs.
    Of course, this is just the beginning of the long journey. We’re very eager to see a larger penetration rate of RTT APs in the coming years.

    Figure 4. Integrating RTT with Android location. (Image: authors)
    Figure 4. Integrating RTT with Android location.(Image: Frank van Diggelen, Roy Want and Wei Wang)

    GPS and the Great Outdoors

    Carrier-phase precision has been in commercial GPS receivers since the 1980s. What is new is the availability of these carrier-phase measurements from phones and dual-frequency measurements in phones. Right now, all of your smart phones, all smart phones everywhere, have GPS or GNSS on one frequency band only. It’s known as L1. But there’s a new frequency in town called L5, and it’s supported by all these GNSS systems: GPS, Galileo, BeiDou QZSS and IRNSS. The availability of a second frequency means that you get much faster convergence to carrier-phase accuracy.

    What about hardware? In the last few months, several companies that produce consumer GPS chips have announced the availability of dual-frequency L1/L5 GPS chips both for the automobile market and for the phone market. These chips are now being designed into cars and phones.

    Let’s talk about the measurements themselves and the APIs. The phone must support the GNSS measurements API. Your app is going to need the ACCESS_FINE_LOCATION permission, and location needs to be on.

    How do you know if a particular phone supports these measurements? At a high level, you can just go to a website that we maintain, g.co/GNSSTools, as part of the Android developer site. A table there lists phones that support the GNSS measurements and also which characteristics they support. It’ll tell you which phones support the measurements and which of those support the carrier-phase measurements.

    Programmatically, you do this as follows: You call the method onStatusChanged and it will return an integer that tells you the capability of the phone, either if the phone just does not support the measurements at all or if it supports it but location is off, or if it supports it and location is on; in that case, you’re good to go.

    Let’s get into some details of the APIs. The most relevant methods for what we’re talking about here are the following three:

    • getConstellationType() tells you which of the different GNSS constellations a particular satellite belongs to.
    • getCarrierFrequencyHz() tells you whether you’re on the L1 or the L5 band for a particular signal.

    Most importantly,

    • getAccumulatedDeltaRangeMeters() tells how far along that carrier wave the receiver has tracked you since it began tracking the signal.

    There’s something else that we need to explain, which is duty cycling. Right now when you’re navigating with your phone and you see the blue dot moving along, you might think that the GPS is on continuously. It’s actually not. What’s happening in the phone is that GPS will, by default, be on for a fraction of a second and then off for the remaining fraction of a second, and then repeat. This is to save battery. You perceive that the GPS is on all the time because the blue dot will move along continually, but actually it’s duty cycling internally.

    For this carrier-phase processing, you have to continually track the carrier wave because the carrier wave is like a finely graduated ruler or tape measure with no numbers on it. So if the GPS was on and your receiver measured your phase and you get the data from the reference station, you’d start processing. If the GPS then goes off for a fraction of a second, you’ve lost where you were. It’ll start again, you’ll reacquire, you’ll be at a different phase on the reacquisition, you’ll start again — well, you’ll never solve the problem. You need the tape measure to stay out and you need to process, and to do that you need to disable duty cycling. You can do that in Android P with a developer option.

    Details of the API. Figures 5 and 6 are screenshots of an application that we’ve put out called GNSS Logger. This enables you to log the raw measurements in the phone. The nice thing about this app is it’s a reference app: the code is open source and available to you on Github, so when you build your app, please make use of our code.

    Figure 5. Screenshot of GNSS Logger. (Image: authors)
    Figure 5. Screenshot of GNSS Logger. (Image: Frank van Diggelen, Roy Want and Wei Wang)
    Figure 6. Sample code for getting GNSS raw measurements. (Image: authors)
    Figure 6. Sample code for getting GNSS raw measurements. (Image: Frank van Diggelen, Roy Want and Wei Wang)

    When you build an app that needs raw measurement, you will need the Android location manager API with the method registerGnssMeasurementsCallback. This method requires you to pass it a GnssMeasurementsEvent callback shown here. You construct this callback, and then override the method onStatusChanged, and that will give you the integer status that we discussed to tell you if measurements are supported.

    If they are, you then override the method onGnssMeasurements Received, and this allows you to receive a GnssMeasurementEvent every epoch, for example, every second. This event gives you the values we’ve been talking about: constellation type, carrier frequency and accumulated Delta range. For duty cycling, that’s a developer option, so you access that through the developer page on your phone as you see there on P. This allows you to disable the duty cycling.

    Keep in mind this introduces a trade-off between getting the continuous measurements and battery life. There will be an impact on battery life. How much? Well even when GPS is on continually, it will use less than 20% of the power that screen-on uses, so that gives you a feel for the magnitude. This is a developer option precisely because it’s a trade-off involving battery life, and we’re very concerned about maximizing battery life, but if you and our team together can prove that there’s value in this option and people want it, then it will be upgraded to a fully supported API in the future.

    Figure 7 shows the basic architecture that we expect if you implement an app for high accuracy. On the bottom of the block diagram on the left you’ve got the GPS/GNSS chip. The GNSS measurements come up through the APIs we’ve just described, and then your app lives at the top in the application layer. You’re going to need access to a reference network to get the data that the reference stations are tracking. There are publicly available reference networks. I’ve listed one at the bottom: the International GNSS Service. You can get data from them free.

    Figure 7. Apps for high-accuracy GPS. (Image: authors)
    Figure 7. Apps for high-accuracy GPS.(Image: Frank van Diggelen, Roy Want and Wei Wang)

    Then you need to process that data in some kind of position library, and that does all the carrier-phase processing, and that too is available as open-source code. RTKLib.com has an open-source package for precise positioning. Then you’re good to go.

    We mentioned that dual frequency gives you much faster convergence to the high accuracy, but you don’t have to wait until the dual-frequency phones come out. You can start doing this with single-frequency phones. Here’s an example of someone who’s already done that. This is an app created by the French Space Agency, and they’re doing exactly what we show on the block diagram on the left and they’re achieving sub-meter accuracy after a few minutes of convergence.

    Here’s some more external analysis that’s been done in a similar way. This is from a paper called “Positioning with Android GNSS.” This is using one of those chips that we showed you, the chip that goes in cell phones that does dual frequency. What’s been shown here is the cumulative results over many different starts of the GPS and what you see is that most of the time the accuracy is better than a meter. You see that on the vertical axis, which is 0 to 1 meters, the accuracy gets to better than a meter in less than one minute and then continues to converge as long as the phone continues to track that carrier phase continuously.

    Here’s a another similar but different paper. This is using one of the chips that’s meant for cars. This was tested in a car driving around that track there, and what the plot here shows is the accuracy after the initial convergence while the car was driving. You see with GNSS alone the accuracy is 1 to 2 meters, and with this carrier-phase processing it’s at a couple of decimeters.

    For you to build this, what are you going to need? Of course you need the device location to be enabled and your app has to have location permissions, so that’s going to come from the user. You need the basic GNSS measurements, that’s been available since Android N. You also need this continuous carrier phase I’ve been talking about and that’s available in P with the developer option. It would be nice to have dual frequency for fast convergence and that’s coming soon. You need a reference network such as the one we already mentioned; there are also commercial reference networks out there and commercially available software to do the same thing, but we recommend you start with the free stuff and go from there.

    Finally there’s the app from you.

    In summary, everything we’ve been showing you here is based on indoor and outdoor technology that’s been evolving kind of in parallel. In each case we have a new technology and Android P gives you a way to access it.

    Indoors Again

    The new technology is Wi-Fi RTT and round-trip time-enabled access points. We give you a public API to access these measurements, but you need access point infrastructure. This is where some of you can move ahead this year, because if you have a customer who owns or controls a venue, they can upgrade their access points — sometimes just a firmware upgrade — and then you have the infrastructure. Android P comes out later this year, and you can implement something and have indoor navigation, or create any other type of context-aware app.

    For example, someone goes in a store: where’s the milk? You can make the world a better place for all of us by saving us from the tyranny of having to ask directions from strangers. And if you’re not one of those people who has access to this now, in a few years the infrastructure will naturally evolve as access points upgrade to RTT, and one-meter location will be automatically available from the Fused Location Provider.

    Now Outdoors

    For this carrier-phase process, it’s not just outdoors, but outdoors with open sky. What do you need? Dual frequency and continuous carrier phase. We give you the API and the developer option to make use of that. You will need reference-station access as we mentioned, and then applications.

    What can you do outdoors with open sky? We already mentioned the traffic example. There are many others that readily come to mind where existing GPS accuracy doesn’t cut it. For example geocaching, where people look for treasures; it would be nice to have one-meter accuracy. Precision sports monitoring. Imagine a snowboarder who wants to measure her tracks very precisely after the fact. Five-meter location is not good enough. One meter would be great.

    Speaking of sports, there are more and more drone apps where you have a kind of “follow me” capability, and the drone will fly along and video you. Well it would be nice if it videos you and not the person next to you. And so on. There are hundreds of apps, and you’re probably thinking of some right now, and that’s the whole point.

    We want you to write those apps, and together we’ll bend the arc of technology history closer to the present. I’m really looking forward to next year to see you back here and see what you’ve created.

    Finally, we want to leave you with a couple of pointers. When you build location apps, please build great location apps. You must have user trust. Please provide the user with transparency and control. You’re going to have to ask for location permissions for this. Explain to them what you’re doing, how it benefits them. When things go wrong, make your app recover gracefully. If these measurements are unavailable for some moment or something goes wrong, you can fall back to the Fused Location Provider location.

    Think about that and, finally, respect the battery life trade-offs that we’ve discussed.


    FRANK VAN DIGGELEN is a principal engineer in the Android location team, leading high-accuracy location including Wi-Fi and GPS. He holds more than 90 U.S. patents on GPS, and is the author of A-GPS, a textbook on Assisted-GPS. He has a Ph.D. from Cambridge University and teaches a GPS class at Stanford.

    ROY WANT received his doctorate in computer science from Cambridge University and is a research scientist at Google. His interests include mobile and ubiquitous computing. He is an IEEE Fellow and secretary for IEEE Task Group 802.11az (Next-Generation Positioning). To date, he holds 100+ issued patents in this area.

    WEI WANG s a software engineer in the Android location and context team. He works on the Fused Location Provider API. His main focus is reducing battery consumption of location, as well increasing location accuracy. He received a master’s degree in information security from Carnegie Mellon University and a master’s degree from Southeast University in China.

    Featured image: Frank van Diggelen, Roy Want and Wei Wang

  • UAVs, new sensors and mapping help with volcano eruption response

    A team of five volunteers armed with drones, advanced sensor systems and GIS technologies joined the response effort at Kilauea Volcano Lower East Rift Zone to assist in tracking and predicting the ongoing volcanic eruption.

    Using small unmanned aerial systems (sUAS) together with air-quality sensors, advanced imaging tools and Esri’s spatial analytics and mapping, the team from the Center for Robot-Assisted Search and Rescue (CRASAR) provided real-time aerial views of the eruption.

    The CRASAR team identified a new fissure not visible from the ground, projected the lava flow rate during the night when manned helicopters were not allowed to fly, and provided ongoing data collection from new thermal sensors technology.

    The CRASAR response marks the first known use of sUAS for emergency response to a volcanic eruption and first known use of sUAS for sampling air quality. The CRASAR team provided Hilo Fire Department and the Civil Defense with live streaming of video from the sUAS over the new FirstNet cellular network.

    “This latest CRASAR mission is another example of dedicated volunteers working together with private sector partners to deploy technology to save lives and property when disaster strikes,” said CRASAR Director and disaster robotics expert Robin Murphy. “With support from technology partners like Esri, Hangar Technologies, RemoteGeo and RMUS, we are able to both respond to active disasters but also demonstrate to the first responder community best practices and benefits of engaging robots and other technologies in disaster response.”

    CRASAR supported tactical response operations at the Leilani, Hawaii, eruption event May 14-19, supplementing the University of Hawaii Hilo’s (UHH) sUAS capabilities and allowing UHH sUAS operators to focus on geographical and volcanology.

    During the six-day Leilani deployment, the CRASAR team flew 44 sUAS flights, including 16 at night, using DJI 200, 210, Inspire, and Mavic Pro drones.

    Esri’s Drone2Map for ArcGIS together with Hangar’s Enterprise Platform for 360-degree imaging enabled rapid 360-imaging for situational awareness.

    DJI’s new XT2 thermal sensor provided unprecedented drone-based air-quality monitoring.

    Video and data were shared with local first responders using FirstNet, the first high-speed, nationwide wireless broadband network dedicated to public safety.

    The CRASAR response team included sUAS pilots Justin Adams of Constellation Consulting Group, David Merrick and Laura Hart of Florida State University Center for Disaster Risk Policy, Jon McBride of Rocky Mountain Unmanned Systems, and Robin Murphy of Texas A&M University. Funding was provided in part through research grants from an insurance partner and the National Science Foundation.

    “This eruption is especially impactful because of its location,” said Esri’s Public Safety Lead, Ryan Lanclos. “That makes the CRASAR’s use of drones and mapping technologies, and the near real-time situational awareness it provides of people, homes, businesses and infrastructure during this disaster, a resource first responders will be able to turn to time and again.”

    CRASAR’s deployment to Hawaii marked a number of firsts for technology applied to disaster response. To interact with the same GIS mapping and imaging technologies responders used on the scene at Kilauea Volcano Lower East Rift Zone, visit this page.

  • Virtual base RTK from JAVAD automates for greater ease

    Virtual base RTK from JAVAD automates for greater ease

    JAVAD GNSS has integrated its Justin software suite, including Verify Base-RTK (VB-RTK) with its Triumph-LS Rover receiver, carrying six different RTK engines, and Triumph-1 or Triumph-2 base units, to make GNSS data collection easier yet more reliable.

    The combination of the J-Field onboard data collection of the Triumph-LS working with the Justin reduction software establishes the project coordinate system with little effort and good confidence in the user’s field data, the company said.


    The Javad Data Processing Online Service (DPOS), built in the Justin software system, works directly with the National Geodetic Survey’s Continuously Operating Reference Station (NGS CORS) system to calculate and establish the project base station within a known coordinate system.

    This system can be based upon the National Spatial Reference System (NSRS) or a localized system. Either way, the user can begin data collection immediately using an autonomous base point, with relative corrections being established to the RTK receiver.

    Before VB-RTK, an extra step (and time) was required to occupy the base point, collect a sufficient amount of data, and upload to the NGS Online Positioning Service (OPUS) for data calculations and positional determination. VB-RTK now automates this process, increasing efficiency and reducing errors.

    Among the main benefits of the software are the vector data check-verification routines and the ability for the user to easily identify random errors (receiver height input, description codes, and so on).

    Justin software enables thorough review of preset parameters and templates to help the user establish a consistent workflow pattern.Additionally, the receiver and software system do not rely on a third-party real-time network (RTN).

    Besides knowing exactly where the base station is broadcasting from, there are no data charges from the RTN nor cellular fees. By having the base station within the project area, the system will also provide the user with faster fixes and more accurate information.

  • FAA surveys commercial drone operators

    FAA surveys commercial drone operators

    If you’ve registered a commercial drone, the U.S. Federal Aviation Administration (FAA) wants to hear from you.

    On June 19, the FAA sent a questionnaire to everyone who has registered a commercial drone – more formally, an unmanned aircraft system (UAS) — for anything but recreational or hobby use.

    Most of these owners fly their drones for commercial purposes, but the survey population also includes government departments and other users.

    Hobbyists are not included in this survey.

    The goal is to collect information on drone flight activities under the FAA’s small drone rule (Part 107), data that will help the FAA improve the services it delivers to the UAS community. Responses to the questionnaire are voluntary and entered 100 percent electronically.

    The survey will take about 10 minutes to complete.

    The questions include areas such as number of drones registered, number and types of missions completed in 2017, primary locations where the operator flies and types of waivers requested. The survey also asks how operators want to get information about drone-related issues from the FAA, and how satisfied they are with the news channels they use now

    The questionnaire is completely anonymous, so responses cannot be attributed to an individual.

    If the questionnaire is still sitting on your computer or mobile device, the FAA wants —  and needs — your input.

  • HxGN SmartNet, AZGPS to expand GNSS correction services in US

    HxGN SmartNet has partnered with AZGPS LLC to expand access to quality network correction services for GNSS users in the southwestern United States.

    HxGN SmartNet, a high-precision, high-availability GNSS network correction service, is provided by Hexagon’s Geosystems division. AZGPS, based in Florence, Arizona, serves professionals across Southern California and Arizona who rely on high-precision GNSS with network correction services, professional support and training.

    The company will remain the local point of contact in the region and now has access to the infrastructure and resources of HxGN SmartNet, including HxGN SmartNet stations and a wide array of Hexagon services.

    “Our number-one goal is to help our customers succeed,” said Travis Thompson, AZGPS. “The ability to leverage the resources of HxGN SmartNet will enable AZGPS to provide even more benefits to GNSS users. We look forward to continuing the superior service our customers have come to rely on for more than 13 years while staying on the leading edge of technology.”

    HxGN SmartNet is fully open to all makes and models of GNSS equipment and is designed to provide the highest reliability and accuracy 24/7. Launched in 2010, HxGN SmartNet is a commercial GNSS network that offers a single connection point for coverage across North America.

    Built on the most advanced GNSS reference station software platform in the world, Leica Geosystems GNSS Spider, HxGN SmartNet provides high-precision, high availability network real-time kinematic (RTK) corrections for any application, the company said.

    A variety of different subscription plans are available at the state, regional and national level for any application requiring precision GNSS corrections. With more than 1,300 stations in 45 states and eight provinces, HxGN SmartNet North America offers extensive network coverage.

    “GNSS users across all applications know they can rely on HxGN SmartNet to make the investments and partnerships needed to provide the easiest, fastest and most precise positions in the industry,” said Wendy Watson, director of operations for HxGN SmartNet North America. “AZGPS has a long track record of providing excellent service to GNSS users in the Southwest through the AZGPS and CALVRS networks. This cooperation between two familiar names in the positioning services industry underscores HxGN SmartNet’s commitment to ‘any constellation, any application and open to all.’”

  • TerraGo releases Smart Streetlights platform with integrated GPS location

    TerraGo, a provider of mobile workforce collaboration solutions, has launched a new version of its TerraGo Streetlights platform, which is designed specifically for smart streetlight projects and includes several field-tested, customer-driven and customizable features that help accelerate savings and lower full life cycle support costs.

    According to TerraGo, Streetlights is fully-integrated with Itron’s leading smart city management software, Streetlight.Vision, and is being utilized on a number of high-profile smart streetlight projects in locations around the world, including Chicago.

    The platform’s latest features, which are all configurable and customizable with zero-code, include automated node commissioning with Itron’s Streetlight.Vision, full inventory chain-of-custody management, MAC address validation, integrated GPS location and proximity detection, advanced mobile app search, custom map symbology, installation status maps and reports, automated workflow updates, crew assignments, task notifications, one-click workflows, configurable asset cards, customizable operational reporting-as-a-service and more.

    According to TerraGo, smart streetlights provide a measurable return on investment to cities by helping them achieve massive reductions in energy costs, carbon dioxide emissions and maintenance expenses — all while laying the open network foundation for smart city applications like traffic management, air quality, noise management and crime prevention. TerraGo Streetlights helps cities and utilities complete projects and really savings sooner, thus increasing the total return on investment while enabling future smart city applications, the company added.

    “TerraGo Streetlights’ features are customer-driven from lessons learned on real-life projects, so we can improve efficiency in every phase from planning and inventory to installation and maintenance,” said Dave Basil, president and CEO of TerraGo. “We believe in being super-focused on our customers’ work, so we can deliver software that makes a real impact for these projects. We even embed our software architects and UX designers with work crews in the field, so we can learn firsthand how to minimize task times, prevent errors and get the job done right the first time.”

  • Esri book highlights analyzing, mapping surface water features

    Esri has published its latest book, “GIS for Surface Water: Using the National Hydrography Dataset,” by Jeff Simley, which details how to use geographic information system (GIS) technology to visualize and analyze data sets. Simley is an award-winning cartographer and the former lead of the Hydrography Program at the United States Geological Survey (USGS).

    The book examines the complexities of surface water systems and shows readers how to use the Esri ArcGIS software, the USGS’s National Hydrography Dataset (NHD) and the Watershed Boundary Dataset (WBD), and the U.S. Environmental Protection Agency’s NHDPlus dataset to better study and manage the United States’ vast water system.

    According to Esri, the book thoroughly examines the representation of water features and their attributes in a GIS and then turns its attention on how that data is structured in the NHD, WBD and NHDPlus datasets. In addition, after seeing how surface water hydrography can be modeled in a GIS, readers can then learn how to use these tools to solve real-world problems, such as protecting and restoring the fisheries habitat in Washington.

    The book also offers instructions to guide readers to create surface water flow-volume maps that show how much water flows through any given river system.

    “This book is unique in that it is the most comprehensive, authoritative source for the NHD,” said hydrologist David Maidment in the book’s foreword. “But it is more than that: It is a monument to the intellectual craft and dedicated effort of a generation of digital mapmakers who devoted their professional careers to the completion of this enormous task.”

  • Ceva releases Dragonfly NB2 for internet of things

    Ceva has launched the successor to its Ceva-Dragonfly NB1 solution targeting the NB-internet of things (IoT) market, the Ceva-Dragonfly NB2.

    The Dragonfly NB2 is a highly integrated and modular solution optimized for Cat-NB2 (3GPP Release 14 eNB-IoT) that can seamlessly be incorporated into chips and modules by the multitude of companies looking to address the large and fast-growing cellular IoT space.

    GNSS hardware package. For customers developing NB-IoT products that also require GNSS capabilities, Ceva-Dragonfly NB2 includes a new power-optimized GNSS hardware package, with GNSS RF receiver and multi-constellation digital front-end.

    The GNSS package speeds up both acquisition and tracking tasks by up to 8 times compared to Ceva-Dragonfly NB1, enabling a host of popular NB-IoT use cases, including people, livestock and asset tracking, and geo-fencing, the company said.

    IoT boom forecast. In the latest edition of the Ericsson Mobility Report, the forecast for cellular IoT increased significantly, almost doubling to 3.5 billion connections for 2023. The report cites large-scale deployments in China and increasing interest in eNB-IoT and Cat-M1 cellular IoT standards as the catalysts for 30 percent CAGR between 2017 and 2023.

    Ceva-Dragonfly NB2 is a licensable Rel14 compliant eNB-IoT solution and builds on the success of Ceva-Dragonfly NB1, which has been widely licensed for a range of use cases and emerging end markets, including smart cities, transport and logistics and consumer electronics. It is centered on the Ceva-X1 DSP/control processor featuring an enhanced Instruction Set Architecture and provides a unified processor environment for both physical layer and protocol stack workloads.

    The solution also includes a highly integrated, worldwide enabled RF transceiver, a power amplifier (PA) and all the associated hardware and software modules required to develop a complete eNB-IoT product, ensuring the lowest possible bill-of-materials (BOM) in the process.

    In addition to the performance improvements enabled by Release 14 including higher data rates and lower latency, Ceva-Dragonfly NB2 features a range of enhancements to ensure higher performance, added functionality and increased security for NB-IoT applications compared to its predecessor.

    A new power management solution, complete with intelligent sleep mechanisms ensures ultra-low sleep power consumption of a few microAmps, further improving the battery life critical to every NB-IoT device.

    The enhanced RF design is already silicon-proven at 55nm and 40nm processes, further lowering the entry barriers for customers with no previous cellular expertise to enter this burgeoning market.

    Ceva-Dragonfly NB2 also includes the fully optimized physical layer and protocol stack firmware designed for Release 14 Cat-NB2. The addition of an on-chip embedded flash memory and controller now allows full NB-IoT design on a single die which further reduces BOM and power consumption.

    Voice trigger. Ceva-Dragonfly NB2 also supports use cases requiring always-listening voice trigger, voice commands and sound sensing. The flexibility of the Ceva-X1 IoT processor allows for these sensing features to be implemented in software. The Ceva ClearVox voice front-end software package, for example, can be used to ensure clear and intelligible voice pickup for use cases such as emergency calls and voice panic buttons. In terms of security, Ceva-Dragonfly NB2 integrates a completely redesigned secure platform, including smart interfaces to connect USIM or eSIM. Ceva also offers other complementary technologies addressing massive IoT, such as Bluetooth 5 dual-mode and low energy and Wi-Fi 802.11n/ac/ax, for short range connectivity which customers can leverage for their product designs.

    “The widespread commercial deployment of NB-IoT is well underway across the globe and we’re proud to be at the forefront of technology innovation for long-range massive IoT,” said Michael Boukaya, vice president and general manager of the wireless business unit at Ceva. “With the introduction of Ceva-Dragonfly NB2, we have built on the considerable success we achieved with our first generation solution, and delivered a unique, silicon-proven eNB-IoT Release 14 solution for our customers that is unprecedented in terms of system completeness, performance and power efficiency.

    “Moreover, the option of power-optimized GNSS, voice and sensing capabilities vastly increases the breadth of use cases our customers can address with this licensable solution,” Boukaya said. “There is no other IP company in the world today that can come close to offering such a complete solution for eNB-IoT and we’re excited to closely partner with our customers to create a whole new wave of applications and devices for the infinite Internet of Things.”

    Ceva-Dragonfly NB2 is available for licensing now. Development kits and reference silicon will be available in the third quarter of this year.

  • U.S. Supreme Court requires warrants for cellphone location data

    U.S. Supreme Court requires warrants for cellphone location data

    The U.S. Supreme Court ruled June 22 that the government needs a warrant to access a person’s cellphone location history.

    In the case Carpenter v. United States, the American Civil Liberties Union represented a man who had months of his cellphone location information turned over to law enforcement without a warrant. Investigators received the cell tower records with a court order that requires a lower standard than the “probable cause” needed to obtain a warrant.

    The court found in a 5-to-4 decision that obtaining such information is a search under the Fourth Amendment and that a warrant from a judge based on probable cause is required.

    “This is a groundbreaking victory for Americans’ privacy rights in the digital age,” said ACLU attorney Nathan Freed Wessler, who argued the case before the court last November. “The Supreme Court has given privacy law an update that it has badly needed for many years, finally bringing it in line with the realities of modern life.

    “The government can no longer claim that the mere act of using technology eliminates the Fourth Amendment’s protections. Today’s decision rightly recognizes the need to protect the highly sensitive location data from our cell phones, but it also provides a path forward for safeguarding other sensitive digital information in future cases — from our emails, smart home appliances, and technology that is yet to be invented.”

    Case background

    In 2011, without getting a probable cause warrant, the government obtained from cell service companies months’ worth of phone location records for suspects in a robbery investigation in Detroit. For one suspect, Timothy Carpenter, the records covered 127 days and revealed 12,898 separate points of location data. Police seek these kinds of cellphone location records from phone companies tens of thousands of times each year.

    After Carpenter was convicted at trial, based in part on the cellphone location evidence, he appealed to the Sixth Circuit Court of Appeals, which ruled 2–1 that no warrant is required under the Fourth Amendment.

    The Supreme Court said in its opinion today, “We decline to grant the state unrestricted access to a wireless carrier’s database of physical location information. In light of the deeply revealing nature of CSLI, its depth, breadth and comprehensive reach, and the inescapable and automatic nature of its collection, the fact that such information is gathered by a third party does not make it any less deserving of Fourth Amendment protection. The government’s acquisition of the cell-site records here was a search under that amendment.”

    Tech companies and media weigh in

    Among the many friend-of-the-court briefs filed in the case is the one from technology companies, which was signed by Google, Facebook, Apple, Verizon, Twitter, Cisco, Microsoft and others. They echoed the ACLU’s arguments, writing that “Fourth Amendment doctrine must adapt to the changing realities of the digital era” and that “Rigid analog-era rules should yield to consideration of reasonable expectations of privacy in the digital age.”

    In another friend-of-the-court brief, the Reporters Committee for Freedom of the Press and 19 other media organizations warned of the chilling effect on First Amendment freedoms that can result from easy law enforcement access to the location information of reporters and their sources.

    Third-party doctrine

    The government’s argument was based on the “third-party doctrine,” which the government reads to provide that by sharing information or records with a “third party” such as a business, a person gives up any reasonable expectation that the information will remain private. The doctrine was established in Supreme Court cases from the 1970s, which reasoned that without an expectation of privacy, there is no Fourth Amendment protection for certain records voluntarily shared with businesses, such as canceled checks sent to a bank or phone numbers dialed on a phone and transmitted over a phone company’s equipment. The government has extended that principle to cover various kinds of digital records, such as cell phone location data.

    “The court’s decision is a vindication of the arguments we have persistently made on behalf of Timothy Carpenter throughout this litigation — that the Constitution’s privacy protections fully apply to the digital location data created by using cell phones,” said attorney Harold Gurewitz, who represents Carpenter alongside the ACLU. “The ruling also affirms that prosecutors are required to get a search warrant in order to seize this kind of sensitive personal information.”

    The data acquired by police in the case provides a stark demonstration of how location data can reveal extraordinarily private details about people’s lives, from where they sleep to where they pray.

    For example, the location data showed that in the early afternoon on a number of Sundays, Carpenter made or received calls from the cell tower sectors nearest to his church. His cellphone records do not routinely show him in that area on other days of the week, implying that he was worshipping at those times. The data also shows which nights he slept at or near his home, and which nights he spent elsewhere.

    Carpenter is represented at the Supreme Court by the ACLU, the ACLU of Michigan, defense attorney Gurewitz of Gurewitz & Raben PLC, and Jeffrey Fisher, co-director of the Stanford Law School Supreme Court Litigation Clinic.