Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature ID (row.names) #15

Closed
edzer opened this issue Feb 26, 2016 · 3 comments
Closed

feature ID (row.names) #15

edzer opened this issue Feb 26, 2016 · 3 comments

Comments

@edzer
Copy link
Member

edzer commented Feb 26, 2016

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).

@fdetsch
Copy link
Collaborator

fdetsch commented Mar 3, 2016

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.

@edzer
Copy link
Member Author

edzer commented Mar 3, 2016

Great, thanks a lot!

@tim-salabim
Copy link
Member

Given that we now have mouseCoordinates and only show lon/lat coordinates for points I am closing this issue

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants