Re: [HOT] QGIS and OSM and..

Tue, 12 May 2015 01:44:55 -0700

Hello Michael,

        Thanks for your response.  I should have known better and pruned off all the old material.  That's a good idea anyway.  I thought it was my attachments that were the problem, might not have helped though.  Thanks for the tip.

        Yes, it seems that OSM has a preset pattern of doing things and their tagging system seems to complicate data transfer.  Of course, sending off-line edits back into the online world would pose a challenge.  But with a little planning I think it could be done.  However, if the final helipad file does not need further verification from the GIS-crowd, then it could be sent directly to the end-users in whatever format suited them best.

        I certainly don't comprehend the licensing issues but don't know why it should be overly difficult, especially in an emergency situation.  I would understand if someone was trying to make a dollar off Google Earth.  Or cause a liability for them somehow.

        However, what are the copyright issues of creating a database of points in QGIS over a Bing, MapQuest or Google maps layer?  I suppose they are all licensed differently perhaps.  More lawyers getting richer!

        I'm not sure if I really have the time to sit down and verify 1500+ helipad points but from the little I have seen of the file so far, it would seem to be useful.  If there was enough interest, I could try to scare up a couple more experienced pilots to speed up the process.

        I have made enough noise on these e-mail threads about it now that if there is no uptake by the high-priced help, I will go back to my local projects here.  I don't get the impression that there is any official channel to deal with these things, just shout out the door and see if a passerby hears you.

        Thanks very much for your help and support, Cheers . . . . . . . . Spring



At 11-05-2015 23:44 Monday, Michael wrote:
Hi Spring,

2015-05-12 0:45 GMT+02:00 Springfield Harrison <[email protected] >:

"Posting of your message titled "RE: [HOT] QGIS and OSM and.." has been rejected by the list moderator." File too big, deleted, sorry for duplication to those who received it earlier . . . .


To avoid problems with message size I recommend quoting only the most recent mail and delete everything else.
Â
        Right, thanks for the update. Introducing yet another data-entry method is certainly not ideal but the perspective view in GE is certainly a great help. I've edited 15 targets so far directly in GE and saved them as a different file. This file loads back into Manifold very well and, when done, I can synthesize a few extra fields of information about each helipad. Currently, I'm coding them 1, 2, 3 and adding altitude and comments. Code 1 is Good, 2 is probably OK, 3 is rejected as built-up, too small, off level, etc. I'm fairly confident with the coding so far, some ground truthing would be good.


While this is valuable information to have I doubt that this should go back into OSM. At least the current tagging of potential landing sites as "leisure=common" does not provide additional tags. So this would require some thoughts about defining addtional tags to hold this information.
Â

        Progress is reasonably quick but there are over 1400. I now see that some of the OSM fields do not show up when the KML lands in Manifold but they are visible in GE itself. We should probably check the aeroway = helipad targets also. Really hard to assess these from purely an overhead view. I always in/zoom out, spin around and get a low level, oblique view before feeling confident. If there are tourist photos, that is also a great help. If there is any doubt about size or surface, I give it a 2.



For my understanding this information must not go back into OSM. At least for my understanding any information gathered via Google Earth is incompatible with OSM due to licensing. So before adding any of this information into OSM I would recommend to clairfy this first. I think even tourist photos retrieved from Panoramio are not straightforward to include. But I am not a lawyer, of course.

This is a very delicate aspect and in general OSM is very carful not to use any information from non-compatible licenses. HOT does not have any special execptins since it potentially causes issues for the entire project.

Thanks,
Michael
_______________________________________________
HOT mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/hot

Reply via email to