Andrea,
I plan on focusing on the Map Service, Geometry Service, and Feature Service in that order as a first cut. My reasoning is as follows:
The Map Service is pretty much a no-brainer in my mind. It’s the thing everyone wants and everyone uses. The Geometry Service should be pretty straight forward and simple. It’s just basic geometry operations that GeoServer has support for through JTS. I see the Geometry Service as low hanging fruit that should be less complex to implement (I could be wrong and it could be a wolf in sheep’s clothing, time will tell). The Feature Service is on my list because I’m partial to services that support returning the raw vector data so that you can do analytical processing and the Feature Service supports a transactional model, which would be cool to show on top of GeoServer.
Obviously, even this paired down set is a lot of work, but I want to start the ball rolling. I’m also helping a few other people see this module and want to help out, you know the saying “Many hands make light work.”
To answer your second question. Yes, I’ve read the Polices and Procedures. My original email was my attempt to fulfill two of the step 1s: Getting Community Commit Access and Getting Approval for Creating a Community Module. I’ve also signed up for CodeHaus and applied to become a GeoServer developer.
Please let me know if I’ve missed anything or if you have any other questions.
Thanks and I look forward to contributing to GeoServer!
Brett
–
Brett Antonides
LMN Solutions, Inc
1750 Presidents Street, Suite 230
Reston, VA 20190
703-673-9526 ext 760
On Wed, Jun 15, 2011 at 2:02 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Wed, Jun 15, 2011 at 5:03 AM, Brett Antonides <bantonid@anonymised.com> wrote:
Hey All,
I’m interested in starting a new community module for GeoServer. Specifically, I want to write a plugin to provide support for the Esri REST API. The full documentation for the REST API as available at http://help.arcgis.com/en/arcgisserver/10.0/apis/rest/index.html. A version of this API has also been submitted to OGC for adoption. A full implementation of this spec on top of GeoServer would allow users of the Esri JavaScript, Flex, and Silverlight APIs to utilize GeoServer in place of ArcGIS Server and give another method for accessing geospatial data that can be used as an alternative to WMS and WFS.
My initial plan behind implementation of this REST API is to implement the ArcGIS Server 10.0 version and then the OGC version later. This way we can use the
Sounds really interesting!
The ArcGisServer API is quite extensive, as a curiosity, what subset do you plan to implement?
Also, did you have a look at the developer guide, in particular the project policies
and procedures?
http://docs.geoserver.org/stable/en/developer/
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
Request accepted. Welcome and happy committing