You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When querying a feature, it would be nice if in addition to the long/lat and attribute value, the feature ID, obtained by row.names(obj), would appear. This makes it easier to identify administrative districts, or sample IDs.
When clicking in polygons, we don't get the long/lat of the clicked point, but that of the center point of the polygon. I'd suggest to replace long/lat with feature ID (row.name) in case of polygons (and perhaps lines).
The text was updated successfully, but these errors were encountered:
Starting from the most recent 'develop' version (1.0.10), feature IDs (i.e., rownames) related with objects of class SpatialPointsDataFrame, SpatialPolygonsDataFrame, and SpatialLinesDataFrame are now being displayed in the pop-up windows. Please note that long/lat coordinates are not explicitly visualized when it comes to the latter, e.g.
mapview(atlStorms2005)
As for polygons, we should soon decide upon the additional value of centroid coordinates. It does not require too much effort to switch on/off such features in the associated pop-up tables.
When querying a feature, it would be nice if in addition to the long/lat and attribute value, the feature ID, obtained by
row.names(obj)
, would appear. This makes it easier to identify administrative districts, or sample IDs.When clicking in polygons, we don't get the long/lat of the clicked point, but that of the center point of the polygon. I'd suggest to replace long/lat with feature ID (row.name) in case of polygons (and perhaps lines).
The text was updated successfully, but these errors were encountered: