[Imports] [Talk-ca] Modifying GeoBase Ways.
acrosscanadatrails at gmail.com
Tue Nov 17 23:43:31 GMT 2009
(Thanks Daniel for the details)
I think we need to fix up the wiki so that the page on "Canada Importing
Data" (from all sources) is more clear (or maybe something bold at the top
of the page?). That hasn't been done yet. Unfortunately.
The idea for imports (of all types) is that the data is available to
'assist' in the development of OpenStreetMap. Inotherwords, it's a *one-way
import*, where the original converted .osm file is available (weather it
gets actually used in OSM or not, *which is why the source shp.zip file(s)
is available as part of the conversion 'package'*
The license of openstreetmap (ODbl) is still under discussions at the
Foundation Level, and as well at the community level. But basically, it's
reciprocal of what the license of Natural Resources Canada has. You can do
what you like to the data and use it at your leisure, provided that you
indicate where the data came from, in a form that is recognizable to the
end-user. (the idea is to help the user of the dataset and not to confuse
And BTW, its great to hear that GeoBase & CanVec is looking to assist their
own dataset based on the changes that the OSM community provide for the
OpenStreetMap project. (I think that TIGER is looking at doing the same
My earlier example (i forget who it was who i was explaining it to), is to
treat the data that is being imported as a 'newbie user'. In fact, on the
import@ list, Andy Allan is working on a document, he wrote in an earlier
As part of a couple of projects, I'd also been asked to write some
guidance on how to "do" imports properly. I've written some guidance,
mainly aimed at the "someone from a uni has their campus in a
shapefile" type of person, not really for ultra-tech
You can find the .pdf file here:
Where in it, he highlights the idea to use a 'dedicated account for
It doesn't go into treating the data as a 'newbie' user, but the concept is
the same. That 'newbie' user, wasn't physically there (most likely) so the
local area mapper knows best.
Although its really only for the situation where some (like myself) is
importing a big area, So i log in with a different account, and then make
the 'tweaks' as my regular account. So then this way, if data needs tobe
removed, it's only the edits from this 'separate account' that gets removed.
And BTW, i am STILL against including the UUID as part of the data thats
imported into the OSM project and INSTEAD use the physical location of the
node/way/area/multi-polygon to compare the old with the new datasets and
create a DIFF file which shows the 'whats missing'
And now with the welcome addition of local datasets, the OSM project becomes
even more complex, where we now have multiple sources of data representing
the same thing. So having that source:UUID tag means less and less, as the
OSM map gets better.
So far, on a technical level, know-one has shown evidence that this tag is
actually useful, (since the physical location trumps whatever tags).
... but alas, only time will tell.. then a bot will need to be made like in
the US which goes around and removes those tags :)
Anyway, the point is that it DOES need to be better documented, as i feel
that James isnt alone in that assumption "dont touch the geobase roads as
it's 'sacred') or rather it gets put up on a 'pedestal' of higher
significance. .. way up their on a high plateau.
(Similar to how the TIGER data in the USA (WAS treated BEFORE more local
data became available), and people saw that TIGER is a *compiled dataset
collection* (just like GeoBase & CanVec is)
... which is why i believe that including that 'UUID' (inadvertently, places
the imported data on that 'high plateau pedestal', where it should really be
treated as a 'newbie user' and just keep the 'attribution & source tag on
there, but dont be concerned about it'
Thats my toonie
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Imports