Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import of depth profile data released under open licenses #125

Open
Skippern opened this issue Jan 15, 2015 · 7 comments
Open

Import of depth profile data released under open licenses #125

Skippern opened this issue Jan 15, 2015 · 7 comments

Comments

@Skippern
Copy link
Member

Is there a possibility to import depth data released under open licenses? It seems that the Norwegian kartverket either have or might soon release their depth data. They have a lot of data released under the terms of Digital Norge, and loads og geospatial data is already or in the process of being released under Public Domain or similar terms.

I have presented this in an issue in my BSB_scripts project

@cleanerx
Copy link
Member

Before we start importing third party data we need to setup our processing chain and get more robustness into it. Otherwise importing and debugging huge amounts of data is really cumbersome. We have data from the German Hydrographic institute we could use as well but first we need to be able to generate meaningful contents from it.

@Skippern
Copy link
Member Author

Ok.

Is it of interest to enter these datas into the pipe preparing for import, or should we keep it on hold until the processing chain is debugged and considered ready for release?

@cleanerx
Copy link
Member

Well we need to analyze what kind of data their are providing. It seems to me that all the data is processed. Currently we focus on raw measured data rather than generated contour lines. I think we need a concept for this kind of integration that is yet to be designed. So unless it is raw data I think holding it off is the best way to handle it.

@Nautic
Copy link
Contributor

Nautic commented Apr 17, 2015

We need a concept for to:
a) qualify raw data
b) qualify processed data
c) mark sources of data
d) mark licenses of data
e) store different quality levels, sources and licenses
f) store/transform different DB-formats

Until we have solutions, we should store such data seperate from our actual process,
added by a full description of source, format, quality, license, etc.

@HalluFIN
Copy link

HalluFIN commented Jul 9, 2015

@cleanerx
Copy link
Member

cleanerx commented Jul 9, 2015

Oh this license tricky. In strict terms I would be the licensee and I'm using the data to show them on the web page. Since I'm therefor redistributing it, it may be used for navigational purposes such as trip planning and positioning and this is exactly what the license forbids.

Is there any reason why this has been excluded ?
I think the section about waving off the liability would be ok but the other right is too restricted to make use of the data.

@HalluFIN
Copy link

I wrote to the ministerium. I'll wait the answer and get back to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants