Re: [orientdb] Spatial Module Doc available in 2.2.x examples mixes lat/long

Hi Tore that was the legacy spatial indexing. EPSG:4326 Seems to be te standard widely used also in other GIS system. 2016-07-28 11:21 GMT+02:00 Tore Austrått : > Hello Enrico, > > in your latest blog post(7/25) you state " ... coordinates (latitude, > longitude) ". >

Re: [orientdb] Spatial Module Doc available in 2.2.x examples mixes lat/long

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 27. jul. 2016 21.01 skrev "Enrico Risa" : > Hi Tore > > the docs is not incorrect. > The Spatial Module uses the spatial

Re: [orientdb] Spatial Module Doc available in 2.2.x examples mixes lat/long

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

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

http://orientdb.com/docs/2.1/Spatial-Module.html 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":