NJTuley
commented
7 years ago Here is a screenshot of the polygons that I was talking about. (Data is for Gwinnett county, but I have tested and this error does happen in other location inpus as well)
Here is the empty values that I was talking about, and you can also see that the color for each polygon (which is the objects being shown) are all set to the same value since the value is undefined:
And these are printed in the debug window for each object that is returned in the citysdk response. They have no place (which would usually be the location we gave them through input, but it does not show a zip, place, or state, which would usually be present with a successful request and ensuing response from citysdk).
This is all I have noticed so far about the error, I have not been able to determine what is causing it, but it is not localized to certain locations or inputs, as I have been able to have it show up in a variety of different locations when I give it location input.
I have not been able to cement the conditions when this occurs, but sometimes when I load up the map and get it to display polygons for citysdk data, the citysdk response (handled by the geocallback function) has all of the geographic data, but whereas in a working response, each point also has a value corresponding to the variable given, these do not, which results in every polygon being the same color, whichever color is associated with a value of 0 (null).
I have been trying to recreate the error for a bit now, and have not been able to (I think it might have something to do with internet connections, but it needs to be looked into I believe), but I will upload screenshots of the error messages and the incorrect polygons when I am able to recreate it.