We want to support many layers of the map and render them separately. we want to be able to combine layers and have masks for doing that.
I was just warned for discussing this site on the mailing list. I cannot belive that it would go against some rules to talk about improving OSM. we should be able to discuss alternative ideas for OSM on the mailing list.
Moderation should be community lead and follow the maximum about... more »
We want to view the changes in an area, like the itoworld tool does, but as a central part of the system. http://www.itoworld.com/static/openstreetmap_tools/osm_mapper.html we need to be able to subscribe to the changes as a georss feed
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
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.
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 »
capture the data that will be deleted and make sure that the maps will be able to be used in the future.
people will want to easily and graphically review the deletion history of the edits and rescue deleted data.
People want tools for merging and comparing layers. they will want to see differences and approve them.
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.