<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote
cite="mid:CEEC7E9E-47E2-4740-BFBA-A5B2ED553D0E@nutiteq.com"
type="cite">
<blockquote type="cite">
<pre wrap="">A simple example is that often I'll see a POI node, and I'll go ahead
and draw the building outline and put the data on the building. I draw
the building and delete the node.
</pre>
</blockquote>
<pre wrap="">
Good case. Do you just delete the node without checking whether it has useful tags and relations which need to be copied to the polygon?
</pre>
</blockquote>
<br>
Here's a case where a tool fix could do a world of good.<br>
The Potlatch/2 "R" shortcut does not work to copy tags from a node
to a way.<br>
Converting a POI node to a building outline is thus a skilled task
if you don't want to damage the original tags.<br>
<br>
Imagine instead two new icons in the bottom right corner of
Potlatch/2:<br>
Convert node --> way<br>
Convert way --> node<br>
Which preserve tags. The <a
href="http://wiki.openstreetmap.org/wiki/Talk:USGS_GNIS">GNIS</a>
import data would benefit greatly. Potlatch mappers could take all
those point features and turn them into outlines, but not disturb
the most important keys.<br>
<br>
I'd even like to see a feature in the API to "lock" certain keys.
At the time of import you could declare certain keys (e.g. <b>gnis:feature_id</b>)
as read-only. The API would reject an attempt to modify those
fields. Of course you could still delete the entire feature, but I
think it would be step to preserving data needed for conflation.<br>
<br>
Would import folks get behind improvements to Potlatch to reduce
damage to imported features?<br>
</body>
</html>