<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p><br>
</p>
<p>Could one of the reasons be that open source developers are doing this in their own time and have a million other responsibilities in their lives?</p>
<p><br>
TBH I think it's a case of live with it and read the documentation. There are more important things to worry about.
<img class="x_EmojiInsert" id="OWAEmoji419123" alt="��" style="vertical-align:bottom" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABMAAAATCAYAAAByUDbMAAAAGXRFWHRTb2Z0d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAAAYpJREFUeNpi/P//PwO1ACM2wf9njBWAVD4QBwCxApLUAyDeAMQTGU3OPkDRA3QUIxaD+oFUAREOaQQa2IDTMKBB84FUAgk+WwA0MBFmGBOaixJIDKYEoD6465igBjkge+3CrW94TUCTr4eGMdxl8TCZxMYHDIZR1xk2HPiA1SCQOEgepA4J5CMbFgAPhM1vwfTFW9+xGgYTh6lD1s8IdKIAkH4PEz1w9jOYVpBiZ1CQZMMw7MHzXwwPnv0Esx2MeRESxmcYWYCUAbJiFAVYAMgCbJbAvPmAWjmACZqS4aHdOOs5wdgEBcWE5a8Y0HIGPAIOwETtjXkYJqIqxAAgeQM1ThTzkQ2biB5mC7a8xZ7kgeICvMzoYTsRJaMDY3U9chIBpaMHz34xxPsKgwMcFIsLgckB5KL+YllkgyYAg6oQJW9Ck8h+5NgFhd3GAx/humAGI2cGIHYEGvYBW0YHGTgf2YX4MjkQF4IMwlkEIeXVfByGwsqzAwTLMywGg7wNcvED9AIR3TCAAAMAqh+p+YMVeBQAAAAASUVORK5CYII="></p>
<p><br>
</p>
<p>Nick<br>
</p>
<font face="Calibri,sans-serif" size="2"><span style="font-size:11pt"><a href="http://www.solent.ac.uk/disclaimer/disclaimer.aspx" target="_blank" id="LPNoLP" title="Ctrl+Click or tap to follow the link"><font face="Trebuchet MS,sans-serif" size="1"><span style="font-size:8pt"></span></font></a></span></font><br>
<div id="x_Signature">
<div id="x_divtagdefaultwrapper" dir="ltr" style="color:rgb(0,0,0); font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt">
</div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Dave F <davefoxfac63@btinternet.com><br>
<b>Sent:</b> 24 April 2017 11:31:24<br>
<b>To:</b> OSM Talk<br>
<b>Subject:</b> Re: [OSM-talk] Coordinates in OSM. Really annoying</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi<br>
<br>
I'm unsure why go on about anyone being "thrown out".<br>
<br>
I'm unsure why doing it inconsistently in the past in 'legacy' code is <br>
any reason for not trying to sort it out for the future.<br>
<br>
Programmers can reformat to any standard* of their desire /within/ their <br>
own program. It can't be hard to do; it is, after all, pure ASCII text.<br>
What's irritating is the responsibility oft the syntax has been passed <br>
on to the end user.<br>
<br>
What are the reasons the authors of the programs listed can't coordinate <br>
with each other to simplify it for users within OSM community?<br>
<br>
* Are they really adhering to a 'standard' or just doing it one way <br>
because a competitor did it another?<br>
<br>
DaveF<br>
<br>
On 23/04/2017 08:29, Roland Olbricht wrote:<br>
> Hi,<br>
><br>
>> Is there /really/ any need for *six* coordinate formats? It's hard<br>
>> enough to learn a new process without basics like this tripping you up.<br>
><br>
> There is nobody who is trusted enough to set an universal standard:<br>
> <a href="https://xkcd.com/927/">https://xkcd.com/927/</a><br>
><br>
> Basically, there is an ISO standard<br>
> <a href="https://en.wikipedia.org/wiki/ISO_6709">https://en.wikipedia.org/wiki/ISO_6709</a><br>
> to have latitude before longitude. Leaflet complies, OpenLayers does not.<br>
><br>
> This is for historical reasons. When multiple projections were <br>
> commonplace as exchange formats, then they often used x and y as names <br>
> for the two numbers, and x often decoded to something loosely or <br>
> tightly related to longitude.<br>
><br>
> However, OpenLayers is too useful to be thrown out just for having the <br>
> wrong coordinate order. The same applies to a lot of other tools with <br>
> legacy coordinate order.<br>
><br>
> To have a gentle pressure towards the ISO standard, the advertised <br>
> interface is latitude-longitude. There are some precautions for inert <br>
> legacy tools:<br>
> <a href="http://dev.overpass-api.de/blog/bounding_boxes.html#lonlat_bbox">http://dev.overpass-api.de/blog/bounding_boxes.html#lonlat_bbox</a><br>
><br>
> As Lester has pointed out, XML requires explicit parameter names. By <br>
> the way, I am not aware of anybody actively using the XML syntax. You <br>
> can safely ignore that.<br>
><br>
> For the delimiter question: There are programming languages with a <br>
> combined market share of almost 90% that agree to have to semanticy in <br>
> whitespace. The sole widespread-used exception is Python. Once again: <br>
> Are you seriously asking the OSM community for a crusade to throw out <br>
> Python for minor syntactic infrigement?<br>
><br>
> Beside Python, the delimiters are always commas and semi-colons. As <br>
> commas tend to be used to delimit parameters, they are for the numbers <br>
> of the bounding box the delimiters of choice.<br>
><br>
> Cheers,<br>
><br>
> Roland<br>
><br>
<br>
<br>
_______________________________________________<br>
talk mailing list<br>
talk@openstreetmap.org<br>
<a href="https://lists.openstreetmap.org/listinfo/talk">https://lists.openstreetmap.org/listinfo/talk</a><br>
</div>
</span></font>
</body>
</html>