[Imports] [Talk-us] boundary import Update

Peter Dobratz peter at dobratz.us
Sun Oct 23 03:57:02 UTC 2011

So you've got a git repository with OSM data that you eventually plan
on uploading to replace data that is already in the official OSM
database?  But you've already demonstrated that your method of
uploading results in lots of duplicate Ways, so I'm not sure this is a
good plan at all.  Is there any reason you can't follow the normal
workflow (download from OSM, edit, upload)?


On Sat, Oct 22, 2011 at 8:30 PM, Metcalf, Calvin (DOT)
<calvin.metcalf at state.ma.us> wrote:
> it is up at http://www.github.com/calvinmetcalf/ma-admin
> at the moment it just has lines and the admin_level=4 tags. I wasn't planing on posting it to github, I was planning on building it on github with the help of anyone else interested, including the deletions etc.  If you look at my account I have one for t data too.
> Sent with Verizon Mobile Email
> ---Original Message---
> From: "Greg Troxel" <gdt at ir.bbn.com>
> Sent: 10/22/2011 8:12 pm
> To: Calvin.Metcalf at dot.state.ma.us
> Cc: imports at openstreetmap.org, talk-us at openstreetmap.org
> Subject: Re: [Imports] boundary import Update
> I think the nuke/replace notion is sensible.
> So I would suggest that you put up (github seems fine, doesn't really
> matter as long as it's broadly accessible) several things:
>  a pointer to the massgis data, and maybe a copy
>  exact recipe for going from that to the .osm to upload (as scripts
>  that others could run, if at all possible), annotated with
>  explanatations for why the various choices are made
>  the proposed .osm to upload
>  how you're going to execute the nuke-existing-ma-borders operation
>  an explanation of what happens to the borders with other states (the
>  notion of leaving two and manual fixup after studying their view of
>  the border makes sense)
>  an explanation of how this relates to the coastline and the 12-nm
>  boundary (saying that it is totally separate for now seems ok)
> For the record, I agree that things are getting better, even if a bit
> messy right now, and that we're on the road to having higher-quality
> boundary data in Mass.
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us

More information about the Imports mailing list