Open jamoross opened 11 years ago
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 to hopefully solve these issues.
On Thu, Jul 11, 2013 at 8:18 PM, Jam notifications@github.com wrote:
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/12978which 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.)
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/GeoSense/issues/14#issuecomment-20856265 .
Sean Bonner web http://seanbonner.com | twitter http://twitter.com/seanbonner | GPG key http://seanbonner.com/contact/sean_bonner_pub.asc (what?https://medium.com/surveillance-state/8294205b92ea )
Q: Why is this email three sentences or less? A: http://three.sentenc.es
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 going to be retiring GeoSense shortly and implementing a new platform to hopefully solve these issues.
On Thu, Jul 11, 2013 at 8:18 PM, Jam notifications@github.com wrote:
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/12978which 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.)
\ Reply to this email directly or view it on GitHubhttps://github.com/Safecast/GeoSense/issues/14#issuecomment-20856265 .
* Sent from my iPhone
Sean Bonner web http://seanbonner.com | twitter http://twitter.com/seanbonner | GPG key http://seanbonner.com/contact/sean_bonner_pub.asc (what?https://medium.com/surveillance-state/8294205b92ea )
Q: Why is this email three sentences or less? A: http://three.sentenc.es \ Reply to this email directly or view it on GitHub.
We're not taking the map down, it's just clearly not working and not able to be fixed so we have to find a new solution and are looking at options for that. Nothing has been done yet other than making the official decision that we're no longer going to push forward with GeoSense.
On Thu, Jul 11, 2013 at 10:36 PM, Jam notifications@github.com wrote:
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.)
- jam
On Jul 12, 2013, at 13:51, seanbonner notifications@github.com wrote:
We're going to be retiring GeoSense shortly and implementing a new platform to hopefully solve these issues.
On Thu, Jul 11, 2013 at 8:18 PM, Jam notifications@github.com wrote:
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/12978which 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.)
\ Reply to this email directly or view it on GitHub< https://github.com/Safecast/GeoSense/issues/14#issuecomment-20856265> .
* Sent from my iPhone
Sean Bonner web http://seanbonner.com | twitter http://twitter.com/seanbonner | GPG key http://seanbonner.com/contact/sean_bonner_pub.asc (what?https://medium.com/surveillance-state/8294205b92ea )
Q: Why is this email three sentences or less? A: http://three.sentenc.es \ Reply to this email directly or view it on GitHub.
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/GeoSense/issues/14#issuecomment-20859304 .
Sean Bonner web http://seanbonner.com | twitter http://twitter.com/seanbonner | GPG key http://seanbonner.com/contact/sean_bonner_pub.asc (what?https://medium.com/surveillance-state/8294205b92ea )
Q: Why is this email three sentences or less? A: http://three.sentenc.es
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.