[postgis-devel] Creation of standard set of geometries for testing? Interested?

Nyall Dawson nyall.dawson at gmail.com
Tue Oct 20 20:53:16 PDT 2015


On 21 October 2015 at 11:19, Paragon Corporation <lr at pcorp.us> wrote:
> I like the idea though I'm not sure we can use it that easily in our regular tests.

I'd love to get you on board with this, so I'm happy to adapt in away
way that would help!

>
> 1. In the garden tests I have I have a set of geometries hard-coded, but did actually want to move these out to a file for easier testing and since I plan to do that anyway, might be just as easy for me to pull it from a csv from some other repo.

I should have said - I'm not sure CSV is the best format... maybe JSON
with some python scripts to format the data into different outputs (eg
the csv used by the QGIS tests) would be a more appropriate choice.
What do you think?

>
> 2. Hadn't really thought of our tests licensing.  Technically they are all GPL like the rest of our code base, but it seems silly to me not to have those public domain.
> Though I'm not sure what kind of headache we'd have changing the license on those.

Yeah... I'm not sure either. I'm not even sure if there'd be issues
copying arbitrary geometries such as these and changing the license.
But then, I'm not a copyright lawyer ;) Maybe we could make a derived
set by slightly altering the existing geometries (such as adding 1 to
all the coordinates)... would that help?

Nyall





>
> Thanks,
> Regina
>
>
>
>
> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Nyall Dawson
> Sent: Tuesday, October 20, 2015 7:57 PM
> To: postgis-devel at lists.osgeo.org
> Subject: [postgis-devel] Creation of standard set of geometries for testing? Interested?
>
> Hi PostGIS crew,
>
> I've been looking at building up QGIS' library of unit tests against its geometry engine, and as part of this I need a whole collection of reference geometries along with their expected area/length/perimeter/num geometries/num rings/num nodes/etc...
>
> I initially started by copying a lot of geometries from regress/measures.sql, regress/regress.sql and regress/tickets.sql than added a bunch of geometries from existing QGIS tests plus some missing geometry types to build up this list:
>
> https://github.com/qgis/QGIS/blob/master/tests/testdata/geom_data.csv
>
> Now, I'm thinking this might be a good sub-project which we could share (possibly other projects like GEOS and turf may also be interested). I'd definitely find it useful to have one master set full of a large variety of possible geometries and the expected values for these, which could be built up over time to cover more and more corner cases/oddities.
>
> So my questions are:
> 1. Would PostGIS devs find this useful? Are you interested in being involved with this?
> 2. Would there be any licensing issue with using the geometry from the PostGIS tests in a public-domain reference data set? (I'm thinking public domain would be the best license for this dataset)
>
> Nyall
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/postgis-devel
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/postgis-devel



More information about the postgis-devel mailing list