Of course.
Could use the ottawa import approach: "leave existing buildings alone".
Matthew Darwin
[email protected]
http://www.mdarwin.ca
On 2018-11-02 7:03 p.m., OSM Volunteer stevea wrote:
On Nov 2, 2018, at 3:58 PM, John Whelan <[email protected]> wrote:
So to paraphrase your reply. A centralised import plan in the wiki which says
the data is approved for import and should be tackled in chunks of some sort of
region since we are a decentralized organization. Which I think is similar to
the way Task Manager works. The project is broken into tiles and each tile is
tackled completed separately. The 'Tiles' would of course be somewhat larger in
area and there is a technical limitation as to how big an area can be
downloaded from the OSM server.
The local mappers certainly have a role to play and because the goal is not
only to import the buildings but to enrich the tags with commercial etc so the
tag enrichment would be a task that a mapathon could tackle. I personally
don't think a new mapper using iD in a mapathon has a role to play in importing
the building outlines into OSM.
The plan should include the technical steps to import the data.
AND, must include how existing data in OSM (as there appears to be "in some cases,
significant" (I haven't examined the entire dataset, to do so would be overwhelming) which
overlap with the "official datasets" will be conflated. That is a critical step.
SteveA
California
_______________________________________________
Talk-ca mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-ca
_______________________________________________
Talk-ca mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-ca
