Archive for October, 2015
In our last webinar the issue of the background tile cache came up. One question was would it be possible to have the tile cache on a thumb drive so that it could easily be moved to another computer. Currently if you go to the tools menu in Depiction and select settings and then the advanced tab.
You will see a display that shows the default location of the tile cache. Currently you can not change this field and you would need to do this in order to place the tile cache in a different location such as a thumb drive. We are exploring the possibility of letting you update this setting to the location of your choice.
If you are unfamiliar with the tile cache let me explain its use. When you are viewing your story in Depiction the back ground map source can be a map or an aerial image. Depending on which you have chosen the program goes out to the internet and finds the desired image tiles for that location and zoom level you have chosen. When it finds them it stores them on your disk in the directory specified in the settings above. However, before Depiction goes to the internet to look for a particular tile or tiles it first looks in the cache directory to see if the tile is already there. If it is then Depiction takes the tile from there and doesn’t go to the internet. The benefit of this is speed and also if the internet is down it is still possible to display the background tiles. The downside of this is that if the map tile has been updated then Depiction will continue to display the old tile. You might particularly notice this if you happen to update an Open Street Map yourself and then don’t see the change you made. To get around this on the Basic Settings screen there is a check box to Overwrite existing cache with new. If you check this box then Depiction will ignore the cache and go directly to the internet. Normally you would want to keep this box unchecked.
So knowing how depiction works using the cached files it would be possible to create your own cached tiles from a map source other than those provided by Depiction. We have one customer in Germany that did just that. He has written a paper on how he achieved this. It is fairly advanced but with his permission I am sharing it with those of you that have the skill set and maybe inclined to attempt this. You can find the document here.
If you use a Gmail account for your live reports email you may have had a frustrating experience of the Live-Reports giving you an error message. Turns out Google has made a change and they won’t allow “unsecured” applications to log in unless you give your permission.
From Google’s website:
Allow less secure apps to access accounts
We have added a feature that allows you to block sign in attempts at the domain or Organizational Unit level from some apps or devices that do not use modern security standards.
See the Frequently Asked Questions section below for examples of apps that do not support the latest security standards.
Since these apps and devices are easier to break into, blocking them helps keep your users’ accounts safer.
Default less secure apps account access
Existing users with any programmatic login requests with plain passwords in the last 90 days will be able to use less secure apps by default. New Google Apps users and existing Google Apps users with no programmatic login requests with plain passwords in the last 90 days will not. Instead, by default, they will see a “Password incorrect” error when trying to sign in to less secure apps.
Enabling less secure apps to access accounts
- Sign in to the Google Admin console .
- Click Security > Basic settings.
Where is it?
- Under Less secure apps, select Go to settings for less secure apps.
- In the subwindow, check Allow users to manage their access to less secure apps .
Once you’ve set Allow users to manage their access to less secure apps to on, affected users within the selected group or Organizational Unit will be able to toggle access for less secure apps on or off themselves.
In order to give it permission log into your Gmail account and choose Sign-in and Security.
scroll to the bottom of the page. Turn on “Allow less secure Apps”
In the previous post I mentioned that the current build of Depiction was not Geo-coding starting locations.
We have fixed the problem and created a new build which you can find here. This build 12614 will geo-code starting locations.
Our initial geocoding of a new location at the Welcome screen is currently not working. This will mainly effect new users. Long time users that have geo-coded their location before won’t run into this because the geo-coding info will be in their cache. We hope to have this resolved soon.