[Talk-ca] Talk-ca Digest, Vol 106, Issue 5
Ellefsen, Bjenk (STATCAN)
bjenk.ellefsen at canada.ca
Thu Dec 22 19:12:57 UTC 2016
Devon, about your point number 1, the big difference is that the large_buildings file contains 15,000 buildings with a minimum number of floors to qualify. The data being released in January has over 325,000 buildings that are not just tall buildings but houses as well.
Bjenk
-----Original Message-----
From: talk-ca-request at openstreetmap.org [mailto:talk-ca-request at openstreetmap.org]
Sent: December-22-16 2:03 PM
To: talk-ca at openstreetmap.org
Subject: Talk-ca Digest, Vol 106, Issue 5
Send Talk-ca mailing list submissions to
talk-ca at openstreetmap.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.openstreetmap.org/listinfo/talk-ca
or, via email, send a message with subject or body 'help' to
talk-ca-request at openstreetmap.org
You can reach the person managing the list at
talk-ca-owner at openstreetmap.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Talk-ca digest..."
Today's Topics:
1. [Import] Ottawa Buildings & Addresses [Statistics Canada
project] (Ellefsen, Bjenk (STATCAN))
2. Re: [Imports] Fwd: [Import] Ottawa Buildings & Addresses
[Statistics Canada project] (Devon Fyson)
3. Re: [Imports] Fwd: [Import] Ottawa Buildings & Addresses
[Statistics Canada project] (James)
4. Re: [Imports] Fwd: [Import] Ottawa Buildings & Addresses
[Statistics Canada project] (James)
----------------------------------------------------------------------
Message: 1
Date: Thu, 22 Dec 2016 18:15:25 +0000
From: "Ellefsen, Bjenk (STATCAN)" <bjenk.ellefsen at canada.ca>
To: "'talk-ca at openstreetmap.org'" <talk-ca at openstreetmap.org>
Subject: [Talk-ca] [Import] Ottawa Buildings & Addresses [Statistics
Canada project]
Message-ID:
<317ee2d57e1c41cb98ea1273b15091d0 at PELEPCDEXC046.birch.int.bell.ca>
Content-Type: text/plain; charset="utf-8"
Hello everyone,
As James wrote yesterday, the City of Ottawa has approved the release of a large building footprints file for their Open Data portal.
We have been working in close collaboration with the City of Ottawa on that front and it is a major contribution.
We are tracking progress and will communicate the changes to the map soon.
We want to thank everyone for your feedback and please continue sending us your suggestions! A new version of the adapted version of iD is live. This updated version was redone to restore the built-in login process of iD and the app doesn’t load in an iframe anymore. This new version is also using the available built-in functions for a number of things. This has improved performance and it is working in all browsers.
If you see any bugs if you have any comments to improve it, let us know! (http://www.crowdid.osmcanada.ca)
We wish the best holidays with your families and friends!
Bjenk
Crowdsourcing team at Statistics Canada
Website: http://www.statcan.gc.ca/eng/crowdsourcing?HPA=1
Email: Bjenk.ellefsen at canada.ca
Project email for feedback: statcan.crowdsource.statcan at canada.ca / statcan.approcheparticipative.statcan at canada.ca
------------------------------
Message: 2
Date: Thu, 22 Dec 2016 13:47:58 -0500
From: Devon Fyson <devonfyson at gmail.com>
To: imports at openstreetmap.org, talk-ca at openstreetmap.org
Subject: Re: [Talk-ca] [Imports] Fwd: [Import] Ottawa Buildings &
Addresses [Statistics Canada project]
Message-ID:
<CAHRJ+yuKmiFat6ZpxkEcsR+vWydePdFGmirZDxg1jO-+7n-3SQ at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Here's are my thoughts on it:
1. Arn't the building polygons already available? I see large buildings
<http://data.ottawa.ca/dataset/large-buildings> and the topographic DWG
file <http://data.ottawa.ca/dataset/cad-topographic-data> which contains
buildings.
2. If this
<https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Plan%20is%20still%20the%20import%20plan>
is still the import plan, it should be gone through and updated.
3. Should make use of the changeset tags
<https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags>
Most importantly type and url. For example:
comment=Import building polygons for Ottawa, Canada. Importing
non-existant polygons <or> Conflating with existing polygons
type=import
url:en=https://wiki.openstreetmap.org/wiki/Canada:
Ontario:Ottawa/Import/Plan
source:date=<date of data. Would be useful when subsequent versions are
released>
source=City of Ottawa (maybe should include the dataset such as CAD
Topographic Mapping Data or Large Buildings)
source:url=http://data.ottawa.ca/en/dataset/cad-topographic-data (not in
the list, but I made a comment about it here
<https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/changeset_tags#source:url.3D.2A>
)
source:license=City of Ottawa Open Data Licence 2.0
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".
4. use source:geometry=
<https://wiki.openstreetmap.org/wiki/Key:source:geometry> instead of
source= tag. Thus if POI information is later added to the polygon, it's
unambiguous as to what the source refers to.
5. 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.
6. 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 other
<https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2>
building imports have done this where they split the dataset into
overlapping and non-overlapping polygons by script.
7. be more specific in the instructions about deciding which footprints
are added. Will they be compared to background imagery? Sometimes
<http://www.openstreetmap.org/changeset/44545610> 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.
8. 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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ca/attachments/20161222/c39e63ba/attachment-0001.html>
------------------------------
Message: 3
Date: Thu, 22 Dec 2016 13:51:46 -0500
From: James <james2432 at gmail.com>
To: Devon Fyson <devonfyson at gmail.com>
Cc: OSM Imports List <imports at openstreetmap.org>, Talk-CA
OpenStreetMap <talk-ca at openstreetmap.org>
Subject: Re: [Talk-ca] [Imports] Fwd: [Import] Ottawa Buildings &
Addresses [Statistics Canada project]
Message-ID:
<CANk4qi8ww3paCFsKxhT09spUdR2-uDavR1cJ2EzahWEYToA9ag at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi devon, those DWG files(if you were following the import thread, you
would already know this) are old and outdated, never to be updated again.
The newer file is an export of what they have to date.
On Thu, Dec 22, 2016 at 1:47 PM, Devon Fyson <devonfyson at gmail.com> wrote:
> Here's are my thoughts on it:
>
> 1. Arn't the building polygons already available? I see large buildings
> <http://data.ottawa.ca/dataset/large-buildings> and the topographic
> DWG file <http://data.ottawa.ca/dataset/cad-topographic-data> which
> contains buildings.
> 2. If this
> <https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Plan%20is%20still%20the%20import%20plan>
> is still the import plan, it should be gone through and updated.
> 3. Should make use of the changeset tags
> <https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags>
> Most importantly type and url. For example:
>
> comment=Import building polygons for Ottawa, Canada. Importing
> non-existant polygons <or> Conflating with existing polygons
> type=import
> url:en=https://wiki.openstreetmap.org/wiki/Canada:Ontario:
> Ottawa/Import/Plan
> source:date=<date of data. Would be useful when subsequent versions
> are released>
> source=City of Ottawa (maybe should include the dataset such as CAD
> Topographic Mapping Data or Large Buildings)
> source:url=http://data.ottawa.ca/en/dataset/cad-topographic-data (not
> in the list, but I made a comment about it here
> <https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/changeset_tags#source:url.3D.2A>
> )
> source:license=City of Ottawa Open Data Licence 2.0
>
> 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".
> 4. use source:geometry=
> <https://wiki.openstreetmap.org/wiki/Key:source:geometry> instead of
> source= tag. Thus if POI information is later added to the polygon,
> it's unambiguous as to what the source refers to.
> 5. 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.
> 6. 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 other
> <https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2>
> building imports have done this where they split the dataset into
> overlapping and non-overlapping polygons by script.
> 7. be more specific in the instructions about deciding which
> footprints are added. Will they be compared to background imagery?
> Sometimes <http://www.openstreetmap.org/changeset/44545610> 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.
> 8. 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?
>
>
> _______________________________________________
> Talk-ca mailing list
> Talk-ca at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
>
--
外に遊びに行こう！
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ca/attachments/20161222/242dead5/attachment-0001.html>
------------------------------
Message: 4
Date: Thu, 22 Dec 2016 14:03:04 -0500
From: James <james2432 at gmail.com>
To: Devon Fyson <devonfyson at gmail.com>
Cc: OSM Imports List <imports at openstreetmap.org>, Talk-CA
OpenStreetMap <talk-ca at openstreetmap.org>
Subject: Re: [Talk-ca] [Imports] Fwd: [Import] Ottawa Buildings &
Addresses [Statistics Canada project]
Message-ID:
<CANk4qi8QbMXqAN4dHVpkfp1KW-raYrcdyhNor4oQATWFe3fpJw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
*1. Arn't the building polygons already available? I see large buildings
<http://data.ottawa.ca/dataset/large-buildings
<http://data.ottawa.ca/dataset/large-buildings>> and the topographic DWG
file <http://data.ottawa.ca/dataset/cad-topographic-data
<http://data.ottawa.ca/dataset/cad-topographic-data>> which contains
buildings.*
See previous email
* 2. If this
<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>>
is still the import plan, it should be gone through and updated.*
It will once data is released.
*3. Should make use of the changeset tags
<https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags
<https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags>>
Most importantly type and url. For example: comment=Import building
polygons for Ottawa, Canada. Importing non-existant polygons <or>
Conflating with existing polygons type=import
url:en=https://wiki.openstreetmap.org/wiki/Canada
<https://wiki.openstreetmap.org/wiki/Canada>:
Ontario:Ottawa/Import/Plan source:date=<date of data. Would be useful
when subsequent versions are released> source=City of Ottawa (maybe
should include the dataset such as CAD Topographic Mapping Data or Large
Buildings)
source:url=http://data.ottawa.ca/en/dataset/cad-topographic-data
<http://data.ottawa.ca/en/dataset/cad-topographic-data> (not in the list,
but I made a comment about it here
<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>>
) source:license=City of Ottawa Open Data Licence 2.0 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".*
If you are suggesting a proposed feature that isn't even supported in JOSM,
why are you making the process more complex?
* 4. use source:geometry=
<https://wiki.openstreetmap.org/wiki/Key:source:geometry
<https://wiki.openstreetmap.org/wiki/Key:source:geometry>> instead of
source= tag. Thus if POI information is later added to the polygon, it's
unambiguous as to what the source refers to.*
+1 Great Idea
*5. 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.*We've already addressed this via the replace geometry tool.
*6. 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
other
<https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2
<https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2>>
building imports have done this where they split the dataset into
overlapping and non-overlapping polygons by script.*Denis has modified the
data service to do this already via qa-tiles from mapbox, process will be
updated when files are released.
*7. be more specific in the instructions about deciding which footprints
are added. Will they be compared to background imagery? Sometimes
<http://www.openstreetmap.org/changeset/44545610
<http://www.openstreetmap.org/changeset/44545610>> 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.*
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.
*8. 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?*
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)
On Thu, Dec 22, 2016 at 1:47 PM, Devon Fyson <devonfyson at gmail.com> wrote:
> Here's are my thoughts on it:
>
> 1. Arn't the building polygons already available? I see large buildings
> <http://data.ottawa.ca/dataset/large-buildings> and the topographic
> DWG file <http://data.ottawa.ca/dataset/cad-topographic-data> which
> contains buildings.
> 2. If this
> <https://wiki.openstreetmap.org/wiki/Canada:Ontario:Ottawa/Import/Plan%20is%20still%20the%20import%20plan>
> is still the import plan, it should be gone through and updated.
> 3. Should make use of the changeset tags
> <https://wiki.openstreetmap.org/wiki/Proposed_features/changeset_tags>
> Most importantly type and url. For example:
>
> comment=Import building polygons for Ottawa, Canada. Importing
> non-existant polygons <or> Conflating with existing polygons
> type=import
> url:en=https://wiki.openstreetmap.org/wiki/Canada:Ontario:
> Ottawa/Import/Plan
> source:date=<date of data. Would be useful when subsequent versions
> are released>
> source=City of Ottawa (maybe should include the dataset such as CAD
> Topographic Mapping Data or Large Buildings)
> source:url=http://data.ottawa.ca/en/dataset/cad-topographic-data (not
> in the list, but I made a comment about it here
> <https://wiki.openstreetmap.org/wiki/Talk:Proposed_features/changeset_tags#source:url.3D.2A>
> )
> source:license=City of Ottawa Open Data Licence 2.0
>
> 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".
> 4. use source:geometry=
> <https://wiki.openstreetmap.org/wiki/Key:source:geometry> instead of
> source= tag. Thus if POI information is later added to the polygon,
> it's unambiguous as to what the source refers to.
> 5. 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.
> 6. 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 other
> <https://wiki.openstreetmap.org/wiki/Helsinki_region_building_import#Import_Type_2>
> building imports have done this where they split the dataset into
> overlapping and non-overlapping polygons by script.
> 7. be more specific in the instructions about deciding which
> footprints are added. Will they be compared to background imagery?
> Sometimes <http://www.openstreetmap.org/changeset/44545610> 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.
> 8. 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?
>
>
> _______________________________________________
> Talk-ca mailing list
> Talk-ca at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
>
>
--
外に遊びに行こう！
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ca/attachments/20161222/37ecafbe/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
Talk-ca mailing list
Talk-ca at openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
------------------------------
End of Talk-ca Digest, Vol 106, Issue 5
***************************************
More information about the Talk-ca
mailing list