[fdo-internals] ArcSDE provider + raster data

[Johan Van de Wauw]

Just a quick note.
The reason why I would consider using WMS or GDAL rather than updating the
fdo driver:
* If you have access to the arcgis server it may be reasonably easy to
configure a wms (if it is a recent version of arcgis server and the license
[1] permits you to do so). Configuring this has the advantage that it can
also be used in other applications apart from mapguide and no programming
is required.
Apart from that, this solution seems more futureproof. I'm not too sure
about the future of arcsde. WMS will probably be supported far longer.
* If you expand the arcSDE driver in GDAL all applications that use gdal
could use the new driver. Actually more people could be testing and/or
maintaining your changes.


Johan
[1]
http://www.esri.com/software/arcgis/arcgisserver/features/functionality-table


On Fri, Feb 15, 2013 at 2:43 PM, Alfredo Muela-Romero
<alfredo.muela at pds.nl>wrote:

> Hi Johan,
>
> First of all, thanks for your reply.
>
> Read-only access would be the first step. Actually, as far as we have
> discussed it with the stakeholder, it might be the only functionality they
> need.
>
> Regarding the WMS FDO Provider, our customer's data stores are not OGC
> WMS-based. Therefore, I discarded the option when I read the description of
> the FDO provider.
>
> Related to the ArcSDE GDAL driver you point (thanks for the link, by the
> way), our first approach was to keep using the FDO architecture. If
> extending the current ArcSDE FDO Provider meant a lot of effort, we would
> need to ponder using the C API SDK (or in this case the driver suggested).
>
> Currently, we have not clarified yet all the details on the raster
> capabilities that will be required (for example, "is reading raster
> catalogs a requirement?"). While we are gathering all that information we
> are also trying to evaluate the amount of effort required for the different
> options.
>
> Would you suggest going for the GDAL driver rather than completing the
> ArcSDE FDO Provider? (in case read-only access is the requirement and any
> non supported features, such as the use of catalogs or NODATA masks, are
> needed).
>
>
> Cheers,
> Alfredo.
>
>
> On Fri, Feb 15, 2013 at 2:08 PM, Johan Van de Wauw <
> johan.vandewauw at gmail.com> wrote:
>
>> Do you need read-only access or read/write?
>>
>> In case you need read only access, I wonder why you would not use WMS or
>> arcsde gdal driver:  http://www.gdal.org/frmt_sde.html ?
>>
>> Johan
>>
>>
>> On Fri, Feb 15, 2013 at 10:05 AM, Alfredo Muela-Romero <
>> alfredo.muela at pds.nl> wrote:
>>
>>> Hi everyone,
>>>
>>> My name is Alfredo Muela. I am a software engineer working for a company
>>> named PDS <http://www.pds.nl/>.
>>>
>>> We are in need of raster functionality with ArcSDE. One of the ways that
>>> we are considering (and the most likely) is to extend the existing FDO
>>> provider and releasing our implementation back to the community.
>>>
>>> In order to do that, we are assessing the effort that it would take. I
>>> have been looking at the existing open source code in the GDAL provider
>>> (read-only raster data) trying to extrapolate the work needed in the ArcSDE
>>> provider.
>>>
>>> If you have any suggestions or even a roadmap already defined to
>>> achieved that goal, it would appreciate them.
>>>
>>>
>>> Regards,
>>> Alfredo.
>>>
>>> _______________________________________________
>>> fdo-internals mailing list
>>> fdo-internals at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>>>
>>>
>>
>> _______________________________________________
>> fdo-internals mailing list
>> fdo-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>>
>>
>
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/fdo-internals/attachments/20130218/46fbbbf7/attachment.html>