-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add LineMerger directed option #597
Conversation
It seems like it should be possible to implement this using most of the current |
You're right, and the solution is much simpler than what I did. I still left |
bf663c0
to
47a7b27
Compare
@dr-jts Updated to include API header changes. |
void object::test<1> | ||
() | ||
{ | ||
auto input = GEOSGeomFromWKT("MULTILINESTRING((0 0, 0 100),(0 -5, 0 0))"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you use geom1_
and geom2_
as the variables, the capitest::utility
will automatically clean them up after each test so you can drop the GEOSGeom_destroy
calls.
Looks fine to me. |
Directed line merger implementation locationtech/jts#773
Is it ok to start with C++ implementation and backport to JTS?