search

openfoodfacts / openfoodfacts-server

Open Food Facts database, API server and web interface - 🐪🦋 Perl, CSS and JS coders welcome 😊 For helping in Python, see Robotoff or taxonomy-editor
GNU Affero General Public License v3.0
611 stars 357 forks source link

Introduce a fishing zone map #535

Open teolemon opened 7 years ago

teolemon commented 7 years ago

What

Part of

hangy commented 7 years ago

The FAO provides GeoJSON via their OWS webservice. However, even the file without coastlines is >4 MiB. Of course, we can cache that file (ie with nginx) to avoid overloading the webservice, but what do you think about embedding a 4 MiB GeoJSON file for that?

teolemon commented 7 years ago

A government representative talked to me about this kind of issues: http://4.bp.blogspot.com/-KCnjTiFhAPU/UlYRmnMYFoI/AAAAAAAABys/WDqkyb2Z4nc/s1600/FAO+Major+Fishing+Areas+Labels+Food+Zones+Fukushima+Contamination+Map+Pacific+Sea+Currents+Fish+Tuna+www.RadioactiveChat.Blogspot.com.jpg

teolemon commented 7 years ago

We could have a simplified version otherwise ?

teolemon commented 7 years ago

Or do that as a separate map

hangy commented 7 years ago

I think this could be a separate issue. There's no need for a map for this - we could very well invent a label for it and display it with a radiation warning. That doesn't need as much space as a map (still need to find a good place for it and the nutrient diagram) and can be used as a filter.

CloCkWeRX commented 6 years ago

I would be keen to normalize the list - "FAO-71", "FAO No 71", "FAO Area 71" for example all refer to the same thing but are modelled differently.

CloCkWeRX commented 6 years ago

A version of the data, thrown through http://mapshaper.org - <300kb. We could further drop attributes we don't need to cut down the size fao.json.txt

teolemon commented 6 years ago

Normalization is usually done through taxonomies. Here's an old attempt at one