caresteouvert / caresteouvert_backend Goto Github PK

Back-end for "Ça reste ouvert" (caresteouvert.fr)

License: GNU Affero General Public License v3.0

JavaScript 98.03% Dockerfile 1.47% Shell 0.49%

caresteouvert_backend's Introduction

Ça reste ouvert (It Remains Open)

Ça reste ouvert, la carte collaborative des lieux ouverts durant la crise sanitaire / the collaborative map of the places open during the health crisis #Covid19.

Toutes les informations sur le projet sont ici / All informations about the project here : https://blog.caresteouvert.fr/about

Ça reste ouvert a été forké : Cartomobil'ité

Architecture

To deploy a complete instance of "Ça reste ouvert", you needs:

this map (see the Developement section)
postgres with postgis and data loaded
pg_tileserv
pg_featureserv
Ça reste ouvert backend (complementary API)

Development

The easiest way to contribute to the map is to use Docker:

./script/server

Otherwise, you can use use yarn:

yarn install
yarn run sprites
yarn run icons
yarn run dev

And go to http://localhost:1234/.

Production

The stack can be started using already built images, on a production environment:

cd db/
docker-compose -f docker-compose.yaml -f docker-compose-prod.yaml up -d pg_tileserv pg_featureserv geoip web worker front

Translation

Translations are managed via Transifex, go here to translate it in your language.

Data

Data used on our map comes from two sources :

OpenStreetMap : the free, worldwide geographic database. We use information about points of interest and also lockdown opening hours
Covid enseignes : chain stores opening rules by country. This allows to mark as open/closed a wide range of shops worldwide.

So you can either directly contribute to OpenStreetMap (using opening_hours:covid19=* tag on individual features), or add rules concerning chain stores in Covid enseignes repository.

Data derivated from Ça reste ouvert can be downloaded at this URL : https://download.osmontrouge.fr/caresteouvert/

License

Released under the AGPL v3 terms, see the LICENSE file to read the full text.

caresteouvert_backend's People

Contributors

Stargazers

Watchers

Forkers

alesarrett cartomobil-ite

caresteouvert_backend's Issues

Split locales into files for Transifex integration

Does it make sense to translate locale.json to the other frontend languages?

NotesReview doesn't filter country hashtag as expected

I think notes tools support combination of hashtags (#10 (comment))

@PanierAvide Unfortunately #caresteouvert #DE doesn't filter notes as expected (because it also matches the word "de"), so I think we need a longer hashtag like #caresteouvert_DE or #cro_DE (in addition to #caresteouvert).

Workflow: Update explicit data AND create note for comment

IMO it would help to update the explicit data (opening_hours, delivery, takeway, drivethrough) automatically, even if a comment was given.

Like this, notes with comments that don't require any changes (like repeating what was already provided, or providing a source), can simply be closed.

Note: This would need to be communicated to the OSM community.

Docker

It would be helpful to have a Dockerfile and docker-compose.yml to test locally.

Add hashtag with country code

To filter notes by country more easily, it would be great to always add a hashtag that includes the country code (i.e. independently from the user locale), e.g. #caresteouvert_DE

Transifex integration

It would be good to have a Transifex integration like in the main repository.

Move colon into locale

In contrast to French, English and German don't put a space before the colon (:).

Therefore the colons (with the space in French) should be moved into the locale:
https://github.com/osmontrouge/caresteouvert_backend/blob/2021bdb8e18ebfbf63bb05a80c94ec13034d27b4/src/osm.js#L58-L62

Add `opening_hours:covid19=open` to Notes from "still open" reports that don't contain opening hours

Example: https://www.openstreetmap.org/note/2158011

It would allow to "copy" the key=value pair directly to JOSM.

Geographically smaller changesets

Could you possibly try and update OSM with geographically smaller changesets?

I'm crossposting that here as requested from https://www.openstreetmap.org/changeset/83765288 .

Also, please note that it is important that you read and if appropriate reply to changeset discussion comments. These will be emailed to you and they are also visible at http://resultmaps.neis-one.org/osm-discussion-comments?uid=10944324 . Normally we (OSM's Data Working Group) enforce this by sending the user a message that they have to read before continuing to edit., but in this case as another communications avenue was suggested I'm trying this first.

Andy Townsend (from OSM's Data Working Group)

Handle features deleted on OSM

If a feature is stored in contributions table but deleted meanwhile on OSM, it stays as not being sent to OSM.