organicmaps/organicmaps-tmp

Archived

Fork 1

Better / more frequent map updates #835

New issue

Open

opened 2021-07-10 18:19:57 +00:00 by ghost · 11 comments

ghost commented

2021-07-10 18:19:57 +00:00

(Migrated from github.com)

#851
organicmaps/organicmaps#2317
organicmaps/organicmaps#8672
generate/release maps more frequently

I have noticed that a few contributions are not showing up on a freshly downloaded map and it does on OsmAnd and OSM web. I think it would be better to have options to update the maps unless theres a reason things are missing/not updating as frequently. ---- - [ ] #851 - [ ] https://git.omaps.dev/organicmaps/organicmaps/issues/2317 - [ ] https://git.omaps.dev/organicmaps/organicmaps/issues/8672 - [ ] generate/release maps more frequently

👍 12

biodranik commented

2021-07-10 18:30:14 +00:00

(Migrated from github.com)

There are several reasons why our maps are not updated instantly:

We have a custom map data format optimized for faster rendering and search.
Maps generation process takes ~3 days now.
Updated maps data historically bound to app updates.
Every update now consumes a lot of traffic from our servers.

We plan to:

Separate maps updates from the app updates so that maps can be updated independently.
Support diffs/patches for updates to reduce download size and servers load.

After that, we'll see how we can improve the generation speed.

There are several reasons why our maps are not updated instantly: 1. We have a custom map data format optimized for faster rendering and search. 2. Maps generation process takes ~3 days now. 3. Updated maps data historically bound to app updates. 4. Every update now consumes a lot of traffic from our servers. We plan to: 1. Separate maps updates from the app updates so that maps can be updated independently. 2. Support diffs/patches for updates to reduce download size and servers load. After that, we'll see how we can improve the generation speed.

👍 21 👀 2 ❤️ 5

ghost commented

2021-07-10 18:35:29 +00:00

(Migrated from github.com)

@biodranik Thank you for the quick answer. Should I close the issue?

ghost commented

2021-07-10 20:09:34 +00:00

(Migrated from github.com)

I will go ahead and close the issue for now.

ccptr commented

2021-08-06 05:14:01 +00:00

(Migrated from github.com)

I would keep it open since it still hasn't been solved, and is needed IMO. Closing valid issues makes them harder to find.

snezhniylis commented

2021-09-25 18:16:23 +00:00

(Migrated from github.com)

Related: #851

pggdt commented

2021-10-25 04:28:46 +00:00

(Migrated from github.com)

Or maybe you could release some tools for users to generate maps on the own computers. I think this will save your server load and bandwidth.

👍 1

biodranik commented

2021-10-25 09:28:39 +00:00

(Migrated from github.com)

Tools are already in the repo, everyone can compile and run them. Building maps locally and installing them locally is a time-consuming process.

😆 2

pggdt commented

2021-10-25 10:04:27 +00:00

(Migrated from github.com)

Tools are already in the repo, everyone can compile and run them. Building maps locally and installing them locally is a time-consuming process.

Great work!

> Tools are already in the repo, everyone can compile and run them. Building maps locally and installing them locally is a time-consuming process. Great work!

pastk commented

2022-03-18 17:03:46 +00:00

Owner

Separate maps updates from the app updates so that maps can be updated independently.

This part is being worked on in #404

> Separate maps updates from the app updates so that maps can be updated independently. This part is being worked on in #404

👍 1

pastk commented

2022-03-18 17:18:42 +00:00

Owner

We plan to:

1. Separate maps updates from the app updates so that maps can be updated independently.

2. Support diffs/patches for updates to reduce download size and servers load.

Another idea to consider is to go away from "update all map regions simultaneously at once" to individual independent updates, hence map regions which see more changes could be updated more often.

E.g. update all map regions once a month at least (like it is now).
And issue additional updates for specific map regions when amount of changes in them exceed some threshold. E.g. a rapidly evolving region could be updated up to twice a week.

It could be especially valuable for rapid publishing of update done by Humanitarian OSM Team.

> We plan to: > > 1. Separate maps updates from the app updates so that maps can be updated independently. > > 2. Support diffs/patches for updates to reduce download size and servers load. > Another idea to consider is to go away from "update all map regions simultaneously at once" to individual independent updates, hence map regions which see more changes could be updated more often. E.g. update all map regions once a month at least (like it is now). And issue additional updates for specific map regions when amount of changes in them exceed some threshold. E.g. a rapidly evolving region could be updated up to twice a week. It could be especially valuable for rapid publishing of update done by Humanitarian OSM Team.

👍 1

biodranik commented

2022-03-20 22:46:25 +00:00

(Migrated from github.com)

It's not feasible with the current implementation of the generator.

This repo is archived. You cannot comment on issues.