<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Recommendation for storing geoLocation in Developers Questions</title>
    <link>https://community.esri.com/t5/developers-questions/recommendation-for-storing-geolocation/m-p/356379#M2291</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm working on a construction web app that could benefit from storing geolocation information.&amp;nbsp; When someone keys in a new construction site, they typically have an address or parcel that they enter.&amp;nbsp; We have a couple of clients who use ESRI and have granted us access to their web service in order to pull layer info based on address/parcel.&amp;nbsp; I've been thinking though that it may be useful to also store the geolocation so that we can graphically display a map with pins indicating project locations.&amp;nbsp; We would probably use Google maps for this portion since we don't have a license to use ESRI ourselves.&amp;nbsp; Being new to GIS im a bit confused on how to best store this geolocation in the database in order to be as flexible as possible.&amp;nbsp; Should i store a lat/lon or a x,y coordinate with a spacial reference?&amp;nbsp; Is any spacial reference more globally adopted than another or does that even matter?&amp;nbsp; My goal is to store the most readily usable format for use in multiple systems.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Oct 2015 17:01:53 GMT</pubDate>
    <dc:creator>JaceColeman1</dc:creator>
    <dc:date>2015-10-26T17:01:53Z</dc:date>
    <item>
      <title>Recommendation for storing geoLocation</title>
      <link>https://community.esri.com/t5/developers-questions/recommendation-for-storing-geolocation/m-p/356379#M2291</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm working on a construction web app that could benefit from storing geolocation information.&amp;nbsp; When someone keys in a new construction site, they typically have an address or parcel that they enter.&amp;nbsp; We have a couple of clients who use ESRI and have granted us access to their web service in order to pull layer info based on address/parcel.&amp;nbsp; I've been thinking though that it may be useful to also store the geolocation so that we can graphically display a map with pins indicating project locations.&amp;nbsp; We would probably use Google maps for this portion since we don't have a license to use ESRI ourselves.&amp;nbsp; Being new to GIS im a bit confused on how to best store this geolocation in the database in order to be as flexible as possible.&amp;nbsp; Should i store a lat/lon or a x,y coordinate with a spacial reference?&amp;nbsp; Is any spacial reference more globally adopted than another or does that even matter?&amp;nbsp; My goal is to store the most readily usable format for use in multiple systems.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Oct 2015 17:01:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-questions/recommendation-for-storing-geolocation/m-p/356379#M2291</guid>
      <dc:creator>JaceColeman1</dc:creator>
      <dc:date>2015-10-26T17:01:53Z</dc:date>
    </item>
  </channel>
</rss>

