Difference between revisions of "Java GIS Collaboration"

From OSGeo
Jump to navigation Jump to search
m (→‎Java-based GIS Projects: correct spelling for deegree and update deegree URL)
 
(17 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
== Collaboration? ==
 
== Collaboration? ==
It seems there is a call for collaboration between Java-based GIS projects like Jump and GeoTools, or uDig and gvSig every once in a while. This is an attempt to move from ''talk'' to ''action'', since we usually just nod and say "yeah, we should collaborate" and it ends there.
+
This page serves as a placeholder for information and discussion about possible opportunities for collaboration between FOSS GIS programs written in Java. This is an attempt to move from ''talk'' to ''action'', since we (members of the FOSS GIS Java community) usually just nod and say "yeah, we should collaborate" and it ends there.
  
 
== Java-based GIS Projects ==
 
== Java-based GIS Projects ==
Line 9: Line 9:
 
* [http://www.jump-project.org/project.php?PID=JTS&SID=OVER JTS]
 
* [http://www.jump-project.org/project.php?PID=JTS&SID=OVER JTS]
 
* [http://udig.refractions.net/ uDig] / [http://www.jgrass.org/ JGrass]
 
* [http://udig.refractions.net/ uDig] / [http://www.jgrass.org/ JGrass]
* [http://deegree.sourceforge.net/ Deegree]  
+
* [http://deegree.org/ deegree]  
 
* ''...''
 
* ''...''
  
Line 20: Line 20:
 
People from each team who are taking part in this discussion:
 
People from each team who are taking part in this discussion:
  
The Sunburned Surveyor
+
OpenJUMP - Landon Blake (sunburned.surveyor@gmail.com)
[sunburned.surveyor@gmail.com]
+
 
 +
uDig / GeoTools / GeoAPI - Cory Horner (chorner at refractions.net)
  
 
== Problems ==
 
== Problems ==
 
'''Licensing'''
 
'''Licensing'''
* LGPL vs GPL: everyone can use the LGPL code; GPL code will get less reuse
+
* LGPL vs GPL: everyone can use the LGPL code; GPL code will get less reuse.
* Different Feature Models. This makes it difficult to share code. For example, I can't just plug-in a data source from the GeoTools library because it won't give me JUMP Feature objects. It gives me GeoTools Feature objects, which I can't use. :] We can work towards a common Feature implementation, but that is difficult in many cases because so much existing code has been written. In the case of OpenJUMP a lot of code is written and also published bia public interfaces to plug-in developers, which makes it much harder to refactor code. (If you want to change things you break a lot of plug-ins.) One solution may be to design, produce, and maintain code that converts between the different object features.)
+
'''Feature'''
 +
* Different Feature Models. This makes it difficult to share code. For example, you can't just plug-in a data source from the GeoTools library into OpenJUMP because it won't give you JUMP Feature objects. It gives you GeoTools Feature objects, which OpenJUMP can't use. :] We can work towards a common Feature implementation, but that is difficult in many cases because so much existing code has been written. In the case of OpenJUMP a lot of code is written and also published bia public interfaces to plug-in developers, which makes it much harder to refactor code. (If you want to change things you break a lot of plug-ins.) One solution may be to design, produce, and maintain code that converts between the different object features.
  
 
== Ideas ==
 
== Ideas ==
 
* draw a picture (who is using what right now?)
 
* draw a picture (who is using what right now?)
 
* have an IRC meeting and figure out where we can collaborate
 
* have an IRC meeting and figure out where we can collaborate
 +
* a BOF at FOSS4G2007 ?
 +
 +
== Collaboration ==
 +
 +
* [[GML Geometry]]
 +
 +
=== Opportunities for Collaboration ===
  
== Opportunities for Collaboration ==
 
 
* Systems built on JTS. (Spatial Relationship Constraints, Geometry Constraints, Topology)
 
* Systems built on JTS. (Spatial Relationship Constraints, Geometry Constraints, Topology)
 
* GIS Components that don't depend directly on the existing feature models. (Annotation/Map Labels Model, Non-Spatial Features)
 
* GIS Components that don't depend directly on the existing feature models. (Annotation/Map Labels Model, Non-Spatial Features)
 +
 +
== Action - Not Talking ==
 +
[http://wiki.osgeo.org/index.php/%28Java_FOSS_GIS%29_DataObject_Framework GeoJOP DataObject Framework]
 +
[[Shared CRS and CRS Transformation Library]]
 +
 +
[[OSGeo Member Java Code Inventory]]
 +
 +
[[Category: Software Stack]]

Latest revision as of 05:32, 26 October 2009

Collaboration?

This page serves as a placeholder for information and discussion about possible opportunities for collaboration between FOSS GIS programs written in Java. This is an attempt to move from talk to action, since we (members of the FOSS GIS Java community) usually just nod and say "yeah, we should collaborate" and it ends there.

Java-based GIS Projects

What components?

  • GeoAPI (OGC/ISO specifications)
  • GeoTools
  • JTS

Contacts

People from each team who are taking part in this discussion:

OpenJUMP - Landon Blake (sunburned.surveyor@gmail.com)

uDig / GeoTools / GeoAPI - Cory Horner (chorner at refractions.net)

Problems

Licensing

  • LGPL vs GPL: everyone can use the LGPL code; GPL code will get less reuse.

Feature

  • Different Feature Models. This makes it difficult to share code. For example, you can't just plug-in a data source from the GeoTools library into OpenJUMP because it won't give you JUMP Feature objects. It gives you GeoTools Feature objects, which OpenJUMP can't use. :] We can work towards a common Feature implementation, but that is difficult in many cases because so much existing code has been written. In the case of OpenJUMP a lot of code is written and also published bia public interfaces to plug-in developers, which makes it much harder to refactor code. (If you want to change things you break a lot of plug-ins.) One solution may be to design, produce, and maintain code that converts between the different object features.

Ideas

  • draw a picture (who is using what right now?)
  • have an IRC meeting and figure out where we can collaborate
  • a BOF at FOSS4G2007 ?

Collaboration

Opportunities for Collaboration

  • Systems built on JTS. (Spatial Relationship Constraints, Geometry Constraints, Topology)
  • GIS Components that don't depend directly on the existing feature models. (Annotation/Map Labels Model, Non-Spatial Features)

Action - Not Talking

GeoJOP DataObject Framework Shared CRS and CRS Transformation Library

OSGeo Member Java Code Inventory