e-mail from Jim on 2013-1-16:

-----

Back in Nov 2012 I created a local Git repo to manage my geovalidation

code as I was developing it and messing around. Technically I'm pretty

sure there is a way to graft it into the BIEN SVN repo you've been

using, but I don't have time to deal with that now, and anyway there may

be advantages to keeping this separate (much as the TNRS development is

independent). I'm happy to give you access so you can clone the Git repo

yourself if you'd like, but in any event, I just created a 'BIEN Geo'

subproject of the main BIEN project in Redmine, and exposed my repo

through the browser therein. It's currently set as a private project,

but you should be able to see this when logged in:

https://projects.nceas.ucsb.edu/nceas/projects/biengeo/repository

So now you should at least be able to view and download the scripts, and

peruse the history. (If you do want to be able to clone the repo, send

me a public key and I'll send you further instructions.)

I just spent some time improving comments in the various files, as well

as writing up a README.txt file that I hope will get you started. Let me

know if (when) you have questions. As I mention in the README, the

scripts are probably not 100% runnable end-to-end without some

intervention here and there. Pretty close, but not quite. That was

certainly my goal, but given that this was all done in a flurry of a few

days with continual changes, it's not quite there.

Also, the shell scripts do have the specific wget commands to grab GADM2

and geonames.org data that need to be imported into the database to

geoscrub/geovalidate-enable it. But if you want (of for that matter if

you have trouble with downloading anything), I can put the files I got

back in November somewhere on vegbiendev. In fact, although the GADM2

data should be unchanged (it's versioned at 2.0), the geonames.org

downloads come from their daily database dumps IIRC, so what you'd get

now might not be the same as what I got. Probably unlikely to be many,

if any, changes in the high-level admin units we're using, but who

knows.

-----