Re: [openstreetmap/openstreetmap-website] Add OpenLocationCode to OSM website (#1807)
ppKrauss left a comment (openstreetmap/openstreetmap-website#1807) **Solution** proposal: use another [domain name](https://en.wikipedia.org/wiki/Domain_name), and redirect the *geocode resolution* to OpenStreetMap (or others like [Wikipedia's Geohack](https://geohack.toolforge.org/geohack.php?pagename=Pra%C3%A7a_da_S%C3%A9¶ms=23_33_01_S_46_38_02_W_source:kolossus-ptwiki_type:landmark)). But a good name. I can **donate the domain name `osm.codes` to this community**. Domain ownership can be similar to that of a condominium: the OSM Foundation owns 45% of the property (to manage foundation's trademark "OSM") and a set of OSM interested members who are also here at *this issue* split the 55% ownership. The only objective of the `osm.codes` will be redirect or "resolve" [geocodes](https://en.wikipedia.org/wiki/Geocode). **Not only OLC**, but also Geohash, postcodes, OSM-IDs and others elected by this community and it rules. Dividing between 10 or more people the *annual cost* (host solution + maintain domain) will be minimal, 20 dollars per person or less. The cited other tools of the OSM ecosystem (like Osmand, OrganicMaps, Mapy.cz, etc.) can be also invited to contribute. PS: as an [persistent and official domain](https://en.wikipedia.org/wiki/Persistent_uniform_resource_locator) it can be used in other initiatives, like [Wikidata](https://www.wikidata.org/wiki/Property:P402), that need not only ID of relations, but also node-IDs and way-IDs interacting with it. It is easy to configure all at NGINX. -- Reply to this email directly or view it on GitHub: https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-2825543561 You are receiving this because you commented. Message ID: ___ rails-dev mailing list rails-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/rails-dev
Re: [openstreetmap/openstreetmap-website] minor changes to graphhopper routing (PR #6011)
karussell left a comment (openstreetmap/openstreetmap-website#6011) Have done so. -- Reply to this email directly or view it on GitHub: https://github.com/openstreetmap/openstreetmap-website/pull/6011#issuecomment-2876046130 You are receiving this because you are subscribed to this thread. Message ID: ___ rails-dev mailing list rails-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/rails-dev
[openstreetmap/openstreetmap-website] minor changes to graphhopper routing (PR #6011)
There are some minor updates to the latest GraphHopper API e.g. `vehicle` was deprecated a few years ago. Also there is no longer a need for the parameter `turn_costs` (related #2695). You can view, comment on, or merge this pull request online at: https://github.com/openstreetmap/openstreetmap-website/pull/6011 -- Commit Summary -- * Update graphhopper.js -- File Changes -- M app/assets/javascripts/index/directions/graphhopper.js (8) -- Patch Links -- https://github.com/openstreetmap/openstreetmap-website/pull/6011.patch https://github.com/openstreetmap/openstreetmap-website/pull/6011.diff -- Reply to this email directly or view it on GitHub: https://github.com/openstreetmap/openstreetmap-website/pull/6011 You are receiving this because you are subscribed to this thread. Message ID:___ rails-dev mailing list rails-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/rails-dev
Re: [openstreetmap/openstreetmap-website] minor changes to graphhopper routing (PR #6011)
@karussell pushed 1 commit. 0c12b1158ad587a1ac74b22e4e30a8e6c3e2b040 Update graphhopper.js -- View it on GitHub: https://github.com/openstreetmap/openstreetmap-website/pull/6011/files/d8eb6ad4366b50dd51958979b5cc06d99971d2ec..0c12b1158ad587a1ac74b22e4e30a8e6c3e2b040 You are receiving this because you are subscribed to this thread. Message ID: ___ rails-dev mailing list rails-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/rails-dev
Re: [openstreetmap/openstreetmap-website] Add OpenLocationCode to OSM website (#1807)
ppKrauss left a comment (openstreetmap/openstreetmap-website#1807) @erik55 You're on the right track when you say, "We just need interoperability and standards". We also need infrastructure to demonstrate usage, enable testing, and build an ecosystem. In this context we need to: 1. Discuss here how to transform `OSM.codes` into a set of [endpoints](https://en.wikipedia.org/wiki/Web_API#Endpoints) for simple **code resolution** (like "name resolution" in [RFC2169](https://datatracker.ietf.org/doc/html/rfc2169)) and future [PURL behavior/functionality](https://en.wikipedia.org/wiki/Persistent_uniform_resource_locator), similar to a [DOI](https://doi.org). 2. Discuss here how to extend the **geo URI** standard (a mature 15-year-old RFC that has never received attention from big tech companies), likely because it's centered on interoperability. See https://en.wikipedia.org/wiki/Geo_URI_scheme My suggestion for next steps is to adopt the syntax `geo:$x,$y;u=$u` as a Latitude/Longitude input. For example, `geo:-23.55,-46.63;u=15`. The `u` parameter stands for "uncertainty radius" (in meters), which can be used to infer the number of digits in the [grid geocode](https://en.wikipedia.org/wiki/Geocode#Hierarchical_grids). In this example, with `u=15`, the OLC geocode is `588MC8QV+C` and the Geohash is `6gyf4bv4`. 3. Discuss here whether we need additional [grid geocodes](https://en.wikipedia.org/wiki/Geocode#Hierarchical_grids) (beyond just OLC and Geohash), and how to extend the geo URI scheme to include them. My suggestion is to adopt the syntax `geo:$t:$g`, where `$t` is the type abbreviation (e.g., "olc" for OLC or "ghs" for Geohash) and `$g` is the geocode. Using the earlier examples: `geo:olc:588MC8QV+C` for OLC and `geo:ghs:6gyf4bv4` for Geohash. PS: regarding your other comments: * We cannot interfere with the `openstreetmap.org` website; unfortunately, that is out of the question. * "We prefer to popularize OLC" is also Google's preference, but in this community, we also want to *offer code resolution* for Geohash and perhaps other popular geocodes (like Uber H3). * The geo URI as interoperability standard is important as "zero [vendor_lock-in](https://en.wikipedia.org/wiki/Vendor_lock-in)". (pure OLC is a Google-standard without any clear technical advantage over Geohash). Imagine using `geo:olc:588MC8QV+C` in WhatsApp text, "I'm here!", or in ChatGPT prompt-text for geographic contextualization. -- Reply to this email directly or view it on GitHub: https://github.com/openstreetmap/openstreetmap-website/issues/1807#issuecomment-2865891223 You are receiving this because you commented. Message ID: ___ rails-dev mailing list rails-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/rails-dev
Re: [openstreetmap/openstreetmap-website] minor changes to graphhopper routing (PR #6011)
karussell left a comment (openstreetmap/openstreetmap-website#6011) Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/openstreetmap/openstreetmap-website/pull/6011#issuecomment-2877766376 You are receiving this because you are subscribed to this thread. Message ID: ___ rails-dev mailing list rails-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/rails-dev
