Hi Malcolm, what do you mean exactly by "Harbour layer database"?
Based on my experience over the last 4 years, there is no public source with a API or such that up to date locode data could be queried. The problem with matching based on port names is horrible, for one thing. What my company does is monitor the UN website for new updates and when detected, the new CSV file is downloaded and processed, to update our database as needed. The UN also has webpages with the locode data, but then you are getting into web scraping if you want to retrieve that metadata dynamically. WorldPortIndex has webpages as well, but web scraping.. they can't be considered to be authoritative... So my recommendation, at least for this locode data, is that it can't be handled dynamically - otherwise we'd be doing it. I guess right now I'd say that my inclination is that locode metadata should go into OSM -- or this Harbour layer database - and then OpenSeamap would have one spot where to get that at least. Locodes are also useful for inland cities and transportation / shipping type applications, so this is a larger topic than just marine related stuff. The script we have is not much and I am CTO so I can do what I want. I see a possible use for OSM in some fashion in the future, so want to contribute to it as well. doug On 04/02/2013 19:22, Malcolm Herring wrote: > Re-posted from thread in tagging list: > > 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 communicate the co-ordinates of this symbol to a separate database > which will overlay an invisible button over that position in the > OpenSeaMap Harbour layer. A right-click on the symbol will then invoke a > pop-up panel that will display the meta-data. The Harbour layer database > will have extracted the metadata form divers public database sources, > including the OSM tags on any feature that invoked the Seamark layer > symbol. This metadata would include LOCODEs where available. > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_jan > _______________________________________________ > Openseamap-maps mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openseamap-maps > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ Openseamap-maps mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openseamap-maps
