On 2/5/18 9:36 AM, Adam Franco wrote: > ---------- Forwarded message ---------- > From: *Adam Franco* <[email protected] <mailto:[email protected]>> > Date: Sun, Feb 4, 2018 at 2:21 PM > Subject: Vermont Town Boundaries import > To: "[email protected] <mailto:[email protected]> > Openstreetmap" <[email protected] > <mailto:[email protected]>> > > > I'm putting together documentation for an import of Vermont Towns at: > https://wiki.openstreetmap.org/wiki/Vermont_Town_Boundary_Import_2018 > <https://wiki.openstreetmap.org/wiki/Vermont_Town_Boundary_Import_2018> > > I'm currently looking at this import as a mostly manual process in > JOSM (relations, tags, etc) with the boundary geometry being the only > thing not hand-crafted. Any feedback or tips would be most welcome. on a quick glance, this looks pretty good.
some years ago i manually imported newish TIGER town/county borders along the eastern border of NY. the state borders at that time were from a rather iffy USGS data set, and i redid it to match the much better TIGER data. i'm interested in your thinking about what to do with any conflicts. this should probably go into the documentation. richard -- [email protected] Averill Park Networking - GIS & IT Consulting OpenStreetMap - PostgreSQL - Linux Java - Web Applications - Search _______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
