Note that the open FileGDB API have several limitations which ArcObjects
does not have:
- FileGDB API only supports file geodatabases from release 10 or later
- Spatial queries is limited to the envelope-intersects operator
- It does not (yet) support rasters
(see the documentation bundled with the C++ library)
None of these limitations apply when ArcObjects is available on the
classpath, which is why I want to add support for both ArcObjects and the
open FileGDB API. ArcObjects will take precedence over the FileGDB API when
the requested geodatabase release is 10 or higher. Below, only geodatabases
releases which is supported by the installed ArcObjects framework will be
supported.
Cheers,
Kenneth
2011/8/8 Kenneth Gulbrandsoy <[email protected]>
> Comments below.
>
> 2011/8/8 Andrea Aime <[email protected]>
>
>> On Mon, Aug 8, 2011 at 5:39 PM, Kenneth Gulbrandsoy
>> <[email protected]> wrote:
>> > Hi Justin!
>> > Good tip! Comments below.
>> > 2011/8/8 Justin Deoliveira <[email protected]>
>> >>
>> >> Just a note that fgdb support was recently added to ogr as a format...
>> so
>> >> using the existing ogr datastore (and its java bindings for ogr) could
>> be an
>> >> easier route to go. However it requires ogr >= 1.9.0.
>> >
>> > According to the documentation, the FileGDB API is not part of the
>> default
>> > OGR build (which makes sense I guess since the API can not be
>> > redistributed). So, what do the user have to do to link the open FileGDB
>> API
>> > with the OGR plug-in? Re-compile with FileGDB API included?
>> > I guess this is a typical question since many formats are not compiled
>> with
>> > OGR by default.
>>
>> An issue I see here is that we have a number of raster formats depending
>> on imageio-ext, which in turn needs a old GDAL build (1.7.x) which
>> unfortunately
>> also comes with OGR.
>> So the main issue with the OGR store approach is that if you also need
>> some
>> GDAL based formats you actually have to go and rebuild the whole shebang
>> in order to have them work at the same time, and you're not free to chose
>> the OGR version anyways
>>
>
> Agree. I don't think this is any good idea before we depend on version >=
> 1.9.0.
>
> Another limitation that make this challenging is that the open FileGDB API
> only supports FileGDB of version 10. According to my knowledge, ESRI tend to
> not support older GDBs "out of the box" each time the upgrade a minor
> version. Additional compatibility layers are required, or upgrading is
> necessary (which all requires a commercial license).
>
> This is the reason why I what to support FileGDB through dynamic linking og
> both ArcObjects and the FileGDB API, much in the same manner as the ArcSDE
> and Oracle plug-ins do. This allows us to support the same FileGDB version
> as the installed ArcGIS runtime environment, and if available as a native
> library, any FileGDB version supported by the open FileGDB API.
>
>
>>
>> Cheers
>> Andrea
>>
>> --
>> -------------------------------------------------------
>> Ing. Andrea Aime
>> GeoSolutions S.A.S.
>> Tech lead
>>
>> Via Poggio alle Viti 1187
>> 55054 Massarosa (LU)
>> Italy
>>
>> phone: +39 0584 962313
>> fax: +39 0584 962313
>>
>> http://www.geo-solutions.it
>> http://geo-solutions.blogspot.com/
>> http://www.youtube.com/user/GeoSolutionsIT
>> http://www.linkedin.com/in/andreaaime
>> http://twitter.com/geowolf
>>
>> -------------------------------------------------------
>>
>
> Cheers,
> Kenneth
>
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
