{"id":9907,"date":"2025-10-08T08:09:03","date_gmt":"2025-10-08T08:09:03","guid":{"rendered":"https:\/\/www.oxts.com\/?p=9907"},"modified":"2026-03-26T12:16:04","modified_gmt":"2026-03-26T12:16:04","slug":"reducing-gnss-denied-localisation-complexity","status":"publish","type":"post","link":"https:\/\/www.oxts.com\/zh\/reducing-gnss-denied-localisation-complexity\/","title":{"rendered":"\u4e0d\u4f9d\u8d56\u5168\u7403\u5bfc\u822a\u536b\u661f\u7cfb\u7edf\u7684\u5b9a\u4f4d\uff1a\u5229\u7528 WayFinder \u964d\u4f4e\u6210\u672c\u548c\u590d\u6742\u6027"},"content":{"rendered":"\n
\n
\n
\n \n \n \n \n\n\n \n\n\n \n\n\n \n\n
Whether you\u2019re an automotive engineer testing ADAS features on the open-road, or a mapping engineer looking to localise another sensor for georeferencing purposes, developing new products that provide accurate localisation without GNSS requires you to integrate additional sensors into a system. <\/h5>\n\n\n
\n

GNSS-denied localisation solutions have one clear goal – to stabilise position drift. That process can be costly, both in terms of integration time (particularly if you have more than two sensors to integrate) and the cost of development. <\/span><\/span>But,<\/span> what if there was an out-of-the-box solution where sensor integration was already taken care of<\/span>.\u00a0 <\/span>A solution that you could take out of the box, mount and use to accurately localise your vehicle in any environment – with or without GNSS!<\/span><\/span><\/p>\n

If <\/span>you\u2019re<\/span> working on a project that involves localisation in a range of different environments, including urban canyons and GNSS-denied spaces, then we have a solution that could do just that \u2013 <\/span>WayFinder<\/span>. <\/span>It\u2019s<\/span> a device that provides <\/span>centimetre-level position accuracy<\/span> in both open-sky and GNSS-denied spaces and can switch seamlessly between them, ensuring uninterrupted positioning everywhere.<\/span><\/span><\/p>\n

In this blog, <\/span>we\u2019ll<\/span> look at several ways using an out-of-the-box solution for localisation in any environment can save you both time and money.<\/span><\/span><\/p>\n\n <\/div>\n\n <\/div>\n <\/div>\n \n \n <\/div>\n\n\n

\n
\n
\n \n \n \n \n\n\n \n\n\n \n\n\n \n\n\n\n
\n
WayFinder cuts GNSS-denied localisation integration complexity<\/span><\/strong><\/h5>\n

Sensor integration and fusion<\/a><\/span> is o<\/span>ne of the most intricate elements of building any localisation solution, particularly those that need to <\/span>operate<\/span> in GNSS-denied spaces<\/span>. The choice of sensors, designing them into your platform, and building interfaces to bring the data from those sensors into your navigation engine are all complex<\/span> pieces of<\/span> work. Our latest solution, WayFinder<\/a><\/span><\/span>, designed for engineers looking to integrate GNSS-denied localisation into their projects, <\/span>removes the need for most of that work with a pre-integrated set of sensors that are ready to use out of the box<\/span>.<\/span><\/span><\/p>\n\n <\/div>\n\n <\/div>\n <\/div>\n \n \n <\/div>\n\n\n

\"WayFinder:<\/figure>\n\n\n\n
\n
\n
\n \n \n \n \n\n\n \n\n\n \n\n\n \n\n\n\n
\n

To enable GNSS-denied localisation, WayFinder makes use of three sensors:<\/span>\u00a0<\/span><\/p>\n