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.
the community should vote on a member to send to the OSMF board, this person would be rotated once in a while.
Be able to share routes you travel often and find travel partners
the Code-Point Open is a postal geography dataset that features a set of geographically referenced points that represent each of the 1.7 million postcode units in Great Britain. The centre of the postcode unit is derived from the precise coordinates of addresses sharing the same postcode unit in Ordnance Survey’s large-scale address database. Licence detail: UK Crown Copyright with data.gov.uk rights; see www.ordnancesurvey.co.uk/opendata/licence ...more »
Geonames should be made available as its own separate layer that is maintained in osm but as its own separate layer and updated on a regular basis
the GNS layer http://earth-info.nga.mil/gns/html/ should be added as its own layer and made available. all changes to it should be tracked and conflicts merged/managed when new updates come in.
when syncing between two OSM instances we need to be able to import just a single ChangeSet id or all the open ones from a user. We want to be able to see all the non imported ones for one area and review and accept them. We want to be able to also exclude individual ones that have been imported already. A simple web service / form interface could be used for this.
n80: we'd need to keep track of which changesets had been applied and which not
and which are remapping or deletions and should definitely not be applie
All soft in app store are unuseful
add an UUID attribute