[HOT] GNS name merging discussion thread

[Blake Girardot]

On 8/14/2014 12:51 PM, Ralf Stephan wrote:
> Good idea, that thread. I have a question: working in an area that
> already has plenty
> placements from the old topo map and full coverage in OSM, I wanted to add
> source=GNS to the places I can confirm using GNS. But only one source
> tag is appropriate, so what to do?

My understanding is that when there is a node already existing for the 
place in question you should check that that the new GNS node does not 
have any additional alternate names and if it does use the 'merge' 
(m-key) to merge them.

You can also merge them if you only want to add the source GNS to 
confirm you saw it in a GNS file as well.

when you merge you will get a dialog that shows you fields not in the 
existing node and fields that conflict with each other. For the source 
filed, just select "all" from the pop down menu and it will put:

source=topo;GNS

into the source field.

You could also just do it by hand, but Andrew mentioned merging was 
better for history reasons.

I have also been resolving the place=village v. place=hamlet conflict by 
making it a hamlet since all the gns nodes are hamlets.

Protip: When you merge two nodes, you use the 'shift' key to select the 
2nd node and it is the 2nd node that will stay on the map after merging 
(it becomes the 'target' node), the first node selected will be the one 
that disappears.


> Also, in one case (Sanga) there were two candidates, one already
> placed with tag "Topo", but from GNS I would say a different hamlet.
> So, I simply place it there, so that there are two differing
> placements? Or does GNS have priority and I can delete the other?

I don't quite understand this question.

You think there were two hamlets that on the map were basically attached 
to each other geographically? I have seen examples of that.

Or you are saying, now that I read it again, that GNS dropped a node 
clearly near/on a hamlet that already had a hamlet tag with a different 
name.

In that case, you have to decide what to do.

I have consulted the JOG map and used that name so it was consistent 
across resources field people might be using and then put the prior 
existing name in an alt_name_1= tag. That works well especially if they 
are similar names, different spellings.

If it is a totally different name, then I would do what you did, put the 
GNS node right there next to the existing node, but make sure it gets 
the 'fixme=Confirm name' tag and a note that explains the problem.

Cheers,
Blake