SensorMap Forum

Sense Web

Tue, 06 Oct 2009 07:27:57 Z

Hi There,
Im a recent user of WebSense.
I would like to ask you about how can any one add sensors or use the Sensemap in general.
I can see that not all regions are covered with sensors.
so, if iwant to use this application, how can i do that . Or its not allowed for any one?

Thanks and Best Regards.

Authentication Error

Wed, 03 Jun 2009 23:03:21 Z

I am trying to register a temperature sensor through the tutorial and giving a hard-coded temperature, but I keep getting an authentication error. And I tried to do it manually on the sensormap by right-clicking and registering a sensor and it gives me an error of inactive publisher or not enough quota. Is there something wrong with the publisher I created?

Lifetime in SenseWeb

Sun, 10 May 2009 20:26:01 Z

Hello everybody!
I would like to know what lifetime mechanisms exist in the registry of SenseWeb.
For example, how do you decide when to "discard" a sensor?
Do you remove a sensor if it does not send any data for a certain amount of time? Is this done automatically?
Is there a paper, or a technical article that describes that kind of issues?

Best Regards,
Kostis

This forum has migrated successfully in January 2009

Fri, 30 Jan 2009 15:52:49 Z

As part of the migration, posting of new threads and messages is no longer allowed on the Forums 2.x platform.

For reporting bugs on the new forums platform, visit: http://social.msdn.microsoft.com/Forums/en-US/reportabug/threads/

For making suggestions on the new forums platform, visit: http://social.msdn.microsoft.com/Forums/en-US/suggest/threads/

Thank you for your patience during the migration.

Alicia.

This forum is moving the week of 1/27/2009

Fri, 23 Jan 2009 05:38:59 Z

Microsoft has created a new forums platform (MSDN | TechNet | Expression | Microsoft) with increased performance, stability, and an improved user experience. During the week of 1/27/2009 this forum will move from the Forums 2.x Platform (http://forums.microsoft.com/) to the Forums 3.x Platform. To make sure this is a smooth transition, we want everyone using this forum to have a chance to try out the new forums in advance, and give feedback. We’ve created a Sandbox forum, where you can create threads and try out functionality, and a suggestions forum where you can give us your feedback. Please take some time to go to the new forums today and let us know what you think.

On the day the forum moves to the new platform, a post will be made letting you know the process has been started, and the forum will be locked to new posts. Once the process is complete, a final post to the forum will be made letting you know the forum has moved.

1. All posts in the forum will be preserved

2. Any points you’ve received for replies will move with you (on a per forum basis)

3. Any bookmarks to this forum or threads within this forum will redirect to their new location

4. Your “My Threads” will be preserved on the new platform

The only thing you’ll need to do after migration is set Windows Live Alerts for any threads you were tracking.

If you have feedback, let us know in the suggestions forum or contact the forum product planners directly at Andrew.Brenner at Microsoft.com or Jeremy.Kelley at Microsoft.com

Thanks,

Alicia

SenseWeb V3.1.20080807 released

Mon, 11 Aug 2008 21:51:10 Z

Major Changes:

- Changed to use type IDs instead of type URIs in polygon queries.

Currently, we support more than 100 types. The total length of type
URIs (used in sensor queries as one parameter) may well exceeds 4000B,
which is the upper bound of parameter sizes in SQL store procedures.
We switch to use IDs instead of URIs to make the system more scalable
to the number of sensor types contained in one query.

- Separated metadata queries and data queries in SensorMap to improve
sensor fetching performance

The previous versions of SensorMap queries both metadata and
real-time/archive data when a user opens SensorMap or changes his/her
view port. Since data are coming from distributed sensor gateways, the
response time of such queries is quite long, taking several to tens of
seconds depending on the number of sensors in view. In addition to
that, data is not refreshed unless the user reloads the page or
changes his/her view port.

To resolve these issues, the current release changed the behavior of
SensorMap as follows: (i) for queries on multiple sensor types,
SensorMap queries only sensor metadata by default. The data of a
specific sensor is queried and displayed once the user moves the mouse
over the sensor to view its detail, and (ii) for queries for a single
sensor type, we query both sensor metadata and data by default.

- Indexing pages for SwissEx projects and RFP projects

Minor Changes:

- Changed sensor names for the SwissEx stations such that real sensor
names instead of database column names are used

- Changed display names in time series charts (e.g., use "Relative
humidity (wan7)" instead of "wan7@1" to denote the relative humidity
sensor on station wan7)

- Randomly display 500 sensors instead of everything when the number of
sensors in view exceeds 500

- Changed the description panel of a sensor to show the "chart" link
even when data is not available currently or for the selected time
period

- Fixed typo: SensorMap Sing-up -> SensorMap Sign-up

Thanks,

Liqian

Issues with SensorMap v3

Wed, 09 Jul 2008 20:53:28 Z

We are still having some problems with the new version and are not sure how to move forward, since it's not clear what is supposed to work.

Firefox v3 does not seem to support most of the new features. At least we cannot seem to get "Manage Visualizations" to work - clicking the link at the top of the page doesn't do anything. In fact none of the links at the top ("Manage Views | Manage Visualizations | etc.") seem to have any effect.

Using Safari on the Mac, none of the sensor nodes show up, even for the Seattle view. I guess Safari is not supported at all?

When clicking on the multivalued sensor nodes (such as the nodes in the SwissEx:Wannengrat view), I can click on the 'Chart' link next to each sensor type. This seems to be broken - I see a blue text appear to the left of the display ("wan7@3" for example) and when I hover over it I see a box with an "X" that appears to be intended to close the chart view - but no chart frame or chart itself is shown. I think something is broken with the window-drawing code.

We'd like to make a real push to flesh out our SensorMap integration this summer and take advantage of the new features, but are a little concerned about these issues since they prevent us from making forward progress.

Thanks!
Matt

SensorMap V3.1.20080714 released

Mon, 21 Jul 2008 18:28:53 Z

Major changes:

- Access control of sensors

Security mechanisms have been deployed to protect data from unauthorized

access. Sensors can be specified as private, protected or public. Each

sensor has an owner and an associated group. Private sensors are

accessible only by their owners. Protected sensors are accessible by

their owners or other users in the associated group.

- Direct overlay of graphs

The previous version always converts graphs to tiles before overlaying

them onto the map. We now support direct overlay of graphs over 2D maps,

which reduces response time from tens of seconds to several seconds. By

default, graphs are directly overlaid on top of 2D maps. For users who

wish to overlay a graph over 3D maps, they can change visualization

output type to "tiles" to convert graphs to tiles, and then switch to 3D

mode as before.

- More interpolation algorithms

The previous version uses Simple Kriging as the interpolation algorithm

during contour map generation. We now support two new algorithms:

Ordinary Kriging (more accurate but slower) and Inverse Distance

Weighting (faster but less accurate). Ordinary Kriging is used by

default. Users can use "Management Visualization -> Settings ->

Interpolation Method" to change to another interpolation method.

Minor changes:

- Fix the following bug: graph tile layer disappears when switching to

Virtual Earth 3D

Liqian

senseweb@microsoft.com

Integrating Web Service with SensorMap

Wed, 09 Jul 2008 13:26:56 Z

Hi,

We are trying to implement our own Data Hub. We have deployed a web service at http://www.ecssensors.org/SensorMap/Service.asmx. We have also registered a sensor at Southampton, Hampshire UK. This sensor has the webServiceUrl pointing to the above service. The sensor appears on the sensor map (in gray color) but it doesn't display the data (its a temperature sensor). We have tested our web service and it is configured correctly and giving the proper output to a test application. It seems to me as if there is something we have missed. Any Idea what might have gone wrong?

Kind Regards,

Muddasser Alam

P.S. I have already registered my account for sensorMap under the email ID muddasseralam@yahoo.com. We are also running another temperature sensor using the default data hub (Microsoft) and this sensor is working fine.

senseWeb v3 accounts

Tue, 29 Apr 2008 16:11:56 Z

Hi all,
I've been trying to create an account for senseWebv3 and got no success. It does let me create an acount, however it doesn't let me log in. I get an error like this in the login page:

Error!

An unexpected error has occurred. Your request has not been processed.

Does anybody have the same problem and/or knows how to solve it. Nobody seems to answer my mails to senseweb@microsoft.com

Thanks

guillem

Low Cost Temprature Sensor

Tue, 20 May 2008 02:02:07 Z

I am looking for a low cost temprature sensor for a public school project. Does anyone have any recommendations ?

Thanks
Pradeep

SenseWeb V3.1.20080514 deployed

Sat, 17 May 2008 01:09:17 Z

SenseWeb V3.1.20080514 has been deployed this morning. Here are the list of changes:

1. Improved query performance

2. Fixed user login errors

3. Enabled and fixed the “Go To Location” functionality

4. Added a link to rainfall sensors in Taiwan

NTHU is the first to implement their own sensor gateways based on the SenseWeb tutorial. Tens of rainfall sensors are registered in Taiwan, where you can see the archival data via the charting functionality. Check it out here:

http://atom.research.microsoft.com/sensewebv3/sensormap/Default.aspx?la=23.553916518321635&lo=121.31378173828128&zl=8&ms=r

5. Fixed a typo: “e privacy” -> “privacy”

Thanks,

Liqian

Missing SWLib.dll workaround

Mon, 29 Oct 2007 23:04:30 Z

You no longer need to use SWlib.dll if you are unable to find it in your installation of MSRSense.

Use RegisterSensor2 instead of RegsiterSensor for web reference at

http://atom.research.microsoft.com/sensordatahub/service.asmx

The arguments can now be generated directly, rather than requiring SWlib.dll. Rest of the steps are same as mentioned in http://research.microsoft.com/nec/msrsense/PublishingTutorial.pdf

Where are my sensors?

Tue, 19 Jun 2007 15:53:31 Z

Hi all,

I've reached my quota on the number of sensors that I can put up for the time being. While I can ask for more, I realized that I don't know where all of my sensors are; especially, after IPSN's tutorial. Is there a tool or page that I should use to find information about the sensors that I have published/registered?

Thanks!

-Matt

Weather sensors on SensorMap

Mon, 30 Jul 2007 07:41:55 Z

We are from the Intelligent Systems Center (IntelliSys) at the
Nanyang Technological University (NTU) in Singapore. We are
working on a project entitled "SensorMap for the National
Weather Study Project", supported by Microsoft Research's
SensorMap RFP 2007. In this project, we are developing a sensor
grid connecting mini weather stations deployed in schools
throughout Singapore.

Our project website is at :
http://nwsp.ntu.edu.sg/sensormap

We have created several weather stations as "generic" sensors
on the SensorMap website. You may check out these sensors by
going to the location "Singapore" on SensorMap. We welcome your
comments and suggestions !

SensorMap IPSN CleanUp

Mon, 18 Jun 2007 12:55:52 Z

Would it be possible for the Cambridge, MA area of SensorMap to be cleaned up? Even though our particular group hasn't put out sensors yet in the Cambridge area, the leftover test sensors from IPSN cloud the landscape and potentially overshadow any genuine data. It seems that post sensors are prefixed in some way with "IPSN" so it won't be difficult to identify most of the sensors that should be removed.

Thanks!

Difficulties with SendBinaryData and SendScalarData

Wed, 13 Jun 2007 19:35:46 Z

We are trying to do a project for our advanced sensor networks class
where we publish data results of video images and/or traffic congestion.
We are using python and the ZSI (Zolera Soap Infrastructure). We are using
the Data Hub Service at http://atom.research.microsoft.com/sensordatahub/service.asmx.

We can now successfully register the video camera sensor. But when we try to publish
using the SendBinaryData Api, it comes back with OK and the number of bytes published
but it doesn't update the image on sensormap. It works when we give specify a url other than the DataHub url but couldn't get it to work when no url is specified. I have a script to dump the sensor info using once it gets created and another to delete it (both use your Api fns).

So then I decided to make the experiment simpler and successfully registered a scalar sensor to see if I could update the readings. I did SendScalarData changing the temperature, but it we finally noticed it takes a long time to see the change reflected on SensorMap (note: the timestamps from the script are changing). I was thinking sensor data should published at the "sampling" rate to the datahub archive and the "reporting" rate is the number of seconds after which SensorMap fetches a new reading from this archive. I set this to both of these to 10 seconds so I would see the change right away but it still took a very long time. Lastly, I added to the script to perform a GetLatestScalarSensorData Api and it does indeed return
the data I just published with the SendScalarData.

I don't know if this problem relates to not setting the sensorinfoXML correctly somehow for the sensor or a lack of understanding on my part of something else I needed to do to for the initial setup. The sensorinfoXML for this scalar sensor is attached.

I did reload on my brower every time I made changes. Any help that you can give would be greatly appreciated. Other questions are:

+ What are the current SensorTypes and DataTypes supported? For SensorTypes I know there is "Video Camera", "Thermometer", "Traffic", "Parking" and "Generic". And for DataTypes there are "jpg","scalar". Are there any others?

+ Is binary data archived as well or is it only scalar data?

+ I noticed if I remove a sensor and readd it with the same name it keeps the old value that was last published and doesn't view it as a new sensor. Is this how it should work?

+ I noticed that if the sensor is removed and I do GetSensorDescriptionByName it says None (which it correct) but then if I do GetLatestScalarSensorData on that removed sensor that it reports the scalar data. Is this how it should work?

Thanks again if you can shed any light on these questions. Most importantly I'd like to understand if I can publish binary data without an url.

I and my colleague Seungweon also discovered that the same problem I was having in python is also occuring in C# under win xp with SendBinaryData. When there is no web camera driver and a single jpeg image file is trying to be published it doesn't do it (even after waiting for .5-1hr like we did for the scalar data). If I install a web camera server on linux and run
it, and specify the url then it publishes under "open in new window" like it does for Seungweon under win xp.

Judy

The sensorXML info is the following:
<?xml version="1.0" encoding="utf-8"?><Sensor xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.
org/2001/XMLSchema"><publisherName>jfisch@cs.pdx.edu</publisherName><sensorName>PSU TEMP2</sensorName><longitude>-122.6812791
824341</longitude><latitude>45.509174009003232</latitude><altitude>0</altitude><unit>Celsius</unit><sensorType>http://researc
h.microsoft.com/nec/sensor/type/SensorType.owl#Thermometer</sensorType><url>https://atom.research.microsoft.com/sensordatahub
/service.asmx</url><keywords>temperature</keywords><description>4th ave building</description><dataType>scalar</dataType><sam
plingPeriod>10</samplingPeriod><reportPeriod>10</reportPeriod><entryTime>2007-05-29T23:56:08.153</entryTime></Sensor>

Could you check the this error when we sign in?

Wed, 13 Jun 2007 18:50:47 Z

I'd like to sign in for registering sensors, so I tried to sign in to SensorMap. However, I got some error like "The type initializer for 'MSR.PII.Proxy.Configurations' threw an exception.".

Could you check it?

Thank you in advance.
Seungweon.

Trying to perform SOAP actions at DataHub no success

Tue, 22 May 2007 09:13:20 Z

Hello. I'm trying to figure out how to use publish and retrieve sensor data via using the datahub web service via the supported SOAP api functions but I am getting the errors below. I've written the steps of what I did along with a snippet of code and the error I'm getting.

1. Manually created an account on Sensor Map.
2. Located my area on map, right mouse click, did add sensor, gave it name 'PSU Camera'
3. Created python script with following code (with publisher info and password blanked out).
    to test using the SOAP api functions

       import SOAPpy
       from SOAPpy import SOAPProxy
       url = 'http://atom.research.microsoft.com/sensordatahub/service.asmx'
       server = SOAPProxy(url)
       publisher = 'xxxx1'
       password = 'xxxx2'
       sensorname = 'PSU Camera'
       smdl = server.GetSensorDescriptionByName(publisher,password,sensorname)
       print smdl
       server.RemoveSensor(publisher,password,smdl)

4. The above code is saved in pull.py
5. I run python -i pull.py
      The error I get back is
       <Fault soap:Client: Server did not recognize the value of HTTP Header SOAPAction: GetSensorDescriptionByName.: >

6. I searched for meaning of this fault and the reason I found is that this occurs when the parameters for the function don't match those of the web service. I've double checked this and it appears I have it right (unless I'm using python incorrectly, since I'm new to it).   It could
be I may need to use ZSI instead of SOAPy library in python.

Let me know if you have suggestions, thoughts or ideas.

Judy

IPSN Slides on SensorMap

Thu, 03 May 2007 18:47:49 Z

Even though the Publishing Tutorial is accessible on the Internet, I was wondering of the slides that were used during the SensorMap Tutorial at IPSN are available for download?

I tried to find them on the various MSRSense, Sense Web, and SensorMap sites, but to no avail.

Thanks!

How to invoke API functions via SOAP

Fri, 04 May 2007 17:51:56 Z

Hello,

We are new to using SensorMap. We are trying to figure out how to use your API (RegisterSensor for example) and we want to invoke these via SOAP files. Do you have information you could share with us to help us understand how to do this?

Thanks,

Platform Compatibiity

Sat, 28 Apr 2007 16:29:18 Z

From: Mathias bavay [mailto:bavay@slf.ch]

Sent: Friday, April 27, 2007 2:45 AM

To: SenseWeb Contacts

Subject: Sensormap, browser/plateform compatibility

Hi!

I am writing to you to report some compatibility testing that I did on SensorMap (since you invite us to give some feedback on these issues...!):

*on Firefox 1.0/Linux, the first page is mostly visible, but the map itself takes all the space and leaves no room for the right hand side bar (and the Javascript console complains about the javascript)

*on Firefox 1.5/Linux, everything seems to be working perfectly

*on Firefox 2.0.0.2/Linux, only the top banner of the page is shown...

*on Firefox 2.0.0.3/Linux and Windows 2K, everything seems to be working perfectly

*on Konqueror 3.5.4/Linux (that is, khtml), only the top banner of the page is shown (I don't have a Safari handy to try it right now, but I guess it would be similar).

*on IE 6/Win2K, everything seems to be working perfectly

To make that long story short: Sensor Map works fine with Firefox, beside some specific releases that have been experiencing some site compatibility regressions.

Mathias Bavay

SLF