Here is the problem: I want to use the tag seamark:type=berth to determine all the places where port authorities allow ships to berth. All good so far. But for any given port, say Port Kembla, I need to distinguish between berths that handle vehicles or containers, with those that handle bulk liquids (oil, gas, etc). I’m not allowed to use cargo=container on node features.
The tag seamark:type=berth often includes vastly different vessel capability. In Sydney Harbour, berths range from ferry terminals in Circular Quay to the Overseas Passenger Terminal. There is a maxlength=350 on the latter which might help distinguish between cargo=passengers of the ferry terminals and the OPT. But how would I restrict my filters to berths that are designed for ships not ferries?
Looking for guidance before I start editing tags that might be reverted later on.
Using the port polygon (https://wiki.openstreetmap.org/wiki/Tag:industrial%3Dport) is not going to work as often one port handles different cargos in different parts of the port. I need to know where the containers, cars, and dry_bulk are being loaded and unloaded.
Thanks Fizzie41 - I think I will go with seamark:berth:goods and assign values that are similar to the tags used for cargo. This will get me to my goal, and hopefully create a dataset that solves the problem of where does road freight start and end (as opposed to berths fed by pipelines and conveyors).
I did go down the https://wiki.openstreetmap.org/wiki/Key:cargo rabbit hole, but it is a secondary attribute that has to be assigned to industrial=port, and industrial=port requires landuse=industrial, and landuse=industrial does not allow nodes.
industrial=port + port=cargo on the area, then cargo=* nodes to show what, where? (cargo= shows as being used 5000 times with 4000 of them being nodes!)
You could even take it a bit further by creating berth so industrial=port as the area, then port=berth + berth=cargo / passengers + cargo=*?
cargo= has been used on =ferry_terminal first. The problem is you shouldn’t use landuse=industrial or industrial=port on individual berths. port= is an attribute for type of ports, not a feature for a part of a part. This style is poor, causing various issues. cemetery= , and playground= are the exceptions. animal= , fitness_station= , and zoo= is visibly troubled.
Awesome detailed response - thank you. Better to get the process established before mapping 82 Australian ports.
I found this too when I reviewed existing locations. Expecting them on the coast, many were on inland rivers of Europe.
From the referenced PDFs, the feature I really want to map is on page 100 of the encoding guide (G.3.19 Terminal) which has a picture of a Real World (container) terminal and a Real World (bulk) terminal. They can be nodes and are landside. In most cases, this will be close to an existing (waterside) berth node.
Certainly, you can start with a point. Only need to remember a “terminal” is the entire landside, that can include multiple berths. Eventually, it can be drawn as an area covering everything. Therefore, don’t create any redundancy. Only 1 point for each “port”/terminal.
As you are using Seamark, you should still have seamark:terminal:goods==containers , =cars, etc, added first. cargo= is for landuse=industrial + industrial=port + port=cargo , when that’s added. They are 2 independent formats existing in parallel.
Strictly, seamark:terminal:goods= should be used on the =terminal . All the =berth will use seamark:berth:goods= .
Also, the =berth will be directly on the perimeter. Eventually, they could also be drawn as areas. which would exist on waters outside the land of =terminal (the new inland waters standard) / =harbour (existing confusion) / =harbour_facility (if we don’t want to follow inland standard yet) . To enclose both, the international standard is hrbare hypothetically =harbour_area , however it has no cargo info directly (likely because a “harbor” can have multiple =terminal , and handle different cargo).
