Blog Week 4

This week, as explained in my last post, we made some final decisions on the technologies we'll be using for the part of the project we'll be in charge of: web/backend.
All these decisions were made mainly according to the requirements of a class I'm not part of, but the rest of the team is. For this reason, and for us not to overstep in each other's way, I will be focused on the Data Analysis part of it all, or as specifically detailed by our client:

developing analytics  features so that the platform administrators can see how the platform is used, such as (for example):
  • how many assets we have, within an area?
  • when were these contributed?
  • what channel and which individual is the biggest contributor?  
  • how many people did this tour? how long did it take?

For me to start actually working on these features, though, a few components of our architecture will have to be ready first. Perhaps we can start agreeing on how the data is going to be structured in our DB or some other details, so that the processing of this data can begin to be implemented already and later on simply just adapted to our real data. We still need to discuss some things as a team.

And... that's all for now, folks. I think.

What is Data Analysis? Learn about Meaning and Examples
image obtained from https://www.ngdata.com/wp-content/uploads/2016/01/what-is-data-analysis.jpg

Comentarios

Publicar un comentario

Entradas más populares de este blog

Team Blog Week 3

Imagen
This week, following our meeting on Monday, our communication with the Alberta team has been more constant. They've let us in some of the details we missed from our video meeting and informed us of some specific requirements their clients have. We've also been discussing with them about which technologies we've used in the past and feel most comfortable with. This has led to some agreement on the most part, deciding that (mostly) we'll be taking on the web development side of the project and them on the mobile client. We were also presented with a general idea of what this app is planned to look like: With all this in mind, we've decided as a team to go with the following system features: visualization of points of Interest in map routes creation with multiple points of interest, in order routes can be approved or dismissed by other users information about MiBici stations for routes information about points of interested can be edited by users automat...
Leer más

Week 1 Planning

Imagen
This week we plan to continue researching about similar projects to what “Yeg AR” aims for, to get a better understanding of what existing products are out there already. Using the document that explains what the project is about, we identified some technologies that are proposed to be used in the project. We will research the technologies as well as how to implement them with AR. It would be great if we find sometime for us to actually chat with the students from Alberta, to agree on the requirements, specifications, tools to be used and how we’ll distribute the work. From what we’ve read in the project description, details aren’t so clear. So we’ll write down concrete questions we would like to ask them. All our team posts will be published with the teampost tag, immediately available through https://martellsmartcities.blogspot.com/search/label/teampost We created a repository for the project but depending on how we organize with the alberta team we might create a...
Leer más

Plan Week 6

Imagen
This week we plan to continue developing our back-end side of the project. Mostly though, we'll be centered on figuring out how to use the Steps API previously developed by the Alberta team so that we add there additional info and media for important landmarks. The thing is, right now the Steps project is structured around "sidewalks", routes. We're not yet sure how we'll add landmarks, perhaps as routes that start and end at the same coordinates? The documentation for Steps is not very clear for where we can add this information. Hopefully we'll figure out a way, or a workaround, soon. image obtained from https://searchengineland.com/founder-openstreetmap-good-better-google-maps-already-192089
Leer más