Hi Wail,
I don't know the spatial space, but I'm a little concerned that these
links point to vendor sites. Are these documents vendors-specific? I
think that we should aim to use formats the provide wide
interoperability (if that's possible). Do you have some insight into
this space and which formats are most widely supported?
Cheers,
Till
On 7 Aug 2015, at 9:48, Wail Alkowaileet wrote:
Hey Chris,
It's actually mapped (or the other way around) to JTS shapes (
http://www.vividsolutions.com/jts/bin/JTS%20Technical%20Specs.pdf).
But as suggested by Mike, ArcGIS seems to support Circle (
https://developers.arcgis.com/javascript/jsapi/circle-amd.html)
On Fri, Aug 7, 2015 at 6:23 AM, Chris Hillery <[email protected]>
wrote:
(I'm pulling this bit of conversation out from the JSON discussion so
it
doesn't get overlooked - it has nothing to do with JSON, but with ADM
primitive types.)
I've noticed that several geospatial serialization formats (at least
"well-known text" and GeoJSON) omit "circle" from their list of basic
geometric forms, even when they have numerous more complex types such
as
multi-curves. This led me to here:
http://forums.mysql.com/read.php?23,148162,152625#msg-152625
which offers a reasonably compelling argument for why "circle" is not
a
reasonable shape to discuss in geospatial contexts (loosely, because
there's no consistent way to map that to a spherical coordinate
system).
Does this mean that perhaps ADM shouldn't *have* a "circle" primitive
type?
I assume that the ADM spatial types are intended for geospatial work,
and
if the consensus of the smart people is that "circle" doesn't fit in
that
world, perhaps we shouldn't include it either?
Ceej
aka Chris Hillery
--
*Regards,*
Wail Alkowaileet
