Hi david. Yes, I understand what you're trying to do now. My proposed solution isn't terribly elegant, but it should provide a good idea of what you'll need to do.

Two sensor feeds are needed: one listing water storage sensors, the other listing current sensors. Of course, you can add as many feeds as you want, one for each type of sensor. Since the feeds are separate, they can be displayed in separate tables using multiple gm:list modules. To have them appear on the same map, you need to copy the contents of each feed to a separate, temporary feed so all entries are aggregated. (You can reference the sample mashup I linked to above which does just this.) The map's data source should be set to this temporary feed.

Since the markers represent different types of sensors, you won't be able to reference custom elements such as gmd:capacidad_actual in the map's "infotemplate" if they are not pertinent to every sensor. Instead, your best bet is to place all pertinent data in an element common to all feeds such as atom:content. Then reference this element in the infotemplate -- this way, no matter which type of sensor is selected, the proper information will appear in your map's info. windows.

One quick note: I notice in your source that you reference elements called atom:capacidad_maxima and atom:capacidad_actual. The atom namespace (which includes, title, summary, content, etc.) is not extensible in this fashion; instead, you should define a custom namespace for elements not in the original specification. geo: is one such namespace for geo fields. GME's built-in feeds support gmd: which is completely extensible. Just some food for thought.

I hope this helps you. Let me know if you have other questions.

On Mar 27, 2:23 pm, david lópez <davi...@googlemail.com> wrote: