Latitudes and Longitudes

[iamkurt]

Has anyone ever used Latitude and Longitude?
If yes, for what reason?

If no one uses it, why did ServiceNow even think of having this field?
Is there any data validation on this field as they are expressed in terms of degrees (°), minutes ('), and seconds (") ??

I hear they are used in Field Service Management but do they have any potential to be used in Hardware Asset Management or Software Asset Management?

[Luiz Lucena]

We used in few reports showing locations and incident numbers in maps.

Is helpful also to track incidents and assets location. Many other possibilities.

[PrabhakarCh]

We used for Crisis management, but with a third party integration. NOW still needs to mature in this area.  

[lastreaction122]

---

@iamkurt wrote:

Has anyone ever used Latitude and Longitude?
If yes, for what reason?

If no one uses it, why did ServiceNow even think of having this field?
Is there any data validation on this field as they are expressed in terms of degrees (°), minutes ('), and seconds (") ??

I hear they are used in Field Service Management but do they have any potential to be used in Hardware Asset Management or Software Asset Management?

---

I use these fields for tasks such as route optimization and asset tracking. For example, in Field Service Management, capturing the exact location allows me to determine the nearest available technician, optimize travel routes, and even visualize service areas on a map.

Even if some users rarely leverage it, I believe ServiceNow included the latitude and longitude fields to support a broad range of geospatial use cases.

I use the fields primarily in a decimal format rather than in a strict degrees/minutes/seconds notation. Out of the box, I’ve found that there isn’t built-in validation enforcing the traditional DMS (degrees, minutes, seconds) format. If I need strict validation, I implement custom client-side scripts or business rules to ensure the input meets the desired format.

I use latitude and longitude extensively in Field Service Management for mapping and tracking purposes. There’s also potential for these fields in Hardware Asset Management recording the physical location of devices across different sites, for instance. However, in Software Asset Management, I’ve found them less useful since software assets aren’t typically tied to physical locations unless you’re mapping out device deployments or network infrastructures.

[Jeffrey Siegel]

I use it on my location records, so I can see live on a map where my open incidents are. Its very handy to visualize the trouble if you have multiple locations.  Especially if you have a field force team, who travels from site to site, so they can organize their days better.