-
Notifications
You must be signed in to change notification settings - Fork 24
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
PSP-8194 Add Complete Support for MultiPolygons #4061
Conversation
✅ No secrets were detected in the code. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #4061 +/- ##
===========================================
- Coverage 85.37% 76.79% -8.59%
===========================================
Files 1609 490 -1119
Lines 121154 17912 -103242
Branches 9375 1229 -8146
===========================================
- Hits 103436 13755 -89681
+ Misses 17414 3857 -13557
+ Partials 304 300 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
var newCoords = property.Boundary.Coordinates.Select(coord => _coordinateService.TransformCoordinates(boundaryGeom.SRID, SpatialReference.BCALBERS, coord)); | ||
var gf = NetTopologySuite.NtsGeometryServices.Instance.CreateGeometryFactory(SpatialReference.BCALBERS); | ||
property.Boundary = gf.CreatePolygon(newCoords.ToArray()); | ||
_coordinateService.TransformGeometry(boundaryGeom.SRID, SpatialReference.BCALBERS, boundaryGeom); |
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.
Does it make sense to do this here, or should we just call the new UpdateLocation method?
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.
The UpdateLocation calls the property repository to- well - update the property in the DB. This method is called when we are adding a brand new one as part of a larger parent entity (say an acquisition file that gets a brand new property added).
Do you have a suggestion on how to reuse the UpdateLocation to not call the DB?
Given the scope of these changes, I think we will be better served by pushing this to 5.4, what do you think? |
I was actually thinking the same, I can change the PR to target the 5.4 branch if you agree. I'd rather see this tested with lots of time ahead for fixes etc |
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.
approved, given that tests are coming in a future PR.
yes, lets push it and the story to 5.4, that will give us some increased confidence, given that a lot of our existing integration tests don't test multipolygons. |
ffcd7c9
to
bf32c66
Compare
✅ No secrets were detected in the code. |
bf32c66
to
d96294b
Compare
✅ No secrets were detected in the code. |
Co-authored-by: Smith <[email protected]>
d96294b
to
b7a91cb
Compare
✅ No secrets were detected in the code. |
Tested by temporarily displaying the boundaries in the PSP database as a map layer. I was able to see multi-polygon boundaries being added to the database and displayed correctly on the map
demo.mp4