Where I am and what I do
I live in Auckland, New Zealand and have been spending my time here mainly mapping various parts of Auckland, or anywhere else i might visit.
I am also a member of the nzopengis google group, where most of the discussions around osm in NZ take place. The big topic at the moment is the forthcoming import of LINZ road and cadastral (properties) data for the country.
Alongside mapping areas of Auckland that i visit, i am also maintaining the WikiProject_New_Zealand page, which is intended to help and coordinate OSM mappers in New Zealand.
I occasionally visit Derbyshire, UK and map anything that i can around that area, using a combination of GPS and the NPE maps.
Having seen a dispute recently on the legal-talk mailing list concerning the origin of data, and realising I appear to have zero evidence of collected data (i.e. GPS traces uploaded to osm), I'd better explain my methods. The areas I've collected data for so far (mostly Auckland) have very good Yahoo coverage, so drawing in streets from that is no problem. Street and POI names are collected by me walking round with a mobile phone and typing them in as I pass them; the route is then re-traced on the Yahoo images when I get home and added in Potlatch.
All my notes are available as draft text messages (terrible phone, the only way I have to store notes to myself) - about 150 of them in all. This will be changing in Sept 2008, when I get my GPS, and proper traces, along with geo-tagged photos will be uploaded for all areas I cover.
I've since started uploading all my GPS tracks to OSM.
i started studying at auckland university in 2008, and since then have been mapping its footpaths, buildings, etc university relations hierarchy:
- sector, path, road
Tags to propose
multi storey car park
cutting/embankment as road/rail key
man_made is horribly vague, and overlaps with sport, shop, highway, ..., all of these are man made. i propose to replace man_made with a number of tags:
top-level tag categories all need to be either form-based, or objective-based. i.e. they fall into a category either because of their physical characteristics or their use.
none of these are settled upon in any way, by me or anyone else...just my meanderings, they'll get formalised/finished when i get round to it
- satellite dishes
- telephone cables and poles
fluid storage, distribution and processing??
natural is similar to man_made - it can cover a huge range of features, with little or no distinction for appearance, use, or any other useful categories.
covers things that grow/are alive
- marsh - salt/fresh water
- wood/forest/rainforest (to include single trees and rows of trees) area, node, way
geological_features (maybe a terrible name...)
covers things that aren't alive, but are naturally occurring
lots of tags in waterway are not ways. lots of tags in waterways are not water-anything, but instead related to water activities. proposal to change waterway to water, and add a new category for accessories to water activities
any water, be it still, flowing; narrow, wide; etc.
- river (to replace stream, brook, creek, etc... all redundant, all do the same thing. if distinction is needed, refer to the name, which usually contains river, creek, etc.)
- snow_line - the extent of the snow, at a given time of year (universal date method)
water_accessories (another terrible name...)
anything which is not water, but is related to people's use of water
there is a proposal for a building tag, to define the physical aspect of buildings. the discussion is not going at all well, some people are confusing form with function. i propose:
key=height value=<number of storeys>
key=material value=timber|metal|brick|tile|glass|slate (combinations are allowed)
key=colour value=text or html colour code
key=other value= (freeform tag, for info such as: verandah, balcony, porch,.....)