Re: [gdal-dev] [GSOC] Integration of cpp GDAL utilities into GDAL core library

[Volker Wichmann]

Hi Nishith,

On 03/18/2015 08:27 PM, Nishith Maheshwari wrote:

Hi,
I am a masters student from IIIT Hyderabad and currently in my final
year of study and working in the Lab for Spatial Informatics here.

I was a part of GSOC 2014 and worked on the project *'Schematization
Plugin for QGIS'* last year [1][2].

I am interested in the project *'Integration of cpp GDAL utilities into
GDAL core library'* .

I have already looked at a few codes of gdal utilities available in the
'apps' folder of the sourcecode and had a few queries -

1. From my understanding of the project description, the aim is to
refactor the individual codes of gdal utilities by removing the main()
and making them available in the form of functions. These functions can
then be accessed by another function like GDALRunUtility() which can be
used to call them individually using specific parameters. Please let me
know if I'm thinking in the right direction.

2. If we are implementing individual functions for every utility we
might not require a separate layer of interaction in the form of
GDALRunUtility(). Any thoughts?


yes, the idea was to move the functionality of the gdal utilities to 
GDAL core in order to have it available directly when using the library 
and thus to facilitate their usage from "external" programs. The 
functionality should be usable with the GDALRunUtility() function. This 
would avoid e.g. a system call to a tool or code duplication which is 
currently needed in order to create a GDAL vrt for example.


It is not intended to remove the GDAL tools, but they would have to be 
reworked to just provide the parameter interface and then to call 
GDALRunUtility() themselves. The idea to have a GDALRunUtility() 
function is to have a unique entry point and common interface to all 
tool functionality.


Best regards,
Volker




[1] http://hub.qgis.org/wiki/quantum-gis/nishithm
[2] https://github.com/nishithm/schematization

Regards,
Nishith Maheshwari
Lab for Spatial Informatics
IIIT Hyderabad, India


___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev



___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

[gdal-dev] Releasing OGR feature from memory in Java

[Ochs, Elke ERDC-RDE-CRREL-NH]

Hello,

What is the proper way in Java (Windows) to release a feature from memory that 
has been loaded from an OGR layer?

I've been using  .delete() on the feature object, but just read in an  OGR API 
Tutorial that DestroyFeature should be used on Windows.  I can't seem to find 
reference to a DestroyFeature in Java.

Regards,
Elke

Elke Ochs, P.E.
US Army ERDC-CRREL
elke.o...@usace.army.mil

___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Re: [gdal-dev] Releasing OGR feature from memory in Java

[Even Rouault]

Elke,

Calling DestroyFeature() rather than delete is specific to C++ / Windows. For
Java, calling .delete() or doing nothing special is fine.

Quoting http://gdal.org/java/org/gdal/ogr/Feature.html#delete() :

"""
public void delete()

Delete (in memory) a feature.

Calling this method is not required as normal garbage collection will
reclaim associated resources when the object goes out of scope. Otherwise
calling delete() explicitely will help release resources sooner. Don't call any
method on a deleted object !
"""

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev