You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> on 2010/03/19 06:12:44 UTC
Re: Alrighty then
Hey Patrick,
I'm reply to list since I think we're all on sis-dev@incubator:
> So the list emails are set up, I believe we have commit karma, need to check,
> I just got out of ER yesterday so taking things a little easy for a couple of
> days.
Sorry to hear that! I think karma is set up for everyone. Please check out:
https://svn.apache.org/repos/asf/incubator/sis/
And start trying to commit. If you see any issues, just let a mentor know --
they should be able to fix for us.
> Can folks subscribe to the following lists so we don't have to maintain this
> list?
> sis-dev-subscribe@incubator.apache.org
> sis-user-subscribe@incubator.apache.org
> sis-commits-subscribe@incubator.apache.org
+1. I think everyone is on the list -- for a sanity check, could everyone
reply to the list saying you are here?
>
> For mentors, committers, etc.
> sis-private-subscribe@incubator.apache.org
+1, done on my end.
>
> Does anyone know how to get MarkMail subscribed ?
Already done! Check out:
http://markmail.org/browse/org.apache.incubator.sis-dev
http://markmail.org/browse/org.apache.incubator.sis-commits
All good!
>
> As for where we are with software, right now we have an ok framework for
> cartography style searching / coordinate system, a poly-line, and convex hull
> method.
Yep, we need to take the first step at porting that code into the o.a.sis.*
framework. I've reported SIS-1 for that. Was hoping to have a second last
weekend to make some headway but haven't found a chance yet. If someone else
does or wants to take the initial step at moving it over from Sourceforge,
by all means. Otherwise, I'm thinking maybe this weekend I'll have time.
> There are a couple of things I'd like to throw out there as ideas, let me know
> what you think of them
> * Create a configuration factory
>> * Allow you to specify projection methods
+1
>> * Custom planetary radii (maybe Enumerate the planets of the solar system to
>> begin with)
>> * A check to verify that some functionality is compatible with the projection
>> method, as EPSG is not compatible with poly-lines (well not without pain)
+1 -- I would imagine that we could do this by checking what the coordinate
system is right? Like if it's lat-lon, in EPSG WGS84. We would need some way
of automatically identifying the incoming spatial reference method though,
and perhaps an object hierarchy for this. I was thinking too that if we have
Points, and Shapes and Polygons as core classes, then we should provide easy
mechanisms to construct say an EPSG WGS84 point from a String, Double, Int,
etc. WDYT?
> * Look at ways to blend transitions
>> * Can we come up with a way to transition a path from one coordinate system
>> to another, such as drawing a line across the poles or meridians, somewhere
>> polar coordinates might make more sense than sinusoidal or Mercator
>> projections?
Good idea. I think if we can:
- Come up with a simple Object diagram: Point *...*, Coordinate System 1 ...
* Projection, ...
- Build a framework that takes in basic Java data types and converts them to
our o.a.sis.core.Objects
- Provide all of the distance functionality (point/radius, bounding box,
polygon)
- Provide translation mechanisms between coordinate spaces
- Provide a simple XML/JSON format for points to take as input and produce
as output
That would be a great framework to do some of the more complex stuff on top
of.
Thoughts?
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: Alrighty then
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Patrick,
Sounds great. That sounds awesome. Should we cm the data maybe in:
/trunk
/src/test/testdata
?
I set up the basic dir structure I posted on the list the other day in
r925655 and r925656, and I set up the testdata dir according the above. If
you think it should go somewhere else, feel free to move it.
Cheers,
Chris
On 3/19/10 3:06 PM, "Patrick O'leary" <pj...@pjaol.com> wrote:
> Thanks Chris-
>
> Digging around for some data that we can use, came across
> http://www.factual.com/ which has open spread sheets, free to download /
> use. One of the data sets is CA restaurants, I can tie in geoapi.com and
> knock out a geo-coded version of the data there for us to use.
>
>
>
> On Fri, Mar 19, 2010 at 1:57 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> LOL @ u guys.
>>
>> +1 from me to tweet away! I'll set up:
>>
>> http://twitter.com/apache_sis/
>>
>> Cheers,
>> Chris
>>
>>
>>
>> On 3/19/10 2:26 PM, "Ian Holsman" <kr...@gmail.com> wrote:
>>
>> On 3/20/10 7:46 AM, patrick o'leary wrote:
>>>
>>> Twitter, have been avoiding that young peoples thing for years, but i
>> guess
>>> it's time to cave :-)
>>>
>>>
>>
>> sadly
>> studies have shown that most social networks are inhabited by 37 year
>> old male dudes.
>> sorry to burst your bubble.
>>>
>>>
>>>>
>>>>
>>>> On 3/20/10 1:17 AM, Greg Reddin wrote:
>>>>
>>>>
>>>>> On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> And start trying to commit. If you see any issues, just let a mentor
>> know
>>>>>> --
>>>>>> they should be able to fix for us.
>>>>>>
>>>>>>
>>>>>>
>>>>> Remember (if you didn't already know) that infra changed the svn
>>>>> authentication to LDAP yesterday so if you have trouble committing it
>>>>> could be related to that. I'll help you work through it if you run
>>>>> into trouble.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> +1. I think everyone is on the list -- for a sanity check, could
>> everyone
>>>>>> reply to the list saying you are here?
>>>>>>
>>>>>>
>>>>>>
>>>>> Present :-)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: Chris.Mattmann@jpl.nasa.gov
>> WWW: http://sunset.usc.edu/~mattmann/<http://sunset.usc.edu/%7Emattmann/>
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: Alrighty then
Posted by patrick o'leary <pj...@pjaol.com>.
Thanks Chris-
Digging around for some data that we can use, came across
http://www.factual.com/ which has open spread sheets, free to download /
use. One of the data sets is CA restaurants, I can tie in geoapi.com and
knock out a geo-coded version of the data there for us to use.
On Fri, Mar 19, 2010 at 1:57 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> LOL @ u guys.
>
> +1 from me to tweet away! I'll set up:
>
> http://twitter.com/apache_sis/
>
> Cheers,
> Chris
>
>
>
> On 3/19/10 2:26 PM, "Ian Holsman" <kr...@gmail.com> wrote:
>
> On 3/20/10 7:46 AM, patrick o'leary wrote:
> >
> > Twitter, have been avoiding that young peoples thing for years, but i
> guess
> > it's time to cave :-)
> >
> >
>
> sadly
> studies have shown that most social networks are inhabited by 37 year
> old male dudes.
> sorry to burst your bubble.
> >
> >
> >>
> >>
> >> On 3/20/10 1:17 AM, Greg Reddin wrote:
> >>
> >>
> >>> On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
> >>> <ch...@jpl.nasa.gov> wrote:
> >>>
> >>>
> >>>
> >>>> And start trying to commit. If you see any issues, just let a mentor
> know
> >>>> --
> >>>> they should be able to fix for us.
> >>>>
> >>>>
> >>>>
> >>> Remember (if you didn't already know) that infra changed the svn
> >>> authentication to LDAP yesterday so if you have trouble committing it
> >>> could be related to that. I'll help you work through it if you run
> >>> into trouble.
> >>>
> >>>
> >>>
> >>>
> >>>> +1. I think everyone is on the list -- for a sanity check, could
> everyone
> >>>> reply to the list saying you are here?
> >>>>
> >>>>
> >>>>
> >>> Present :-)
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: Chris.Mattmann@jpl.nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/<http://sunset.usc.edu/%7Emattmann/>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
Re: Alrighty then
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
LOL @ u guys.
+1 from me to tweet away! I'll set up:
http://twitter.com/apache_sis/
Cheers,
Chris
On 3/19/10 2:26 PM, "Ian Holsman" <kr...@gmail.com> wrote:
On 3/20/10 7:46 AM, patrick o'leary wrote:
>
> Twitter, have been avoiding that young peoples thing for years, but i guess
> it's time to cave :-)
>
>
sadly
studies have shown that most social networks are inhabited by 37 year
old male dudes.
sorry to burst your bubble.
>
>
>>
>>
>> On 3/20/10 1:17 AM, Greg Reddin wrote:
>>
>>
>>> On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>
>>>
>>>
>>>> And start trying to commit. If you see any issues, just let a mentor know
>>>> --
>>>> they should be able to fix for us.
>>>>
>>>>
>>>>
>>> Remember (if you didn't already know) that infra changed the svn
>>> authentication to LDAP yesterday so if you have trouble committing it
>>> could be related to that. I'll help you work through it if you run
>>> into trouble.
>>>
>>>
>>>
>>>
>>>> +1. I think everyone is on the list -- for a sanity check, could everyone
>>>> reply to the list saying you are here?
>>>>
>>>>
>>>>
>>> Present :-)
>>>
>>>
>>>
>>>
>>
>>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: Alrighty then
Posted by Ian Holsman <kr...@gmail.com>.
On 3/20/10 7:46 AM, patrick o'leary wrote:
>
> Twitter, have been avoiding that young peoples thing for years, but i guess
> it's time to cave :-)
>
>
sadly
studies have shown that most social networks are inhabited by 37 year
old male dudes.
sorry to burst your bubble.
>
>
>>
>>
>> On 3/20/10 1:17 AM, Greg Reddin wrote:
>>
>>
>>> On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
>>> <ch...@jpl.nasa.gov> wrote:
>>>
>>>
>>>
>>>> And start trying to commit. If you see any issues, just let a mentor know
>>>> --
>>>> they should be able to fix for us.
>>>>
>>>>
>>>>
>>> Remember (if you didn't already know) that infra changed the svn
>>> authentication to LDAP yesterday so if you have trouble committing it
>>> could be related to that. I'll help you work through it if you run
>>> into trouble.
>>>
>>>
>>>
>>>
>>>> +1. I think everyone is on the list -- for a sanity check, could everyone
>>>> reply to the list saying you are here?
>>>>
>>>>
>>>>
>>> Present :-)
>>>
>>>
>>>
>>>
>>
>>
>
Re: Alrighty then
Posted by patrick o'leary <pj...@pjaol.com>.
On Fri, Mar 19, 2010 at 11:51 AM, Ian Holsman <kr...@gmail.com> wrote:
> I'm here as well.
>
> can I make a suggestion.
> then while we are building up the framework, we also build a "semi-serious"
> application that uses it alongside the framework.
> this might help new developers come up to speed with how to use the
> framework and in-turn will start using it more.
>
> Good idea, was thinking of doing something with townme data set.
> probably should also set up a twitter account to post announcements/minor
> achievements on as well. (also helps to get the message out there).
Twitter, have been avoiding that young peoples thing for years, but i guess
it's time to cave :-)
>
>
>
> On 3/20/10 1:17 AM, Greg Reddin wrote:
>
>> On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
>> <ch...@jpl.nasa.gov> wrote:
>>
>>
>>> And start trying to commit. If you see any issues, just let a mentor know
>>> --
>>> they should be able to fix for us.
>>>
>>>
>> Remember (if you didn't already know) that infra changed the svn
>> authentication to LDAP yesterday so if you have trouble committing it
>> could be related to that. I'll help you work through it if you run
>> into trouble.
>>
>>
>>
>>> +1. I think everyone is on the list -- for a sanity check, could everyone
>>> reply to the list saying you are here?
>>>
>>>
>> Present :-)
>>
>>
>>
>
>
Re: Alrighty then
Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ian,
+1 to your suggestion. I have a couple of use cases from NASA that I think we can build around. Here's a stream of consciousness from the oceans world:
1. for all GODAE High Resolution Sea Surface Temperature (GHRSST) data from NOAA's National Oceanographic Data Center (NODC):
* get the data (maybe use OODT)
* extract out the metadata from the files (maybe use Tika for this, will need HDF/netCDF extractors, which aren't currently there)
* compute equator crossing point from orbital swath parameters (use SIS distance, projection functions for this, and lookup the orbital parameters somewhere)
* compute lat/lon from equator crossing point using SIS
* use SIS to output, for each GHRSST granule (100s of thousands-millions), a JSON .met file (or XML .met file) containing the granule name and its lat/lon that defines the lat/lon for all points in time for the orbital swath defined by each GRHSST granule
If we can build SIS so that it supports that use case, that would definitely help...
The Twitter account is up: http://twitter.com/apache_sis/
Cheers,
Chris
On 3/19/10 12:51 PM, "Ian Holsman" <kr...@gmail.com> wrote:
I'm here as well.
can I make a suggestion.
then while we are building up the framework, we also build a
"semi-serious" application that uses it alongside the framework.
this might help new developers come up to speed with how to use the
framework and in-turn will start using it more.
probably should also set up a twitter account to post
announcements/minor achievements on as well. (also helps to get the
message out there).
On 3/20/10 1:17 AM, Greg Reddin wrote:
> On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>
>> And start trying to commit. If you see any issues, just let a mentor know --
>> they should be able to fix for us.
>>
> Remember (if you didn't already know) that infra changed the svn
> authentication to LDAP yesterday so if you have trouble committing it
> could be related to that. I'll help you work through it if you run
> into trouble.
>
>
>> +1. I think everyone is on the list -- for a sanity check, could everyone
>> reply to the list saying you are here?
>>
> Present :-)
>
>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Re: Alrighty then
Posted by Ian Holsman <kr...@gmail.com>.
I'm here as well.
can I make a suggestion.
then while we are building up the framework, we also build a
"semi-serious" application that uses it alongside the framework.
this might help new developers come up to speed with how to use the
framework and in-turn will start using it more.
probably should also set up a twitter account to post
announcements/minor achievements on as well. (also helps to get the
message out there).
On 3/20/10 1:17 AM, Greg Reddin wrote:
> On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
>
>> And start trying to commit. If you see any issues, just let a mentor know --
>> they should be able to fix for us.
>>
> Remember (if you didn't already know) that infra changed the svn
> authentication to LDAP yesterday so if you have trouble committing it
> could be related to that. I'll help you work through it if you run
> into trouble.
>
>
>> +1. I think everyone is on the list -- for a sanity check, could everyone
>> reply to the list saying you are here?
>>
> Present :-)
>
>
Re: Alrighty then
Posted by Greg Reddin <gr...@gmail.com>.
On Fri, Mar 19, 2010 at 12:12 AM, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> And start trying to commit. If you see any issues, just let a mentor know --
> they should be able to fix for us.
Remember (if you didn't already know) that infra changed the svn
authentication to LDAP yesterday so if you have trouble committing it
could be related to that. I'll help you work through it if you run
into trouble.
> +1. I think everyone is on the list -- for a sanity check, could everyone
> reply to the list saying you are here?
Present :-)
Re: Alrighty then
Posted by patrick o'leary <pj...@pjaol.com>.
On Thu, Mar 18, 2010 at 11:35 PM, Mccleese, Sean W (388A) <
sean.w.mccleese@jpl.nasa.gov> wrote:
> Hey everyone,
>
> Just to follow up: I'm also subscribed to all the SIS lists (dev, user,
> commits, private).
> My comments are below:
>
> Patrick wrote:
> > There are a couple of things I'd like to throw out there as ideas, let me
> know
> > what you think of them
> > * Create a configuration factory
> >> * Allow you to specify projection methods
>
> I totally agree with this. That would be hugely helpful for the various
> sorts of use cases I think we're going to encounter moving forward. A lot of
> the frameworks I've seen so far make far too many assumptions (or, simply,
> try to make things too simple for their own good) on what sort of
> projections you're going to be using (see: JTS). Putting some facility
> upfront to specify that in a simple standard way would be a great first
> step, I think.
>
> Chris wrote:
> - Come up with a simple Object diagram: Point *...*, Coordinate System 1
> ...
> * Projection, ...
>
> - Build a framework that takes in basic Java data types and converts them
> to
> our o.a.sis.core.Objects
>
Like java Point to SIS Point?
> - Provide all of the distance functionality (point/radius, bounding box,
> polygon)
> - Provide translation mechanisms between coordinate spaces
> - Provide a simple XML/JSON format for points to take as input and produce
> as output
>
> +1 to this as well. It would be awesome to have a native XML/JSON
> input/output factory. That would be awesome for the stuff we're trying to do
> here at JPL and, I imagine, a lot of other uses in the community.
>
>
+1 think that we should keep it simple, as output writers often become
complex and restrictive very quickly
> One addition: I think it would be awesome if we, natively, supported some
> sort of elliptical / swath orbit polygon functions. Right now there's all
> sorts of ugly stuff you have to do to fit that into the polygon paradigm
> that so many frameworks force you into. I think that would really go far in
> making SIS a go-to application for a lot of under served communities right
> now. Anyway, just throwing that out there.
>
Yeah, makes sense as a corridor, which would be a range between 2 polylines,
would the definition of it make sense as the center vertexes of the path,
and a width?
> -Sean
> ________________________________________
> From: Mattmann, Chris A (388J) [chris.a.mattmann@jpl.nasa.gov]
> Sent: Thursday, March 18, 2010 10:12 PM
> To: sis-dev@incubator.apache.org
> Subject: Re: Alrighty then
>
> Hey Patrick,
>
> I'm reply to list since I think we're all on sis-dev@incubator:
>
> > So the list emails are set up, I believe we have commit karma, need to
> check,
> > I just got out of ER yesterday so taking things a little easy for a
> couple of
> > days.
>
> Sorry to hear that! I think karma is set up for everyone. Please check out:
>
> https://svn.apache.org/repos/asf/incubator/sis/
>
> And start trying to commit. If you see any issues, just let a mentor know
> --
> they should be able to fix for us.
>
> > Can folks subscribe to the following lists so we don't have to maintain
> this
> > list?
> > sis-dev-subscribe@incubator.apache.org
> > sis-user-subscribe@incubator.apache.org
> > sis-commits-subscribe@incubator.apache.org
>
> +1. I think everyone is on the list -- for a sanity check, could everyone
> reply to the list saying you are here?
>
> >
> > For mentors, committers, etc.
> > sis-private-subscribe@incubator.apache.org
>
> +1, done on my end.
>
> >
> > Does anyone know how to get MarkMail subscribed ?
>
> Already done! Check out:
>
> http://markmail.org/browse/org.apache.incubator.sis-dev
> http://markmail.org/browse/org.apache.incubator.sis-commits
>
> All good!
>
> >
> > As for where we are with software, right now we have an ok framework for
> > cartography style searching / coordinate system, a poly-line, and convex
> hull
> > method.
>
> Yep, we need to take the first step at porting that code into the o.a.sis.*
> framework. I've reported SIS-1 for that. Was hoping to have a second last
> weekend to make some headway but haven't found a chance yet. If someone
> else
> does or wants to take the initial step at moving it over from Sourceforge,
> by all means. Otherwise, I'm thinking maybe this weekend I'll have time.
>
>
> > There are a couple of things I'd like to throw out there as ideas, let me
> know
> > what you think of them
> > * Create a configuration factory
> >> * Allow you to specify projection methods
>
> +1
>
> >> * Custom planetary radii (maybe Enumerate the planets of the solar
> system to
> >> begin with)
> >> * A check to verify that some functionality is compatible with the
> projection
> >> method, as EPSG is not compatible with poly-lines (well not without
> pain)
>
> +1 -- I would imagine that we could do this by checking what the coordinate
> system is right? Like if it's lat-lon, in EPSG WGS84. We would need some
> way
> of automatically identifying the incoming spatial reference method though,
> and perhaps an object hierarchy for this. I was thinking too that if we
> have
> Points, and Shapes and Polygons as core classes, then we should provide
> easy
> mechanisms to construct say an EPSG WGS84 point from a String, Double, Int,
> etc. WDYT?
>
> > * Look at ways to blend transitions
> >> * Can we come up with a way to transition a path from one coordinate
> system
> >> to another, such as drawing a line across the poles or meridians,
> somewhere
> >> polar coordinates might make more sense than sinusoidal or Mercator
> >> projections?
>
> Good idea. I think if we can:
>
> - Come up with a simple Object diagram: Point *...*, Coordinate System 1
> ...
> * Projection, ...
> - Build a framework that takes in basic Java data types and converts them
> to
> our o.a.sis.core.Objects
> - Provide all of the distance functionality (point/radius, bounding box,
> polygon)
> - Provide translation mechanisms between coordinate spaces
> - Provide a simple XML/JSON format for points to take as input and produce
> as output
>
> That would be a great framework to do some of the more complex stuff on top
> of.
>
> Thoughts?
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: Chris.Mattmann@jpl.nasa.gov
> WWW: http://sunset.usc.edu/~mattmann/<http://sunset.usc.edu/%7Emattmann/>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
RE: Alrighty then
Posted by "Mccleese, Sean W (388A)" <se...@jpl.nasa.gov>.
Hey everyone,
Just to follow up: I'm also subscribed to all the SIS lists (dev, user, commits, private).
My comments are below:
Patrick wrote:
> There are a couple of things I'd like to throw out there as ideas, let me know
> what you think of them
> * Create a configuration factory
>> * Allow you to specify projection methods
I totally agree with this. That would be hugely helpful for the various sorts of use cases I think we're going to encounter moving forward. A lot of the frameworks I've seen so far make far too many assumptions (or, simply, try to make things too simple for their own good) on what sort of projections you're going to be using (see: JTS). Putting some facility upfront to specify that in a simple standard way would be a great first step, I think.
Chris wrote:
- Come up with a simple Object diagram: Point *...*, Coordinate System 1 ...
* Projection, ...
- Build a framework that takes in basic Java data types and converts them to
our o.a.sis.core.Objects
- Provide all of the distance functionality (point/radius, bounding box,
polygon)
- Provide translation mechanisms between coordinate spaces
- Provide a simple XML/JSON format for points to take as input and produce
as output
+1 to this as well. It would be awesome to have a native XML/JSON input/output factory. That would be awesome for the stuff we're trying to do here at JPL and, I imagine, a lot of other uses in the community.
One addition: I think it would be awesome if we, natively, supported some sort of elliptical / swath orbit polygon functions. Right now there's all sorts of ugly stuff you have to do to fit that into the polygon paradigm that so many frameworks force you into. I think that would really go far in making SIS a go-to application for a lot of under served communities right now. Anyway, just throwing that out there.
-Sean
________________________________________
From: Mattmann, Chris A (388J) [chris.a.mattmann@jpl.nasa.gov]
Sent: Thursday, March 18, 2010 10:12 PM
To: sis-dev@incubator.apache.org
Subject: Re: Alrighty then
Hey Patrick,
I'm reply to list since I think we're all on sis-dev@incubator:
> So the list emails are set up, I believe we have commit karma, need to check,
> I just got out of ER yesterday so taking things a little easy for a couple of
> days.
Sorry to hear that! I think karma is set up for everyone. Please check out:
https://svn.apache.org/repos/asf/incubator/sis/
And start trying to commit. If you see any issues, just let a mentor know --
they should be able to fix for us.
> Can folks subscribe to the following lists so we don't have to maintain this
> list?
> sis-dev-subscribe@incubator.apache.org
> sis-user-subscribe@incubator.apache.org
> sis-commits-subscribe@incubator.apache.org
+1. I think everyone is on the list -- for a sanity check, could everyone
reply to the list saying you are here?
>
> For mentors, committers, etc.
> sis-private-subscribe@incubator.apache.org
+1, done on my end.
>
> Does anyone know how to get MarkMail subscribed ?
Already done! Check out:
http://markmail.org/browse/org.apache.incubator.sis-dev
http://markmail.org/browse/org.apache.incubator.sis-commits
All good!
>
> As for where we are with software, right now we have an ok framework for
> cartography style searching / coordinate system, a poly-line, and convex hull
> method.
Yep, we need to take the first step at porting that code into the o.a.sis.*
framework. I've reported SIS-1 for that. Was hoping to have a second last
weekend to make some headway but haven't found a chance yet. If someone else
does or wants to take the initial step at moving it over from Sourceforge,
by all means. Otherwise, I'm thinking maybe this weekend I'll have time.
> There are a couple of things I'd like to throw out there as ideas, let me know
> what you think of them
> * Create a configuration factory
>> * Allow you to specify projection methods
+1
>> * Custom planetary radii (maybe Enumerate the planets of the solar system to
>> begin with)
>> * A check to verify that some functionality is compatible with the projection
>> method, as EPSG is not compatible with poly-lines (well not without pain)
+1 -- I would imagine that we could do this by checking what the coordinate
system is right? Like if it's lat-lon, in EPSG WGS84. We would need some way
of automatically identifying the incoming spatial reference method though,
and perhaps an object hierarchy for this. I was thinking too that if we have
Points, and Shapes and Polygons as core classes, then we should provide easy
mechanisms to construct say an EPSG WGS84 point from a String, Double, Int,
etc. WDYT?
> * Look at ways to blend transitions
>> * Can we come up with a way to transition a path from one coordinate system
>> to another, such as drawing a line across the poles or meridians, somewhere
>> polar coordinates might make more sense than sinusoidal or Mercator
>> projections?
Good idea. I think if we can:
- Come up with a simple Object diagram: Point *...*, Coordinate System 1 ...
* Projection, ...
- Build a framework that takes in basic Java data types and converts them to
our o.a.sis.core.Objects
- Provide all of the distance functionality (point/radius, bounding box,
polygon)
- Provide translation mechanisms between coordinate spaces
- Provide a simple XML/JSON format for points to take as input and produce
as output
That would be a great framework to do some of the more complex stuff on top
of.
Thoughts?
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++