This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am wondering about the spatial data type capability of LightSpeed. We don’t have any significant quantity of spatial data today but it is likely we’ll need to start storing some soon. It appears that spatial data is only supported in MSSQL. 1) Is there a technical limitation that explains this? 2) Is spatial data support for MySQL planned for a future LightSpeed release? 3) If support similar to that enabled by MSSQL is not on the cards, how do other people work with spatial data in MySQL (or other non-MSSQL DBs) in a simple and efficient manner? 4) Are any of the GIS standards differences in MySQL vs MariaDB relevant to LightSpeed? Apologies for the rather open questions but since I’ve had little experience with spatial data, I am hoping someone here could give some insight and pointers. Thanks, Chris |
|
|
Hi Chris, The only technical limitation here is on the support provided through the .NET connector. Primarily this hasnt been implemented to date due to no requests being made for this support. Funnily enough Ive just been pinged by a few different people the other day about this and have been looking at adding this in and we will have some initial bits in tonights nightly build if you want to have a look at that. Note that due to limitations in the .NET connector for MySQL only POINT's are currently supported in the nightly bits. Im having a look at some options for open GIS libraries we can use to support the other GIS types properly.
|
|
|
Hi Jeremy, Without knowing much about GIS I can't say exactly what types we'd need yet but I expect some form of polygon range representation would be necessary (we'd most likely be looking at ways to process ranges on maps, intersections with country borders, etc.) Any work on this is still at least a month or two away so there's no huge rush but I'll keep an eye on this thread and the usual nightly build blog posts and bear this in mind when talking with colleagues about the options available to us. Thanks, Chris |
|