<div dir="ltr"><div><i>1. Arn't the building polygons already available? I see large buildings<br> <<a href="http://data.ottawa.ca/dataset/large-buildings">http://data.ottawa.ca/dataset/large-buildings</a>> and the topographic DWG<br> file <<a href="http://data.ottawa.ca/dataset/cad-topographic-data">http://data.ottawa.ca/dataset/cad-topographic-data</a>> which contains<br> buildings.<br></i><br>See previous email<br><br><i> 2. If this<br> <<a href="https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Plan%20is%20still%20the%20import%20plan">https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Plan%20is%20still%20the%20import%20plan</a>><br> is still the import plan, it should be gone through and updated.<br></i><br></div>It will once data is released.<br><div><br> <i>3. Should make use of the changeset tags<br> <<a href="https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags">https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags</a>><br> Most importantly type and url. For example:<br><br> comment=Import building polygons for Ottawa, Canada. Importing<br> non-existant polygons <or> Conflating with existing polygons<br> type=import<br> url:en=<a href="https://wiki.openstreetmap.org/wiki/Canada">https://wiki.openstreetmap.org/wiki/Canada</a>:<br> Ontario:Ottawa/Import/Plan<br> source:date=<date of data. Would be useful when subsequent versions are<br> released><br> source=City of Ottawa (maybe should include the dataset such as CAD<br> Topographic Mapping Data or Large Buildings)<br> source:url=<a href="http://data.ottawa.ca/en/dataset/cad-topographic-data">http://data.ottawa.ca/en/dataset/cad-topographic-data</a> (not in<br> the list, but I made a comment about it here<br> <<a href="https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/changeset_tags#source:url.3D.2A">https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/changeset_tags#source:url.3D.2A</a>><br> )<br> source:license=City of Ottawa Open Data Licence 2.0<br><br> I'm not sure if the tasking manager to JOSM pipeline supports this, but<br> if not it's easy to copy/paste all the correct tags in one go under "Tags<br> of new changeset".<br><br></i></div><div>If you are suggesting a proposed feature that isn't even supported in JOSM, why are you making the process more complex?<br></div><div><i><br></i> <i> 4. use source:geometry=<br> <<a href="https://wiki.openstreetmap.org/wiki/Key:source:geometry">https://wiki.openstreetmap.org/wiki/Key:source:geometry</a>> instead of<br> source= tag. Thus if POI information is later added to the polygon, it's<br> unambiguous as to what the source refers to.</i><br></div><div>+1 Great Idea<br><br></div><div> <i>5. I think building replacements (deletions and additions) should be<br> done within the same changeset to make it safer. Deleting all the buildings<br> first caused a headache the first time this import was attempted and some<br> buildings which were of better quality than the import were wiped out.<br></i>We've already addressed this via the replace geometry tool.<br><br> <i>6. split into non-existing and pre-existing buildings. Conflating with<br> existing polygons will be more difficult and time consuming. Thus it would<br> be good to keep that step in separate changesets with appropriate comments<br> so it's easier to review each others work, and disagreements can be more<br> easily rectified without touching undisputed work. I've noticed other<br> <<a href="https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2">https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2</a>><br> building imports have done this where they split the dataset into<br> overlapping and non-overlapping polygons by script.<br><br></i>Denis has modified the data service to do this already via qa-tiles from mapbox, process will be updated when files are released.<br><br> <i>7. be more specific in the instructions about deciding which footprints<br> are added. Will they be compared to background imagery? Sometimes<br> <<a href="http://www.openstreetmap.org/changeset/44545610">http://www.openstreetmap.org/changeset/44545610</a>> buildings are<br> completely wrong (mixed up in their dataset). And picking between existing<br> and imported data is subjective, thus more detailed instructions would be<br> good to improve quality and consistency between users.<br><br></i></div><div>Only a select few will be doing the import, comparisons will be done via the imagery available. The change set you linked is in Gatineau and unrelated to the Ottawa Import.<br></div><div><i><br></i> <i>8. I would also like to see instructions on checking and copying over<br> tags in pre-existing buildings which are to be replaced. And discuss how to<br> handle offsets. What's the quality of the building survey? Should the<br> aerial imagery be aligned to the polygon, or vise versa?<br></i></div><div>Tags are automatically "copied" over with replace geometry tool(IF REPLACED AT ALL) (Please refer to old import mailing list as these concerns have already been addressed)<i><br></i></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 22, 2016 at 1:47 PM, Devon Fyson <span dir="ltr"><<a href="mailto:devonfyson@gmail.com" target="_blank">devonfyson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Here's are my thoughts on it:<br><div class="gmail_quote"><div dir="ltr"><div><ol><li>Arn't the building polygons already available? I see <a href="http://data.ottawa.ca/dataset/large-buildings" target="_blank">large buildings</a> and the <a href="http://data.ottawa.ca/dataset/cad-topographic-data" target="_blank">topographic DWG file</a> which contains buildings.</li><li>If <a href="https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Plan%20is%20still%20the%20import%20plan" target="_blank">this</a> is still the import plan, it should be gone through and updated.</li><li>Should make use of the <a href="https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags" target="_blank">changeset tags</a> Most importantly <span style="font-family:monospace,monospace">type</span> and <span style="font-family:monospace,monospace">url</span>. For example:<br><br><span style="font-family:monospace,monospace">comment=Import building polygons for Ottawa, Canada. Importing non-existant polygons <or> Conflating with existing polygons<br>type=import<br>url:en=<a href="https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Plan" target="_blank">https://wiki.openstreet<wbr>map.org/wiki/Canada:Ontario:<wbr>Ottawa/Import/Plan</a><br>source:date=</span><span style="font-family:arial,helvetica,sans-serif"><date of data. Would be useful when subsequent versions are released></span><span style="font-family:monospace,monospace"><br>source=City of Ottawa </span><span style="font-family:arial,helvetica,sans-serif">(maybe should include the dataset such as CAD Topographic Mapping Data or Large Buildings)</span><span style="font-family:monospace,monospace"> <br>source:url=<a href="http://data.ottawa.ca/en/dataset/cad-topographic-data" target="_blank">http://data.ottawa.<wbr>ca/en/dataset/cad-topographic-<wbr>data</a> </span><span style="font-family:arial,helvetica,sans-serif">(not in the list, but I made a comment about it <a href="https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/changeset_tags#source:url.3D.2A" target="_blank">here</a></span><span style="font-family:monospace,monospace">)<br>source:license=City of Ottawa Open Data Licence 2.0</span><br><br>I'm not sure if the tasking manager to JOSM pipeline supports this, but if not it's easy to copy/paste all the correct tags in one go under "Tags of new changeset".<br></li><li>use <a href="https://wiki.openstreetmap.org/wiki/Key:source:geometry" target="_blank"><span style="font-family:monospace,monospace">source:geometry=</span></a> instead of <span style="font-family:monospace,monospace">source=</span> tag. Thus if POI information is later added to the polygon, it's unambiguous as to what the source refers to.</li><li>I think building replacements (deletions and additions) should be done within the same changeset to make it safer. Deleting all the buildings first caused a headache the first time this import was attempted and some buildings which were of better quality than the import were wiped out.</li><li>split into non-existing and pre-existing buildings. Conflating with existing polygons will be more difficult and time consuming. Thus it would be good to keep that step in separate changesets with appropriate comments so it's easier to review each others work, and disagreements can be more easily rectified without touching undisputed work. I've noticed <a href="https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2" target="_blank">other</a>
building imports have done this where they split the dataset into overlapping and non-overlapping polygons by script.<br></li><li>be more specific in the instructions about deciding which footprints are added. Will they be compared to background imagery? <a href="http://www.openstreetmap.org/changeset/44545610" target="_blank">Sometimes</a> buildings are completely wrong (mixed up in their dataset). And picking between existing and imported data is subjective, thus more detailed instructions would be good to improve quality and consistency between users.<br></li><li>I would also like to see instructions on checking and copying over tags in pre-existing buildings which are to be replaced. And discuss how to handle offsets. What's the quality of the building survey? Should the aerial imagery be aligned to the polygon, or vise versa?<br></li></ol></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Talk-ca mailing list<br>
<a href="mailto:Talk-ca@openstreetmap.org">Talk-ca@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/talk-ca</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div>外に遊びに行こう！</div></div>
</div>