[Talk-GB] [OSM-talk] Coordinates in OSM. Really annoying

Dave F davefoxfac63 at btinternet.com
Sat Apr 22 15:23:15 UTC 2017


In this context I'm unsure what you mean by "interface standards"

On 22/04/2017 15:45, Lester Caine wrote:
> On 22/04/17 15:28, Dave F wrote:
>> As they're parameters, the format can be standardised for the end user &
>> any programme should be able to sort out syntax behind the scenes.
> Totally agree except passing box="w,s,e,n" is STILL a matter of the
> passing mechanism the target application is built around. There would be
> no problem with the box selector simply providing the right input via a
> link to the target application, and a graphic interface providing a
> suitable 'box' into which to put the coordinate string into for GUI
> interfaces, but as I said ... the problem is the vast number of
> interface standards currently in use and not a simple one to solve for
> one piece of data.
>
>> On 22/04/2017 15:15, Lester Caine wrote:
>>> On 22/04/17 14:19, Dave F wrote:
>>>> It's to provide the numerous coordinates format for each of the
>>>> programs. Select a boundary box (Alt+LButton mouse drag) & you get:
>>>>
>>>> https://pbs.twimg.com/media/C-BP_QdWsAEN-Ac.jpg
>>>>
>>>> I can't understand the need for the variations in syntax
>>> Not worked out how to stop 'ALT' moving the window so I could not see
>>> the results. :) Essentially there are two 'problems'. Overpass using
>>> different orders on the different API has been a problem with other
>>> API's, but the other 5 are all essentially the same and it would not
>>> take much for them to take box="w,s,e,n" as an alternative input. But
>>> the range of 'standards' for passing parameters is the problem here not
>>> simply what is being passed. With each OS and programming language
>>> having it's own style of working there is simply to many variables to
>>> create a single standard :(
>




More information about the Talk-GB mailing list