Project

General

Profile

1 7254 aaronmk
e-mail from Jim on 2012-11-16:
2 6236 aaronmk
-----
3
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.
4
5
Here is the essential schema info:
6
7
 decimallatitude double precision
8
 decimallongitude double precision
9
 country text
10
 stateprovince text
11
 county text
12
 countrystd text
13
 stateprovincestd text
14
 countystd text
15
 latlonvalidity integer
16
 countryvalidity integer
17
 stateprovincevalidity integer
18
 countyvalidity integer
19
20
The first 6 columns are identical to what you provided me as input, and if you do a projection over them, you should be able to recover the geoscrub_input table exactly. I confirmed this is the case in my database, but after importing on your end you should double check to make sure nothing screwy happened during the dump to CSV.
21
22
The added countrystd, stateprovincestd, and countystd columns contain the corresponding GADM place names in cases where the scrubbing procedure yielded a match to GADM. And the four *validity columns contain scores as described in my email to the bien-db list a few minutes ago.
23
-----
24 7254 aaronmk
25
e-mail from Jim on 2012-11-16:
26
-----
27 6236 aaronmk
Attached is a tabulation of provisional geo validity scores I generated for the full set of 1707970 geoscrub_input records Aaron provided me a couple of weeks ago (from schema public.2012-11-04-07-34-10.r5984). This goes all the way down to level of county/parish (i.e., 2nd order administrative divisions), although I know the scrubbing can still be improved especially at that lower level. Hence my "provisional" qualifier.
28
29
To produce these scores, I first passed the data through a geoscrubbing pipeline that attempts to translate asserted names into GADM (http://gadm.org) names with the help of geonames.org data, some custom mappings, and a few other tricks. Then I pushed them through a geovalidation pipeline that assesses the proximity of asserted lat/lon coordinates to their putative administrative areas in cases where scrubbing was successful. All operations happen in a Postgis database, and the full procedure ran for me in ~2 hours on a virtual server similar to vegbiendev. (This doesn't include the time it takes to set things up by importing GADM and geonames data and building appropriate indexes, but that's a one-time cost anyway.)
30
31
I still need to do a detailed writeup of the geoscrubbing and geovalidation procedures, but I think you have all the context you need for this email.
32
33
My validity codes are defined as follows, with the general rule that bigger numbers are better:
34
35
For latlonvalidity:
36
-1: Latitude and/or longitude is null
37
 0: Coordinate is not a valid geographic location
38
 1: Coordinate is a valid geographic location
39
40
For countryvalidity/stateprovincevalidity/countyvalidity:
41
-1: Name is null at this or some higher level
42
 0: Complete name provided, but couldn't be scrubbed to GADM
43
 1: Point is >5km from putative GADM polygon
44
 2: Point is <=5km from putative GADM polygon, but still outside it
45
 3: Point is in (or on border of) putative GADM polygon
46
47
Importantly, note that validity at each administrative level below country is constrained by the validity at higher levels. For example, if a stateprovince name is given but the country name is null, then the stateprovincevalidity score is -1. And of course, if a point doesn't fall within the scrubbed country, it certainly can't fall within the scrubbed stateprovince. To put it another way, the integer validity code at a lower level can never be larger than that of higher levels.
48
49
You could generate this yourself from the attached data, but for convenience, here is a tabulation of the lat/lon validity scores by themselves:
50
51
 latlonvalidity   count
52
             -1       0
53
              0    4981
54
              1 1702989
55
56
... and here are separate tabulations of the scores for each administrative level, in each case considering only locations with a valid coordinate (i.e., where latlonvalidity is 1):
57
58
 countryvalidity   count
59
              -1  222078
60
               0    6521
61
               1   49137
62
               2   23444
63
               3 1401809
64
65
 stateprovincevalidity   count
66
                    -1  298969
67
                     0   19282
68
                     1  107985
69
                     2   34634
70
                     3 1242119
71
72
 countyvalidity   count
73
             -1 1429935
74
              0   61266
75
              1   24842
76
              2   12477
77
              3  174469
78
-----
79 7253 aaronmk
80
e-mail from Jim on 2013-1-16:
81
-----
82
Back in Nov 2012 I created a local Git repo to manage my geovalidation
83
code as I was developing it and messing around. Technically I'm pretty
84
sure there is a way to graft it into the BIEN SVN repo you've been
85
using, but I don't have time to deal with that now, and anyway there may
86
be advantages to keeping this separate (much as the TNRS development is
87
independent). I'm happy to give you access so you can clone the Git repo
88
yourself if you'd like, but in any event, I just created a 'BIEN Geo'
89
subproject of the main BIEN project in Redmine, and exposed my repo
90
through the browser therein. It's currently set as a private project,
91
but you should be able to see this when logged in:
92
93
https://projects.nceas.ucsb.edu/nceas/projects/biengeo/repository
94
95
So now you should at least be able to view and download the scripts, and
96
peruse the history. (If you do want to be able to clone the repo, send
97
me a public key and I'll send you further instructions.)
98
99
I just spent some time improving comments in the various files, as well
100
as writing up a README.txt file that I hope will get you started. Let me
101
know if (when) you have questions. As I mention in the README, the
102
scripts are probably not 100% runnable end-to-end without some
103
intervention here and there. Pretty close, but not quite. That was
104
certainly my goal, but given that this was all done in a flurry of a few
105
days with continual changes, it's not quite there.
106
107
Also, the shell scripts do have the specific wget commands to grab GADM2
108
and geonames.org data that need to be imported into the database to
109
geoscrub/geovalidate-enable it. But if you want (of for that matter if
110
you have trouble with downloading anything), I can put the files I got
111
back in November somewhere on vegbiendev. In fact, although the GADM2
112
data should be unchanged (it's versioned at 2.0), the geonames.org
113
downloads come from their daily database dumps IIRC, so what you'd get
114
now might not be the same as what I got. Probably unlikely to be many,
115
if any, changes in the high-level admin units we're using, but who
116
knows.
117
-----
118 7324 aaronmk
119
e-mail from Jim on 2013-1-18:
120
-----
121
Regarding calculation of precision estimates for counties, I just resuscitated something I had started working up (with Bob's inspiration) back on the final Friday afternoon of the Nov 2012 BIEN WG meeting at NCEAS. Using GADM2 administrative polygons data (http://www.gadm.org), this calculation works by first reprojecting a given county into whatever UTM zone contains the county centroid, then (just as Bob suggested in his email) computing the distance from the centroid to the most distance point on the county border.
122
123
Have a look at the attached CSV of results for US counties, and mull over whether this seems useful. Maybe even sanity-check against your favorite county or two! For those who care, the SQL statement is pasted below my sig, along with a 'utmzone' function that I borrowed from the PostGIS wiki.
124
125
Note that I did the whole UTM reprojection bit because the GADM2 data are in a geographic projection, for which planar distance calculations aren't in meaningful units and aren't consistent across latitudes. Although postgis provides some functions that know how to work directly on the WGS 84 ellipsoid and don't require a projection, the exact functions we need for this aren't available.
126
127
Some misc things that were in my head as I did this:
128
129
1. This precision measure is conservative insofar as it basically describes a circle of radius equal to the precision value, and most counties will only actually occupy a fraction of the circle depending on their shape -- think of long skinny counties, or those which have an offshore island under their jurisdiction. Totally reasonable! But this _is_ just one conception of what "precision" means for county data.
130
131
2. In GADM2, counties are the lowest admin level for the US, making things easy. But other countries have additional levels below county/parish, meaning that we'd need to add a step that first unions those smaller polygons into a single polygon for the county/parish.
132
133
3. I was a little concerned about the, um, precision of these UTM-based precision estimates. Although UTM is convenient insofar as a local zone can be applied when looking at a given smallish area (like a county), distance is not perfectly preserved in this projection, which suffers from distortion as you approach the edges of a given zone. However, I just did some testing of the UTM distortion using points at roughly opposite east-west ends of Santa Barbara County. SB makes for a decent test case because it's a fairly large county that lies across two UTM zones. Distance between the test points I used is 100833 meters in UTM, and 100782 meters using the more accurate ellipsoid calculation. So I'm pretty confident we could say that our county precision estimates are themselves precise to 1 km (and probably usually much better than that), which I assume is fine?
134
135
As an aside, I was curious to see Franklin County, VA, showing up as having one of the worst precision values. Turns out GADM2 counts Franklin County as including the independent city of Franklin located a few hundred km east (http://en.wikipedia.org/wiki/Franklin,_Virginia). What can I say, anything we do is only as good as our inputs.
136
137
Cheers,
138
Jim
139
140
141
-- generate precision estimates for all US counties
142
-- (requires utmzone function, defined below)
143
SELECT name_1 AS state, name_2 AS county,
144
       ROUND(ST_Length(
145
         ST_Longestline(
146
           ST_Transform(geom, utmzone(ST_Centroid(geom))),
147
           ST_Centroid(ST_Transform(geom, utmzone(ST_Centroid(geom))))
148
         )
149
       )::numeric/1000, 3) AS error_km
150
  FROM gadm2
151
  WHERE name_0='United States'
152
  ORDER BY state, county;
153
154
-- function taken from postgis users wiki
155
CREATE OR REPLACE FUNCTION utmzone(geometry)
156
   RETURNS integer AS
157
 $BODY$
158
 DECLARE
159
     geomgeog geometry;
160
     zone int;
161
     pref int;
162
163
 BEGIN
164
     geomgeog:= ST_Transform($1,4326);
165
166
     IF (ST_Y(geomgeog))>0 THEN
167
        pref:=32600;
168
     ELSE
169
        pref:=32700;
170
     END IF;
171
172
     zone:=floor((ST_X(geomgeog)+180)/6)+1;
173
174
     RETURN zone+pref;
175
 END;
176
 $BODY$ LANGUAGE 'plpgsql' IMMUTABLE
177
   COST 100;
178
-----
179
180
e-mail from Jim on 2013-1-18:
181
-----
182
See attached, same as before but now with centroid coordinates (after
183
back-transforming from the local UTM zone to WGS84), along with their
184
calculated precision in km. Note that these centroids may differ from
185
what other authorities claim, because of differences in the method
186
and/or differences in the input polygons.
187
188
Revised CSV attached, revised SQL statement below.
189
190
Cheers,
191
Jim
192
193
SELECT name_1 AS state, name_2 AS county,
194
       ST_Y(ST_Transform(ST_Centroid(geom), 4326)) AS latitude,
195
       ST_X(ST_Transform(ST_Centroid(geom), 4326)) AS longitude,
196
       ROUND(
197
         ST_Length(ST_Longestline(geom, ST_Centroid(geom))
198
       )::numeric/1000, 3) AS error_km
199
  FROM (
200
    SELECT name_0, name_1, name_2,
201
           ST_Transform(geom, utmzone(ST_Centroid(geom))) AS geom
202
      FROM gadm2
203
      WHERE name_0='United States') AS gadm2_utm
204
  ORDER BY state, county
205
-----