-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zeitreihen print contains data that is not officially released #1628
Comments
the print request json is executing the following query in the database: SELECT gid AS public_meta_20_gid, ST_AsEWKB(the_geom) AS public_meta_20_the_geom, release_year AS public_meta_20_release_year, bgdi_order AS public_meta_20_bgdi_order
FROM public.meta_20
WHERE ST_DWITHIN(the_geom, ST_GeomFromWKB('\x01030000000100000005000000f913957db2d72441aa46afa6e2921141f913957db2d724419e9acbed05931141f33d2321c4d724419e9acbed05931141f33d2321c4d72441aa46afa6e2921141f913957db2d72441aa46afa6e2921141'::bytea, 21781), 0.0) ORDER BY bgdi_order
psql -x -c "SELECT gid AS public_meta_20_gid, ST_AsEWKB(the_geom) AS public_meta_20_the_geom, release_year AS public_meta_20_release_year, bgdi_order AS public_meta_20_bgdi_order
FROM public.meta_20
WHERE ST_DWITHIN(the_geom, ST_GeomFromWKB('\x01030000000100000005000000f913957db2d72441aa46afa6e2921141f913957db2d724419e9acbed05931141f33d2321c4d724419e9acbed05931141f33d2321c4d72441aa46afa6e2921141f913957db2d72441aa46afa6e2921141'::bytea, 21781), 0.0) ORDER BY bgdi_order
" -d zeitreihen_prod
-[ RECORD 1 ]---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
public_meta_20_gid | 18868
public_meta_20_the_geom | \x010600002015550000010000000103000000010000000500000000000000c0eb22410000000080010f4100000000a00e25410000000080010f4100000000a00e254100000000c06e124100000000c0eb224100000000c06e124100000000c0eb22410000000080010f41
public_meta_20_release_year | {2006,2000,1994,1988,1982,1976,1970,1959}
public_meta_20_bgdi_order | 1
-[ RECORD 2 ]---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
public_meta_20_gid | 32371
public_meta_20_the_geom | \x010600002015550000010000000103000000010000000500000000000000c0eb22410000000080010f4100000000a00e25410000000080010f4100000000a00e254100000000c06e124100000000c0eb224100000000c06e124100000000c0eb22410000000080010f41
public_meta_20_release_year | {1934,1916,1912,1909,1906,1904,1899,1893,1889,1884,1879,1875,1869,1866,1863,1859,1849}
public_meta_20_bgdi_order | 2 This table contains lk100 and tk100. |
Can you verify that the correct meta model (lk25) contains the correct data? Seems like we are choosing the wrong model. It's either caused by wrong parameters passed to releases service or wrong calculation of the resolution from those parameters. I'll have a look tomorrow. |
yes the good table would be meta_22 $ psql -x -c "SELECT gid AS public_meta_20_gid, ST_AsEWKB(the_geom) AS public_meta_20_the_geom, release_year AS public_meta_20_release_year, bgdi_order AS public_meta_20_bgdi_order
FROM public.meta_22
WHERE ST_DWITHIN(the_geom, ST_GeomFromWKB('\x01030000000100000005000000f913957db2d72441aa46afa6e2921141f913957db2d724419e9acbed05931141f33d2321c4d724419e9acbed05931141f33d2321c4d72441aa46afa6e2921141f913957db2d72441aa46afa6e2921141'::bytea, 21781), 0.0) ORDER BY bgdi_order
" -d zeitreihen_prod
-[ RECORD 1 ]---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
public_meta_20_gid | 573
public_meta_20_the_geom | \x010600002015550000010000000103000000010000000500000000000000e885244100000000c0f7104100000000a00e254100000000c0f7104100000000a00e25410000000040b3114100000000e88524410000000040b3114100000000e885244100000000c0f71041
public_meta_20_release_year | {2013,2007,2000,1994,1988,1982,1976,1971,1966,1957,1955}
public_meta_20_bgdi_order | 1
-[ RECORD 2 ]---------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
public_meta_20_gid | 5417
public_meta_20_the_geom | \x01060000201555000001000000010300000001000000050000000000000044ca2441000000008055114100000000a00e2541000000008055114100000000a00e25410000000040b311410000000044ca24410000000040b311410000000044ca24410000000080551141
public_meta_20_release_year | {1943,1932,1922,1915,1895,1882}
public_meta_20_bgdi_order | 2
|
Thanks alot for verifying. We ignore the passed scale and try to calculate it based on passed Bbox, center, etc..., which is probably wrong. |
When printing 1:25'000 with https://map.geo.admin.ch/?X=288058.07&Y=682938.66&zoom=7&topic=ech&lang=de&bgLayer=ch.swisstopo.pixelkarte-farbe&layers=ch.swisstopo.zeitreihen&time=2013&layers_timestamp=20131231 and do a multipage, the multipage pdf is containg the last lk25'000 of 2006. But in the application, we have the last lk25'000 of 2013.
The print request json is in [1].
My assumption is that the releases service used ([2] in this case) is delivering the wrong timestamps. In fact, as can be seen by [2], which was triggered by [1], it doesn't contain 2006 but not 2013. It seems like our metadata and the data we should in the application don't match.
@ltclm @daguer Could it be that on the last updates, we forgot to update the meta data? Or what could be wrong?
[1] http://api3.geo.admin.ch/rest/services/ech/MapServer/ch.swisstopo.zeitreihen/releases?imageDisplay=1%2C1%2C96&mapExtent=682969.245278%2C287928.662778%2C682978.064722%2C287937.482222
[2]
The text was updated successfully, but these errors were encountered: