[Ssc-dev] lat long order in j3m

[Jonathan]

We’ve got it sorted out. Named key-value pairs save the day.


> On Oct 30, 2014, at 11:27 AM, Harlo Holmes <harlo.holmes at gmail.com> wrote:
> 
> while i definitely agree with the rationale presented, and i, too, am used to seeing lat/lng, this doesn't change the fact that ELS requires data to be massaged into one of those formats (as per the link I last submitted.)
> 
> Jonny & Svetlana: now that you have all the information available concerning why the data is the way it is, can you let us know if that's indeed a blocker for displaying lat/lng properly?
> 
> On Thu, Oct 30, 2014 at 2:20 PM, David Oliver <david at guardianproject.info <mailto:david at guardianproject.info>> wrote:
> Once again, I'm cool with anything we'd want to do internally.  But, I'd be at a loss to explain why we do anything other than display our data in a way users best understand.  
> 
> Well prior to the advent of computers (as in 1879), organizations like the US Geological Survey <http://en.wikipedia.org/wiki/United_States_Geological_Survey> were making definitive (and binding in law, in some cases) maps of the landscape.  Here's their definition:
> 
> http://education.usgs.gov/lessons/coordinatesystems.pdf <http://education.usgs.gov/lessons/coordinatesystems.pdf>
> 
> These standards - re-published in 2013 - use latitude/longitude.
> 
> 
> 
> 
> David M. Oliver | david at g <mailto:david at olivercoady.com>uardianproject.info <http://uardianproject.info/> | http://g <http://olivercoady.com/>uardianproject.info <http://uardianproject.info/> | @davidmoliver | +1 970 368 2366 <tel:%2B1%20970%20368%202366>
> On Thu, Oct 30, 2014 at 2:01 PM, Jonathan <megabulk at gmail.com <mailto:megabulk at gmail.com>> wrote:
> And then there’s this: http://docs.geotools.org/latest/userguide/library/referencing/order.html <http://docs.geotools.org/latest/userguide/library/referencing/order.html>
> It’s a snarly situation caused by programmers deciding early on that latitude/longitude should conform to X/Y and thus be in the opposite order from what most people expect. It’s kind of a SNAFU.
> 
> Svetlana, if you can return the proper lat and long from your API, I’ll be totally content.
> 
>> On Oct 30, 2014, at 10:54 AM, David Oliver <david at guardianproject.info <mailto:david at guardianproject.info>> wrote:
>> 
>> Harlo, 
>> 
>> I think it would be wise to distinguish between what is a standard in our internal data representation from what is displayed to users.  I've emailed a friend of mine with 30 years of experience in geographic information systems (including ESRI, the most prominent commercial GIS) and, as I suspected, his views align with the majority of things you see on the web related to display of earth-positioning data: lat/long is the order people are used to seeing.  
>> 
>> I looked at the GeoJSON website and see that they use terminology not familiar to most normal people, but probably ingrained in actual working cartographers (because it maps well to the idea of the Cartesian plane): "easting" and "northing".  In an absolutely hilarious error, this page on Wikipedia describes the meaning, and how to display.....then get's it backwards because....well, because that's what people expect: latitude, followed by longitude:
>> 
>> http://en.wikipedia.org/wiki/Easting_and_northing <http://en.wikipedia.org/wiki/Easting_and_northing>
>> 
>> By the way, who are "Elastic Search" and why is that of overriding importance to us?
>> 
>> 
>> 
>> 
>> 
>> 
>> David M. Oliver | david at g <mailto:david at olivercoady.com>uardianproject.info <http://uardianproject.info/> | http://g <http://olivercoady.com/>uardianproject.info <http://uardianproject.info/> | @davidmoliver | +1 970 368 2366 <tel:%2B1%20970%20368%202366>
>> On Thu, Oct 30, 2014 at 11:53 AM, Harlo Holmes <harlo.holmes at gmail.com <mailto:harlo.holmes at gmail.com>> wrote:
>> Actually, the order is Lon, Lat, to conform to GeoJSON standards (which is required by Elasticsearch.)
>> 
>> On Thu, Oct 30, 2014 at 11:52 AM, David Oliver <david at guardianproject.info <mailto:david at guardianproject.info>> wrote:
>> Agreed - the order is LAT, LONG
>> 
>> more info: http://www.geomidpoint.com/latlon.html <http://www.geomidpoint.com/latlon.html>
>> 
>> 
>> 
>> David M. Oliver | david at g <mailto:david at olivercoady.com>uardianproject.info <http://uardianproject.info/> | http://g <http://olivercoady.com/>uardianproject.info <http://uardianproject.info/> | @davidmoliver | +1 970 368 2366 <tel:%2B1%20970%20368%202366>
>> On Thu, Oct 30, 2014 at 10:53 AM, Svetlana Chirkova <schirkova at gmail.com <mailto:schirkova at gmail.com>> wrote:
>> Hi guys, just wanted to confirm that standard/convention of gps coordinates ordering (lat,lon vs lon,lat)
>> 
>> i always thought it was lat, lon (http://stackoverflow.com/questions/7309121/preferred-order-of-writing-latitude-longitude-tuples <http://stackoverflow.com/questions/7309121/preferred-order-of-writing-latitude-longitude-tuples>)
>> 
>> but j3m is lon,lat at the moment.
>> 
>> just wanted to confirm that:
>> - it's suppuposed to be 'long,lat'
>> - j3m will continie to be 'long,lat'
>> 
>> ?
>> 
>> where am i...
>> 
>> Thanks!
>> 
>> _______________________________________________
>> Ssc-dev mailing list
>> 
>> Post: Ssc-dev at lists.mayfirst.org <mailto:Ssc-dev at lists.mayfirst.org>
>> List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev <https://lists.mayfirst.org/mailman/listinfo/ssc-dev>
>> 
>> To Unsubscribe
>>         Send email to:  Ssc-dev-unsubscribe at lists.mayfirst.org <mailto:Ssc-dev-unsubscribe at lists.mayfirst.org>
>>         Or visit: https://lists.mayfirst.org/mailman/options/ssc-dev/david%40guardianproject.info <https://lists.mayfirst.org/mailman/options/ssc-dev/david%40guardianproject.info>
>> 
>> You are subscribed as: david at guardianproject.info <mailto:david at guardianproject.info>
>> 
>> 
>> 
>> _______________________________________________
>> Ssc-dev mailing list
>> 
>> Post: Ssc-dev at lists.mayfirst.org <mailto:Ssc-dev at lists.mayfirst.org>
>> List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev <https://lists.mayfirst.org/mailman/listinfo/ssc-dev>
>> 
>> To Unsubscribe
>>         Send email to:  Ssc-dev-unsubscribe at lists.mayfirst.org <mailto:Ssc-dev-unsubscribe at lists.mayfirst.org>
>>         Or visit: https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com <https://lists.mayfirst.org/mailman/options/ssc-dev/harlo.holmes%40gmail.com>
>> 
>> You are subscribed as: harlo.holmes at gmail.com <mailto:harlo.holmes at gmail.com>
>> 
>> 
>> 
>> _______________________________________________
>> Ssc-dev mailing list
>> 
>> Post: Ssc-dev at lists.mayfirst.org <mailto:Ssc-dev at lists.mayfirst.org>
>> List info: https://lists.mayfirst.org/mailman/listinfo/ssc-dev <https://lists.mayfirst.org/mailman/listinfo/ssc-dev>
>> 
>> To Unsubscribe
>>        Send email to:  Ssc-dev-unsubscribe at lists.mayfirst.org <mailto:Ssc-dev-unsubscribe at lists.mayfirst.org>
>>        Or visit: https://lists.mayfirst.org/mailman/options/ssc-dev/megabulk%40gmail.com <https://lists.mayfirst.org/mailman/options/ssc-dev/megabulk%40gmail.com>
>> 
>> You are subscribed as: megabulk at gmail.com <mailto:megabulk at gmail.com>
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/ssc-dev/attachments/20141030/79f774ee/attachment.html>