GSoC - JOpenStreetMap

[Sergio Charpinel Jr]

Hi,

I've written a proposal for JOpenStreetMap component. I'd like to hear
your suggestions.

http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/sergio_ufes/8002

Thanks in advance.
Cheers.

[Elin Waring]

Hi Sergio,

Would you spell out some more details about how you plan to structure this package? 

Elin

[Sergio Charpinel Jr.]

Hi Elin,

Thanks for asking. I would follow JGitHub package structure, so basically it would have the following classes:

JOpenStreetMapObject, JOpenStreetMapHTTP, JOpenStreetMap, JOpenStreetMapWay, JOpenStreetMapNode, JOpenStreetMapRelation, JOpenStreetMapChangeset, JOpenStreetMapUser

I would also have to look http://wiki.openstreetmap.org/wiki/API_v0.6#GPS_Traces .

What do you think? 

Cheers.

--
Sergio Roberto Charpinel Jr.

[Elin Waring]

On Sunday, April 1, 2012 7:00:30 PM UTC-4, Sergio Charpinel Jr wrote:

On Sunday, April 1, 2012 7:00:30 PM UTC-4, Sergio Charpinel Jr wrote:

[Elin Waring]

Well that's basically telling me the structure of the OSM api, which is a good start.

You want to pay attention to how class naming is done in the platform. For example it is JGithub not JGitHub ... otherwise the names won't work with the autoloader. 

Elin

[Elin Waring]

One product you might want to think about as part of the documenting process is a plugin for Potlatch 2 as a demonstration of how to use the APIs.

Elin

[Sergio Charpinel Jr.]

Hi Ellin,

Very good idea. So we can have a very practical and useful documentation, and another way of validating the component as well. About the class naming, thanks for pointing that out. I didn't have time to correct these things in the application, but they are noted.

If you have more ideas, suggestions, please let me know.

Thanks again!

Cheers.