Skip to content

Instantly share code, notes, and snippets.

@max-mapper

max-mapper/open-civic-data.json

Forked from boazsender/open-civic-data.json
Created February 6, 2011 04:59
Show Gist options
  • Save max-mapper/813141 to your computer and use it in GitHub Desktop.
Save max-mapper/813141 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
open-civic-data.json
{
title: "title of data", // eg: 'the xyz murder', 'blizzard of 2011', 'chelmsburry bike path', 'MBTA green line', 'bus stop schedule event' etc
type: "type of data", // eg: event, physical feature
set: "what data set data is from if any", // if data is from national data set e.g. 2000 census
category: [category, category], // develop this taxonomy
description: "description of data", // text description of data
start: RFC3339DateTime, // optional start date
end: RFC3339DateTime, // optional end date
geometry : {}// optional geojson location feature (http://geojson.org/geojson-spec.html)
}
}
@boazsender
Copy link

This is a really good point. I suppose that hashing IDs to represent the data is a good way for preventing conflicts. I would think, however, that our validators would be have to evaluate the data in a more holistic way.

While not wildly complicated, this International Open Civic Data Service will have several complex points, the most of which I believe is this one that you raise; dealing with and merging duplicates. Consider for example, two very similar datum from two different data sets. What is the desired behavior?

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