Fix compilation failure with Boost 1.90.0

[Copilot]

Boost 1.90.0 reorganized geometry headers, moving multi_point.hpp from boost/geometry/multi/geometries/ to boost/geometry/geometries/. This broke compilation on Alpine Linux and other platforms using BH 1.90.0.

Changes

• weights/VoronoiUtils.cpp: Removed unused <boost/geometry/multi/geometries/multi_point.hpp> include (file doesn't use multi_point types)
• clustering/spatial_validation.cpp: Added explicit <boost/geometry/geometries/multi_point.hpp> include using new path (file uses bg::model::multi_point but relied on transitive includes)

Changes are backward compatible—the new header path exists in older Boost versions.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>compilation failure with new BH 1.90.0 #56</issue_title>
<issue_description>Installing the R package rgeoda on Alpine Linux fails, ending with

libgeoda/weights/VoronoiUtils.cpp:30:10: fatal error: boost/geometry/multi/geometries/multi_point.hpp: No such file or directory
30 | #include <boost/geometry/multi/geometries/multi_point.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
The deprecated geometry/multi headers were removed in Boost 1.89.0.

According to https://www.boost.org/doc/libs/latest/libs/geometry/doc/html/geometry/reference/models/model_multi_point.html, the correct include directive is:

#include <boost/geometry/geometries/multi_point.hpp></issue_description>

<agent_instructions>Please fix it</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes compilation failure with new BH 1.90.0 #56 #10

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[lixun910]

why do you add new include here?

[Copilot]

spatial_validation.cpp uses bg::model::multi_point on line 436 but was relying on transitive includes from <boost/geometry.hpp>. In Boost 1.90.0, the main header may not transitively include all geometry types, so I added the explicit include to ensure the code compiles with both old and new Boost versions.

[lixun910]

why just remove the include? should #include <boost/geometry/geometries/multi_point.hpp> be added here?

[Copilot]

VoronoiUtils.cpp doesn't actually use any multi_point types in its code, so the include was unnecessary and could be safely removed. The old include path was causing the compilation failure, but since the file doesn't use multi_point, adding the new path would just add an unused header.