Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Menion

#10171
also 20.000km max distance is not a good argument

I'm trying last weeks to improve GUI (it started with map manager) to bring locus also to basic users with no extra knowledge, so it is argument for me. Also extra settings for this is really not needed, it will only confuse others. So it's one on one now :). Other votes are needed ...
#10172
Hi Franc,
  this is on discussion. Current state is intent, not a bug. Locations from wi-fi/bts/whatever except GPS are usually not very precise. So display of distance should be very confusing in case that your real location is for example one km away. I personally do not see sense in displaying this line when GPS location is missing. Terrible precision, confusing for not experience users ...
#10173
ah sorry but please post it to locus(@)asamm.com , this jabber address is just ... for jabber and do not work for me as email address, thanks :)
#10174
ah don't know this. Thanks Jusc!

OK, I'll try to read some blog posts about it (if exist) and if expected time for new data will take a long, I'll generate maps from these last published data
#10175
yes I know this site, but it's useless for me.

best place is here http://ftp.heanet.ie/mirrors/openstreetmap.org/pbf/ but even here "planet-latest.osm.pbf " file is three weeks old, hmm...
#10176
Hello Peter,
  hmm you're correct, looks like issue ... I'm going to check it ...

EDIT after half an hour: during some updates of whole navigation system, this parameter was completely ignored. Sorry, fixed now. Thanks for report
#10177
ah sorry ... currently biggest problem is that planet dump of OSM data is not actualized since start of April, so I'm looking for another source

EDIT: damn, anybody know about place for download whole PBF world file later then from start of April?
#10178
a promin. Je třeba je vyfiltrovat pomocí filtru. Tzn. zobrazit obrazovku se seznamem bodů a pak tlačítko 9
http://www.locusmap.eu/support/manual/s ... poi-screen
#10179
correct. In February maps were generated in older 0.2 format. Difference is mainly not supported skinning and some details. New maps on Vectormaps4Locus will be in next generating session ... so probably in first half of May
#10180
Hi Jens,
  I already read you email. Sorry but I have no idea how to simply remove some part of map from file. It's a basic SQLite database so If I have same problem, I'll download for example extension to firefox (SQLite manager) and manually delete some lines and rows by executing SQL query.
#10181
jabber.cz, no to ani nevím jak se na takový mail leze.

každopádně nebylo třeba. Tvůj popis bohatě stačil. Ani jsem netušil že lze na gc.com měnit souřadnice a přidávat poznámku. Moc nelovím ale tohle je docela milé. No zpět k problému - díky za report, opraveno. Další verze bude asi iž v pátek, tak pak prosím vyzkoušej a kdyby ještě zlobilo, tak pořešíme
#10182
both maps are "same". If you're comfortable with manual downloading, you can use it. Anyway maps in external site are managed by one user here from forum and are actually little bit outdated. System is simple. When I generate new maps for Locus itself (for in-app shop), I send them also to this user to external site. But not everytime :). Currently there are maps from I think February
#10183
I'm aware of it, don't worry. I don't want to just right now start generating new maps with contours :). "Problem" is that I spend too much time work on locus itself, so I'm not sure if I'll be able to help make this system better. We'll see. Anyway I think that if generating will work correctly in the end, it should be really a massive improvement for tourist usage of MapsForge maps not even in Locus. And because here is so many skilled people like you, I'm sure result will be impressive ;)
#10184
ah found it ...

However, areas where there is no data (voids) are assigned a value of 32768.
this is a problem. On such places aren't altitude data (probably due to really inaccurate values) ... so how to handle it. Cancel complete compute and notify as "altitude data aren't available from SRTM files"? or similar ...
#10185
sorry, I was looking on it just before I published new 2.2.3 and forget to answer. Have to look precisely on data because interpolation in Locus seems to be correct but data I received from file seems to have some problems and still return value (256*256) / 2 ... I'll check it more carefully

also there should be one more problem. In case that data will not be correct and I'll not have available altitude value for some points, how to handle whole track? because I have no system when part of track don't have altitude values and part have ...