asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Carey <>
Subject Re: ASTERIXDB-1371: Support the standard GIS objects
Date Fri, 12 May 2017 20:15:29 GMT
Just to chime in briefly on the "format" thread - there are two formats 
to keep in mind - the input format (serialized format, e.g., how JSON 
relates to the spatial types) and the internal format (which in 
AsterixDB is a different, more efficient, binary format).  We can look 
at both in the project. Also important are the OPERATIONS that go with 
the format (i.e., the functions that we'll have in the query language 
for operating on, writing predicates about, etc., the spatial data).



On 5/11/17 2:28 PM, Ahmed Eldawy wrote:
> Hi Riyafa,
> I'm glad you started looking into the details. I agree with Mike that you
> need to study the current geo support first. It will be highly desirable
> for your work to be compatible with the current support so that we can
> seamlessly unify the underlying code without disrupting the high-level API.
> As for the format, it would be nice to support both WKT and GeoJSON as they
> are both widely used. However, I think we should start with GeoJSON since
> it is becoming more popular with modern devices, e.g., GPS, smart phones,
> and IoT sensors. Later, we can support WKT as well. It will be a matter of
> writing a different parse function.
> Esri library [] supports both WKT
> and GeoJSON. You can study it and see if we can use it in our project.
> Thanks
> Ahmed
> On Wed, May 10, 2017 at 7:11 AM, Mike Carey <> wrote:
>> I will leave it to the official GSC mentor (who's also a leading expert on
>> big spatial data) to direct - I was just suggesting that step 0 should be
>> to become familiar with what's already there currently, to have a working
>> knowledge of that as background.
>> :-)
>> Looking forward to seeing this project unfold!
>> Cheers,
>> Mike
>> On 5/9/17 10:14 PM, Riyafa Abdul Hameed wrote:
>>> Hi,
>>> As I understand by playing with current support of GIS objects( point,
>>> polygon, circle, and rectangle) is similar to the Well known text
>>> format--correct me if I am mistaken. Hence initially we could support
>>> other
>>> GIS objects in WKT and support GeoJSON if time permits.
>>> Thank you.
>>> Yours sincerely,
>>> Riyafa
>>> On 8 May 2017 at 23:31, Mike Carey <> wrote:
>>> I would also suggest playing with the current geo support in AsterixDB
>>>> (curretn types and indexing and functions in queries) to get warmed up.
>>>> Welcome aboard...!!
>>>> Cheers,
>>>> Mike
>>>> On 5/8/17 8:51 AM, Riyafa Abdul Hameed wrote:
>>>> Hi,
>>>>> I have been selected to contribute to the issue ASTERIXDB-1371
>>>>> <> for GSoC
>>>>> time.
>>>>> This being the community bonding period I am trying to familiarize
>>>>> myself
>>>>> with the code base of AsterixDB and to get a grasp of the task.
>>>>> I am under the impression that the package *
>>>>> <> *has the classes for handling data
>>>>> models
>>>>> for AsterixDB and have been looking into them to figure out the
>>>>> implementation details. Please correct me if I am mistaken.
>>>>> I have also been reading on the specification for well known text[1]
>>>>> GeoJSON[2] and have been trying to figure out if implementing one of
>>>>> them
>>>>> would suffice (if so which one) or if both needs to be implemented. If
>>>>> both
>>>>> needs to be implemented we should decide which needs to be implemented
>>>>> first. I was thinking of going for GeoJSON as it seems to have a wider
>>>>> usage.
>>>>> Any suggestions on how I should proceed with the project would be highly
>>>>> valued.
>>>>> [1]
>>>>> [2]
>>>>> Thank you.
>>>>> Yours sincerely,
>>>>> Riyafa

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message