Doug,
Since you're pretty knowledgable about this topic, it'd probably also be
good if you could flesh out the harbor:LOCODE page on the wiki (
http://wiki.openstreetmap.org/wiki/Key:harbour:LOCODE). It's part of this
big harbour proposal: wiki.openstreetmap.org/wiki/Proposed_features/Harbour
On 04/02/2013 18:26, Douglas Fraser wrote:
The data management issues are important, so I'm inclined to update the
wiki page to direct people to OpenSeamap as that seems like a more
logical place to keep specialized metadata like this and they'd be more
inclined to keep the data updated.
well, I'd like to contribute but I don't want to stomp all over already done work - we have a fairly complete and
authoritative set of LOCODEs, including the shipping carrier specific ones (shipping companies feel free to make up
their own set of LOCODEs sometimes)
so the big question is where
2013/2/4 Douglas Fraser doug.fra...@tarisoga.com:
as for LOCODE and locode, it is an acronym and so I tend to capitalize it.
but if iata isn't... There are LOCODE / locode / harbour:locode / unlocode
tags - what are the general guidelines about cleaning up tag confetti?
general tagging
On 04/02/2013 18:54, Douglas Fraser wrote:
Have design decisions been made?
Only the design outline has thus far been discussed. In summary, any
feature tagged as a port, harbour, marina or anchorage will have the
relevant symbol rendered on the OpenSeaMap Seamark layer. The renderer
will
Followup to my post:
I am here at the London OSM Hack Weekend and spoke to someone who explained
to me the larger issues and questions about importing / updating metadata
like LOCODEs that can't be surveyed - i.e. data where managing the process
of keeping it current may be troublesome.
I
