The easiest way to fix this may just be with a text editor and
xapi/overpass queries. First do a query to get a file of affected objects
in a given area, then load the area in a text editor and do a search for
the double space. Jumping the search ahead should take you not only to the
given
Message-
From: Paul Norman [mailto:penor...@mac.com]
Sent: Saturday, March 17, 2012 12:04 AM
To: talk-ca@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
, 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
]
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
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
5 matches
Mail list logo
