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

Pin Logos #25

Open
vonbearshark opened this issue Jan 23, 2017 · 13 comments
Open

Pin Logos #25

vonbearshark opened this issue Jan 23, 2017 · 13 comments
Assignees

Comments

@vonbearshark
Copy link
Contributor

We need to distinguish the pins based on the data coming in. We need to have at least separate icons/colors for the city 311 and police data, for now. But we also need icons for the campus police data, fire data, health and safety restaurant inspection data, etc.

@brlodi
Copy link
Collaborator

brlodi commented Jan 24, 2017

In the short term, thoughts on pin color? I'd color code as follows:

  • Police – blue (if we want to differentiate campus vs. city could be blue/yellow and blue/white)
  • 311 – yellow
  • Fire – red
  • Health – green

We should be able to do standard pins in straight CSS, unless people feel strongly about generating raster image assets for it?

@vonbearshark
Copy link
Contributor Author

Those work for me. Just need to make sure it matches up to whatever we use for #37. I think image icons would be a neat feature to have, but we can add them in later if someone gets the energy.

For posterity, here's how we'll implement the icons in the future: https://leafletjs.com/examples/custom-icons/.

@brlodi
Copy link
Collaborator

brlodi commented Jan 24, 2017

So preferring L.icon to L.divIcon?

@vonbearshark
Copy link
Contributor Author

It might be simpler, but we can cross that bridge when we revisit it, too. Docs on divIcon for future: https://leafletjs.com/reference.html#divicon

@brlodi
Copy link
Collaborator

brlodi commented Jan 25, 2017

With regard to color-blindness support, my thinking was to have iconography associated with the pins in addition to color, at least as a long-term. Something like this, but not thrown together in 2 minutes (the 311 numerals don't work at small scale).
artboard 1 2x
artboard 2 2x

@vonbearshark
Copy link
Contributor Author

Those would be dope for now

@brlodi
Copy link
Collaborator

brlodi commented Jan 25, 2017

@vonbearshark could you assign me to this issue? I'm working on at least some basic flat-ui icons.
Speaking of the icons, should I create a map-pins directory in the root or nest it within an images directory?
Also, the sources file for these icons is in Illustrator. It's not a huge file but it's definitely a binary file. Should I commit it?

@vonbearshark
Copy link
Contributor Author

vonbearshark commented Jan 25, 2017

For sure! Thanks, @brlodi! Let's nest it in an assets dir. I think we should keep them out of the git path for now. Maybe we can put the long-term assets' source files in version control, but I think we can get away without it now.

Edit: looks like I can't assign you--could you join the PittCSC org as a member?

@brlodi
Copy link
Collaborator

brlodi commented Jan 25, 2017

@vonbearshark You'd need to invite me. There's no option for non-members to request membership

@vonbearshark
Copy link
Contributor Author

Of course there's not. That would be simple. Just sent you an inv

@vonbearshark
Copy link
Contributor Author

We should delete assets while we're at it

@brlodi
Copy link
Collaborator

brlodi commented Jan 26, 2017

Should be auto-removed once the files in map-pins are gone, no?

@vonbearshark
Copy link
Contributor Author

Yeah, that's what I mean

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

No branches or pull requests

3 participants