Coverage remained the same at 80.925% when pulling 9dd9a0c on mwtoews:appveyor into 10d6ea9 on Toblerity:master.

This looks good to me, I lack the Windows and AppVeyor expertise that might be needed to see any problems. For my part: I'll work on setting up AppVeyor support for this repo.

Related: I recently acquired the https://github.com/shapely organization and am curious to know what you'd like about moving the repo there. Toblerity is pretty obscure and shapely seems like a more normal organization name for the project and its related projects.

@sgillies when an AppVeyor account is created and linked to this repo, I'll add another commit to add a build status badge to README.rst and also trigger the first build.

As for potential repo move, it's your call, but I don't see any issues with it. Two things to double-check if links get redirected (e.g. would https://github.com/Toblerity/Shapely/pull/819 navigate to https://github.com/shapely/shapely/pull/819?). The second check is to ensure the issue and PR numbers are not reset to 1. My hunch is that neither of these are issues if you transfer an existing repo. Also, would Fiona and rtree follow along to the new organization name?

I'd also suggest renaming this repo name from titlecase "Shapely" to lowercase "shapely". In a possibly related curiosity, Fiona and rtree shows how many other projects depend on them with a "Used by" button at the top of the main repo website. Why does Shapely not show this?

@mwtoews I created a new "frs-ci" account on AppVeyor, made each of us members of the team with admin role, and created a new project: https://ci.appveyor.com/project/frsci/shapely.

As to the GitHub "used by" button, my understanding is that it may (or may not?) appear at some future time. It seems to be a slow rollout.

This PR is now ready to be merged. Full build takes about 1 hour, but the GEOS builds are cached, so subsequent builds shouldn't take too long (~1 min x 8 in current matrix).