Open makella opened 8 years ago
This would be great!
I would be willing to help write a tool that converts our list in Google Docs to JSON or markdown files that can be compiled into something a little more user friendly than the master spreadsheet. The spreadsheet is designed to be read by software, so it would be easy to use to generate individual JSON / Markdown files.
Another option would be just to use the existing JSON document that iD is using: http://insidemaps.nps.gov/dist/presets.js and write a tool to display that information in a more user friendly environment.
Or the *other option is to maintain the JSON files that are currently maintained as part of iD in the Places Tracing Guide repository and then load them into iD from there. ;-)
Seriously though, I've seen some chatter on the iD project issue tracker about moving those presets out of the iD repository altogether, so this may not be a bad solution.
That way we could start maintaining all of this information in one place, and the tracing guide would always be up-to-date.
Per our discussion earlier this week, it might make more sense to create these separately from the guide - possibly a CartoDB API guide similar in structure to https://api.open.fec.gov/developers and another for Mapbox (specifically how to pull data in and what values to expect for styling).
We will be developing this into its own Technical User Documentation, including all features (while Guide is limited to the basic and most common "starter kit" of features) along with both CartoDB API + Mapbox integrations.
As discussed in today's scrum it would be great to come up with an addition to the guide where CartoDB and Mapbox attributes are outlined in relation to raw OSM tags so people can easily extract the data they want from CartoDB and/or use the vector tile data source to style maps.