Look into hosting tiles on archive.org
People will want to have a public domain OSM layer for only PD data, it will be separate from the CC-BY-SA layer etc and will have rules for when data is promoted (tainted) to a different license. We will want to possibly have versions of the objects if someone copies them into a different license and changes them to track branches of objects.
Sometimes there are changesets that are really strange. It would be cool if we could create Bugtracker tickets from Changeset IDs. This would help to get in contact with the Changeset user and help to revert or fix strange/wrong/vandalism changesets.
you could post the basic data about an osm changeset using a short bounding box the basic data in it and a link to the data in twitter and then aggregate the data. this could use a geohash or something similar to easily select the area.
Look at the google maps api and see if it can be supported by osm.
look into rendering and hosting tiles on the wikipedia toolserver
we should setup a jabber server for fosm to use it with kestrel, or rework kestrel to run over irc
we want the Ability to use GIT or version control to manage small sections of the map.
http://fosm.wikia.com/wiki/Fosm_Wiki the wikia wiki should be less work to prevent spammers
In 2010, Yihua Chen and John Krumm have published a paper at ACM GIS about “Probabilistic Modeling of Traffic Lanes from GPS Traces“. Chen and Krum apply Gaussian micture Models (GMM) on a data set of 55 shuttle vehicles driving between the Microsoft corporate buildings in the Seattle area. The vehicles were tracked for an average of 12.7 days resulting in about 20 million GPS points. By applying their algorithm to this ...more »
for remote places, with bad internet connections, we want to have the main server to be local to the users in the internet. Some users might find that the server in london is slow. they will want simple tools to setup and host a local cache and CPU pool that is used in the larger OSM scheme.