Osana

@langsmith Do we need the swap or do we need to provide the right encoding?

@kbauhaus I modified `BasicGeocoding` to load the example you provided and got the following response: ``` public class BasicGeocoding { public static void main(String[] args) { MapboxGeocoding geocoding = MapboxGeocoding.builder()...

I did a bit of testing on how much memory Point takes in 2.x.x based code vs 3.0 (with AutoValue). Number of points | size in 2.x.x mapbox-java | size...

Also tried comparing loading of sample json with FeatureCollection: { "type": "FeatureCollection", "features": [ { "type": "Feature", "geometry": { "type": "Point", "coordinates": [ 102, 0.5 ] }, "properties": { "prop0":...

@zugaldia @tobrun I think the next steps could be as @tobrun points out - remove AutoValue from geoJson as there is no real need - If we want to go...

@zugaldia good idea to look at v2.x code and I agree that having two packages next to each other is a good way to compare.

Android JSON Parsers Comparison: https://medium.com/@IlyaEremin/android-json-parsers-comparison-2017-8b5221721e31 Looks like `Jackson` would perform best for our needs.

@zugaldia I will check this out

Thank you for reporting this. I confirm that there is a problem in supporting `https://api.mapbox.com/geocoding/v5/mapbox.places/-77.0366,38.8971.json?access_token=pk...&language=en_us,ru,es` We correctly do the request for multiple languages but the response object is not parsed...

Here are a couple of examples of possible responses based on the language requests. It is easier to show the difference in case of CarmenContext (text). The same applies to...