-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor: Add new data #186
Comments
Google Maps has a map style wizard at http://gmaps-samples-v3.googlecode.com/svn/trunk/styledmaps/wizard/index.html It allows you to select a variety of features based on category, then define the style for it. That user interface is obviously very clunky and I'm wondering how a better interface to select a set of data to style could look. Basically, we have a variety of "groups"/layers in our vector tiles, like I'm wondering whether we should build the editor to allow users the construct arbitrary "queries" against a vector tile, or, define a specific set of features, like "parks", "motorway bridges", "restaurants". /cc @samanpwbb @tristen |
Same as Young here that this doesn't feel essential to making a cool demo - we should just make a simple, robust interface. The level of functionality I've seen is already very clearly a mindblowing future that will be absolutely crazy. I think that styling interfaces should be around two axes:
We should nail these and find great ways of explaining more complicated z-index relationships like attachments. For getting / filtering data, we should create a very smart sampling algorithm and a table synced with a preview map view that makes the result of any kind of filter (ideally specified without code) clear. ^ ideas above are just braindump: as in pt 1 I think this is an area ripe for punting and focusing on making a simple map ui rock. |
regarding a demo, yeah, I can have something very light. |
This is done. |
Build an interface for adding new buckets from the data tile. This involves:
Maybe the current way we parse the data tile is not good enough to cover all use cases. This is also highly dependent on how we structure the actual data tiles; e.g. we could deliver data tiles that are not split up into "layers" and that only differentiate between features based on the tags, much like OSM's data is already structured.
The text was updated successfully, but these errors were encountered: