Better story for creating complex spatial types

[roji]

According to your documentation, it would seem that creating spatial types beyond GeometryPoint pretty much requires one to download a separate SpatialFactory.cs file from your test suite. It's not an amazing user story for a library to not come with decent means to create its own types - does it make sense to simply include SpatialFactory.cs inside the library?

[AlanWong-MS]

@roji, thanks for bringing this up. The SpatialFactory.cs file that you linked does seem to have valuable code that could belong in the library itself. A good point from here is to open a PR with the proposed change, and then we can take a more formal look at it.

[roji]

Hi Alan, thanks for the quick answer.

I've looked inside, and SpatialFactory seems to cover a lot of internal complexity. The API it exposes seems to be pretty good, so it could be a matter of just including it into your package - unless you want to review the API and see if it could be improved. I'm not sure exactly what value I can bring to this, though...

/cc @divega @ajcvickers

[xuzhg]

Closed as duplicated to #509.