or someone deleted them?
Potlatch has an undo mode open the area where you expect it to be and use u or
U. tend to forget which one is correct
On 10 Feb 2010, at 16:17 , Mike Thompson wrote:
> It seems that not all GNIS Feature_Classes were imported, at least not
> in Rocky Mountain National Par
It seems that not all GNIS Feature_Classes were imported, at least not
in Rocky Mountain National Park in Colorado. For example, in this
area
(http://www.openstreetmap.org/?lat=40.4038&lon=-105.52128&zoom=15&layers=B000FTF)
there is a prominent rock formation called "Twin Owls". It is shown
on t
Does anyone know if there is a free source of higher resolution
imagery for Wyandotte County, KS? I've gotten ahold of the NAIP
imagery from 2008 and it isn't much better than the Yahoo imagery.
Wyandotte County has imagery, but wants $$$. The Kansas Geospatial
Commons doesn't appear to have anyt
"Mike N." writes:
> b.) All current scripts I know of require significant rework, short of
> importing the NHD into a local GEO database, then exporting it to remove
> duplicate nodes.
I have been thinking about imports (but not getting around to it, partly
because it's more time than I have
Yeah they're 46006, which is wrong. So looks like I can kill them after triple
checking with a local.
On Feb 10, 2010, at 9:37 AM, Ian Dees wrote:
> On Wed, Feb 10, 2010 at 10:27 AM, SteveC wrote:
> How accurate is NHD data?
>
> I have a lot of streams going approximately down ski runs in CO
On 10 February 2010 16:32, Ian Dees wrote:
> On Wed, Feb 10, 2010 at 9:34 AM, SteveC wrote:
>
>> any way the importer can
>>
>> a) go back and fix all the millions of duplicated nodes
>>
>> b) not do it in future?
>
>
> This is my fault, Steve. I ran the import but the bulk upload script I used
On Wed, Feb 10, 2010 at 10:27 AM, SteveC wrote:
> How accurate is NHD data?
>
> I have a lot of streams going approximately down ski runs in CO here:
>
>http://www.openstreetmap.org/?lat=39.8671&lon=-105.7518&zoom=14
>
> (yes the ski runs need mapping too)
>
> There's no streams for many
On Wed, Feb 10, 2010 at 9:34 AM, SteveC wrote:
> any way the importer can
>
> a) go back and fix all the millions of duplicated nodes
>
> b) not do it in future?
This is my fault, Steve. I ran the import but the bulk upload script I used
had problems with the way I had created the OSM files (th
How accurate is NHD data?
I have a lot of streams going approximately down ski runs in CO here:
http://www.openstreetmap.org/?lat=39.8671&lon=-105.7518&zoom=14
(yes the ski runs need mapping too)
There's no streams for many of those there in winter. I'm pretty sure summer is
the same b
On Feb 10, 2010, at 8:48 AM, Mike N. wrote:
>> any way the importer can
>>
>> a) go back and fix all the millions of duplicated nodes
>>
>> b) not do it in future?
>
> I'm working on both points -
>
> a) Happens in several cases:
> 1. At the joining of streams to waterbodies. The duplicate
> any way the importer can
>
> a) go back and fix all the millions of duplicated nodes
>
> b) not do it in future?
I'm working on both points -
a) Happens in several cases:
1. At the joining of streams to waterbodies. The duplicate happens
because data comes from 2 separate sources (Flowlin
any way the importer can
a) go back and fix all the millions of duplicated nodes
b) not do it in future?
:-)
Yours &c.
Steve
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
On Feb 9, 2010, at 8:35 PM, Mike Thompson wrote:
> It appears that there is a systematic error in the summit elevations
> in OSM, at least in Colorado.
Well I was given a map, a guide book and a diary for xmas all for climbing
every 14er, so... I can go fix those :-)
Talking about CO it's this
I somewhat glibly asked "what should the height spec be" and I think the
answer should be "orthometric heights based on WGS84 and the current
associated geoid model".
When converting to feet there is the wrinkle of US survey feet vs the
international foot. This matters in state plane systems, bu
It appears that there is a systematic error in the summit elevations
in OSM, at least in Colorado. For example, Longs Peak is listed in
OSM as having an elevation of 4340 meters (14,239 ft). The topo map
has it as 14,251 ft. I have noticed the same type of issue with
nearby peaks. I
15 matches
Mail list logo
