<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 1/26/2015 5:59 PM, Henry Haselgrove wrote:<br>
<blockquote cite="mid:002c01d039d4$f043f5a0$d0cbe0e0$@gmail.com"
type="cite">
<p class="MsoNormal">The purpose of this email is to announce a
plan to import a subset of approximately 10,000 of those
features.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p>Here is a link to the wiki page:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p><a moz-do-not-send="true"
href="https://wiki.openstreetmap.org/wiki/Import/South_Australian_Waterbodies">https://wiki.openstreetmap.org/wiki/Import/South_Australian_Waterbodies</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p>Thanks in advance for any
feedback you have.<o:p></o:p></p>
</blockquote>
Hello,<br>
<br>
You are proposing to use bulk_upload.py. Have you tested it on the
dev servers? It is known for being tricky. You will also need to
make sure that your changesets are a reasonable size, probably under
10 000.<br>
<br>
I reviewed the .osm file, and noted a few things<br>
<br>
- Some features have a name of (disused) and appear disused<br>
<br>
- I selected random dams, and about 30-40% didn't have any sign of
water on Bing. I'm aware of the cyclical nature of water features in
Australia, but several of them showed no signs of water nor did they
seem like a likely location to have a new dam built.<br>
<br>
- Other features did not have a great accuracy rate, although it is
harder to tell wetlands from the air<br>
<br>
- Many features are badly overnoded (e.g. the water at -34.21985
140.35764). A simplify with a 2m threshold in JOSM brought the
number of nodes down ten-fold for some features.<br>
<br>
- Best practice would not be to include datasa:FEATURECOD and
datasa:OBJECTID<br>
<br>
- Opinion is divided on if source is necessary with a source tag on
the changeset<br>
<br>
- What kind of plans are there for updates?<br>
</body>
</html>