Translation offered

[prunacomar]

Hi there. Great project! I have a CSV file with all the name you use for the elements translated into Spanish. If you think it might be helpful to add a translated version (or eventually add another property like "NAME_ES" or "NAME_SP" for example, just let me know and I send it over.

[prunacomar]

Hi there! As an addition to my previous comment: I see lots of minor adjustments to the data that can be done. As a couple of examples, for "Pamaps cultures", the correct name should be "Pampas cultures", and the geojson points seems to be ordered different at some years (so, for example, files world_900.geojson and world_1000.geojson start different, while there's no noticeable different in the region). If you agree, I can help to tidy all these and share with you, it you are willing to receive and merge this adjustments after revision. Please let me know.

[aourednik]

Hi, yes, many thanks for your proposal. I am willing to receive the pull requests

[prunacomar]

Awesome! 2 initial pull requests sent. #36 & #37

[prunacomar]

Before translating, I think it's important to organize the data. Same cultures receive different names in different files. As a simple example: Teotihuacán appears also as Teotihuacàn or Teotihuac�n.

Besides correcting the names, I think it'd very useful to add an "id" (perhaps simply an integer number) to each element, and repeat when the same element continues in another years. Then, you can say "all this Teotihuacán are the same folks". Or, if you want to add some extra complexity, some other relations, like "continues", so you can say for example "British American Colonies" "is continued by" "United States of America".

[prunacomar]

Hey there! Were you able to review this?

[aourednik]

Hi, I've merged to files you've sent me. Unfortunately, I don't have resources to correct typos myself, so it's cool when others like you help out.
For the 'continues' relation, I wouldn't write it directly to a field but have an relational table stored in csv or JSON format:

predecessor, successor
worldA."British American Colonies", worldB."United States of America"

where wordA and worldB are individual GeoJSON files. For unique ID's, hm, that would be nice but a whole different story. Basing relations on text is much simpler in this case, as it is easier to correct typos than to manage transhistoric UIDs.