标签：#Navi

Building Global and Local Path Planners for Autonomous Robots Autonomous navigation is not just about finding a route from A to B. A robot must plan a useful route through a map and continuously adapt that route to obstacles, other robots, people, and changes in its environment. A practical navigation system therefore separates global planning from local planning . Global vs Local Planning Global Map | v +------------------+ | Global Planner | +------------------+ | v Global Path | v +------------------+ Sensors>| Local Planner | +------------------+ | v Velocity Commands | v Robot Global Planner The global planner considers the larger environment. Its job is typically to find a route such as: Start ---> Corridor ---> Door ---> Room ---> Goal Common approaches include: A* Dijkstra Graph search Grid-based planning Sampling-based planning Local Planner The local planner operates closer to the robot and reacts to current observations. It considers: Nearby obstacles Robot velocity Robot footprint Dynamic objects Current trajectory Short-term goal direction Why Both Are Needed Suppose the global path is: Robot -----> Hallway -----> Goal A person suddenly walks into the hallway. The global route may still be valid, but the robot needs to slow down, stop, or temporarily move around the person. That is the local planner's job. Grid-Based Global Planning Represent the environment as a costmap: . . . . . . . . . # # . . . . . # # . . . . . . . . . . . . . . . G . S . . . . . . A planner searches through free cells while assigning higher costs to undesirable regions. Local Planning A local planner can generate multiple candidate trajectories: obstacle ### Robot --> / | \ / | / | candidate trajectories Each trajectory can be scored based on: Collision risk Distance to path Distance to goal Smoothness Velocity Clearance ROS 2 Architecture /map | v /global_planner | v /global_plan | v /local_planner <--- /scan /pointcloud | v /cmd_vel Keep the global and local planners modular so

The investment comes amid Navi plans to go public.

Apply a style when someone navigates from one specific page to another. The idea being it'd make the sources for cross-document view transitions declarative in CSS rather than managing that stuff in JavaScript. CSS Navigation Matching, Early Days originally handwritten and published with love on CSS-Tricks . You should really get the newsletter as well.

Tracking smells in turbulent air takes a keen sense of direction and sharp memory.

Xona aims to deploy 258 satellites into low-Earth orbit as a GPS alternative.

Some of the new features are powered by Google's Gemini AI assistant, which reflects the tech giant's broader push to integrate Gemini across its products while also better positioning Waze to compete with rival services such as Apple Maps.

Lyft details a new pickup experience to improve reliability in gated communities, where 25–30% of rides face routing and access challenges. The system uses mapping signals, boundary detection, and routing improvements to reduce cancellations and coordination overhead between riders and drivers, highlighting how real-world constraints drive evolution in geospatial systems. By Leela Kumili

If you've spent any time building React Native apps, you've already bumped into the question. You're setting up a new project, you need to move users between screens, and suddenly you're 40 minutes deep in a documentation rabbit hole wondering whether to go with the familiar React Navigation setup or take the leap to Expo Router. This article is going to break it all down, no hype, no fanboy energy, just an honest look at both options so you can make the call that actually fits your project. First, What Does "Routing" Even Mean in a Mobile App? On the web, routing is pretty intuitive. You type a URL, the browser goes to a page. Simple. In mobile apps, there's no URL bar, no browser history button, nothing like that. But users still need to move between screens, go back to where they came from, open modals, tab between sections, and all of that has to feel smooth and natural. So in mobile development, routing is basically the system you use to manage how screens stack on top of each other, how state is preserved when you go back, how deep links work, and how the app knows which screen to show based on where the user is in the flow. Think of it like this: routing is "moving between screens while keeping your app's memory intact." When someone logs in, fills out a form, gets distracted and opens a modal, then comes back, the app should remember all of that. Routing is the machinery underneath that makes it happen. In React Native, this doesn't come out of the box. The framework gives you the building blocks, but you have to wire up the navigation yourself. That's where libraries come in. Why Navigation Is Such a Big Deal in React Native React Native apps are essentially single-page applications. Everything runs in one JavaScript thread, rendered to native views. There's no browser doing the heavy lifting of managing history or transitions. You're responsible for it all. Bad navigation kills good apps. A janky transition, a broken back button, a modal that doesn't dismi