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

Allow Shield Symbolizer to build an image filename from k:v pairs #352

Closed
artemp opened this issue Oct 11, 2011 · 8 comments
Closed

Allow Shield Symbolizer to build an image filename from k:v pairs #352

artemp opened this issue Oct 11, 2011 · 8 comments
Milestone

Comments

@artemp
Copy link
Member

artemp commented Oct 11, 2011

Thousands of distinct highway shields add visual cues to the North American highway lifestyle. ShieldSymbolizer expects all shields to start with a single base graphic. Shields from ubiquitous red over blue Interstate shields to collector-tempting Historic Route 66 shields are ignored by the default ShieldSymbolizer.

A plea for the ability to create a filename for the base graphic element from k:v pairs is discussed[1] as a method to allow OSM users of mapnik to easily add the vast variety of highway shields to their map of everything.

[1] http://weait.com/content/badges-badges

Pretty please?

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[migurski] ++?

There's a bigger, hairier and more general issue that this opens up, and that's the introduction of data-driven symbolizer parameters. E.g., the ability to put a string like "{$foo}" into a value and have it read a value from the data source. This would open up Mapnik for cloropleths, better shields, etc.

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[migurski] See URI templates for an example of this kind of thing in a different domain: http://bitworking.org/news/URI_Templates

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[springmeyer] Yes, exactly migurski. see also #359

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[springmeyer] pushing to 0.7.0 for consideration (since the 0.6.1 release is next week)

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[artem] Replying to [comment:1 migurski]:

++?

There's a bigger, hairier and more general issue that this opens up, and that's the introduction of data-driven symbolizer parameters. E.g., the ability to put a string like "{$foo}" into a value and have it read a value from the data source. This would open up Mapnik for cloropleths, better shields, etc.

I agree, this should be implemented in most generic way.

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[springmeyer] for those following this ticket, work has started on this in trunk, please provide any feedback:

http://mapnik.org/news/2009/dec/08/future_mapnik2/
http://trac.mapnik.org/wiki/Mapnik2

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[springmeyer] this is done in mapnik2 for a while now of course. closing.

@artemp artemp closed this as completed Oct 11, 2011
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

1 participant