[postgis-devel] Public Raster C API

[Nathaniel Clay]

Bborie,

I'll ticket the problem and as I said earlier, I will fix it myself. You
comfortable with getting the change into 2.2?

Thanks,

Nathaniel Hunter Clay

On Wed, May 27, 2015 at 8:10 PM, Bborie Park <dustymugs at gmail.com> wrote:

> Hm... Sounds like the Makefile needs changing to install librtcore.so.
>
> On Wed, May 27, 2015 at 4:22 PM, Nathaniel Clay <clay.nathaniel at gmail.com>
> wrote:
>
>> Bborie,
>>
>> I think it all gets rolled up into rtpostgis.so. As far as I can tell
>> there is no librtcore.so.
>>
>> Thanks,
>>
>> Nathaniel Hunter Clay
>>
>> On Wed, May 27, 2015 at 7:13 PM, Bborie Park <dustymugs at gmail.com> wrote:
>>
>>> Nah. The library was meant to be consumed by whomever wants to consume
>>> it. If the header is not copied, that'd be an oversight and a ticket should
>>> be filed... Having said that I need to see where librtcore.so gets
>>> installed...
>>>
>>> On Wed, May 27, 2015 at 2:41 PM, Nathaniel Clay <
>>> clay.nathaniel at gmail.com> wrote:
>>>
>>>> Bborie,
>>>>
>>>> The librtcore header is not copied, to /usr/include so I am assuming
>>>> that the library functions included in the library were meant to be
>>>> private. This is for a external project. Is this an over-site? Or am I
>>>> missing something fundamental.
>>>>
>>>> Thanks as Always,
>>>>
>>>> Nathaniel Hunter Clay
>>>>
>>>> On Wed, May 27, 2015 at 5:35 PM, Bborie Park <dustymugs at gmail.com>
>>>> wrote:
>>>>
>>>>> Actually, yes. raster2pgsql directly consumes librtcore...
>>>>>
>>>>> On Wed, May 27, 2015 at 2:33 PM, Bborie Park <dustymugs at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Do you mean directly accessing librtcore? I believe you can go
>>>>>> directly at that library if so inclined.
>>>>>>
>>>>>> -bborie
>>>>>>
>>>>>> On Wed, May 27, 2015 at 2:31 PM, Nathaiel Clay <
>>>>>> clay.nathaniel at gmail.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Could we expose some of the raster C functions to read and write to
>>>>>>> raster’s, and low level pixel to geo-point and geo-point to pixel and etc.
>>>>>>> Just want your input, I am more than willing to do the work myself.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Nathaniel Hunter Clay
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> postgis-devel mailing list
>>>>>>> postgis-devel at lists.osgeo.org
>>>>>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> postgis-devel mailing list
>>>>> postgis-devel at lists.osgeo.org
>>>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> postgis-devel mailing list
>>>> postgis-devel at lists.osgeo.org
>>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>>>
>>>
>>>
>>> _______________________________________________
>>> postgis-devel mailing list
>>> postgis-devel at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>>
>>
>>
>> _______________________________________________
>> postgis-devel mailing list
>> postgis-devel at lists.osgeo.org
>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>>
>
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20150527/b1b22fe5/attachment.html>