[Imports] Building footprints for Bend, Oregon
ajzeigert at gmail.com
Thu Oct 6 17:39:07 UTC 2016
I'll also see if I can confirm the Oregon open data law and provide a link.
On Thu, Oct 6, 2016 at 10:38 AM, Andy Zeigert <ajzeigert at gmail.com> wrote:
>> - your plans are still very incomplete, in-detail assessment is not
>> possible at this time, you will need to re-post here later for proper
>> import assessment according to the guidelines.
> Yeah, my group is going to meet and discuss some of the missing pieces
> this evening (Oct. 6). There are many aspects of importing (task
> management, for example) that are outside my area of expertise, but
> members of our group are more familiar with. I wanted to post what we
> had so far and hit up this group so I could relay any important
> discussion points that might be brought up in the mailing list.
>> - the 'permission statement' is not a license statement about the data -
>> offering something "as a service to the public for no charge or fee"
>> does not mean the public may do anything with that data except looking
>> at it and there does not seem to be any more comprehensive statement on
>> the download site so you will need to get something more specific and
>> elaborate from the owner.
> I think someone from the city is going to be at our planning meeting
> and I will discuss getting a more clear license. Could someone point
> me to a good example that I could show our city GIS rep?
>> - your plan outline indicates you plan to add attributes (in particular
>> height) to the import data (and possibly also existing data in OSM)
>> from separate, automatically produced and originally unrelated data
>> without manual per case review - a.k.a. bot mapping. There are many
>> mappers who believe such data should be kept separate and should not
>> get into the OSM database because it would make work more difficult
>> both for mappers and data users.
> I'll post more in-depth documentation on my technique for extracting
> building heights from lidar ASAP, but ground-truthing a subset of the
> automatically-derived values to develop a confidence interval is part
> of it. I think that lidar derivation is a pretty common and accepted
> practice for extracting building heights? I think this data would be a
> valuable addition to the OSM database, as it's unlikely that this data
> will be acquired any other way or entered by users. Perhaps it could
> be tagged in a certain way to indicate that it is created by GIS
>> Have you announced your plans on talk-us? It would be good to get more of the US community involved. You should also join our slack channel, #imports on osmus.slack.com
> This is my first real experience on a wiki. I'm not familiar with
> talk-us? How does that work? And could someone invite me to the osmus
>> I'm interested in how you will added building height to building outlines.
> Working on an in-depth and easily-repeatable outline on that. Will
> post to wiki and here ASAP.
> On Thu, Oct 6, 2016 at 7:40 AM, Christoph Hormann <chris_hormann at gmx.de> wrote:
>> On Thursday 06 October 2016, Clifford Snow wrote:
>> > I believe that Oregon has an open data law so the permission
>> > statement probably isn't really required.
>> Well - then a link to the law in question would be helpful.
>> > > - your plan outline indicates you plan to add attributes (in
>> > > particular height) to the import data (and possibly also existing
>> > > data in OSM) from separate, automatically produced and originally
>> > > unrelated data without manual per case review - a.k.a. bot mapping.
>> > > There are many mappers who believe such data should be kept
>> > > separate and should not get into the OSM database because it would
>> > > make work more difficult both for mappers and data users.
>> > I haven't heard that building height shouldn't be added to building
>> > footprints. Can you provide a link to some documentation on why
>> > height shouldn't be added to building footprints?
>> Huh? Don't think i have said anything along those lines.
>> What i was talking about is the problem of a mechanical edit or import
>> of such data produced through a fully automated process without
>> individual manual verification.
>> Christoph Hormann
>> Imports mailing list
>> Imports at openstreetmap.org
More information about the Imports