Thanks :)Bonkers? ... perhaps :@)
Actually, that would be the just the 1st step. meaning that; On those
mapped areas where say - if the actual shapes were imported, you would see
'ghost lines'. .. this is not preferred. So, by just seeing the reference
points, then these shapes can be drawn in
Thanks Tom D,
storage requirements, which is why I have concerns about creating tens
of millions of nodes which have many duplicated tags or which will wind
up never being used and will just be deleted again.
If it's only 10 tiles of 12539, why bother with importing anything at all
for
2008/12/17 Sam Vekemans acrosscanadatra...@gmail.com:
So for example, importing a park (in a mapped area) we would just show
the outline dots of the park, and the user can connect the dots and
show it the 'right' way osm-style.
So we would discard the knowledge of the sequence in which the
Sam Vekemans wrote:
Bonkers? ... perhaps :@)
Well if I've understood correctly then what you're suggesting is that we
add what amounts to presumably some tens of millions of nodes each of
which would presumably have a large number of highly duplicative tags.
If that is what you're saying
Hi,
Sam Vekemans wrote:
And so, im not sure that the local are mappers would want to have a manual
merge (wiping out what they did, importing all the roads, then slowely
bringing back the OSM roads if any are needed)
By having the roads which were not mapped available as nodes to be traced,
Doesn't get my vote. If it's a feature already why would we want to have to
recreate it manually. Also by just importing nodes how can we
visually/easily tell what nodes relate to what feature, especially if
features overlap or cross.
I can understand the difficulty in adding new data into
2008/12/18 Tom Hughes t...@compton.nu
So far, it looks like the majority of the country would be able to
accept a full import of everything... except the roads. .. it's only 10
or so tiles that nothing would be imported (just nodes), and less than
100 where only roads would be omitted.
Sam Vekemans wrote:
I wanted to float the idea (to the general talk list) about importing
the full data base that is available, not as shapes/ways/lines, but as
nodes which show
what map features the node represents.
So for example, importing a park (in a mapped area) we would just show
Hi all,
Such great feedback from my latest 'rant: importing GeoBase nodes'
Thanks :)
What this did was sparked some major issues that need to be addressed.
I think this is more important, than going deeper on that rant.
I created a new wiki page Importing Government Data
Oh ya, the talk-ca list needs to keep upto date :)If anyone on the list
knows more about openlayers, it might help.
Sam
-- Forwarded message --
From: Sam Vekemans acrosscanadatra...@gmail.com
Date: Thu, Dec 18, 2008 at 8:32 PM
Subject: GeoBase / CanVec data as an OpenLayer
To:
Cool :)
what can be done is creating a section for all the options for
importing government data - including the ones that were 'mud' but
state 'why' it was rejected.
Also list pending or aproved stuff
I got a start;
disaproved:
blow away data and replace on-mass
-slap on imported data create
11 matches
Mail list logo