search

mezerotm / cmv

CMV is a citySDK based map visualizatoin tool
5 stars 5 forks source link

Accurate Dating #8

Open mezerotm opened 7 years ago

mezerotm commented 7 years ago

Be able to check what year range we receive from the API; When you ask the API for a year for example 2018, the API may not have 2018 so it usually gives you the next best thing so maybe 2017, we need to be able to see what range it has given us to more accurately represent what date we're looking at as opposed to what we think we're looking at.

NJTuley commented 7 years ago

Clarification/Observation: The citysdk request object that we send to the citysdk servers has a variable called api. The current version has us hard-coding in the value 'acs5' for this variable. The acs is a constant value that as far as I am aware, we are not going to be changing. The 5 is (I believe) the year range (so acs5 would get a 5-year range, acs10 would get a 10-year range, etc.). I think that this could be useful for resolving this issue, but I am not 100% sure about this, but I am sure that there are more details in the citysdk documentation, so please fact check me. Also, we might want to look at the 'year' variable in the citysdk request object in order to help with this issue.

mezerotm commented 7 years ago

Gitter "Your somewhat on track with talking about the ACS5 I have more information on it in the documentation.js but basically ACS5 is what API you want to request from the citySDK since the citySDK was created in order to centralize all these bureau's API's" Further Information: Like I said in the Gitter. What the citySDK does, is it takes information from all the bureau's API's and it centralizes them; Over on the citySDK's own documentation they have a drop down that lists all the data sets (API's) they currently support. I can't find them listing these anywhere else; What you need to do in order to allow the user to set a specific date is that ahead of time you need to know what years the API you are requesting from accepts. This requires some slight research; Right now the only solution I can imagine for knowing the dates ahead of time, is by reading through the individual API's and getting an intimate understanding of what they take as years. This may not be the only solution but it's all I can think of having the information I do have.

mezerotm commented 7 years ago

Looking at citySDK's documentation I found a great list of available data sets and they're corresponding years

hardnett commented 7 years ago

This may be a bit more involved for the alpha release because of the way the census collects and names datasets. I am of the mind to push this to the beta release. Thoughts?

ravenusmc commented 7 years ago

I agree, move it to Beta

hardnett commented 7 years ago

Complete data sets for the Census: https://api.census.gov/data.html

mezerotm commented 7 years ago

Remote Branch

Created a remote branch where I impliment an idea of where we can take dateing. In it I take an approved list of API's and I run cmv.census.availableDatasets to get dates avilaible by API. Then actively request dropdown info to fill citySDK requests.

Issues

state change

I'v programmed it in a way that maps that have been submitted remember their state of information. What this means is that when you focus on an active map which is already populated, if selected the year '2014' as opposed to the default '2010' then when you click the map it will change to '2014'. This is an issue because when you have not clicked submit when you change any info, year for example. Once you change it and then you move the map it will change it's state to where it previously was not to what you set it. Not unless you click submit and don't touch the map.