HI Gerd, the mods look fine to me. I don't think documenting a config file
in a sample file is a good idea. I think it is much better if all the
documentation is in one place. I also think it make sense to keep the
--nearby-poi-rules option as I expect some users would just want something
like --
Hi Carlos,
please try the attached patch or this binary based on r4483:
http://files.mkgmap.org.uk/download/468/mkgmap.jar
I hope I found all the places that need to be changed. I've only tested with a
map around the point N50 E118.
Gerd
Von: mkgmap-dev
Great new!! Thanks for your support
El 21/4/20 a las 11:19, Gerd Petermann escribió:
Hi Carlos,
yes, I see that the source code handles this format. I finally found
https://dds.cr.usgs.gov/srtm/version2_1/Documentation/MIL-PDF-89020B.pdf
I think "TABLE I. Matrix intervals for DTED Level 0."
Hi Carlos,
yes, I see that the source code handles this format. I finally found
https://dds.cr.usgs.gov/srtm/version2_1/Documentation/MIL-PDF-89020B.pdf
I think "TABLE I. Matrix intervals for DTED Level 0."
shows how to interpret the data. It seems there are a few more variants...
For now I'll
HI Gerd
I don't think conversion is wrong. If input geotiff file is 24MB, output
hgt file is 24 MB, if input tiff is 12MB, output hgt is 12MB
I use this command on Linux:
for i in *.tif ; do gdal_translate -strict -q -eco -of SRTMHGT $i
`basename $i tif`hgt ; done ; rm -f *.hgt.aux.xml
BTW,
Hi Mike,
attached is a modified version of the patch. I've removed some of the changes
in StyledConverter and did some cleanup on the NearbyPoiHandler.
I think you got me wrong regarding the config file. With similar to
--road-name-config=filename I really meant that the config file should be
