Add GPS coordinates to the location page

[Jaspotn0612]

Snipe-IT Version

5.1.8

Operating System

Oracle Linux 7

Web Server

Apache

PHP Version

7.4.22

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

My company has some sites that don't have an exact address as they are in remote locations, the best we can do is put the road that they are on but there are some roads that a quite long. So adding an address to a location can be broad.

Describe the solution you'd like A clear and concise description of what you want to happen.

I'd like to be able to add GPS Long/Lat coordinates to a location as well so if some needs to get to a location that they've never been before, they can use them for directions.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

N/A

Additional context Add any other context or screenshots about the feature request here.

This is similar to feature request #1828 however that more referred to a mobile device usage. I'm referring to the location tab within the interface as it is now.

[snipe]

This is an esoteric but kinda cool feature request. We'll try to squeeze it in. Thanks for the suggestion!

[Pierre-Lannoy]

Would love to see it too! I'm currently unable to automate mobile technicians planning because this field is missing.

[snipe]

@Pierre-Lannoy can you explain a little more how you’d expect this to work?

[Pierre-Lannoy]

Yes, of course.

First of all, I would like to tell you we're using Snipe-IT as "reference" for many data (like locations, assets, etc.) and we've developed some tools that intensively use API (for features that are specific to us). So when we think about Snipe-IT we're thinking about it as the place where all needed details are available.

We have many use cases where coordinates (latitude & longitude) are needed in these external "home applications". As it is not standard fields in Snipe-IT, we've decided ton "encode" these informations in the second address line - yes it's dirty, but we haven't choice for now.

The two main use-cases are:

1. The planning application to "schedule" and optimize trips for technicians. This home application use home APIs to determine places where technician is needed and collect the address (well, the coordinates ;) ) in Snipe-IT to build a road book for technicians. As some of locations (more than 30%) haven't a precise address, or address precisely recognized by geocoding, we have made the choice to only base this road book on coordinates.
2. The monitoring application to put on a map main monitoring KPIs. Many of our locations are datacenters - well not as you think about it, it's more like "closets" aha. And to make the match between monitorable assets and map coordinates… you got it, we use Snipe-IT.

To be honest, it's working. But our method is not error proof (if someone set a wrong character in the address line that have coordinates for example). And it would make so much sense to have coordinates as standard fields. A location is a geographical place. So yes it have an address, but explicit coordinates too for all cases where geocoding is not working or precise. For us, it's not an edge case…

Hope it's more clear for you.