https://community.cloudera.com/t5/Archives-of-Support-Questions/ESRI-Spatial-Framework-does-not-provide-a-native-geometry/m-p/167949#M37129 <P>@<A href="https://community.hortonworks.com/users/12061/mahipalramidi.html">Mahipal Ramidi</A></P><P>Taking in account how ST_GeomFromText or St_GeomFromJson functions are used to convert text or json to geometry and then geometry is used in various functions, they provide the same functionality. If the value as text or json had to be parsed with some special conditions, then JSON would have been a better choice for processing, but that is not a known use case. As such, overall, used as explained above, text makes more sense, taking even less space (no structure included). If there will be a case where the above assumption is not true, add another column to your table, shape_json and convert text to json, or apply a text to json function for the specific scenario if performance is not impacted. If performance is impacted, denormalize by adding shape_json column.</P> Tue, 09 Aug 2016 03:20:19 GMT cstanca 2016-08-09T03:20:19Z https://community.cloudera.com/t5/Archives-of-Support-Questions/ESRI-Spatial-Framework-does-not-provide-a-native-geometry/m-p/167948#M37128 <P>ESRI Spatial Framework does not provide a native geometry type in Hive, the alternative is to store the geometry in text or json format. What is better for functionality and performance.</P> Mon, 08 Aug 2016 02:51:28 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/ESRI-Spatial-Framework-does-not-provide-a-native-geometry/m-p/167948#M37128 mahipal_ramidi 2016-08-08T02:51:28Z https://community.cloudera.com/t5/Archives-of-Support-Questions/ESRI-Spatial-Framework-does-not-provide-a-native-geometry/m-p/167949#M37129 <P>@<A href="https://community.hortonworks.com/users/12061/mahipalramidi.html">Mahipal Ramidi</A></P><P>Taking in account how ST_GeomFromText or St_GeomFromJson functions are used to convert text or json to geometry and then geometry is used in various functions, they provide the same functionality. If the value as text or json had to be parsed with some special conditions, then JSON would have been a better choice for processing, but that is not a known use case. As such, overall, used as explained above, text makes more sense, taking even less space (no structure included). If there will be a case where the above assumption is not true, add another column to your table, shape_json and convert text to json, or apply a text to json function for the specific scenario if performance is not impacted. If performance is impacted, denormalize by adding shape_json column.</P> Tue, 09 Aug 2016 03:20:19 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/ESRI-Spatial-Framework-does-not-provide-a-native-geometry/m-p/167949#M37129 cstanca 2016-08-09T03:20:19Z