Geospatial Data
Hi Team,
Will our DQ tool work with geospatial data? Client primarily has aeronautical Information like: airspace, runway location data, etc?
Thanks!
michaelwilcox
Posted 5 years ago · Edited 1 year ago·Last reply 5 years ago
3 comments
michaelwilcox
OP5 years ago · EditedThanks Kirk. Good to know. Although not merchant locations, I think the use case and capabilities you mentioned may be useful. Will confirm details with client and follow-up with the team accordingly. Thanks again.
kirkhaslbeck
·5 years ago · EditedWe have seen cases with simple LAT LNG like the kind in google maps where DQ can work such as merchant locations. CONCATing LAT and LNG does provide a unique data point on the map or validating that they are valid decimals or the proper length can provide some basic DQ on these elements. What it does not do is compute a POINT or understand the distance between geospatial points
leonkim
·5 years ago · EditedNo. This should be added into Ideation. Geospatial data is complicated because the data types can be quite complex.
One thing to watch out for in the current version of DQ is that if you have your location as latitude and longitude in decimals, DQ will falsely detect it as a normal decimal and treat it as a number. It is suggested that these columns are omitted from DQ Job as it is very misleading. We could consider detecting these columns as part of our semantic search (like how PII columns are automatically tagged). This should also be in the ideation process