Skip to content
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

Closed
kkaefer opened this issue Nov 7, 2013 · 5 comments
Closed

Editor: Add new data #186

kkaefer opened this issue Nov 7, 2013 · 5 comments

Comments

@kkaefer
Copy link
Member

kkaefer commented Nov 7, 2013

Build an interface for adding new buckets from the data tile. This involves:

  • select tile layer
  • filter by value (string matching, number ranges!)
  • show taginfo stats
    • update them while the user pans around
  • show temporary highlight while selecting new data

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.

kkaefer added a commit that referenced this issue Nov 7, 2013
it's easier to support additional filter rules like number ranges (think admin level)
when we sort features into buckets based in custom filter rules

refs #151, #186
@kkaefer
Copy link
Member Author

kkaefer commented Nov 11, 2013

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 landuse, waterway, water, building, tunnel, road, bridge, admin, poi that contain features with various tags. Here's an example.

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

@yhahn
Copy link
Member

yhahn commented Nov 11, 2013

@kkaefer I would like to be convinced that committing to a larger styling paradigm is needed to get to a good demo.

@tmcw would love your thinking here.

@tmcw
Copy link
Contributor

tmcw commented Nov 11, 2013

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:

  • layers, in z-space
  • clickable features, in x / y

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.

@gundersen
Copy link

regarding a demo, yeah, I can have something very light.

@kkaefer
Copy link
Member Author

kkaefer commented Nov 21, 2013

This is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants