... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Other DEM file format ?
#1
Hello,

If I understood well, RC can use DEM data only in files in SRTM/HGT format. So, the resolution nis limited up to 1" arc.

In some country, more precise DEM are available now. For example, in France, french IGN release freely the RGEALTI DEM at 5m since 1st of january, and the one at 1m will be available soon.

Is there a possibility that RC became able to read and use DEM files in other format ? GeoTIFF or BIL/HDR for example ?

Best regards,
Reply
#2
(13.01.2021, 11:00)tybern Wrote: Is there a possibility that RC became able to read and use DEM files in other format ? GeoTIFF or BIL/HDR for example ?

DEM files are raster data, apart from HGT the only raster file format RC can handle is MBTiles, the only possible projection is web mercator. For anything beyond that I would suggest to use a GIS.
Grüße
Hans

Reply
#3
(13.01.2021, 13:27)nordlicht Wrote:
(13.01.2021, 11:00)tybern Wrote: Is there a possibility that RC became able to read and use DEM files in other format ? GeoTIFF or BIL/HDR for example ?

Yes, it's possible to extend the supported formats. The ElevationService interface looks like this:
https://github.com/cpesch/RouteConverter...rvice.java

The HGT files as an inspiration is here:
https://github.com/cpesch/RouteConverter...Files.java

(13.01.2021, 13:27)nordlicht Wrote: DEM files are raster data, apart from HGT the only raster file format RC can handle is MBTiles, the only possible projection is web mercator. For anything beyond that I would suggest to use a GIS.

The API to fulfill is

Double getElevationFor(double longitude, double latitude) throws IOException;

with WGS84 coordinates. If @tybern wants to spend time parsing other files which need to be queried with other algorithms – why not try it?
--
Christian
Reply
#4
(13.01.2021, 13:59)routeconverter Wrote: ...why not try it?

...  and open Pandora's box? Wink
Grüße
Hans

Reply
#5
(13.01.2021, 14:04)nordlicht Wrote: ...  and open Pandora's box? Wink

Don't understand...
Reply
#6
@routeconverter :

I'm not Java programmer, my (hidden) question was : can you add this feature... ?

Best regards
Reply
#7
(13.01.2021, 14:08)tybern Wrote: I'm not Java programmer, my (hidden) question was : can you add this feature... ?

I don't know. If it's a simple as the MBTiles – probably.

But I don't want to search for a specification of the file format and example files. Can you do some research and post links here?
--
Christian
Reply
#8
(13.01.2021, 14:52)routeconverter Wrote: But I don't want to search for a specification of the file format and example files. Can you do some research and post links here?

Yes, it's possible.

I will do as soon as possible.

To be continued... ;-)
Reply
#9
Christian,

There a lot of DEM file formats.
So, I think the better (minus work) will be BIL (band interveaved by line).
The HGT format is a BIL format. In HGT, data are in Integer 16, and stand for square tiles 1°x1°, 3061 data per rows.

For the purpose of better accuracy DEM file, I will suggest BIL/HDR/PRJ format (also called ESRI HDR labelled, or ESRI BILL format), :

The .PRJ file is an ASCII file for projection, like that :

Code:
GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]]


This file is mandatory if you want to accept different type of projection. But if you want, for example, only WGS84, it is enough to say "it is WGS84" (HGT files are WGS84, it's conventional).

The .HDR file is an ASCII file for description of the BIL file, like that :

Code:
BYTEORDER      I
LAYOUT         BIL
NROWS          3601
NCOLS          7201
NBANDS         1
NBITS          32
BANDROWBYTES   28804
TOTALROWBYTES  28804
PIXELTYPE      FLOAT
ULXMAP         -4.0000000001111
ULYMAP         48.0000000001111
XDIM           0.000277777777808638
YDIM           0.000277777777839488

In this example, the PRJ and HDR are files after converting an two HGT files into one BIL format.

The .BIL file is like in .HGT. In HGT, pixel  type is INT16, in BIL, it can be other types, FLOAT 32 in this example.

So, I can give you files for testing, but say to me if you prefer any projection (WGS84, or Lambert 93, or...), or only WGS84.
Do you prefer square tiles, or any rectangular size ? Do you prefer Interger16 data or is it possible to use Float type ? (I think float is better for accuracy).

After your reply, I will generate files for you, for testing.

Best regards,

Bernard
Reply
#10
(13.01.2021, 17:07)tybern Wrote: So, I can give you files for testing, but say to me if you prefer any projection (WGS84, or Lambert 93, or...), or only WGS84.
Do you prefer square tiles, or any rectangular size ? Do you prefer Interger16 data or is it possible to use Float type ? (I think float is better for accuracy).

Hi Bernard,

I'm still in the analysis phase – please consider my naive/stupid questions:
  1. Why do you need a higher accuracy than 1" arc - which is a net of data points with data every 30m and a iinear interpolation between them?
  2. How accurate are the position informations that you have? +/- 15m?
  3. Are you aware that RouteConverter uses full meters to represent elevation?
  4. Are you aware that RouteConverter by default strips exported longitude and latitude to 7 digits (configurable)?
  5. Won't a GIS like @Nordpol suggested be a better choice for your requirements?
Looking forward to your answers
--
Christian
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)