Geo first stable version?

I would also love to see this go stable. I am the developer for the geobrowser module and would love to add support for geo

I can't give a firm timeline. It largely depends on who can fund the work. The dirty secret of open source is things happen more quickly when money is involved.

Also, geo needs to figure out it it will support mysql and at what level.

Sorry that's not a better answer.

-Mark

I'm committed to getting this done, but I have been off on another project for a while.. I should be returning to doing geospatial work in Drupal full time later this week.

Yay - you rock bdragon

Hello,

And now what is the status of this project? I see the last commit on November 8, 2007 more stuff are doing?

I would like create a module to add hierarchical location (simple point) via a google map. Your module would be nice to stock the long/lat point, fast proximity search are possible with spatially database...

Your module provide an API to add/remove/search point?

A lot of modules can stock longitude/latitude like:
Geonames CCK, CCK Latitude Longitude, Location, GeoLocation. But Why all this module?

Thanks

subscribing... this module sounds fantastic.

Right, so I have just committed the last of the destructive changes I've been planning (removing geo_* field types, and just using 'geo' ). From here out it's about getting stable and adding critical features.

This means improving views support and getting at least one widget that doesn't require you to know WKT. Once it's all at the point where a "normal" person can download and install the module, and then start adding fields like a normal person would; we're ready to roll a 1.0.

Thanks!

Thanks loads for the update. I'm genuinely very excited about the Geo module. IMHO, geo-spatial functionality will play an increasingly important role in many websites, especially now that many mobile phones are starting to incorporate GPS functionality and lots of people are getting used to the power and convenience of Google maps etc.

I'm not much of a coder but (if I have the time) I'll definitely help out with beta-testing and that sort of thing once you feel the module is ready to be tested by non-ninja-coder folks.

I'd like to help out with Geo. My job involves using spatial in MS SQL Server 2008, so as soon as Drupal natively supports SQL Server as a backend database, I'd be really interested in helping to add the required extensions to support that (http://groups.drupal.org/node/15557 - although I accept that this is not required to get a v1.0 release)... However, I've also got good knowledge of the OGC SFS specifications and general spatial functions.

I appreciate that the main module developers are busy (after all - we all have our day-jobs to do as well!), so what is the best way for others to help get a stable release finished? Is there a list of remaining tasks to do before v1.0 can be rolled? I couldn't see a ToDo.txt in the CVS release. Is there a roadmap? If not, is it simply better to hold out until the first release and then offer to do testing?

Sorry for the questions - I'm just trying to maximise any effort spent on this, since I too agree that this will be a really powerful API for the future of Drupal.

Is there a lack on interest for this module? Seems like months pass between any signs of life!

+1 sub

Now a year passed by after Allie announced #7. Any progress in thinking about releasing an alpha?

OK, since 6.x-1.0-alpha1 has recently been released, I think this ticket can be closed.