-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, May 29, 2014 at 10:12:02PM -0400, Eric H. Christensen wrote:
> On Thu, Dec 12, 2013 at 05:17:59PM -0800, Paul Norman wrote:
> > You'll need to develop a translation for the shapefiles that converts
> > shapefile attributes to OSM tags, for u
On Fri, May 30, 2014 at 09:55:01AM -0400, Phil! Gold wrote:
> * Gregory Arenius [2014-05-30 00:52 -0700]:
> > The only other thing that stuck out to me about the data was the B & A
> > trail. You have a polygon for the trail which is awesome but I would also
> > add in a properly tagged linear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, May 30, 2014 at 12:52:30AM -0700, Gregory Arenius wrote:
> I wouldn't import the data per say, as in uploading the .osm file you
> have. I would download the current OSM data for the area covered. Then,
> in the import file I would check
* Gregory Arenius [2014-05-30 00:52 -0700]:
> The only other thing that stuck out to me about the data was the B & A
> trail. You have a polygon for the trail which is awesome but I would also
> add in a properly tagged linear way. It will make it possible for routers
> to use it as well as re
Hi Eric,
It looks like a good start to me. There were a couple of things that
stuck out to me: many of the parks and schools are already in OSM, even if
just as a GNIS point. Also, many of the curves in the import are over
digitized. We don't need curves of that size to have that many points.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, Dec 12, 2013 at 05:17:59PM -0800, Paul Norman wrote:
> You'll need to develop a translation for the shapefiles that converts
> shapefile attributes to OSM tags, for use with ogr2osm or shp2osm.jar.
> This is moderately technical.
I used JO
6 matches
Mail list logo
