Spatial Module Doc available in 2.2.x examples mixes lat/long

42 views
Skip to first unread message

Tore

unread,
Jul 27, 2016, 2:33:29 PM7/27/16
to OrientDB

The examples are mixing latitude and longitude.
Please check this: (it appears the restaurant is located in Ethiopia) This goes for all the examples. Please correct.
Thanks.

INSERT INTO  Restaurant SET name = 'Dar Poeta', location = {"@class": "OPoint","coordinates" : [12.4684635,41.8914114]}

Enrico Risa

unread,
Jul 27, 2016, 3:01:33 PM7/27/16
to orient-...@googlegroups.com
Hi Tore

the docs is not incorrect.
The Spatial Module uses the spatial reference system EPSG 4326

http://spatialreference.org/ref/epsg/wgs-84/

and the x & y are projected in longitude (-180 +180) and latitude( -90 +90).

See here

http://geojson.org/geojson-spec.html#positions

and here

http://edndoc.esri.com/arcsde/9.1/general_topics/what_coord_sys.htm

Thanks
Enrico

--

---
You received this message because you are subscribed to the Google Groups "OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tore Austrått

unread,
Jul 27, 2016, 3:14:49 PM7/27/16
to orient-...@googlegroups.com

Thanks Enrico
I used google coord and that worked. I wrongly assumed that was the system in question.
I will review the docs you provided.

Tore


You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/0suULkswLxU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.

Tore Austrått

unread,
Jul 28, 2016, 5:21:50 AM7/28/16
to orient-...@googlegroups.com
Hello Enrico,

in your latest blog post(7/25) you state " ... coordinates (latitude, longitude) ".
It seems that this is the common understanding. All positions from Google
comes in this format(see attached png) and hence this was the way I understood it. 
In my view this will cause confusion as you can't expect every developer to
be a full fledged navigator. So why not say this explicitly - ODB does it the opposite way?

How come OrientDB selected EPSG:4326 ?

T.


--

---
You received this message because you are subscribed to a topic in the Google Groups "OrientDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/orient-database/0suULkswLxU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to orient-databa...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Tore Austrått
phone +47 90657231
restaurante.png

Enrico Risa

unread,
Jul 28, 2016, 5:58:43 AM7/28/16
to orient-...@googlegroups.com
Hi Tore

that was the legacy spatial indexing.  

EPSG:4326
Seems to be te standard widely used also in other GIS system.
Reply all
Reply to author
Forward
0 new messages