Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upgeocode: optionally return DisplayPosition #53
Comments
|
Not sure what the best way forward would be. I.e. return only one of the two, depending on an additional function argument. Or just return both? Seeing that |
|
Thank you very much for pointing out the difference between the two types of latitude/longitude. To be honest the choice of the navigation position was not on purpose. As you suggest it seems to make more sense to return the position as default and deliver the navigational optionally via an additional function argument or as an additional simple feature geometry list column ( When the Geocoding API is updated to v7 as mentioned in #52 the display position ( |
|
The position and access coordinates are now returned by default:
If the returned value should be a
The only downside of this solution is a warning when plotting the geocoded addresses with the {mapview} package:
Session info
|
geocode()currently returns the latitude/longitude values of theNavigationPosition.From https://developer.here.com/documentation/geocoder/dev_guide/topics/resource-type-response-geocode.html#resource-type-response-geocode__location
Depending on the use case, e.g. mapping, the alternative
DisplayPositionmay be better suited:Would you consider optionally returning the
DisplayPositionlat/lngpair? I have been bitten by this, namely that two or more distinct addresse have the sameNavigationPosition(i.e. access from the road), but differentDisplayPositions.NavigationPositionandDisplayPositionare respectively calledaccessandpositionin the v7 API (Navigate to Geocode > Responses > 200 > items).