Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
Needs more info comment that > 10 days [ID: 963198]
Comment such as: SPAM, non-actionable [ID: 963127]
Resolved actionable follow-up comments [ID: 963027]
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
Feature Request
-----------------------
Currently the API geocodes business with different suite numbers as the same location in tall city buildings. A common problem, especially in Manhattan, is that suites in a tall building need to be kept separate. For example a business on the 1st floor is at a very different geolocation than the one on the 10th floor. Even when the suite numbers are separate in an address, the API currently provides a lat/lng that is the same.
For our application it is not necessary to know the altitude of the suites, but it is critical to know they are distinct locations. We would also like to have enough information from the API to help estimate the 'travel time' between the suites. To learn more about our application, see
Note, in many cases where there are strip malls with adjoining suites side by side, the API usually gives a slightly different lat/lng which is helpful. However in cities with tall buildings, suites that are on top of one another often give the same lat/lng even though they may be 100's of feet apart. It seems like suite number parsing should be part of the API rather than leaving it to us to geocode the suite number separately.