Content Provider + Service

[lurtz]

was noch gemacht werden muss: der content provider muss fertig gestellt werden und der service, dann muessten wir soweit sein, dass der YaohaMapListener den OsmNodeRetrieverService mit ner query anstossen kann, der holt dann im Hintergrund Daten vom overpass-server, parst sie, packt sie in die datenbank und sagt dem YaohaMapListener mittels callback bescheid, dass er fertig ist. Der YaohaMapListener kann dann die Daten in die View malen. Dafuer muessen wir uns noch mal mit der Overlay-API auseinandersetzen

[hellfyre]

Partly done, partly wontfix. We'll do without a content provider for now and the service has been downgraded to an asynchronous task. That and the listener are done however, therefore closing this issue.

[lurtz]

I ran into reliability problems, while testing yaoha: -It crashes sometimes, which I think is caused by concurrent access to our HashMap containing the data -The data we get from OSM is not complete many times

We can cover this by saving data from OSM permanently and updating it, while moving the map. This will have no benefit to our netload, but this doesn't matter because the OSM tiles alone are big enough.

[lurtz]

Why don't you reuse the primary key from OSM? When using our own primary key we might get duplicate entries in our database.

[lurtz]

We don't need a content provider. This is only necessary if we want to share our OSM data with other applications. I would create a SQLite database and put the data into it. Another option would be to write our data into a file. But rewriting the entire file for each update is not good and we have to keep track of duplicates ourself.

[hellfyre]

Um, ok. I'd say SQlite is by far the best solution. As for the primary key: I quickly rigged some code together and didn't spend much time thinking 'bout the details.

[lurtz]

SQLite database is done