- orientation is in radians
- placement is text justification, like on a keyboard numpad
tag node as `name=fields.name`? what else?
RP: some of these will be covered by place=locality (obvious ones which spring to mind in NZ are Harp of Erin, Greenwoods Corner, Cuthill corner
most are irrelevant though, and are only a shortcut to including data we have from elsewhere
Glen: I say we don't import this for now. I think what we can do though is have a task on the wiki to go back and process this file after everything else has been done and see if we can pick up the interesting bits.
HB: ok, everything else has now pretty much been done.
Some of these POI seem to be repeats of other layers, others seem to be unique to this layer. here are some examples from the Chathams:
k="name" v="Old stone cottage"
k="name" v="Basaltic dyke"
k="name" v="Moriori rock carvings"
k="name" v="Abandoned flying boat base"
k="name" v="Rocks with fossils"
k="name" v="Nature reserve"
k="name" v="Mineral spring"
k="name" v="Moriori tree carvings"
k="name" v="Historic reserve"
k="name" v="Fish factory"
Presumably, when overlap exists, they will be merged with the already-uploaded features they belong to on a case-by-case basis (e.g. with existing building=yes). As they seem to be pretty much free-form I don't see much point in trying to map the tag names automatically. Cleaning script for common generics added in the OSM wiki, URL is above.
Uploaded for Chathams 8 June 2010 (HB).
uploaded for the mainland 31 March 2011 in changeset 7715319 (HB) -- let the massive merging task begin.
Uploaded for the Antipodes 3 Sept 2012 in changeset 12963917 (HB).
Peter S wrote on the NZOGPS ml:
> The point coords describe the left, vertical lower case center location of
> the label as it was applied to the 260 series maps, and usually to be found
> in the most blank spot on the map near the proper location, the offset can
> be literally kilometers away.
HB 18 Aug 2012: updated for new linz data dump field names. (most are now gone)