GPS Field (Reviews of offline busineses)

[maltfield]

This ticket is a feature request to add a new data field that users can fill-in when adding a review to lib.reviews:

1. GPS Coordinates

Problem

Currently there is a required field that users must enter in order to submit a new entry to lib.reviews:

1. URL of review subject

I specifically signed-up for lib.reviews because I'm trying to add information about businesses that do not have a web presence.

I live in a country in South America, where there's an avalanche small businesses. Most businesses here don't have a web presence. As a result, if you need a specialty item (like, say, some specialty carpentry tool or kitchen equipment), then it's extremely difficult to find out where to go (ie which stores might sell what you need) by an Internet search.

This is exactly the problem I was hoping to solve with lib.reviews. For example, I wanted to visit all of the hardware stores in a given city in South America and write a review that talks about the general inventory that they have, and any specialty items that they sell.

This is currently not possible on lib.reviews because

1. The URL of review subject field is required and
2. There is no way to enter the GPS Coordinates of review subject

Solution

As an alternative to the required URL of review subject field, we should add a GPS Coordinates of review subject field. Either one of these should suffice.

[maltfield]

This is also a good first-step (with much lower hanging fruit = easier to implement) to get to #52 & #319

[eloquence]

Hi @maltfield , I know it's not exactly what you're asking, but in cases like this, if the business is in OSM, it should be possible to review by OSM URL, e.g.:

https://www.openstreetmap.org/node/5559066593

lib.reviews will look up a label (and keep it up-to-date with OSM) if one is configured there. For example, here I'm reviewing a supermarket in Pretoria that doesn't appear to have an independent web presence. The OSM adapter in lib.reviews fetches the label from OSM and inserts it, and an automatic sync job will regularly ensure it is up-to-date:

[maltfield]

That's a good workaround for now, thank you :)