Hi Frank, > I had a look at the wiki documentation ( > http://code.google.com/p/geopaparazzi/wiki/ExportData3) and have a view > questions: > > - Are you talking about the capability to import gpx and kml/kmz files into > udig?
no, it is really the ability to connect the phone to the pc, supply the folder to the wizard and import the data of a geopaparazzi survey project into uDig suitable data. Until now I found shapefiles the most suitable format. It is already possible to export kmz and gpx from geopaparazzi directly. The added value in my opinion is to be able to get "GIS" data for further analysis. > - Where is the reference to the images stored for a feature? Is it an > attribute in kml? Not sure what you mean here. In my proposal it would be the path inside an attribute of the point shapefile layer created. Ideally uDig would be able to understand when images or media files are referenced inside the attribute table and would have a way to open those :) Ideally... > - What do you think about an additional RFC for bookmark import/export > capabilites for the existing bundle > (https://github.com/uDig/udig-platform/tree/master/plugins/org.tcat.citd.sim.udig.bookmarks) > which stores/reads from csv I think that is a great idea. Didn't think about it. Will surely add that if the proposal gets through. > IMHO the bookmark feature could be easily added to udig > (org.tcat.citd.sim.udig.bookmarks). I'm not sure about the other features, > because of : > - existing kml/kmz support bundle (Import/export kml/kmz) - properly we > could improve this plugin with the features coming from BeeGIS in addition > to catalog support > - geopaparazzi exchange structure/format is a kind of special > structure/format and should not be in the core of udig, How about the > community repository and a P2 update site for geopaparazzi support? Well, in that case I would leave it in BeeGIS, since it would be the same. My feeling is that it would be good to have a direct link to a mobile open application for surveying data. And the data structure of geopaparazzi is not really a data structure. It is a very simple data model. > +1 for the the GPS/GPX plugins from BeeGIS > (eu.hydrologis.jgrass.gpsbabel & eu.hydrologis.jgrass.gpsnmea) this would be > a major Improvement for udig-core :) Hmmm, the gpsbabel hasn't been changed in a long while (actually I wanted to drop it, I am not sure if anyone is using it) and needs the gpsbabel executables for all platforms. So this would be a heavy addition in terms of space. The GPS support is not a small one. It comes with plugins that handle databases connections through hibernate (postgres and H2), has a database browsers and quite some views. Also the UI has too many icons in the toolbar to be ported as it is in uDig. So, all in all, those two would in case need a different RFC, backed by some more time. The geopaparazzi import is just a lightweight one, which is why I was daring to propose it. It is kind of like GvSIG Mobile stands to GvSIG. And I had people complaining about having to install BeeGIS just to import field data in uDig or transform them to shapefiles. Thanks for your comments, Andrea > > Cheers, > Frank > > > 2012/6/11 andrea antonello <andrea.antone...@gmail.com> >> >> Hi PSC members, >> can I draw your attention to this very small RFC? >> >> >> http://udig.refractions.net/confluence/display/UDIG/Move+support+for+geopaparazzi+projects+from+BeeGIS+to+uDig >> >> Thank you, >> Andrea >> _______________________________________________ >> User-friendly Desktop Internet GIS (uDig) >> http://udig.refractions.net >> http://lists.refractions.net/mailman/listinfo/udig-devel > > > > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
