feat: Climb/Route coordinates #1092
Conversation
|
@alexoj46 is attempting to deploy a commit to the openbeta-dev Team on Vercel. A member of the Team first needs to authorize it. |
|
Rather than showing NA, we should inherit the parents coordinates. |
|
See #1057 for discussion of
why inheriting parent coordinates may not be the best approach.
…On Sat, Feb 10, 2024, 23:22 Blake McCord ***@***.***> wrote:
Rather than showing NA, we should inherit the parents coordinates.
—
Reply to this email directly, view it on GitHub
<#1092 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD7ET7FRSYMGIONLS4EKGCLYTBBRPAVCNFSM6AAAAABDAVOWQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGQYTSNZRGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
That makes sense for areas, however if we have a coordinate for an area we should show it on the route page as a very high percentage of the time they will be that same (for our purposes as climbers). Route coordinates are only really usefully for a handful of areas that are very low density. What about indicating that the coordinates displayed are that of the area? |
|
Yes, that would probably do the trick - maybe even just show them grayed
out?
…On Sat, Feb 10, 2024, 23:34 Blake McCord ***@***.***> wrote:
See #1057 <#1057> for
discussion of why inheriting parent coordinates may not be the best
approach.
That makes sense for areas, however if we have a coordinate for an area we
should show it on the route page as a very high percentage of the time they
will be that same (for our purposes as climbers).
Route coordinates are only really usefully for a handful of areas that are
very low density.
What about indicating that the coordinates displayed are that of the area?
—
Reply to this email directly, view it on GitHub
<#1092 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD7ET7EZCX4QG32JYODYTITYTBC5PAVCNFSM6AAAAABDAVOWQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGQZDCOBRGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I've just looked at the backend code. When creating a new route, the backend populates the climb's coordinate pair with that of the parent. We can hash out more detail in #1057. For this PR we can just deal with the visual. If the climb object doesn't have coordinates, it's not easy to fetch the parent's nor it is worth it to deal with in the frontend (I think the backend is a better place for it). Can we just not show it if that's the case? What about adding some wording to indicate the coordinates are inherited form the parent? Something like 
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
If this is the case I would think it's not possible to tell if it's inherited or not...? I guess that right now they are all inherited since we have now editing functionality for climb coordinates currently? |
Right now they all inherited, but we can't edit climb coordinates at the moment. |
| 34.18008, | ||
| -85.81680 |
There was a problem hiding this comment.
Can you swap the order? Coordinate pair is expressed as longitude/lat (x,y) in geojson
name: feat: Climb/Route coordinates
What type of PR is this?(check all applicable)
Description
Implemented FrontEnd solution to Issue #1078 to add climb/route coordinates to climb pages.
Related Issues
Issue #1078
What this PR achieves
Added FrontEnd component to climb/route page to display route coordinates. The component will also link to Google Maps, and will add a tick to the map on the website.
Screenshots, recordings
Notes
If coordinates are not present in metadata for that climb, the lat, lng display will still appear, with NA, NA as the value (as shown in the photo).
Also added my contributor information.