client-side data

[incanus]

Master ticket for building out client-side data (e.g. non-vector tiles). This is the last big feature we need for viable initial iOS deployment in apps.

Use cases:

• Plot user location with e.g. Core Location
• Show arbitrary point/polyline features
  • GeoJSON (about the only format we'll worry about parsing internally)
  • Externally-parsed formats like KML, Shapefile, etc.
  • Runtime-added features (e.g. here's an array of points; render them)

Progressive feature set:

1. Spatial indexing and/or pre-tiling of feature data.
2. Rendering of features with static styling (also hits user location use case).
3. Arbitrary styling of polylines.
4. Arbitrary imagery for points (sprite atlas etc.)
5. Animated native views for points (a là MKAnnotationView on iOS).

Let's treat clustering (#320) as a separate milestone.

Related/obsoletes:

• marker support #60
• Markers #468
• [NOT READY] GeoJSON support #170

[abhay-agarwal]

Hey incanus, Mapbox-gl-cocoa looks and acts great. Any idea of release dates for these features? Specifically the run-time added features with arbitrary sprites (that's about all we need). Also, will these features follow the format of the RM objects (i.e. MGLAnnotation instead of RMAnnotation)?

[incanus]

Not sure on a timeline yet @abhay-agarwal, but stay tuned. For API, this will be more like MapKit (MKAnnotation protocol) than the SDK (RMAnnotation class).

[aleksandr-vin]

Suddenly discovered "source type not implemented" for geojson. Really need it. Subscribed.

[mourner]

The big GeoJSON rewrite is done — see mapbox/mapbox-gl-js#464 comments. We now need to port geojson-vt to C++11 and from there it'll be easy to add robust and fast GeoJSON support.

[incanus]

We now need to port geojson-vt to C++11

I'm going to start taking a crack at this today.

[incanus]

Making some headway on this. Believe it or not I'm using Swift to do it, since basically all of the geojson-vt code needs to be made strongly typed, and Swift's now my fastest typed language, plus playgrounds let me make small progress without explicitly having to compile or to suffer C++'s overhead in Xcode.

We'll need to build out formal structures for all of the parts used (features, points, feature types, tiles, stats, GeoJSONVT options, etc. as well as the strongly typed array/dictionary containers required by C++ and countering the looseness of JS's Int/Double numbers) and banging through it in a lightweight language is letting me move fast as I understand the code. Most of the way through tile.js & index.js thus far.