Responding to point C below,
I would strongly suggest that we not confuse the process of importing
new data with that of updating/modifying existing data in the OSM
database. One of the things I really disliked about the initial building
import was that it overwrote existing data at the same ti
The page "The Open Database of Buildings" has been moved to the "Canada - The
Open Database of Buildings" not to confuse wiki users from outside the country
(a Tim Elrick suggestion).
Tim also identified another way to identify local mappers. I added a link to
his recipe in the above wiki page,
Hello Nate,
I understand that you don't like to see an import process that both bring in
new objects and overwrite existing ones. You also suggest removing "overlapped"
building from ODB prior to import it. Such pre-processing, that would ensure
there will be no buildings "overwrite" during the
My understanding is that is when we imported Ottawa we followed the normal
process as detailed by Daniel and that seemed to work quite nicely.
Cheerio John
On Thu, Jan 16, 2020, 2:57 PM Daniel @jfd553, wrote:
> Hello Nate,
>
> I understand that you don’t like to see an import process that both
Daniel,
The section you cite from the import guidelines seems to support my
position. Perhaps that means I haven't explained my thoughts well? It says:
"If you are importing data where there is already some data in OSM, then
you need to combine this data in an appropriate way or suppress the
Part of the building import was the idea that once an outline was in
place it could be tagged with more detail by someone with local
knowledge. Sometimes some of this this information might be available
from Mapillary.
For example building=house rather than building=yes
In Coburg there are a
On Jan 16, 2020, at 2:37 PM, John Whelan wrote:
> Is there somewhere that offers guidelines on how to add additional tags? and
> which tags are more interesting and which should be avoided? For example
> country=Canada is probably superfluous.
As it hasn't been touched in five months, I'm not
That sort of works but doesn't include roof:levels.
The easy tag would be building=detached but then you get building=house
which can be used for a semi detached house.
Locally we have some split levels so a single floor at ground level then a
garage often slightly sunk with another room or two o
On Jan 16, 2020, at 3:56 PM, john whelan wrote:
> I think what is in the wiki is a sort of dream. An accurate building date
> for example is often difficult to determine. but probably it needs a sort of
> low hanging fruit section of what should be easy to tag.
One of the best parts of an open
I would assume in most cases the imported building footprint will be
more precise than existing data. For me, this would be a reason to
replace already existing objects. However, I think this is a case by
case decision. However, I think it is important to keep tags and history
of buildings alre
10 matches
Mail list logo
