-
Notifications
You must be signed in to change notification settings - Fork 19
More data #4
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
Comments
We could support country TLDs pretty easily since they mostly map to ISO codes. We would just have to note the exceptions. |
Another thing I ran into with the community index conversion.. It would be useful to have an "area" property. We use this in downstream projects to sort the features, and it would be nice to have it in the data so consumers don't need to calculate it. I know that these are very rough polygons and so the area is not very accurate, but for relative size it works ok. In community index, the area is calculated like this: const calcArea = require('@mapbox/geojson-area');
...
// calculate area and set a property for it
let props = feature.properties || {};
let area = calcArea.geometry(feature.geometry) / 1e6; // m² to km²
props.area = Number(area.toFixed(2)); (the conversion and rounding is just to make the numbers more human readable - it's not really important) |
@bhousel Area sounds useful. Might be best to just include the official areas from Wikidata or whatnot since some of the island features have enormously distorted shapes. |
A random assortment:
One thing to keep in mind is that we’re potentially reinventing the wheel with some of this data. Traffic speed units are provided by CLDR, though CLDR happens to be less accurate than country-coder in this case. (CLDR is a gold mine of internationalization data, so definitely take a look at it for inspiration.) |
Let's brainstorm here on what other data we want to include for each country. Would be great to remove some of these datasets from iD.
The text was updated successfully, but these errors were encountered: