Re: [OSM-talk] Coordinates in OSM. Really annoying

[Viet Nguyen]

Not to mention [longitude, latitude] vs [latitude, longitude] issue.

I'm working on a web app using Leaflet library and had spent hours
debugging my own code trying to figure out why data points didn't show up
or showed up in the wrong continent.   As it turned out Leaflet expects [x,
y] cartesian coordinates or [latitude, longitude].  I just had to remember
flipping my coordinates.


Viet



On Sat, Apr 22, 2017 at 5:57 AM, Oleksiy Muzalyev <
oleksiy.muzal...@bluewin.ch> wrote:

> On 21.04.17 17:28, Dave F wrote:
>
>> Hi
>>
>> This is one of my OSM bugbears: http://osm.duschmarke.de/bbox.html
>>
>> Is there /really/ any need for *six* coordinate formats? It's hard enough
>> to learn a new process without basics like this tripping you up. Is there
>> any reason why the developers of these programs can't talk to each other &
>> simplify the situation?
>>
>> Cheers
>> DaveF.
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>>
>> ___
>> talk mailing list
>> talk@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
>
> Hi,
>
> But such a situation is the same everywhere. Take Plug & socket types
> http://www.worldstandards.eu/electricity/plugs-and-sockets/
>
> These plugs types (and adapters) are the cause of numerous problems for
> travelers (like searching in a town for an adapter at night, sigh...).
> However, it seems indeed people can't talk to each other.
>
> Cheers,
>
> O.
>
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk

[OSM-talk] How to define a climbing crag/area?

[Viet Nguyen]

Greetings!

I'm an avid rock climber and open source enthusiast.  I want to build
better climbing maps and an easy-to-use mobile app for climbers to share
information.

Many climbing walls/crags/areas are currently defined as nodes in OSM.  In
contrast, in my proof-of-concept app users can define and save crag
boundaries by drawing polygons on the map.  The search function would then
use spatial queries to find features contained within a polygon.

The linked photo below illustrates typical layout of a climbing area. Crag
boundaries are often loosely defined by climbers... so I'm not sure whether
saving those polygons to OSM is a good idea.

https://s9.postimg.org/xg4dq6mbj/nested-boundaries-example.jpg


Also I have looked into using Relations but the concept seems rigid for
this use case as it would require the users (or the code) to associate
climbing routes to a relation.  Perhaps I misunderstand the concept of
relations?

I'm looking for guidance and suggestions on how to best implement this
feature.  Having all geo-data in OSM (single source of truth) would be
ideal, but I can just store those polygons in my own database as well.

Here's my proposal:

https://wiki.openstreetmap.org/wiki/Proposed_features/
OpenBeta_Initiative_workflow


Thanks,

Viet Nguyen

















https://s9.postimg.org/xg4dq6mbj/nested-boundaries-example.jpg
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk