Should data be updated manually in csv files or we have an API we can refer to and get latest data?

[VigneshVaidyanathan]

Hey,

I really like the structure of the data provided from the API and I could see few things are not updated with regards to the latest patches. Just wanted to know if we need to manually modify the CSV when changes are pushed as patches or did you use any API to actually get the data and format it in this way?

Im trying to build a quick Tech Tree app 🤷 so just wanted to know how data would be updated here so I can use it.

Also, really cool feature I like is the applies_to and the develops_in properties. Its good to have those extra pointers but again, was that derived from any source?

[aalises]

Yes, the data is static! I just extracted it from https://aoestats.io/

[VigneshVaidyanathan]

Do you think this can be automated? I tried to find the data from https://aoestats.io/ but it has only match data. I am curious to know if you had any backend service running to parse the raw data into the form you are using from the CSV or is it something we can get from somewhere.

Also, how difficult is it to update the details, I would like to help but I am not sure how to get anywhere.

I want to see this applies_to data mainly in a Tech tree format so it can be widely used for beginners to know what techs will affect which units/buildings.

[kprkr]

I too am wondering where you got the rest of the data from as on aoestats.io I can only find the player-match data and nothing relating to civs, units or tech.

Really interested in this API and would love to expand upon it, just struggling to find a starting point

[simonsan]

What about this https://github.com/SiegeEngineers/aoe2techtree/blob/master/data/data.json or https://github.com/SiegeEngineers/halfon/blob/master/data/units_buildings_techs.de.json

[aalises]

Hello legends! Just stumbled back into the repository after a while, so I'm not sure of the status of it. Anyways, there's much to improve on it so feel free to submit some PRs or fork it themselves!

Dynamically getting the data from a maintained source would indeed be a nice improvement. I would imagine something along the lines of (for whoever wants to give it a swing)

• Create a script that pulls the latest data from a maintained source (can be an API, some static JSON files, scraping a website...)
• Sanitize and do some data engineering on the source to adapt it to our data model
• Insert it into our database

We could then run that script on demand as a pre-requisite step when building the application and jazz 🎷, up-to-date data for the API!