As you've confirmed that you cannot get location data because the GPS signal indoor is too weak, I considered your problem (1) solved.  At least you know what you should check if you don't get location data reported  in the web-console or related reports.

Mocked GPS location is primarily there to support Android developers debugging apps using location-based services.   I would rather not talk about it because normal MDM use-cases don't intend to have device(s) reporting faked location information.  On the contrary, there is a feature control option to "Disallow reporting mocked location when GPS is not available" to cover this loophole. Having such information discussed in a public forum may render some hackers much easier to exploit and attack the MDM/EMM system, and weaken security and effectiveness of MobiControl used by Soti's and my customers.

Finally, as far as I know, both Soti and my company do not encourage customers to directly manipulate data in the SQL database, as minor mishandling or corruption of the critical data can cause catastrophic effects on the system.    I don't know if Soti will void your warranty if you do so and ask them for subsequent support, but my company can void/refuse our support service, or charge the customer a lot for diagnosing what was done and for recovering the system in the hope that  no device needs to be recalled for re-enrollment.     So, I would also not spend any time to discuss individual table in the database.

 For (1), in your so-called offline facility, are your devices and MobiControl server in a closed Wifi/Ethernet  network without Internet access?  Or are all communication channel (Wifi, Bluetooth, Mobile data, infrared, NFC, ..., etc.)  of your devices disabled?  For the former case, you can still have the GPS hardware on the device enabled, and the server can still get the location info collected via the communication channel in your closed network.  You can add a data-collection rule to collect such location information.  The only thing missing in you location service is the use Bing map to show your device location within the web-console interface because your Mobicontrol server cannot have the Bing map license token validated in your closed network.   However, the simple free alternative is to start another browser session, and go to google map page and input the coordinate collected and shown in the data collection tab in the web-console  

For (2), you need to provide more details.

For (3), there is no built-in feature to support what you need.   You should look for such camera app on Google Play store, though the spec might not exactly match what you want.   My customers previously also asked for something similar.   I might work on a paid app with some added features optimized for use together with MobiControl.

thanks for your quick response.

for (1), regarding the collection rule, how might someone go about doing that?

On Android/Android+ platform, add a new "data collection rule", include "location", and set the time interval between sample collection.  Assign the rule to your target device(s).  Location data stored in the device memory buffer will be synced back to the server and stored in the SQL database.  You can then see the location data in the  "Collected Data" tab in the web-console.

I did do that actually
But I can't seem to find where the data is
It doesn't show in the "Collected Data " tab in mobicontrol.

and in the agent's log it says that the device's GPS location is disabled even though it clearly is activated

What is  brand and model of your device?  On Android platform?  Did you forget to grant the device-agent's permission to use location information?  

the device is a Zebra Technologies ET5X Android tablet

and yes the agent has all his permissions granted

Is it possible that the GPS signal is too weak or there is problem with your GPS hardware.  Have you tried installing any GPS app (e.g. https://play.google.com/store/apps/details?id=com.chartcross.gpstest) on the device and confirm that you can get longitude/latitude information from the app using the GPS hardware.

If you can read location data with the above-mentioned app, but you get no data reported in the collected-data tab, then check how frequent you set the data collection  and the buffer size set in the data-collection rule. Is it possible that they are set to large that no samples get synced back to your server yet?  You can easily confirm if this is the issue by including battery level in your data collection rule, and set the sampling interval to be 2 or 5 minutes.  If you can get battery level information reported in the collected-data tab, but not location data, then the problem must be related to either the GPS signal strength or location permission.  If they are OK, then the remaining problem is probably related to the device agent, which you should reported to Soti support team and see if they can find any problem from the detailed device/server log files.

Because i was indoors gps location wasn't collected properly
network location didn't work also

I used a mock location tool to bypass it.

now the device, indeed, sends the (mock) location to the server

I checked the database table DeviceStatLocation , the data is there.

but how do i know which data is meant for which device?

Or more precisely, how do I make the correspondance between the DeviceId field in the database table and the friendly name of the device

thanks

thank you very much