Skip to content

Instantly share code, notes, and snippets.

@tmcw

tmcw/geojsonio_styling.md

Created August 12, 2013 15:35
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tmcw/6211964 to your computer and use it in GitHub Desktop.
Save tmcw/6211964 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
geojsonio_styling.md

I had previously implemented a basic styling interface, but dropped it for the time being, because of a few factors:

  1. No established standard for GeoJSON styling (GeoJSON CSS is a flawed spec without any implementations)
  2. The focus of GeoJSON.io is data, not styling
  3. A styling interface is likely its own thing.

Basically, given that GeoJSON is taken as the language of the site, I don't want to create expectations of compatibility that won't stand - if I invent some styling language, people will expect it to work, or at least be supportable, outside of the editor, and this promise will quickly be broken. I think conceptually the way to 'fix this' is to tie styling strongly to a publish interface that can make that guarantee, and write implementations in d3/openlayers/leaflet/etc for the language if/when it exists.

A bit of a big task :) The experience of working on CartoCSS has given me a bit of appreciation/fear of the area of styling languages in general and I think they should diverge from CSS a bit in order to learn more about the space.

@wboykinm
Copy link

Does Github have any plans for a styling implementation beyond the existing marker spec? Might be helpful to dovetail . . .

@tmcw
Copy link
Author

tmcw commented Nov 4, 2013

Does Github have any plans for a styling implementation beyond the existing marker spec?

I don't know: for now they use MapBox.js and thus simplestyle-spec.

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