Build a local api proxy that you can tell it to publish your changesets to multiple server, to your blog and to sync and resolve changes and conflicts
we want real time rendering. we want to be able to have changes rendered immediately.
that we can page through and review the changes and rate them.
we want to see all the CS in a area. See if there are deletes or modifications. See if they are modifying or deleting other peoples work.
with a simple ajax API to the backend
The app would be able to
1. flag changesets for revert.
2. flag users for separation/deletion... more »
The OSM planet file is sorted by ID, this makes processing it cumbersom because you need to load in all the ids to know what id is in what geographic location. it would be better to sort the file by geographic location. my idea was to use a geohash as a sorting mechanism. or to use some block system. in any case some sorting would be great.
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.
we need to have a scheduling system for coordinating rendering of tiles. Some People will want to render some parts immediately to fix problems and see the results asap. others will have computers to donate off hours. Others will have old computers to use. others will rent cloud computers for dedicated rendering. Some will want to render only their own town. all these need to be considered.
People will want to import georss feeds into the system and also produce edits as georss.
People will want to post changesets and blogposts with annotations and pictures. they will want to render tiles and show what they have edited. They will want to store the OSM change data in the blogpost and not have to store it in some central server.
we should raise money for hackathons and prizes for implementing these ideas that we find valuable.
Look into hosting tiles on archive.org
we want to subscribe to peoples edits via georss and have them rendered on top of other maps.
we want the Ability to use GIT or version control to manage small sections of the map.
Using semantic web to describe the structure of the tags. Include reasoning engine to evaluate properties. see also linkedgeodata.org and schematroll and other schema tools
we can use geohashs to split and sort the data for easy selection. If the osm data is split into a directory structure based on its geohash then it would be easier to select data based on its location without a database server needed. such a split dataset could be hosted on a simple ftp file server.