Collaborative Maps: Some Initial Research

1
Collaborative Maps Some Initial Research

• Familiarization Brainstorming

2
Some questions

• The CORK encapsulation structure seems to allow
  easy adaptation of single-user programs can we
  do this simply by just storing an apps methods
  into a database and wrapping everything with CORK
  objects?
• How is this tool different from the paint tool
  with layers? Is it just a more advanced paint
  tool?
• Is it vector/raster compatible?
  Latitude/longitude?
• Should we study GIS tool design? (eg. GeoVISTA?)
• Objects Database or XML or GIS objects?
• Navigation issue is a better key-id file
  structure possible?
• Please explain Bridge and the various CORK layers
  as applied to this map editing tool

3
Goal Find Comparable Tools?

• What categories of single-user tools?
• GIS (including GIS database pools)
• Raster/vector modeling
• CAD
• 3-D Modeling

• What categories of collaborative tools?
• Joint Editing Systems (CMS-related)
• Extensions of CAD or GIS software
• Multi-user online 3D environments (games)
• Search engines for other uses, databases
• WYSIWIS for instructor v. student permissions

4
Examples of whats out there

• Toucan Navigate
• http//www.infopatterns.net/Products/ToucanNavigat
  e/TNDataSheet.pdf
• commercial Groove software, best relevant tool
  found
• Comprehensive interface
• Features
• Co-navigation options
• Sharing map databases
• Customize layer options
• Map item details
• Zoom
• Address look-up
• Editing window

5
More examples of whats out there

• CAD Synchronous Collaboration tools
• AutoVUE, CoCreates OneSPACE, ArcView, etc.
• Synchronous CMAP Tools http//cmap.ihmc.us/mapinde
  x.html
• GeoVISTA Studio http//www.geovistastudio.psu.edu/
  jsp/index.jsp
• Geocollaboration multi-modal GIS CSCW

6
Task Analysis Projects Already Done

• Book IT Roadmap to a Geospatial Future
• Report by National Center for Geographic Info
  Analysis http//www.ncgia.ucsb.edu/Publications/T
  ech_Reports/95/95-14.pdf
• Outlines usability issues
• Contact them and see what info they have on
  current research?
• How does current theory on collaborative spatial
  decision-making and multi-criteria
  decision-making apply to making a toolkit?
• They discuss the collaborative solution-seeking
  PROCESS
• Stages that might apply to map interface uses,
  processes
• 1) Strategizing getting background info,
  approach
• 2) Exploration generate solutions
• 3) Convergence narrowing focus, evaluating,
  interpolation

7
Clarification of goals

• What is the immediate goal?
• What is the audience and environment and how
  diverse are their skill levels?
• What were the limitations and advantages of the
  previous tools?
• What would be best to imitate?
• Can we streamline the whole process of adapting
  single-user apps to Bridge?
• What are the datasets like?

8
Scenarios, Possible Tools

• Simple
• Movable objects, fronts
• Textboxes
• Cut Paste
• Zooming in
• Changing angles
• Selecting shapes
• Snap to map lines

• Slightly harder
• Radar lines
• Ruler and spatial measurements
• Background grid
• Linking to other maps
• Key features or region database
• Navigator options baton passing vs. synchronous

• Harder
• Contours related GIS data
• Pixelated building view
• (eg. Habbo, SimCity)
• Change over time, Interpolation
• Synchronizing differing displays
• (eg. Ground level vs. top level)
• Building custom views and simulations

• How about an option to add more tools if
  necessary but to keep the interface simple
  otherwise? (scaffolding)

9
Potential Applications

• Engineering design
• Scientific modeling
• Building design
• Library interfaces
• Land surveys
• Meterology
• Transportation
• Graphic design
• Exploratory collaborating
• Collaborative database mining

• Business Forecasting
• Medical collaboration
• Scientific modeling
• Building design
• Library interfaces
• Shared virtual spaces
• Historical tracing
• Co-editing
• Website/graphic design
• Better concept mapping

10
How Do We Get There?

• Any relevant background information
• Design Framework CORK, Bridge
• Timeline
• Design document?

11
Available Options

• Get GeoVISTA code, adapt to Bridge?
• Make simpler tools from scratch first to discover
  implementation issues on a smaller scale?
• Get a licensed copy of Toucan Navigate from
  infopatterns?

12
Notes from the Meeting

• Cork
• Single-user apps can be adapted only if
• Code is in JavaBeans with clear-cut set/get
  mechanisms

• Latitude/Longitude/Elevation
• GIS v. Shapefiles v. SVG?
• What kinds of metadata come with these types?
• Elevation data? Vectors?
• Explore open-source solutions like GeoTools,
  OpenMap, contact GeoVISTA

13
Notes from the meeting (contd)

• Not just for the GIS community
• Community groups, Historical society, Teachers

• Bridge file structure
• better user readability
• permissions verification and easier deletion
• (Maybe an id-based database would also be useful
  depending different types of kind of map data for
  networking nodes)

14
Notes from the meeting (contd)

• Coding
• What will be the necessary shared objects?
• There are things we dont need to share like map
  shapefiles that are too big

• Current work
• Developing a web version of the map for the
  historical society
• Zoom features on the web version
• Panning
• Snapshots/Thumbnails

15
Next Steps

• Meet with GeoVista Studio developers
• (see Lus agenda email)
• Get some standard map files which format is
  best?
• What tools are absolutely useful?
• Get their sourcecode. Is their code CORK-worthy?
• Ask them about comparable tools
• Contact Toucan Navigate about a demo and possible
  collaboration
• Meeting on using CORK on Monday
• What are the multiple layer replication features
  and how to identify good single-user apps to
  possibly adapt?