Skip to content
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

OGR layer algebra: honour PROMOTE_TO_MULTI=YES for Points #10258

Merged
merged 1 commit into from
Jun 22, 2024

Conversation

rouault
Copy link
Member

@rouault rouault commented Jun 20, 2024

@rouault rouault force-pushed the ogr_layer_algebra_multipoint branch from c30e1ba to 800f922 Compare June 20, 2024 18:32
@coveralls
Copy link
Collaborator

Coverage Status

coverage: 69.241% (-0.005%) from 69.246%
when pulling 800f922 on rouault:ogr_layer_algebra_multipoint
into 082d0e7 on OSGeo:master.

@rouault rouault merged commit 46988b5 into OSGeo:master Jun 22, 2024
35 checks passed
@jratike80
Copy link
Collaborator

jratike80 commented Jun 23, 2024

Does promote_to_multi now change all points into multipoints? A shapefile has different shapetype for points and multipoints and I am wondering if that can make
confusion. Multipoint is also a rather uncommon datatype in real world data and it may be that some software and algorithms will have troubles with multipoints, even if they have only one member. And with constrained datastores (shape, PostGIS, GeoPackage) the digitizing tools should be prepared to create multipoints.

Based on my experience and memory, users have not had much problems because points have not been turned into multipoints. I am not sure if this change is for good or bad.

@rouault
Copy link
Member Author

rouault commented Jun 23, 2024

Does promote_to_multi now change all points into multipoints?

yes

@jratike80
Copy link
Collaborator

Well, maybe the new behaviour can give unintentional results only if
a) user has a habit to write PROMOTE_TO_MULTI always, even when working with point data when the argument has not been doing anything, or
b) user works with source data that contains mixed geometries, including points, or
c) if SQL query or layer algebra creates points and user did not think that it can happen.

Maybe there is no need to be worried.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants