Great question! I’ve run into this exact issue with the Snap to Road API before—let’s break down why you’re missing points and how to fix it:

Common Reasons for Missing Points #

• Points are too far from any road: The Snap to Road API automatically filters out points that fall outside its matching radius (usually hundreds of meters from a mapped road). If a point has no valid road to snap to, it gets excluded from the results.
• Overly dense consecutive points: If multiple input points are clustered extremely close together on the same road segment, the API simplifies the path by merging redundant points to create a smoother, more logical road-aligned route.
• Path simplification is intentional: Snap to Road is built to generate a coherent road-following path, not to return a 1:1 match for every input coordinate. It prioritizes route flow over preserving every single raw point you send.

Actionable Solutions to Retrieve All Matching Results #

1. Check the API Response for Warnings #

First, dig into the full API response—look for warnings or error fields. The API often explicitly lists which points were skipped and why, which will help you target exactly which coordinates need adjustment.

2. Fix Outlier Points #

For points that are too far from roads:

• If your use case allows, manually tweak the coordinates to be closer to a known road.
• Use the Geocoding API to resolve the outlier to the nearest accessible road location before passing it to Snap to Road.

3. Split Your Request into Smaller Batches #

Instead of sending all 99 points in one go, split them into smaller batches (like 20-30 points per request). This reduces the API's need to simplify dense clusters, as each batch has fewer points to process and optimize. You can then combine the results from each batch to get your full set of snapped points.

4. Switch to the Nearest Roads API (If You Need 1:1 Matches) #

If your priority is getting a matched point for every single input coordinate (rather than a continuous road path), the Nearest Roads API is a better tool. This API returns the nearest road coordinate for each input point, ensuring you get a result for every valid coordinate (as long as it’s within a reasonable distance from a road).

5. Enable Interpolation (For Filling Path Gaps) #

If you just need a complete road path (not the original missing input points), add the interpolate=true parameter to your Snap to Road request. This inserts extra points along the road between your snapped results to create a continuous path, though it won’t recover the original excluded input points.

内容的提问来源于stack exchange，提问作者Matt Westlake