[Talk-ca] Proposed mechanical edits: GeoBase/CanVec Service Surface and GeoBase/CanVec name spaces

Andrew Lester a-lester at shaw.ca
Sat Aug 11 20:38:41 BST 2012


I've seen the double (and even triple) space problem here on Vancouver
Island, and I've stumbled upon it when looking at data in other parts of
Canada. I think all of the Geobase and Canvec 9 or earlier data is affected.
I just checked and the problem has been fixed with Canvec 10, so if the
existing data can be fixed, the problem won't come back.
Andrew Lester
Victoria, BC

-----Original Message-----
From: Paul Norman [mailto:penorman at mac.com] 
Sent: Saturday, August 11, 2012 10:54 AM
To: 'Harald Kliems'
Cc: talk-ca at openstreetmap.org
Subject: Re: [Talk-ca] Proposed mechanical edits: GeoBase/CanVec Service
Surface and GeoBase/CanVec name spaces

No one pointed out any areas with problems outside the lower mainland so I
only did this locally. As for an entirely automated way to deal with name:"
" ways, there isn't one.

> From: Harald Kliems [mailto:kliems at gmail.com]
> Sent: Saturday, August 11, 2012 8:21 AM
> Subject: Re: [Talk-ca] Proposed mechanical edits: GeoBase/CanVec 
> Service Surface and GeoBase/CanVec name spaces
> 
> Hi Paul,
> did you ever get around to doing this? I was recently adding a bunch 
> of street names based on Geobase along the St. Lawrence between 
> Montreal and Quebec City and I noticed that there are still lots of 
> streets (and house number interpolations) with the double blanks. And 
> can somebody please tell me how to do a search and replace in JOSM to 
> deal with this semi-manually?
> Best,
>  Harald.
> 
> On Fri, Apr 6, 2012 at 4:34 PM, Paul Norman <penorman at mac.com> wrote:
> > Since no one has objected (or commented) I'll go ahead with this if 
> > I can get it in before the rebuild starts.
> >
> >> -----Original Message-----
> >> From: Paul Norman [mailto:penorman at mac.com]
> >> Sent: Saturday, March 17, 2012 12:04 AM
> >> To: talk-ca at openstreetmap.org
> >> Subject: Re: [Talk-ca] Proposed mechanical edits: GeoBase/CanVec 
> >> Service Surface and GeoBase/CanVec name spaces
> >>
> >> Not listed in this message was the area this would be over. This 
> >> would only be over the lower mainland unless requested for another
> area.
> >>
> >> > -----Original Message-----
> >> > From: Paul Norman [mailto:penorman at mac.com]
> >> > Subject: [Talk-ca] Proposed mechanical edits: GeoBase/CanVec 
> >> > Service Surface and GeoBase/CanVec name spaces
> >> >
> >> > The GeoBase and CanVec imports in the lower mainland suffered 
> >> > from two tagging errors I propose fixing with two one-time 
> >> > mechanical
> edits.
> >> >
> >> > 1. surface=unpaved service ways
> >> >
> >> > GeoBase and CanVec highway=service ways are mis-tagged with 
> >> > surface=unpaved regardless of if they are paved or not. I propose 
> >> > removing this tag as it is misleading. To avoid removal of this 
> >> > tag where a mapper has reviewed it, I will only do the obvious 
> >> > cases automatically and review the others.
> >> >
> >> > The obvious case is ways where none of the tagging has changed 
> >> > since the import with the possible exception of geobase:uuid 
> >> > which may have been combined with the value from another way in a
merge.
> >> >
> >> > These will be identified by the tags attribution=GeoBaseR 
> >> > geobase:acquisitionTechnique=Orthophoto
> >> > geobase:datasetName=NRN:British Columbia geobase:uuid=*
> >> > source=Geobase_Import_2009 surface=unpaved highway=service
> >> >
> >> > 2. Double-spaced names
> >> >
> >> > GeoBase and CanVec sometimes have names with two spaces in them.
> >> > For example, "West  70th Street". I propose fixing these.
> >> > Unfortunately this is less automated and will require searching 
> >> > through the road network with JOSM for name:"  ".
> >> >
> >> > The edit will be from my imports/mechanical edit account and 
> >> > appropriately documented.
> >> >
> >> > As these edits will require touching a large number of roads I 
> >> > also propose cleaning up unnecessary meta-information from the 
> >> > import that is duplicated by other tags. For example, 
> >> > geobase:datasetName=NRN:British Columbia can be inferred from 
> >> > source=Geobase_Import_2009, being located in BC, and matching
> >> highway=*.
> >> >
> >> > It is not worth creating a new version of objects solely to 
> >> > remove these tags, but since fixing the tagging requires creating 
> >> > a new object anyways it is worth doing it in this case.
> >> >
> >> >
> >> > _______________________________________________
> >> > 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
> >
> >
> > _______________________________________________
> > Talk-ca mailing list
> > Talk-ca at openstreetmap.org
> > http://lists.openstreetmap.org/listinfo/talk-ca
> 
> 
> 
> --
> Please use encrypted communication whenever possible!
> Key-ID: 0x199DC50F


_______________________________________________
Talk-ca mailing list
Talk-ca at openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-ca





More information about the Talk-ca mailing list