[ 
https://issues.apache.org/jira/browse/ASTERIXDB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215731#comment-15215731
 ] 

Wail Alkowaileet commented on ASTERIXDB-1371:
---------------------------------------------

I'm in favor of GeoJSON. It's everywhere and allows us to convert and ingest 
different spatial formats such as [Shape 
Files|https://en.wikipedia.org/wiki/Shapefile]

My current way on reading GeoJSON is by creating an external dataset then 
transform it to ADM shapes format. It would be great to just load it directly 
and Asterix understand it as geo-spatial type. 

However there're some challenges:
1- There's no support for multi-polygon in AsterixDB
2- There's no circle in GeoJSON
          Circle in CLEAN JSON is heterogeneous  {noformat}[ [10.1234, 1.11], 
0.102 ] {noformat}) ... it confuses Spark :-)
3- A validation mechanism has to be implemented (polygons in GeoJSON has to 
start and end at the same point)
4- How to extend Asterix shape types to include all other fields of GeoJSON.


> Support the standard GIS objects
> --------------------------------
>
>                 Key: ASTERIXDB-1371
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1371
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: Data Formats, Data Model
>            Reporter: Jianfeng Jia
>            Priority: Minor
>              Labels: gsoc2016
>
> We current support point, polygon, circle, and rectangle. The GIS world has 
> more data shapes as described in [Well-know 
> text|https://en.wikipedia.org/wiki/Well-known_text]. 
> [PostGIS|http://postgis.net/docs/manual-2.2/using_postgis_dbmanagement.html#RefObject]
>  is also a good referecne. It will be very nice we can support all standard 
> spatial object internally and can parse/format the spatial object in a 
> "well-known" way. e.g. well-know format or [geojson|http://geojson.org/] 
> format



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to