| It looks OK...In reality a lot of heatmaps have a lot of overlap
    because they often mirror population density :) 
 But it is useful when mapping one feature that is very sparse on top
    of another more common feature as long as its on top and the colors
    are discernible.
 
 
 On 07/21/2016 10:47 AM, Emilio
      Lahr-Vivaz wrote:
 
      
      We could pretty easily combine the grids. We'd need to create a
        WPS process to wrap everything up though. How does the multiple
        heatmap overlay end up looking?
 
 On 07/21/2016 10:43 AM, Andrew
        Hulbert wrote:
 
        
        The only thing that I've seen done so far is generating 3
        heatmaps from 3 different queries/layers and overlaying them on
        the same map.
 Could we run the Z3 density iterator over 3 different types and
        then combine the returned grids to create a single grid?
 
 
 On 07/21/2016 09:38 AM, Emilio
          Lahr-Vivaz wrote:
 
          
          Hi Diane,
 We don't currently support generating heatmaps from multiple
          schemas at once, so sharing of catalogs won't matter in that
          regard. Possibly you could generate heatmaps from multiple
          layers in a single request, and use alpha transparency to
          overlay them? I believe that should be possible with SLDs, but
          I'm not entirely sure.
 
 Thanks,
 
 Emilio
 
 
 On 07/21/2016 09:24 AM, Diane
            Griffith wrote:
 
            
            
            
            
              So building on my question of
                multiple simple feature types in one geomesa catalog,  I
                was asking that because I was under an assumption if I
                wanted to use the geomesa server generated heatmap
                across different simple feature types that they
                potentially would need to be in the same catalog.   The better question really was can
                the geomesa heatmap feature generate a heatmap for
                multiple simple feature types at once?    If so how does
                it have to be structured?   Or does putting it in the same
                catalog not help and it would require a shared simple
                feature type schema to support one heat map for all the
                types of data?   Thanks, Diane 
 
 _______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users 
 
 
 _______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users 
 
 
 _______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users 
 
 
 _______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users 
 |