I have worked out how to access the MySQL connections via GeoRaptor. So that part should be OK.
I have also worked out how to access the internal geometry format that MySQL uses. This is needed to be able to handle native SQL Select statements etc without insisting that all SQL include a conversion to WKT or WKB.
Much of what is in GeoRaptor is set to work with Oracle. To work with MySQL will take a fair bit of engineering.
I am not sure how many people would want MySQL access.
I'm of the view that to do this properly would take me a lot of time and I am not prepared to dedicate the resources to it with some sort of incentive.
Cracker Jack,
I am investigating whether this can be done. It may be that the SQL Developer developer API is not able to expose MySQL Geometry objects to GeoRaptor.
I am awaiting an email back from the SQL Developer team.
regards
Simon
Cracker Jack,
I have worked out how to access the MySQL connections via GeoRaptor. So that part should be OK.
I have also worked out how to access the internal geometry format that MySQL uses. This is needed to be able to handle native SQL Select statements etc without insisting that all SQL include a conversion to WKT or WKB.
Much of what is in GeoRaptor is set to work with Oracle. To work with MySQL will take a fair bit of engineering.
I am not sure how many people would want MySQL access.
I'm of the view that to do this properly would take me a lot of time and I am not prepared to dedicate the resources to it with some sort of incentive.
I am looking at trying to do this via http://www.pledgebank.com
regards
Simon