Details
Minor
Description
1. Add altitude coordinate.
That involves adding 3-rd coordinate to the points in geometry and
implementing the set of functions to operate with it.
2. Convertors.
There is a lack of functions in MariaDB to export and import data
from/to various spatial data formats. So we need to implement functions
as
ST_GeomFromEWKB - ST_AsEWKB
ST_GeomFromGML - ST_AsGML
ST_GeomFromGeoJSON - ST_AsGeoJSON
ST_GeomFromKML - ST_AsKML
3. Getting data from SHP format.
It's good to have domesticated shp2sql convertor as
a separate tool and same functionality available inside the server
as the MariaDB SQL command.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Hi
I am Chick Delveri and interested in this task.
Im aware the project requires us to add support for a 3rd coordinate in storage but will this require creating a new Geometry class say GEOMETRY_M or maintain the current class by adding it directly to sql/spatial.** and writing functions to retrieve it like Z(PointFromText('POINT('x y z'))) ?
My worry is we could have a column that contains 2D and 3D data mixed.
Can someone clarify this for me?
No, the mixed 2D and 3D points shouldn't be stored in one column.
Hi Alexey
In that case i think a possible implementation could be creating new
Geometry types like Point(x,y,z) from the parent GEOMETRY class to
distinguish it from the current subclass Point(x,Y) and implementing
function like GeomFromEWKT() to operate with it.
or do we redefine a new Geometry hierachy ?
2015-03-17 10:50 GMT+01:00 Alexey Botchkov (JIRA) <
Hi !!
I'm a student who will join in GSOC 2014, and I'm interested in this idea. I want to be corrected my draft rather than directly submitting my proposal, so who can I contact with?