Hey AJ,

Thanks for understanding, this project has been discussed many times at the
local OSM Ottawa Meetup and we've proven this method of import is very
efficient on smaller scale projects.

We might of leaned a bit too much on StatsCan to tackle the "legal" part of
it, however everything has been sorted out between the City of Ottawa, OSM
& Open Data license. It might just not be as documented on the internet
since StatsCan doesn't promote the use of internet in their office and work
mostly in an offline environment.

There are two datasets we are currently working with, building footprints &
address points. The address one is currently released under the OpenData
Ottawa portal and the building footprint has been released, however not
available yet under the OpenData portal, they are trying to figure out
which portal to disseminate to.

Currently the TM project is private, log in and we can grant you access.



*Step 1:* Select a Tile & Start Mapping

*Step 2:* Edit with JOSM

*Step 3:* Apply an inverse filter to find any existing databuilding=*

*Step 4:* Download data - Found in the *Extra Instructions*

*Step 5:* Add feature or merge new data with existing features *(try not to
delete features)*. Check for any existing buildings that might create
conflicts (keep existing, merge tags or only update building footprint)

*Step 6:* Merge address points to building using JOSM address plugin.

*Step 7:* Click JOSM validate and fix any errors or warnings that appear
before submitting your changset.
*Completion Status*

Since adding all the buildings can take a lot of time uploading a single
changeset and the validation requires having the building footprint +
address be available. We've divided the task into two parts "Done" &

Once all the building footprints & address are added, you can mark the tile
as *Done *and the next step would be to validate the tile.

This step will require a lot of time and effort. Here are some of the basic
validation process:

   1. Align Address nodes to the center of the building footprints.
   2. Merge Address nodes with building footprints using the JOSM address
   3. Any buildings that don't have an address (Sheds, garages, etc...)
   either tag them with a specific tag or remove them since it causes
   confusion to clearly identify the primary building.
   4. Replace all building footprints from building=yes with an appropriate osm
   building tag <http://wiki.openstreetmap.org/wiki/Key:building>, we've
   been tagging all the residential houses withbuilding=residential.
   5. Use the validate JOSM process to detect any warnings or errors and
   fix them accordingly. You only need to validate the address & building
   footprints, however you decide to fix other OSM related issues, fill your

*Denis Carriere*
*GIS Software & Systems Specialist*

*Twitter: @DenisCarriere <https://twitter.com/DenisCarriere/>*
*OSM: DenisCarriere <https://www.openstreetmap.org/user/DenisCarriere>*
GitHub: DenisCarriere <https://github.com/DenisCarriere>
Email: carriere.de...@gmail.com

On Mon, Oct 17, 2016 at 9:07 PM, AJ Ashton <a...@ajashton.ca> wrote:

> Hi John,
> Thanks for the writeup. I think this is the first post that's made it
> fully clear what is going on. As I was re-reading the previous StatCan
> thread earlier today I seemed to be missing something - now I guess it was
> context available to those who attended in-person meetings. I don't think
> it was even clear to the list until now how much in-person community
> discussion has been happening.
> Basically the issue is that all the online discussion about this looks to
> have been about the StatCan crowdsourcing half of the project and none at
> all about the building import half. I didn't pay too much attention to the
> original StatCan thread at the time because it so clearly sounded like a
> local mapping project with no large-scale import component.
> Unfortunately I no longer live in Ottawa and couldn't have made it to the
> meetings. However I lived there for many years, have done a lot of mapping
> there, and have a continued interest in the area. I would still like to see
> the the building import happen and even help out where I can. But I think
> it's important to do more planning and discussion on this list and the
> imports list, and to take things in smaller and more manageable chunks.
> I guess the next step would be to continue on a proper path to import the
> buildings per the guidelines per http://wiki.openstreetmap.org/
> wiki/Import/Guidelines . This would include:
> - Wiki documentation of the where the data is, what it contains & its
> license / permissions
> - A plan to conflate with existing data - preserving history, keeping
> existing attributes, and merging addresses onto buildings where possible
> before the data is uploaded
> - A specific plan for uploading the data. Eg how the data will be divided
> up into chunks and step-by-step instructions for JOSM, etc. A task server
> was mentioned several times - who is running this and how can others
> participate?
> - A proper review on the imports mailing list
> I don't necessarily agree with every single rule in the import guidelines,
> but they are what the community has decided on and I think for the most
> part they help avoid the kinds of issues I had with deleted and duplicated
> data in Ottawa.
> --
>   AJ Ashton
>   a...@ajashton.ca
> _______________________________________________
> Talk-ca mailing list
> Talk-ca@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-ca
Talk-ca mailing list

Reply via email to