Major progress to report. One version is the generic unit map, the
other (messier) version is the more finely divided map.
other (messier) version is the more finely divided map.
Friday, April 30, 2010
Friday, April 23, 2010
State of the Map: Clark County, Nevada (2)
Immediately following the previous post, I got this image from the
team's co-leader. This one portends the diversity in the final map
that we have planned.
State of the Map: Clark County, Nevada
The clean version indicates the huge progress that we have made in
developing the generalized map. The 'messy' version portends the
variety of alluvial fan deposit (mainly) that we will soon be
beginning to methodically attribute and carve-out (where
necessary) to create the finished map.
Hooray for the Nevada Digital Dirt Mapping Team!
developing the generalized map. The 'messy' version portends the
variety of alluvial fan deposit (mainly) that we will soon be
beginning to methodically attribute and carve-out (where
necessary) to create the finished map.
Hooray for the Nevada Digital Dirt Mapping Team!
Tuesday, April 20, 2010
State of the Clark County (Nevada) Map
Huge progress in last two weeks. Leveraging the skills of multiple
users in ArcSDE...would be dead without it. A viable example of
'supervised' crowd-sourcing of geologic and gis expertise.
Friday, April 16, 2010
Editor Tracking Tool in ArcGIS.
Presently, I am trying to manage 9 mappers working simultaneously on the Clark County surficial mapping project...the number may swell to about 12 or 15 in the next week or so. This effort is being made possible by using ArcSDE...there is really no other way to do such a thing efficiently...more on that later.
Recently, we discovered an editor tracking tool that can be installed that provides records of who edited what and when. We found it quite late in the game, but now that we have had it for about 3 weeks, it provides a useful and promising perspective on the progress with the map. Each line that is touched by an individual and edited in some way (no matter how small) becomes tagged with that person's ID. Looking at the map symbolized by mappers is interesting, shows progress, and also...well...lets you hone in on potential trouble spots. Also, the fact that if an editor touches a very long line by fixing only a small segment helps motivate the individual to investigate the entirety of the line. Sweet!
The tracking tool can be downloaded from ESRI at: http://arcscripts.esri.com/details.asp?dbid=15694
Here is an example that shows the tool's results as well as some serious progress on this huge, huge, huge map. Did I mention that the map is huge?
Recently, we discovered an editor tracking tool that can be installed that provides records of who edited what and when. We found it quite late in the game, but now that we have had it for about 3 weeks, it provides a useful and promising perspective on the progress with the map. Each line that is touched by an individual and edited in some way (no matter how small) becomes tagged with that person's ID. Looking at the map symbolized by mappers is interesting, shows progress, and also...well...lets you hone in on potential trouble spots. Also, the fact that if an editor touches a very long line by fixing only a small segment helps motivate the individual to investigate the entirety of the line. Sweet!
The tracking tool can be downloaded from ESRI at: http://arcscripts.esri.com/details.asp?dbid=15694
Here is an example that shows the tool's results as well as some serious progress on this huge, huge, huge map. Did I mention that the map is huge?
Subscribe to:
Posts (Atom)