-
Notifications
You must be signed in to change notification settings - Fork 16
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
OSM workflow restructuring #769
Conversation
Improve data processing perfs
…in a continous domain when the location is represented by a set of polygons e.g islands
@@ -162,8 +162,8 @@ IProcess neighborsProperties() { | |||
} | |||
query += """$ID_FIELD FROM ( | |||
SELECT | |||
ST_INTERSECTION(a.$GEOMETRIC_FIELD, | |||
b.$GEOMETRIC_FIELD) AS the_geom, | |||
ST_INTERSECTION(st_makevalid(a.$GEOMETRIC_FIELD), |
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.
Shouldn't they made valid before ? We will be back to put makevalid everywhere otherwise no ?
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.
In therory yes, but I don't know why. If I remove the st_valid we have a topology exception
…ve multipolygons. So we check only the dimension
This PR introduces improvements on OSM module :