For the Jackson parser implementation for GeoJSON [1]... Polygon should start and end at the same point (as in [2]) and does not allow polygon with holes.
[1] https://asterix-gerrit.ics.uci.edu/#/c/2076/ [2] https://tools.ietf.org/html/rfc7946#page-9 On Thu, Nov 30, 2017 at 11:07 AM, Wail Alkowaileet <[email protected]> wrote: > Thanks Sattam... :-) > > @Ahmed, I would be grateful for your input.... > > On Thu, Nov 30, 2017 at 7:43 AM, Mike Carey <[email protected]> wrote: > >> @Ahmed? Since you're the new defacto CGO (Chief Geo Officer) in >> AsterixDB - do you happen to know? (I know you are on the GeoJSON side - >> but - not sure if you looked at the old polygon support/code at first?) >> >> >> On 11/30/17 12:57 AM, Sattam Alsubaiee wrote: >> >>> Both convex and concave polygons are supported. As far as I remember, >>> complex polygons such as self interesting polygons and polygons with >>> holes >>> are not supported. Not sure if they are supported now. >>> >>> Sattam >>> >>> On Nov 30, 2017 3:50 AM, "Wail Alkowaileet" <[email protected]> wrote: >>> >>> Hi Dev, >>>> >>>> What's the polygon definition we have in AsterixDB? >>>> I'm a little bit confused. The only constraint we have is that the >>>> polygon >>>> must have at least 3 points. I remember Sattam was mentioning something >>>> like only "convex" (not sure) polygons are allowed. But it seems there >>>> are >>>> no enforcement to any constraint. >>>> >>>> -- >>>> >>>> *Regards,* >>>> Wail Alkowaileet >>>> >>>> >> > > > -- > > *Regards,* > Wail Alkowaileet > -- *Regards,* Wail Alkowaileet
