migrate-to-ogc branch

[hernanmd]

Laurine told me there is a branch named migrate-to-ogc which can be used with the OGC-Pharo package.
For example:

GeoJSONReader fromString: GeoJSONExamples barsLilleGJ.

All is needed is to load 'OGC-Spheric' and 'OGC-Spheric-Tests' before.
And GeoJSON-Examples after loading GeoJSON.

So far I checked and it seems this branch add new classes prefixed with GJ like GJAddress.
Is the idea to migrate all source of this branch to OGC project?

[noha]

The GJAddress class was added quite some time ago. It is in the main branch. The migrate-to-ogc branch has yet not been merged because I don't find time and there are some adjustments to do like adjusting GJAddress and voyage/mongo extensions. So it needs to be polished in order to make it the default.
But yes I planned to do the move to OGC so we start a common ground for geo tools. I switched my KML reader already because now I can read KML and save as GeoJSON. My biggest problem so far is that OGCPoint is rather heavy with its 4 instVars and that makes GeoJSON probably bloated as well. But also no time to think if that can be done differently by choosing the model or making OGC more modular.
What do you think? I pushed Laurine to also do an inspector morph. So we can actually have good tools to read from the net and show directly on a map.