[Talk-ca] canvec2osm update (an easy question this time)

[Sam Vekemans]

Yup, this is why the talk-ca list is to vital to the sucess of this project
:-)  So everyone knows whats up.

I think I need to remember that there are currently
*86 Non-digested Members of Talk-ca:
and **21 Digested Members of Talk-ca:*
So that means when i message talk-ca list im talking to 86 people across
Canada (and around the world), and 21 of them will read the digest version.
... it also means that many might get the emails, but not read them right
away. ... so it might get lost in the inbox vortex to be 'marked as read'.
(so waiting a couple days might be a good enough time-frame to let all those
who might be thinking about answering, todo so)

Steve mentioned it earlier today that the wiki is being updated all the
time, and as more people figure out how to work the geobase2osm program. ...
(and likewise, later on) how to work canvec2osm, the more people working on
it, the easier it will become for more people to work on it.

Based on that info, i think my focus should be on getting the script (the
rules.txt files) all organized ... and working correctly. So than i can
place it on the svn, so that even if it may be messey, someone who knows the
dataset well could understand it.:) ... and then help to create a set of
instructions for people to follow to get the area they want imported.

Anyway, i uploaded a couple sample features to Port Renfrew, BC

http://www.openstreetmap.org/browse/relation/163132


What tags should be removed??... but more importantly, WHY..  so that it can
be documented on the wiki, incase people wonder why later on.  Then we will
have a definitive answer. .. I proved an answer... and cause this is wiki, i
answer my own questions with an idea :)

ie.
canvec:definition was removed because it is a 'statement' which describes
the previous tag'  in OSM, all statements which describe the tags are paced
on the wiki in a clearly defind manor (based on what the community wants).
"key=note", could possably be used, however it is redendunt to have listed,
because the user would be going to the wiki for more details.

That said, 'for more details'  The canvec feature catelogue is searchable by
the
canvec:CODE = 1370012 tag, where the user could simply enter in this code on
the PDF file to see the details.  .. so all information which can be
acquired from this CODE, could be omited, and moved to an OSM wiki page.

This wiki page, just like the page landuse=residential (which has a
redirect, unfortunatly)
http://wiki.openstreetmap.org/wiki/Key:landuse

Having a wiki page for each type Code would be benificial, so that changes
to this code, or things that were done... ie.. when the source updates thier
dataset and makes changes, we note when these features were loaded. As i can
make a new script that just creates a single .osm file so data can be
reverted or changed or updated if needed. ... and less scrolling through
charts to find what your looking for.

I would argue that every one of these tags are 'usefull' because they
'attribute' and tell the user exactly what the data is; how it was acquired
and catalogued in the system.  It also make it a 2-way street, so that the
data would become more 'useful' to a new set of users... users who might
want to 'varify' the accuracy of the data.   I dont want to have thousands
of people contacting me,
as sking me 'When was this data acquired?'
How was it acuried?
What dataset do i have to look at?
What's the UUID?
What agency provided this data?
... im looking at the canvec feature catelogue and TRYING to figure out
where it came from, (so i can source it) what's the CODE? ...
What is the minimum size that defines a 'residential area'?
On OSM standard, OSM doesn't have a min_size... so a Snoopy's dog house
could be a residential area :-) .. maybe...     But of course, as i made the
rules.txt file... i think it's all good :-)
... and just incase you (OSM community) dont like these tags,  i edited the
script so that it will create an .osm file for each feature which contains
all the tags. ... so it's fine if you want me to remove most of them :-)

Anyway, thats all for now,

Cheers,
Sam Vekemans
Across Canada Trails

Twitter: @Acrosscanada
Facebook: http://www.facebook.com/sam.vekemans


On Wed, Jun 24, 2009 at 5:23 PM, Robert Shand <bob at shand.org.uk> wrote:

> Steve,
>
> Thanks for the info. I've done that. Perhaps I'm just doing something
> wrong. I'll give it a try again soon, however I've got a beer calling
> my name tonight.
>
> Cheers
>
> Sent from my iPhone
>
> On 2009-06-24, at 9:02 PM, Steve Singer <ssinger_pg at sympatico.ca> wrote:
>
> > On Wed, 24 Jun 2009, Robert Shand wrote:
> >
> >> HI Everyone,
> >>
> >> I've been looking at the NRN import for PEI.  I've hit a bit of a
> >> stumbling block.  I've imported Canada.osm into PostGIS database all
> >> good.
> >>
> >
> >> Can I export the data from the Canada.osm that I have loaded?  Anyone
> >> have any details on how to do this?
> >
> > See
> >
> http://wiki.openstreetmap.org/wiki/Geobase_NRN_-_OSM_Map_Feature#Creating_OSM_and_NRN_Shapefiles_with_PostGIS
> >
> > After you've imported canada.osm into postgis (with osm2pgsql not
> > Osmosis) you can generate a shapefile that contains just on the OSM
> > data for your area with pgsql2shp using the select_osm_roadtile
> > function that is defined higher up on that wiki page.
> >
> > Steve
> >
> >
> >>
> >> Thanks
> >>
> >> Bob
> >>
> >>
> >> _______________________________________________
> >> Talk-ca mailing list
> >> Talk-ca at openstreetmap.org
> >> http://lists.openstreetmap.org/listinfo/talk-ca
> >>
> >
>
> _______________________________________________
> Talk-ca mailing list
> Talk-ca at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-ca
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ca/attachments/20090624/c2b84a71/attachment.html>