I don't know of any tools for visualizing the data, but the mysql function astext(geometry) and asgeom(wkt_text) will help you convert between the internal format (geom) and wkt, which is what you'll want to process on. If you want to visualize the data outside of google maps, I recommend looking into the ogr2ogr command-line utility which will allow you to export a mysql geometry table as a shapefile, which can easily be viewed using an open-source GIS tool such as Quantum GIS. I just navigated this mess in the last couple months, so if you'd like more direct help, feel free to email me off the list.
-Chris On Jan 31, 2010, at 9:05 AM, jbogdani wrote: > Thank you very much! > I can not use postgres actually (my provider doesn't offer this > service), and I'm trying with spatial MySQL, but I can not find on > line any free tool that I can use to view / edit geodata stored in > MySQL. > Can anybody help me? > Thank you > > On 30 Gen, 22:46, Chris Apolzon <[email protected]> wrote: >> If you will ever be doing advanced processing on the data (i.e. unions, >> points on polys, etc.), I highly recommend a spatial-enabled MySQL setup (or >> postgres (postgis) if you're willing to switch). You can then get the data >> out in WKT format, and its pretty trivial to convert this into processable >> lat/lng pairs if you're using a backend scripting language.On Fri, Jan 29, >> 2010 at 4:33 AM, jbogdani <[email protected]> wrote: >>> Hello all, >>> I'm developing an app witch uses google maps api v3 and a MySQL >>> database to store geo data (points, polygons, polylines and >>> georeferenced images). >>> I wanted to kow someone could help me in choosing the best format to >>> store the data in the database. >>> The main problem concerns polygons and polylines: actually I use, for >>> polygons and polylines, the following format: >>> lat1,long1;lat2,long2; etc... (commas to separate lat and lng and >>> semicolon to separate different points). I can parse this format >>> easily using javascript, but I was wondering if is there any >>> recommended format to store the data. >>> I don't want to find a solution that is good for me (already found it) >>> but a widely shared one (if there is one). >>> I see KML uses tabs to separate lat/lng and new lines to separate >>> points. Is there any standard for this? >>> Is there any standard way to "serialize" (to say it with a php term) >>> MVCArrays? >>> Thank you >> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google Maps JavaScript API v3" group. >>> To post to this group, send email to >>> [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<google-maps-js-api-v3%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
