Le mercredi 06 février 2013 22:47:33, Chris Barker - NOAA Federal a écrit :
On Wed, Feb 6, 2013 at 11:29 AM, Even Rouault
even.roua...@mines-paris.org wrote:
Chris, GDAL_SUBPROCESS matches indeed the current state of the
implementation. However, as I answered to Livneh, it could be
Selon Livneh Yehiyam ye...@rafael.co.il:
Perhaps GDAL_PROXY?
This is a possibility, although there's already a GDALProxyDataset class in
GDAL, subclassed by GDALProxyPoolDataset, that is used internally by some
drivers (VRT, RPFTOC) that want to proxy the access to underlying datasets
without
On 6 February 2013 16:33, Even Rouault even.roua...@mines-paris.org wrote:
All in all, i'm ok with GDAL_PROXY if nobody else has a better suggestion.
GDAL_API_RPC
GDAL_API_PROXY
GDAL_API_SERVER
to clearly indicate the purpose: interacting with API calls.
Otherwise, it may be easily confused
Mateusz
+1
I vote for GDAL_API_PROXY.
Best regards,
Dmitriy
06.02.2013 20:40, Mateusz Loskot пишет:
On 6 February 2013 16:33, Even Rouault even.roua...@mines-paris.org wrote:
All in all, i'm ok with GDAL_PROXY if nobody else has a better suggestion.
GDAL_API_RPC
GDAL_API_PROXY
GDAL_API_RPC
GDAL_API_PROXY
GDAL_API_SERVER
IIUC, the proposed functionality is not really a Remote Procedure
Call, or a Proxy, or a SErver.
i.e. could the driver be run on a remote server with this mechanism?
Rather, it is a way to run a driver in a sub-process. So maybe:
DGAL_SUBPROCESS
Le mercredi 06 février 2013 18:57:46, Chris Barker - NOAA Federal a écrit :
GDAL_API_RPC
GDAL_API_PROXY
GDAL_API_SERVER
IIUC, the proposed functionality is not really a Remote Procedure
Call, or a Proxy, or a SErver.
i.e. could the driver be run on a remote server with this
Hi,
Just to inform you that I've just commited in trunk a new feature.
See http://trac.osgeo.org/gdal/ticket/4979 :
When dealing with some file formats, particularly the drivers relying on third-
party (potentially closed-source) libraries, it is difficult to ensure that
those third-party
Even,
This sounds great. I'm guessing RPC in this context stands for Remote
Procedure Call. It seems like this could potentially lead to some confusion
with existing GDAL functionality (e.g., gdal_rpc.cpp) and options (e.g.
RPC_DEM) where RPC stands for Rational Polynomial Coefficients used
Le mercredi 06 février 2013 01:59:46, David Shean a écrit :
This sounds great. I'm guessing RPC in this context stands for Remote
Procedure Call. It seems like this could potentially lead to some
confusion with existing GDAL functionality (e.g., gdal_rpc.cpp) and
options (e.g. RPC_DEM) where
