Revision 11168
Added by Aaron Marcuse-Kubitza over 10 years ago
| README.TXT | ||
|---|---|---|
| 1 | 1 |
see also: |
| 2 | 2 |
http://wiki.vegpath.org/2012-11-09_conference_call#Geovalidation |
| 3 | 3 |
|
| 4 |
mailto:administrator@johndonoghue.net?John_Donoghue.2012-4-3:17:05.Re:+[Bien-db]+VegBIEN+validation+utilities |
|
| 5 |
----- |
|
| 6 |
my geographic coordinate validation routines involved passing data between BIEN2 (MySQL) to ArcGIS (for spatial joins) to PostGIS (for spatial overlay via geo-aware SQL scripts, and back to BIEN2. It wasn't a pretty system but it was the only way to work around the limitations we had for doing true spatial work in MySQL. If BIEN3 was implemented in PostgreSQL (with PostGIS extensions), I think we could implement the whole workflow in a series of SQL scripts. |
|
| 7 |
----- |
|
| 8 |
|
|
| 4 | 9 |
e-mail from Jim on 2012-11-16: |
| 5 | 10 |
----- |
| 6 | 11 |
As a quick but hopefully sufficient way of transferring the geoscrub results back to you, I dumped my geoscrub output table out to CSV and stuck it on vegbiendev at /tmp/public.2012-11-04-07-34-10.r5984.geoscrub_output.csv. |
Also available in: Unified diff
inputs/.geoscrub/_src/README.TXT: added e-mail from John Donoghue with general description of the BIEN2 geovalidation workflow