From GeoWiki

This section can be seen as a roadmap for development of the GeoTracing platform.

Table of contents

1 Open Source 2 Documentation 3 Features 3.1 General 3.2 Server 3.3 WebClient 3.4 MobiTracer 3.5 TraceBox 3.6 KeyWorx 4 Research 5 Old GeoSkating issues

Open Source

GeoTracing is now Open Source.

• hosting by CodeHaus (done geotracing.codehaus.org) DONE
• cleanup CVS DONE
• migrate to SVN DONE
• migrate Wiki to Confluence
• Determine licensing type for code (LGPL?). DONE
• Determine licensing type for content (Creative Commons?)
• make real roadmap
• make project organisation plan
• release plan
• documentation plan
• Invite more developers (now 3)

Documentation

• determine documentation technology (Wiki/DocBook/XBook)
• write whitepaper
• document architecture
• document protocols
• document JavaScript (JSDoc)

Features

General

• how to deal with time/timezones throughout framework (all UTC?)
• internationalization throughout

Server

• user registration
• map-making daemon (generates maps from all trackpoints)
• location-based triggers (user sets condition like area or point and is triggered through protocol)
• introduce Event service (g_event table) to attach tracks to events (startdate/endate)
• add tagging of anything
• GPX import protocol
• media handling (movie conversion quality, movie thumbnails, image w/h, investigate Scilla)
• support text media
• support configurable POI-types (possibly do away with POIs entirely and use text media + tagging)
• support configurable trackpoint rating (now numbers 1-5)
• export to Google Earth KML
• allow commenting on data items (tracks, media, POIs etc)
• trackpoints should go into table (not in g_track file field)

WebClient

• user registration and login
• user resource management (tracks, media)
• more flexible layout (allow different layouts)
• improve color schemes and all icons
• determine AJAX approach and use of (existing) widget framework (Dojo, qooxdo)
• upload GPX tracks
• manage media (e.g. add/replace photo's to existing tracks) DONE
• manage POIs DONE (POIs are text media with tags now)
• evolve to GMap2 DONE
• resolve collisions like multiple media at one point (see e.g. PanoramaExplorer)

MobiTracer

• allow registration plus download
• use relative screen sizes
• improve GPS info (km/h, direction) (done)
• filter bad GPS data
• show where you are on map (done for Google Maps)
• obfuscate (done)
• make signed ?
• view tracks and other users on map
• send GPS based on criteria: quality, time and movement (send on minimal distance or time)
• move to J2MEPolish

TraceBox

Making MobiTracer and applications for each possible phone/PDA is a dead end. Given all the issues around software platform, high-end requirements (need smartphone with Bluetooth) and per phone/provider GPRS hassle. The TraceBox is planned to be a GPS/GPRS embedded hardware device. Its main function is to connect to a GeoTracing server submit GPS ssamples and dependent on hardware allow a user to submit some parameters. The real application will then be executed on any other device (phone, PDA, laptop) through e.g. a webbrowser using the KeyWorx multi-channel session capabilities. The TraceBox will be a matchbox-size device with a few LEDs, buttons and possibly a one-line display. It should be easy reprogrammable/configurable.

• determine hard/software platform (Siemens TC-series, Telin)
• work out usage scenarios

KeyWorx

These are features of a more general nature that woud be better implemented in KeyWorx base.

• generic query mechanism/protocol (backport GT query, deal with field naming, deal with security)
• general interceptor architecture for Handlers (use for e.g. LBS and notification)
• improve AJAX client
• make KWAdmin AJAX app that is extensible (app can add own menu items/handlers)
• introduce per-server automatic configuration of resource URLs (based on server name/address particular configuration settings are set like the base URL).
• improve security (no clear passwords in config)
• KWAdmin session in DaemonContext
• adapt to standards: use XML schema for protocols
• allow index-setting for fields in in Oase table config
• use JAI i.s.o. ImageMagick
• investigate incorporating Scilla for media management
• image JPEG photo upload should use time in photo as creation time if possible (FLOSS)
• uniform backup/restore (now two mechanisms) through KWadmin

Research

This concerns researching technologies/approaches with the idea of supporting and/or using these.

• using a geospatial database like PostGIS or MySQL spatial
• which/how to support OGC standards (WMS+WFS+WFS-T)
• using KML and Google Earth
• georss
• MapBuilder project
• tiling JS (OSM) openlayers
• using XHTML apps for mobile phones/PDAs (what can be done with AJAX here e.g. Opera Mobile/Platform)

Old GeoSkating issues

(Just kept for nostalgic reasons)

Media

• V List return at import/upload
• V improve media/location query (join media+ location)
• V show date/time
• show thumbnail i.s.i. green dot
• V show inline (in iframe i.s.o. pop-up)
• text/sound import

Commenting

• editing
• showing

Routes

• editing
• showing

GeoRender

• true layers (map, trails, media, comments, routes)
• ability to replay logs animated by day
• showing speeds

Map Menu

• make smart menu/dropdown toolbox

MultiUser

• V add geolog table (called g_track)
• V add geolog protocol + handler
• V make daemon geolistener (listens to geolog table)
• V use KW protocol in mobile client