I’m thinking about participating in GSoC this year, if I find some interesting topic. I went through GRASS GSoC ideas. The two most interesting for me are Vector legend and Extracting the medial axis of polygon. I would appreciate if anyone can give me more information to these topics.
The first one is maybe described enough and I just need to study that more to understand it better, but still anything more regarding that would be appreciated.
The medial axis is not really clear to me. I know what is medial axis, but I would like to know more about desired results. How it should be integrated to GRASS (some new module?). Is it necessary to write it in C (why not python)? Should the result algorithm extract the exact medial axis or the approximation? …
And one more question. Is any of these topics suitable for me if I am not experienced in GRASS at all?
Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.
On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová
<tfiedlerova@gmail.com> wrote:
Hello,
I'm thinking about participating in GSoC this year, if I find some
interesting topic. I went through GRASS GSoC ideas. The two most interesting
for me are Vector legend and Extracting the medial axis of polygon. I would
appreciate if anyone can give me more information to these topics.
The first one is maybe described enough and I just need to study that more
to understand it better, but still anything more regarding that would be
appreciated.
The medial axis is not really clear to me. I know what is medial axis, but I
would like to know more about desired results. How it should be integrated
to GRASS (some new module?). Is it necessary to write it in C (why not
python)? Should the result algorithm extract the exact medial axis or the
approximation? ...
A good approximation would be fine. It would be necessary to write in
C for efficiency reasons and because C library functions need to be
heavily used. Additionally, search structures like balanced binary
search trees and min heaps are needed which are already implemented in
GRASS as C code. I have already written 2 different C modules trying
to extract the medial axis, both are incredibly complex and none of
them works properly. I am familiar with GRASS, C, and Python and like
to use the easiest approach. In this case I am pretty sure that the
easiest and most appropriate approach is using C, not Python.
Therefore I would recommend a good knowledge of C and some knowledge
of the GRASS C API for this project.
Markus M
And one more question. Is any of these topics suitable for me if I am not
experienced in GRASS at all?
On Thu, Feb 20, 2014 at 4:06 PM, Markus Metz
<markus.metz.giswork@gmail.com>wrote:
On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová
<tfiedlerova@gmail.com> wrote:
> Hello,
>
> I'm thinking about participating in GSoC this year, if I find some
> interesting topic. I went through GRASS GSoC ideas. The two most
interesting
> for me are Vector legend and Extracting the medial axis of polygon. I
would
> appreciate if anyone can give me more information to these topics.
>
> The first one is maybe described enough and I just need to study that
more
> to understand it better, but still anything more regarding that would be
> appreciated.
>
> The medial axis is not really clear to me. I know what is medial axis,
but I
> would like to know more about desired results. How it should be
integrated
> to GRASS (some new module?). Is it necessary to write it in C (why not
> python)? Should the result algorithm extract the exact medial axis or the
> approximation? ...
A good approximation would be fine. It would be necessary to write in
C for efficiency reasons and because C library functions need to be
heavily used. Additionally, search structures like balanced binary
search trees and min heaps are needed which are already implemented in
GRASS as C code. I have already written 2 different C modules trying
to extract the medial axis, both are incredibly complex and none of
them works properly. I am familiar with GRASS, C, and Python and like
to use the easiest approach. In this case I am pretty sure that the
easiest and most appropriate approach is using C, not Python.
Therefore I would recommend a good knowledge of C and some knowledge
of the GRASS C API for this project.
Markus M
Just in case it would be useful (at least for Tereza, it's mostly in Czech):
this is a presentation on straight skeleton algorithm (if medial axis is
the same or at least related?).
Anna
>
> And one more question. Is any of these topics suitable for me if I am not
> experienced in GRASS at all?
>
> Thank you
>
> Tereza Fiedlerová
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
On Thu, Feb 20, 2014 at 10:47 PM, Anna Petrášová <kratochanna@gmail.com> wrote:
On Thu, Feb 20, 2014 at 4:06 PM, Markus Metz <markus.metz.giswork@gmail.com>
wrote:
On Thu, Feb 20, 2014 at 9:08 AM, Tereza Fiedlerová
<tfiedlerova@gmail.com> wrote:
> Hello,
>
> I'm thinking about participating in GSoC this year, if I find some
> interesting topic. I went through GRASS GSoC ideas. The two most
> interesting
> for me are Vector legend and Extracting the medial axis of polygon. I
> would
> appreciate if anyone can give me more information to these topics.
>
> The first one is maybe described enough and I just need to study that
> more
> to understand it better, but still anything more regarding that would be
> appreciated.
>
> The medial axis is not really clear to me. I know what is medial axis,
> but I
> would like to know more about desired results. How it should be
> integrated
> to GRASS (some new module?). Is it necessary to write it in C (why not
> python)? Should the result algorithm extract the exact medial axis or
> the
> approximation? ...
A good approximation would be fine. It would be necessary to write in
C for efficiency reasons and because C library functions need to be
heavily used. Additionally, search structures like balanced binary
search trees and min heaps are needed which are already implemented in
GRASS as C code. I have already written 2 different C modules trying
to extract the medial axis, both are incredibly complex and none of
them works properly. I am familiar with GRASS, C, and Python and like
to use the easiest approach. In this case I am pretty sure that the
easiest and most appropriate approach is using C, not Python.
Therefore I would recommend a good knowledge of C and some knowledge
of the GRASS C API for this project.
Markus M
Just in case it would be useful (at least for Tereza, it's mostly in Czech):
this is a presentation on straight skeleton algorithm (if medial axis is the
same or at least related?).
A straight skeleton is not the same like a medial axis: only the
medial axis is equidistant to the polygon boundaries.
Markus M
Anna
>
> And one more question. Is any of these topics suitable for me if I am
> not
> experienced in GRASS at all?
>
> Thank you
>
> Tereza Fiedlerová
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
finally I considered the metadata topic is probably the most appropriate for me. My aim now is to find out as much as I can about it to have better idea what is going on. If you have any additional information or resources I could study, please let me know. Thanks
Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.
finally I considered the metadata topic is probably the most appropriate for
me. My aim now is to find out as much as I can about it to have better idea
what is going on. If you have any additional information or resources I
could study, please let me know. Thanks
perfect, in this regard I would like to open discussion whether to
speak just about metadata (ISO, Inspire) or also about supporting
Inspire services (view and download)...
finally I considered the metadata topic is probably the most appropriate for
me. My aim now is to find out as much as I can about it to have better idea
what is going on. If you have any additional information or resources I
could study, please let me know. Thanks
perfect, in this regard I would like to open discussion whether to
speak just about metadata (ISO, Inspire) or also about supporting
Inspire services (view and download)…
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
finally I considered the metadata topic is probably the most appropriate for
me. My aim now is to find out as much as I can about it to have better idea
what is going on. If you have any additional information or resources I
could study, please let me know. Thanks
Tereza, I’m glad to hear that. As several hints have already come, I’d suggest to set a page in the trac where we can store all these inputs that otherwise would be difficult to find again.
perfect, in this regard I would like to open discussion whether to
speak just about metadata (ISO, Inspire) or also about supporting
Inspire services (view and download)…
Martin, this makes sense, but I’d stick with a target that is reachable within the GSoC. Of course the occasion is suitable to gather all the ideas which can be developed in the future.
Thanks,
MaDi
–
Best regards,
Dr. Margherita DI LEO
Scientific / technical project officer
European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261
Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.
From what I understand, the ISO 19115-1 metadata standard should be finalized shortly. Getting an official copy of the standard for this work ( if they finalize in time) would be useful.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
finally I considered the metadata topic is probably the most appropriate for
me. My aim now is to find out as much as I can about it to have better idea
what is going on. If you have any additional information or resources I
could study, please let me know. Thanks
Tereza, I’m glad to hear that. As several hints have already come, I’d suggest to set a page in the trac where we can store all these inputs that otherwise would be difficult to find again.
perfect, in this regard I would like to open discussion whether to
speak just about metadata (ISO, Inspire) or also about supporting
Inspire services (view and download)…
Martin, this makes sense, but I’d stick with a target that is reachable within the GSoC. Of course the occasion is suitable to gather all the ideas which can be developed in the future.
Thanks,
MaDi
–
Best regards,
Dr. Margherita DI LEO
Scientific / technical project officer
European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261
Disclaimer: The views expressed are purely those of the writer and may not in any circumstance be regarded as stating an official position of the European Commission.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
First, my apologies for not responding to your earlier nudge. However there’s not a great deal to report on the plugin - MapAction remains keen to take it forward, but doesn’t have the development resources at the moment to be able to do much about it. We’d be happy to expand on the documentation though, and the osgeo gsoc could be an opportunity to get things moving if people were interested. Certainly our experiences in the Philippines last year underlined our need for better metadata creation and management tools, so it’s high on our list of action points for follow up.
Look forward to seeing how things develop, and we’ll see if there’s anything we can contribute.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
First, my apologies for not responding to your earlier nudge. However there’s not a great deal to report on the plugin - MapAction remains keen to take it forward, but doesn’t have the development resources at the moment to be able to do much about it. We’d be happy to expand on the documentation though, and the osgeo gsoc could be an opportunity to get things moving if people were interested. Certainly our experiences in the Philippines last year underlined our need for better metadata creation and management tools, so it’s high on our list of action points for follow up.
Look forward to seeing how things develop, and we’ll see if there’s anything we can contribute.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
