Actually I have already made a basic google map for the website[1] meant to replace the old developers map. Check out the blog post at http://people.planetpostgresql.org/xzilla/index.php?/archives/76-Maptastic.html I'd be interested in talking more about getting more content into the map and getting it in officially; One concern I had was finding a way to include information that won't bog down end users with too much data. (I've noticed large numbers of points tend to do that) Robert Treat On Tue, 2005-10-25 at 12:11, Claire McLister wrote: > Thanks. > > I looked at the Mapserver maps, and at first glance it seems Google > Maps API provides better map images and more interactive features > (zooming, panning, JS popups, satellite/map views, etc.) > > So, what would be the advantage of Mapserver apart from it being based > on Open Source? > > We use Postgresql server to store the data. Currently, we do not use > PostGIS as we do not do much geographical queries. Over time we could > move in that direction to offer better geographical query support. > > Posting this (or a more detailed map) on the Postgresql web site sounds > like a great idea. We could even allow people to add markers for their > locations, and even enter more information about themselves to help > postgresql users connect with each other. One potential opportunity is > for users to quickly find consultants in their own area. > > How would we initiate this activity? > > Best wishes > > Claire > > On Oct 24, 2005, at 2:28 PM, Brent Wood wrote: > > > How about using Postgres/PostGIS & UMN mapserver for a fully Open > > Source > > software & Postgres based map? > > > > For a map like the one at > > http://www.qgis.org/index.php?option=com_wrapper&Itemid=53 > > > > perhaps on the Postgres web site? > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
