-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Data Not Depicted #14
Comments
This issue is still outstanding (from my point of view anyway). While the data mentioned in the original description got onto the map after a private request to run a manual update, new drives that upload still do not appear automatically. My current test case is api.safecast.org/en-US/bgeigie_imports/12978 which was processed and approved three weeks ago but still isn't depicted on the GeoSense map. (Search for "Mt. Nasu" to zoom near points only on this drive.) |
We're going to be retiring GeoSense shortly and implementing a new platform On Thu, Jul 11, 2013 at 8:18 PM, Jam notifications@github.com wrote:
* Sent from my iPhoneSean Bonner Q: Why is this email three sentences or less? |
Sean - How shortly? I'm intending to drive street by street in Okuma next week and need a way to know which streets (if any) have been covered recently. Is there perhaps a beta site I can use? (Okuma is the town at the center of The Zone.)
On Jul 12, 2013, at 13:51, seanbonner notifications@github.com wrote:
|
We're not taking the map down, it's just clearly not working and not able On Thu, Jul 11, 2013 at 10:36 PM, Jam notifications@github.com wrote:
* Sent from my iPhoneSean Bonner Q: Why is this email three sentences or less? |
When new bGeigie log files are added to the database, they should get on the map in a timely, predictable fashion. Currently, data points approved weeks ago still aren't shown.
For instance, the town of Owase on the east coast of Mie Pref. has many measurements that are shown by the iOS app but not on GeoSense.
Something must be stuck.
The text was updated successfully, but these errors were encountered: