On 31 Jan 2009, at 17:56, Bill Ricker wrote:
> On Fri, Jan 30, 2009 at 10:01 PM, Bill Ricker
> wrote:
>> On Fri, Jan 30, 2009 at 9:47 AM, Christopher Schmidt
>> wrote:
>>> just assumed it was a renderer problem instead of a data problem.
>>
>> looks like it's both ?-)
>>
>> can you or someone
In Massachusetts osm has state GIS data, and a number of the 1-way ways
are the wrong direction. This is particularly obvious for divided
highways, e.g. Rt 2 inside 128, 495 near Rt 2.
Clearly I could go edit these manually. But I wonder if there is
automated way to fix this, perhaps by going b
On Sun, Feb 01, 2009 at 10:33:24AM -0500, Greg Troxel wrote:
>
> In Massachusetts osm has state GIS data, and a number of the 1-way ways
> are the wrong direction. This is particularly obvious for divided
> highways, e.g. Rt 2 inside 128, 495 near Rt 2.
>
> Clearly I could go edit these manually
Christopher Schmidt writes:
> MassGIS does not encode the direction. Oneways which are potentially
> wrong are marked with a FIXME note to fix the incorrect directionality.
> (I believe it is 'FIXME: Unconfirmed oneway'.) MassGIS pays NavTeq for
> routing data, and does not have a 'free' source
On Sun, Feb 01, 2009 at 10:55:56AM -0500, Greg Troxel wrote:
>
> Christopher Schmidt writes:
>
> > MassGIS does not encode the direction. Oneways which are potentially
> > wrong are marked with a FIXME note to fix the incorrect directionality.
> > (I believe it is 'FIXME: Unconfirmed oneway'.) M
Tiger line files are incomplete, especially as regards streets in new
developments. It's possible to draw the streets from Yahoo imagery. But
where to get the names? Must they come off of street signs? Is it a
violation of copyright to take the names (and ONLY the names) from Google,
Yahoo, or
Hilton Long said:
> Tiger line files are incomplete, especially as regards streets in new
> developments. It's possible to draw the streets from Yahoo imagery. But
> where to get the names? Must they come off of street signs? Is it a
> violation of copyright to take the names (and ONLY the name
On Sun, Feb 1, 2009 at 3:25 PM, wrote:
> Hilton Long said:
> > Tiger line files are incomplete, especially as regards streets in new
> > developments. It's possible to draw the streets from Yahoo imagery. But
> > where to get the names? Must they come off of street signs? Is it a
> > violatio
On Sun, Feb 1, 2009 at 1:36 PM, Ian Dees wrote:
>
>
> On Sun, Feb 1, 2009 at 3:25 PM, wrote:
>
>> Hilton Long said:
>> > Tiger line files are incomplete, especially as regards streets in new
>> > developments. It's possible to draw the streets from Yahoo imagery.
>> But
>> > where to get the n
Google, Yahoo, don't match in a lot of cases. Google uses Tele
Atlas data which is obviously derived from same sources as Tiger and
often completely outdated, in wrong places
On 1 Feb 2009, at 13:36 , Ian Dees wrote:
On Sun, Feb 1, 2009 at 3:25 PM, wrote:
Hilton Long said:
have started to play a bit with route relations as proposed in
http://wiki.openstreetmap.org/wiki/United_States_roads_tagging
relations are really great especially when using JOSM.
But without documentation what has been done already it may end in
multiple relations created fro the same Intersta
On Sun, Feb 1, 2009 at 9:36 PM, Ian Dees wrote:
>
>
> On Sun, Feb 1, 2009 at 3:25 PM, wrote:
>
>> Hilton Long said:
>> > Tiger line files are incomplete, especially as regards streets in new
>> > developments. It's possible to draw the streets from Yahoo imagery.
>> But
>> > where to get the n
On 1 Feb 2009, at 13:36, Ian Dees wrote:
>
>
> On Sun, Feb 1, 2009 at 3:25 PM, wrote:
> Hilton Long said:
> > Tiger line files are incomplete, especially as regards streets in
> new
> > developments. It's possible to draw the streets from Yahoo
> imagery. But
> > where to get the names? M
SteveC writes:
> Right but the names on the streets might not be facts. They might be
> wrong *on purpose*.
>
> http://wiki.openstreetmap.org/wiki/Copyright_Easter_Eggs
What about the public domain USGS topographic maps and DOQ (Digital
Orthographic Quads aka aerial photos) available v
On Sun, Feb 1, 2009 at 9:05 PM, Russ Nelson wrote:
> SteveC writes:
> > Right but the names on the streets might not be facts. They might be
> > wrong *on purpose*.
> >
> > http://wiki.openstreetmap.org/wiki/Copyright_Easter_Eggs
>
>
> The reason mapmakers get away with copyrighting fact
One issue here is that while U.S. law does say that facts aren't
copyrightable (I believe the original case dealt with copying of names
and numbers from phone directories), that does not mean that every
jurisdiction in the world agrees (notably, I am pretty sure that
Britain's courts ruled differen
Chris Lawrence writes:
> I think OSM is probably on the safest legal ground by stating that you
> shouldn't copy anything from any map (at least no map that isn't under
> a compatible license or in the public domain),
To be clear, you are replying to Ian Dees (given the References
header) and n
On Sun, Feb 1, 2009 at 4:01 PM, Apollinaris Schoell wrote:
> have started to play a bit with route relations as proposed in
> http://wiki.openstreetmap.org/wiki/United_States_roads_tagging
>
> relations are really great especially when using JOSM.
> But without documentation what has been done alr
18 matches
Mail list logo
