Another DB with spatial extensions:

http://postgis.refractions.net/
"PostGIS adds support for geographic objects to the PostgreSQL object-
relational database. In effect, PostGIS "spatially enables" the
PostgreSQL server, allowing it to be used as a backend spatial
database for geographic information systems (GIS), much like ESRI's
SDE or Oracle's Spatial extension. PostGIS follows the OpenGIS "Simple
Features Specification for SQL" and has been certified as compliant
with the "Types and Functions" profile. "

There are GIS extension for DB/2 and Oracle too.

On 22 Nov., 14:59, tanoshimi <[EMAIL PROTECTED]> wrote:
> If you're not tied to MySQL, then you might want to check out SQL
> Server 2008 as a backend database instead.
> The new geometry and geography datatypes in SQL Server (including the
> freely-available express edition) provide native methods to create,
> store, and analyse points, linestrings, and polygons, including the
> full range of OGC-compliant methods to test for e.g. whether a polygon
> contains another features, touches it, crosses it, or is a a certain
> distance away from it.
> You can then conduct all your spatial analysis in the database, and
> pass back the data to Google Maps to render as a front end.
>
> sc0rpi0 wrote:
> > Hi,
>
> > After reading Pamela's tutorial about using php&mysql in google maps
> > (http://code.google.com/support/bin/answer.py?
> > answer=65622&topic=11367&ctx=sibling) i was wondering how  would i do
> > to represent a polygon in a mysql database instead of a single marker?
>
> > Since each marker add a different key how would i connect different
> > points to being from the same polygon?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" 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-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to