[mkgmap-dev] remove splitter option align-for-dem again or change mkgmap?

[Gerd Petermann]

Hi all,

with current code in mkgmap this option is of no use, as mkgmap rounds the 
dem-dist values (down) to multiples of 16.
(9942 -> 9936 , 3314 ->3312)
This means that points are always interpolated, no matter where the tile 
boundaries are.

So, I see two possibilites:
1) remove the option from splitter (it is not yet documented anyway)
2) change the code in mkgmap to allow using the exact dem-dist values without 
rounding
I think this works fine with MapSource and Basecamp, but maybe some devices 
will not be able to handle that,
as Garmin maps always use the rounded values. 
A possible benefit of the exact values is that we may be able to avoid 
interpolation, at least in some areas of the world.

What do you think?

Gerd



___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Re: [mkgmap-dev] Splitter doc patch

[Gerd Petermann]

Hi Carlos,

thanks, I've applied the changes to the other files as well in r588.

Gerd



Von: mkgmap-dev  im Auftrag von Carlos 
Dávila 
Gesendet: Donnerstag, 25. Januar 2018 23:15
An: Development list for mkgmap
Betreff: [mkgmap-dev] Splitter doc patch

Hi Gerd
Attached is a patch that tries to improve splitter documentation and fix
some typos. Please commit it if you find it correct.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] Splitter doc patch

[Carlos Dávila]

Hi Gerd
Attached is a patch that tries to improve splitter documentation and fix 
some typos. Please commit it if you find it correct.
Index: doc/splitter.txt
===
--- doc/splitter.txt	(revisión: 585)
+++ doc/splitter.txt	(copia de trabajo)
@@ -21,12 +21,12 @@
 area. A few options allow configuring how much memory you need.  With the
 default parameters, you need about 4-5 bytes for every node and way. This
 doesn't sound a lot but there are about 1700 million nodes in the whole planet
-file and so you cannot process the whole planet in one pass file on a 32 bit
-machine using this utility as the maximum java heap space is 2G. It is
+file and so you cannot process the whole planet in one pass on a 32 bit
+machine using this utility, as the maximum java heap space is 2G. It is
 possible with 64 bit java and about 7GB of heap or with multiple passes.
 
 The Europe extract from Cloudmade or Geofabrik can be processed within the 2G
-limit if you have sufficient memory. With the default options europe is split
+limit if you have sufficient memory. With the default options Europe is split
 into about 750 tiles. The Europe extract is about half of the size of the
 complete planet file.
 
@@ -50,21 +50,20 @@
 There are also other files produced:
 
 The ''template.args'' file is a file that can be used with the -c option of
-mkgmap that will compile all the files. You can use it as is or you can copy
-it and edit it to include your own options. For example instead of each
+mkgmap that will compile all the files. You can use it as is or you can 
+edit it to include your own options. For example instead of each
 description being "OSM Map" it could be "NW Scotland" as appropriate.
 
 The ''areas.list'' file is the list of bounding boxes that were calculated. If
-you want you can use this on a subsequent call the the splitter using the
+you want, you can use this on subsequent calls of splitter using the
 --split-file option to use exactly the same areas as last time. This might be
 useful if you produce a map regularly and want to keep the tile areas the same
 from month to month. It is also useful to avoid the time it takes to
 regenerate the file each time (currently about a third of the overall time
 taken to perform the split). Of course if the map grows enough that one of the
-tiles overflows you will have to re-calculate the areas again.
+tiles overflows, you will have to re-calculate the areas again.
 
 The ''areas.poly'' file contains the bounding polygon of the calculated areas.
-See option --polygon-file how this can be used.
 
 The ''densities-out.txt'' file is written when no split-file is given and
 contains debugging information only. 
@@ -167,14 +166,14 @@
 ;--polygon-file
 :  The name of a file containing a bounding polygon in the
 [http://wiki.openstreetmap.org/wiki/Osmosis/Polygon_Filter_File_Format osmosis polygon file format].
-Splitter uses this fie when calculating the areas. It first calculates a grid
+Splitter uses this file when calculating the areas. It first calculates a grid
 using the given --resolution. The input file is read and for each node, a
 counter is increased for the related grid area. If the input file contains a
 bounding box, this is applied to the grid so that nodes outside of the
 bounding box are ignored. Next, if specified, the bounding polygon is used to
-zero those grid elements outside of the bounding polygon area. If the polygon
-area(s) describe(s) a rectilinear area with no more than 40 vertices, splitter
-will try to create output files that fit exactly into the area, otherwise it
+zero those grid elements outside of the bounding polygon area. If the polygon-file
+describes one or more rectilinear areas with no more than 40 vertices, splitter
+will try to create output files that fit exactly into each area, otherwise it
 will approximate the polygon area with rectangles. 
 
 ;--precomp-sea
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] WG: How to handle missing hgt files or files with voids?

[Gerd Petermann]

Hi all,

replied to David instead of the list...
See below

Gerd


Von: Gerd Petermann 
Gesendet: Donnerstag, 25. Januar 2018 18:08
An: Pazapas
Betreff: AW: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi all,

see http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4089
and
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4090

@David: You are free to use any source, the program will always try to read hgt 
data.
This is only about the message that is produced when a hgt file is not found.
With 4090 you will see a list of files that were not found although we know 
that hgt info exists.

Hope that makes it clearer now?

Gerd


Von: Pazapas 
Gesendet: Donnerstag, 25. Januar 2018 17:38
An: Gerd Petermann
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hello,
Why a list of missing hgt is needed ? I would prefer that mkgmap adds itself 
avirtual void tile and writes a warning in console or output a report of the 
compilation in a text file. We then are free to use any sourc of custom  hgt 
files.

Again, chapeau bas for all your work,
David



Pazapas
> Le 25 janv. 2018 à 13:11, Gerd Petermann  a 
> écrit :
>
> Hi Nick,
>
> I think it is not a matter of speed, the file is only read once.
> I think I'll keep the human readable format, the size of mkgmap.jar probably 
> doesn't
> matter much.
>
> Reg. --dem-interpolation see
> http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4087
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von 
> osm@pinns 
> Gesendet: Donnerstag, 25. Januar 2018 13:03
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
>
> Hi Gerd
>
>
> A binary file sounds very 'Garminesque' and if its a matter of speed then I 
> would prefer such a format -
>
> btw  has the --dem-interpolation option been implemented yet ?
>
> Nick
>
> On 25/01/2018 11:59, thesurve...@wolke7.net 
> wrote:
> Hi Gerd,
>
> first many thanks for your work on mkgmap.
>
> for the list of available hgt files: I prefer a human readable format
>
> Regards,
> Gert
>
>
>
> Gesendet: Donnerstag, 25. Januar 2018 um 12:40 Uhr
> Von: "Gerd Petermann" 
> 
> An: "Development list for mkgmap" 
> 
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
> Hi all,
>
> I've played with the list of available hgt files created by Henning.
> I've coded a reader for the list so that mkgmap can
> check if a missing hgt file should exist or if it covers ocean.
> The idea is to print a warning if a file was not found when it should be.
> The check is fast, but the list is long, so I wonder
> if I should store it "as is" in the mkgmap binary like we do with 
> LocatorConfig.xml
> or if I should use another format.
> The most obvious for me would be a binary file containing 180*360 bits, a 1 
> bit for every
> file that should exist.
>
> What do you think?
>
> Gerd
>
>
> 
> Von: mkgmap-dev 
> 
>  im Auftrag von Gerd Petermann 
> 
> Gesendet: Montag, 15. Januar 2018 14:25
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
>
> Hi Henning,
>
> I'll see if I can use srtm.zip.
> I think voids are interesting. When I started coding DEM support I searched 
> my PC for *.hgt files and found them in several places.
> Later I found out that some of those files have voids and that better data 
> exists (assuming that files without voids have fewer errors)
> So, I think it would be good to have a list of those files that have voids.
>
> I'll see what is needed for this.
>
> Gerd
>
> 
> Von: mkgmap-dev 
> 
>  im Auftrag von Henning Scholland 
> 
> Gesendet: Montag, 15. Januar 2018 12:21:09
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
>
> This would be the list of all hgt-files available on viewfinder.
>
> In each zip-file of viewfinder there are 6° in E-W direction and 3° in
> N-S. The scheme of naming is also simple. That list I also attached.
>
> In general I think it's better to just output a list, which
> hgt-files/viefinder-tiles are missing than writing a downloader. I mean
> in total it's 13GB of data. If you need to download it manually, you are
> more aware of what you are doing and not just download them all.
>
> Regarding voids: I think if there is a possibility the user can fix the
> hgt file, A list can be helpful. Otherwise I don't know

Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

[Henning Scholland]

Hi Gerd,

I think such a binary map should be efficient. Maybe the human readable
list can be delivered in the zip-file of mkgmap or stored somewhere else.

Henning

On 25.01.2018 19:40, Gerd Petermann wrote:
> Hi all,
>
> I've played with the list of available hgt files created by Henning.
> I've coded a reader for the list so that mkgmap can
> check if a missing hgt file should exist or if it covers ocean.
> The idea is to print a warning if a file was not found when it should be.
> The check is fast, but the list is long, so I wonder
> if I should store it "as is" in the mkgmap binary like we do with 
> LocatorConfig.xml
> or if I should use another format.
> The most obvious for me would be a binary file containing 180*360 bits, a 1 
> bit for every
> file that should exist.
>
> What do you think?
>
> Gerd
>
>
> 
> Von: mkgmap-dev  im Auftrag von Gerd 
> Petermann 
> Gesendet: Montag, 15. Januar 2018 14:25
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files  with  
>   voids?
>
> Hi Henning,
>
> I'll see if I can use srtm.zip.
> I think voids are interesting. When I started coding DEM support I searched 
> my PC for *.hgt files and found them in several places.
> Later I found out that some of those files have voids and that better data 
> exists (assuming that files without voids have fewer errors)
> So, I think it would be good to have a list of those files that have voids.
>
> I'll see what is needed for this.
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von 
> Henning Scholland 
> Gesendet: Montag, 15. Januar 2018 12:21:09
> An: mkgmap-dev@lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
>
> This would be the list of all hgt-files available on viewfinder.
>
> In each zip-file of viewfinder there are 6° in E-W direction and 3° in
> N-S. The scheme of naming is also simple. That list I also attached.
>
> In general I think it's better to just output a list, which
> hgt-files/viefinder-tiles are missing than writing a downloader. I mean
> in total it's 13GB of data. If you need to download it manually, you are
> more aware of what you are doing and not just download them all.
>
> Regarding voids: I think if there is a possibility the user can fix the
> hgt file, A list can be helpful. Otherwise I don't know if a list would
> be helpful. Only use case I see is to ask the user to use better data.
> But then we need a list, which source is best in which area. And finally
> all the different sources need to match each other. Otherwise it will
> lead to a hard border between 2 sources. I think this will be much to
> complicated...
>
> Maybe for advanced users there can be a Warning message, hgt-file
> N00E100.hgt contains 3 voids. So user can compare different sources
> manually.
>
> Henning
>
> On 15.01.2018 16:55, Gerd Petermann wrote:
>> Hi Henning,
>>
>> checking data is not that easy, but I'll think about that option.
>>
>> I'd like to add a short howto that describes ways to get good hgt data, but 
>> I don't know any method for Windows users.
>> phyghtmap is good, but installation on Win is complex and doc for that looks 
>> out-aged.
>> Srtm2Osm seems out-dated, as well as Groundtruth.
>>
>> So, up to now I try to guess what areas I have to download from viewfinder.
>> Any hints ?
>>
>> Gerd
>>
>> 
>> Von: mkgmap-dev  im Auftrag von 
>> Henning Scholland 
>> Gesendet: Montag, 15. Januar 2018 09:05:24
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with 
>> voids?
>>
>> Hi Gerd,
>>
>> regarding 1) I can create a list of existing tiles of Viewfinder (which 
>> covers all land area so far I see). But it will be a long list. I remember 
>> it's about 25000 files in total. So maybe it's easier to create a polygon or 
>> at least take the list and let software create the polygon. An easier way 
>> can be to check if data is available. No data might be sea. Of course it's 
>> not 100% sure, as there are deserts and ferries.
>>
>> Another idea I had during the weekend was to output a osm-file with missing 
>> areas. So then user can check. But I came to conclusion, that it's easily 
>> visible in the map later. So I'm not sure it's useful at all.
>>
>> Henning
>>
>> On 2018-01-15 15:45, Gerd Petermann wrote:
>>
>> Hi all,
>>
>> 1) The current code (only) writes a log message with severity WARNING for a 
>> missing hgt file:
>> "file xxx.hgt not found. Is expected to cover sea."
>> I wonder if we can create a list of files that can exist or maybe a polygon 
>> that can be tested so that
>> tiles which are knwon to cover land are reported as errors.
>> When you look at 
>> http://viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org3.htm
>> you can see that such a polygon would be quite complex.
>> Did anybody already t

Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

[osm@pinns]

Hi Gerd

Thanks , for that , downloaded 4088 by mistake.


Nick


On 25/01/2018 12:11, Gerd Petermann wrote:

Hi Nick,

I think it is not a matter of speed, the file is only read once.
I think I'll keep the human readable format, the size of mkgmap.jar probably 
doesn't
matter much.

Reg. --dem-interpolation see
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4087

Gerd


Von: mkgmap-dev  im Auftrag von osm@pinns 

Gesendet: Donnerstag, 25. Januar 2018 13:03
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi Gerd


A binary file sounds very 'Garminesque' and if its a matter of speed then I 
would prefer such a format -

btw  has the --dem-interpolation option been implemented yet ?

Nick

On 25/01/2018 11:59, thesurve...@wolke7.net 
wrote:
Hi Gerd,

first many thanks for your work on mkgmap.

for the list of available hgt files: I prefer a human readable format

Regards,
Gert



Gesendet: Donnerstag, 25. Januar 2018 um 12:40 Uhr
Von: "Gerd Petermann" 

An: "Development list for mkgmap" 

Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
Hi all,

I've played with the list of available hgt files created by Henning.
I've coded a reader for the list so that mkgmap can
check if a missing hgt file should exist or if it covers ocean.
The idea is to print a warning if a file was not found when it should be.
The check is fast, but the list is long, so I wonder
if I should store it "as is" in the mkgmap binary like we do with 
LocatorConfig.xml
or if I should use another format.
The most obvious for me would be a binary file containing 180*360 bits, a 1 bit 
for every
file that should exist.

What do you think?

Gerd



Von: mkgmap-dev 
 im 
Auftrag von Gerd Petermann 

Gesendet: Montag, 15. Januar 2018 14:25
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi Henning,

I'll see if I can use srtm.zip.
I think voids are interesting. When I started coding DEM support I searched my 
PC for *.hgt files and found them in several places.
Later I found out that some of those files have voids and that better data 
exists (assuming that files without voids have fewer errors)
So, I think it would be good to have a list of those files that have voids.

I'll see what is needed for this.

Gerd


Von: mkgmap-dev 
 im 
Auftrag von Henning Scholland 
Gesendet: Montag, 15. Januar 2018 12:21:09
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

This would be the list of all hgt-files available on viewfinder.

In each zip-file of viewfinder there are 6° in E-W direction and 3° in
N-S. The scheme of naming is also simple. That list I also attached.

In general I think it's better to just output a list, which
hgt-files/viefinder-tiles are missing than writing a downloader. I mean
in total it's 13GB of data. If you need to download it manually, you are
more aware of what you are doing and not just download them all.

Regarding voids: I think if there is a possibility the user can fix the
hgt file, A list can be helpful. Otherwise I don't know if a list would
be helpful. Only use case I see is to ask the user to use better data.
But then we need a list, which source is best in which area. And finally
all the different sources need to match each other. Otherwise it will
lead to a hard border between 2 sources. I think this will be much to
complicated...

Maybe for advanced users there can be a Warning message, hgt-file
N00E100.hgt contains 3 voids. So user can compare different sources
manually.

Henning

On 15.01.2018 16:55, Gerd Petermann wrote:

Hi Henning,

checking data is not that easy, but I'll think about that option.

I'd like to add a short howto that describes ways to get good hgt data, but I 
don't know any method for Windows users.
phyghtmap is good, but installation on Win is complex and doc for that looks 
out-aged.
Srtm2Osm seems out-dated, as well as Groundtruth.

So, up to now I try to guess what areas I have to download from viewfinder.
Any hints ?

Gerd


Von: mkgmap-dev 
 im 
Auftrag von Henning Scholland 
Gesendet: Montag, 15. Januar 2018 09:05:24
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi Gerd,

regarding 1) I can create a list of existing tiles of Viewfinder (which covers 
all

Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

[Gerd Petermann]

Hi Nick,

I think it is not a matter of speed, the file is only read once.
I think I'll keep the human readable format, the size of mkgmap.jar probably 
doesn't
matter much.

Reg. --dem-interpolation see
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4087

Gerd


Von: mkgmap-dev  im Auftrag von 
osm@pinns 
Gesendet: Donnerstag, 25. Januar 2018 13:03
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi Gerd


A binary file sounds very 'Garminesque' and if its a matter of speed then I 
would prefer such a format -

btw  has the --dem-interpolation option been implemented yet ?

Nick

On 25/01/2018 11:59, thesurve...@wolke7.net 
wrote:
Hi Gerd,

first many thanks for your work on mkgmap.

for the list of available hgt files: I prefer a human readable format

Regards,
Gert



Gesendet: Donnerstag, 25. Januar 2018 um 12:40 Uhr
Von: "Gerd Petermann" 

An: "Development list for mkgmap" 

Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
Hi all,

I've played with the list of available hgt files created by Henning.
I've coded a reader for the list so that mkgmap can
check if a missing hgt file should exist or if it covers ocean.
The idea is to print a warning if a file was not found when it should be.
The check is fast, but the list is long, so I wonder
if I should store it "as is" in the mkgmap binary like we do with 
LocatorConfig.xml
or if I should use another format.
The most obvious for me would be a binary file containing 180*360 bits, a 1 bit 
for every
file that should exist.

What do you think?

Gerd



Von: mkgmap-dev 

 im Auftrag von Gerd Petermann 

Gesendet: Montag, 15. Januar 2018 14:25
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi Henning,

I'll see if I can use srtm.zip.
I think voids are interesting. When I started coding DEM support I searched my 
PC for *.hgt files and found them in several places.
Later I found out that some of those files have voids and that better data 
exists (assuming that files without voids have fewer errors)
So, I think it would be good to have a list of those files that have voids.

I'll see what is needed for this.

Gerd


Von: mkgmap-dev 

 im Auftrag von Henning Scholland 

Gesendet: Montag, 15. Januar 2018 12:21:09
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

This would be the list of all hgt-files available on viewfinder.

In each zip-file of viewfinder there are 6° in E-W direction and 3° in
N-S. The scheme of naming is also simple. That list I also attached.

In general I think it's better to just output a list, which
hgt-files/viefinder-tiles are missing than writing a downloader. I mean
in total it's 13GB of data. If you need to download it manually, you are
more aware of what you are doing and not just download them all.

Regarding voids: I think if there is a possibility the user can fix the
hgt file, A list can be helpful. Otherwise I don't know if a list would
be helpful. Only use case I see is to ask the user to use better data.
But then we need a list, which source is best in which area. And finally
all the different sources need to match each other. Otherwise it will
lead to a hard border between 2 sources. I think this will be much to
complicated...

Maybe for advanced users there can be a Warning message, hgt-file
N00E100.hgt contains 3 voids. So user can compare different sources
manually.

Henning

On 15.01.2018 16:55, Gerd Petermann wrote:
> Hi Henning,
>
> checking data is not that easy, but I'll think about that option.
>
> I'd like to add a short howto that describes ways to get good hgt data, but I 
> don't know any method for Windows users.
> phyghtmap is good, but installation on Win is complex and doc for that looks 
> out-aged.
> Srtm2Osm seems out-dated, as well as Groundtruth.
>
> So, up to now I try to guess what areas I have to download from viewfinder.
> Any hints ?
>
> Gerd
>
> 
> Von: mkgmap-dev 
> 
>  im Auftrag von Henning Scholland 
> 
> Gesendet: Montag, 15. Januar 2018 09:05:24
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
>
> Hi Gerd,
>
> regarding 1) I can create a list of existing tiles of Viewfinder (which 
> covers all land area so far I see). But it will be a long list. I remem

Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

[osm@pinns]

Hi Gerd


A binary file sounds very 'Garminesque' and if its a matter of speed 
then I would prefer such a format -


btw  has the --dem-interpolation option been implemented yet ?

Nick


On 25/01/2018 11:59, thesurve...@wolke7.net wrote:

Hi Gerd,
first many thanks for your work on mkgmap.
for the list of available hgt files: I prefer a human readable format
Regards,
Gert
*Gesendet:* Donnerstag, 25. Januar 2018 um 12:40 Uhr
*Von:* "Gerd Petermann" 
*An:* "Development list for mkgmap" 
*Betreff:* Re: [mkgmap-dev] How to handle missing hgt files or files 
with voids?

Hi all,

I've played with the list of available hgt files created by Henning.
I've coded a reader for the list so that mkgmap can
check if a missing hgt file should exist or if it covers ocean.
The idea is to print a warning if a file was not found when it should be.
The check is fast, but the list is long, so I wonder
if I should store it "as is" in the mkgmap binary like we do with 
LocatorConfig.xml

or if I should use another format.
The most obvious for me would be a binary file containing 180*360 
bits, a 1 bit for every

file that should exist.

What do you think?

Gerd



Von: mkgmap-dev  im Auftrag 
von Gerd Petermann 

Gesendet: Montag, 15. Januar 2018 14:25
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files 
with voids?


Hi Henning,

I'll see if I can use srtm.zip.
I think voids are interesting. When I started coding DEM support I 
searched my PC for *.hgt files and found them in several places.
Later I found out that some of those files have voids and that better 
data exists (assuming that files without voids have fewer errors)
So, I think it would be good to have a list of those files that have 
voids.


I'll see what is needed for this.

Gerd


Von: mkgmap-dev  im Auftrag 
von Henning Scholland 

Gesendet: Montag, 15. Januar 2018 12:21:09
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files 
with voids?


This would be the list of all hgt-files available on viewfinder.

In each zip-file of viewfinder there are 6° in E-W direction and 3° in
N-S. The scheme of naming is also simple. That list I also attached.

In general I think it's better to just output a list, which
hgt-files/viefinder-tiles are missing than writing a downloader. I mean
in total it's 13GB of data. If you need to download it manually, you are
more aware of what you are doing and not just download them all.

Regarding voids: I think if there is a possibility the user can fix the
hgt file, A list can be helpful. Otherwise I don't know if a list would
be helpful. Only use case I see is to ask the user to use better data.
But then we need a list, which source is best in which area. And finally
all the different sources need to match each other. Otherwise it will
lead to a hard border between 2 sources. I think this will be much to
complicated...

Maybe for advanced users there can be a Warning message, hgt-file
N00E100.hgt contains 3 voids. So user can compare different sources
manually.

Henning

On 15.01.2018 16:55, Gerd Petermann wrote:
> Hi Henning,
>
> checking data is not that easy, but I'll think about that option.
>
> I'd like to add a short howto that describes ways to get good hgt 
data, but I don't know any method for Windows users.
> phyghtmap is good, but installation on Win is complex and doc for 
that looks out-aged.

> Srtm2Osm seems out-dated, as well as Groundtruth.
>
> So, up to now I try to guess what areas I have to download from 
viewfinder.

> Any hints ?
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag 
von Henning Scholland 

> Gesendet: Montag, 15. Januar 2018 09:05:24
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files 
with voids?

>
> Hi Gerd,
>
> regarding 1) I can create a list of existing tiles of Viewfinder 
(which covers all land area so far I see). But it will be a long list. 
I remember it's about 25000 files in total. So maybe it's easier to 
create a polygon or at least take the list and let software create the 
polygon. An easier way can be to check if data is available. No data 
might be sea. Of course it's not 100% sure, as there are deserts and 
ferries.

>
> Another idea I had during the weekend was to output a osm-file with 
missing areas. So then user can check. But I came to conclusion, that 
it's easily visible in the map later. So I'm not sure it's useful at all.

>
> Henning
>
> On 2018-01-15 15:45, Gerd Petermann wrote:
>
> Hi all,
>
> 1) The current code (only) writes a log message with severity 
WARNING for a missing hgt file:

> "file xxx.hgt not found. Is expected to cover sea."
> I wonder if we can create a list of files that can exist or maybe a 
polygon that can be tested so that

> tiles which are knwon to cover land are reported as errors.
> When 

Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

[thesurveyor]

Hi Gerd,

 

first many thanks for your work on mkgmap.

 

for the list of available hgt files: I prefer a human readable format

 

Regards,

Gert 

 

 

 

Gesendet: Donnerstag, 25. Januar 2018 um 12:40 Uhr
Von: "Gerd Petermann" 
An: "Development list for mkgmap" 
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi all,

I've played with the list of available hgt files created by Henning.
I've coded a reader for the list so that mkgmap can
check if a missing hgt file should exist or if it covers ocean.
The idea is to print a warning if a file was not found when it should be.
The check is fast, but the list is long, so I wonder
if I should store it "as is" in the mkgmap binary like we do with LocatorConfig.xml
or if I should use another format.
The most obvious for me would be a binary file containing 180*360 bits, a 1 bit for every
file that should exist.

What do you think?

Gerd



Von: mkgmap-dev  im Auftrag von Gerd Petermann 
Gesendet: Montag, 15. Januar 2018 14:25
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

Hi Henning,

I'll see if I can use srtm.zip.
I think voids are interesting. When I started coding DEM support I searched my PC for *.hgt files and found them in several places.
Later I found out that some of those files have voids and that better data exists (assuming that files without voids have fewer errors)
So, I think it would be good to have a list of those files that have voids.

I'll see what is needed for this.

Gerd


Von: mkgmap-dev  im Auftrag von Henning Scholland 
Gesendet: Montag, 15. Januar 2018 12:21:09
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

This would be the list of all hgt-files available on viewfinder.

In each zip-file of viewfinder there are 6° in E-W direction and 3° in
N-S. The scheme of naming is also simple. That list I also attached.

In general I think it's better to just output a list, which
hgt-files/viefinder-tiles are missing than writing a downloader. I mean
in total it's 13GB of data. If you need to download it manually, you are
more aware of what you are doing and not just download them all.

Regarding voids: I think if there is a possibility the user can fix the
hgt file, A list can be helpful. Otherwise I don't know if a list would
be helpful. Only use case I see is to ask the user to use better data.
But then we need a list, which source is best in which area. And finally
all the different sources need to match each other. Otherwise it will
lead to a hard border between 2 sources. I think this will be much to
complicated...

Maybe for advanced users there can be a Warning message, hgt-file
N00E100.hgt contains 3 voids. So user can compare different sources
manually.

Henning

On 15.01.2018 16:55, Gerd Petermann wrote:
> Hi Henning,
>
> checking data is not that easy, but I'll think about that option.
>
> I'd like to add a short howto that describes ways to get good hgt data, but I don't know any method for Windows users.
> phyghtmap is good, but installation on Win is complex and doc for that looks out-aged.
> Srtm2Osm seems out-dated, as well as Groundtruth.
>
> So, up to now I try to guess what areas I have to download from viewfinder.
> Any hints ?
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von Henning Scholland 
> Gesendet: Montag, 15. Januar 2018 09:05:24
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
>
> Hi Gerd,
>
> regarding 1) I can create a list of existing tiles of Viewfinder (which covers all land area so far I see). But it will be a long list. I remember it's about 25000 files in total. So maybe it's easier to create a polygon or at least take the list and let software create the polygon. An easier way can be to check if data is available. No data might be sea. Of course it's not 100% sure, as there are deserts and ferries.
>
> Another idea I had during the weekend was to output a osm-file with missing areas. So then user can check. But I came to conclusion, that it's easily visible in the map later. So I'm not sure it's useful at all.
>
> Henning
>
> On 2018-01-15 15:45, Gerd Petermann wrote:
>
> Hi all,
>
> 1) The current code (only) writes a log message with severity WARNING for a missing hgt file:
> "file xxx.hgt not found. Is expected to cover sea."
> I wonder if we can create a list of files that can exist or maybe a polygon that can be tested so that
> tiles which are knwon to cover land are reported as errors.
> When you look at http://viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org3.htm
> you can see that such a polygon would be quite complex.
> Did anybody already try to define such a polygon or list of files that would cover only ocean?
>
> 2) Should mkgmap 

Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

[Gerd Petermann]

Hi all,

I've played with the list of available hgt files created by Henning.
I've coded a reader for the list so that mkgmap can
check if a missing hgt file should exist or if it covers ocean.
The idea is to print a warning if a file was not found when it should be.
The check is fast, but the list is long, so I wonder
if I should store it "as is" in the mkgmap binary like we do with 
LocatorConfig.xml
or if I should use another format.
The most obvious for me would be a binary file containing 180*360 bits, a 1 bit 
for every
file that should exist.

What do you think?

Gerd



Von: mkgmap-dev  im Auftrag von Gerd 
Petermann 
Gesendet: Montag, 15. Januar 2018 14:25
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files  with
voids?

Hi Henning,

I'll see if I can use srtm.zip.
I think voids are interesting. When I started coding DEM support I searched my 
PC for *.hgt files and found them in several places.
Later I found out that some of those files have voids and that better data 
exists (assuming that files without voids have fewer errors)
So, I think it would be good to have a list of those files that have voids.

I'll see what is needed for this.

Gerd


Von: mkgmap-dev  im Auftrag von Henning 
Scholland 
Gesendet: Montag, 15. Januar 2018 12:21:09
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?

This would be the list of all hgt-files available on viewfinder.

In each zip-file of viewfinder there are 6° in E-W direction and 3° in
N-S. The scheme of naming is also simple. That list I also attached.

In general I think it's better to just output a list, which
hgt-files/viefinder-tiles are missing than writing a downloader. I mean
in total it's 13GB of data. If you need to download it manually, you are
more aware of what you are doing and not just download them all.

Regarding voids: I think if there is a possibility the user can fix the
hgt file, A list can be helpful. Otherwise I don't know if a list would
be helpful. Only use case I see is to ask the user to use better data.
But then we need a list, which source is best in which area. And finally
all the different sources need to match each other. Otherwise it will
lead to a hard border between 2 sources. I think this will be much to
complicated...

Maybe for advanced users there can be a Warning message, hgt-file
N00E100.hgt contains 3 voids. So user can compare different sources
manually.

Henning

On 15.01.2018 16:55, Gerd Petermann wrote:
> Hi Henning,
>
> checking data is not that easy, but I'll think about that option.
>
> I'd like to add a short howto that describes ways to get good hgt data, but I 
> don't know any method for Windows users.
> phyghtmap is good, but installation on Win is complex and doc for that looks 
> out-aged.
> Srtm2Osm seems out-dated, as well as Groundtruth.
>
> So, up to now I try to guess what areas I have to download from viewfinder.
> Any hints ?
>
> Gerd
>
> 
> Von: mkgmap-dev  im Auftrag von 
> Henning Scholland 
> Gesendet: Montag, 15. Januar 2018 09:05:24
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] How to handle missing hgt files or files with voids?
>
> Hi Gerd,
>
> regarding 1) I can create a list of existing tiles of Viewfinder (which 
> covers all land area so far I see). But it will be a long list. I remember 
> it's about 25000 files in total. So maybe it's easier to create a polygon or 
> at least take the list and let software create the polygon. An easier way can 
> be to check if data is available. No data might be sea. Of course it's not 
> 100% sure, as there are deserts and ferries.
>
> Another idea I had during the weekend was to output a osm-file with missing 
> areas. So then user can check. But I came to conclusion, that it's easily 
> visible in the map later. So I'm not sure it's useful at all.
>
> Henning
>
> On 2018-01-15 15:45, Gerd Petermann wrote:
>
> Hi all,
>
> 1) The current code (only) writes a log message with severity WARNING for a 
> missing hgt file:
> "file xxx.hgt not found. Is expected to cover sea."
> I wonder if we can create a list of files that can exist or maybe a polygon 
> that can be tested so that
> tiles which are knwon to cover land are reported as errors.
> When you look at 
> http://viewfinderpanoramas.org/Coverage%20map%20viewfinderpanoramas_org3.htm
> you can see that such a polygon would be quite complex.
> Did anybody already try to define such a polygon or list of files that would 
> cover only ocean?
>
> 2) Should mkgmap print a warning when voids in the hgt file(s) have an 
> influence on the DEM data?
> I think yes, but it is a bit more complex to measure the real effect.
> Reason: We read the 4 hgt values next to the wanted DEM point and use 
> interpolation to calculate the height
> that is stored in the 

[mkgmap-dev] Commit r4088: Fix problems in LocatorConfig.xml

[svn commit]

Version mkgmap-r4088 was committed by gerd on Thu, 25 Jan 2018

Fix problems in LocatorConfig.xml
- Tonga is a drive-on-left country
- Pitcairn is one island, the country is called "Pitcairn Islands"

LocatorConfig.patch by Carlos Davida

http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4088
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev