Categories
github activity
- jachym commented on issue openmaptiles/openmaptiles#1699jachym commented on openmaptiles/openmaptiles#1699 · December 20, 2024 12:46 jachym commented Dec 20, 2024 Acknowledging attribution is quite common among open licenses. CC-BY 4.0 is quite established open license, nothing exotic. MapTiler is the founder…
- jachym commented on issue domlysz/BlenderGIS#934jachym commented on domlysz/BlenderGIS#934 · December 4, 2024 07:07 jachym commented Dec 4, 2024 Having the same error Seems to be an issue of Python 3.13 - imghdr was removed from Python 3.13 https://docs.python.org/3/library/imghdr.html
- jachym opened an issue in alicevision/Meshroomjachym opened an issue in alicevision/Meshroom · November 30, 2024 15:52 [bug] Precompiled Meshroom can not be downloaded #2611 The link from the Releases https://github.com/alicevision/Meshroom/releases pointing to Linux precompiled libraries https://www.fosshub.com/Meshroo…
- jachym opened an issue in thingbomb/flowtidejachym opened an issue in thingbomb/flowtide · November 26, 2024 11:35 Enable flowtide for new windows #10 New windows do not seem to be supported. If there is a chance for some special URL, that would do the job
- jachym forked jachym/valhalla-just_gtfs from valhalla/just_gtfsjachym forked jachym/valhalla-just_gtfs from valhalla/just_gtfs · November 13, 2024 12:05 valhalla/just_gtfs C++17 header-only library for reading and writing GTFS 🌍 Updated Jun 29, 2023
- jachym commented on issue openmaptiles/openmaptiles#1699
Tags
Add new tag Code Sprint development ESRI foss4g geodatahackaton geojson GIS GIS Novinky github GPS GRASS HSLayers INSPIRE Kolo MapServer OGC opendata OpenLayers Open Source OpenStreetMap OSGeo OSM OWS Pes Proxy4OWS Python PyWPS QGIS rakovina varlete REST RUIAN Sport TopoJSON Ubuntu WFS wikipedia WMS WPS školeníArchives
- March 2018
- December 2015
- June 2014
- April 2014
- December 2013
- August 2013
- June 2013
- May 2013
- March 2013
- October 2012
- July 2012
- March 2012
- February 2012
- December 2011
- September 2011
- July 2011
- June 2011
- February 2011
- January 2011
- September 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- November 2009
- October 2009
- August 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- February 2008
- January 2008
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- May 2005
- April 2005
- February 2005
- January 2005
Meta
12 Responses to “INSPIRE view services – why it sucks”
I fully agree. WMTS and pre-rendered or cached tiles is the way to go for background maps.
BTW for CUZK there is now also TMS: http://tms.cuzk.cz/ made with MapTiler.
We have published an open-source project which allows distribution of OGC WMTS compliant (including compatibility with ArcGIS Desktop clients and QGIS) services from an ordinary LAMP (=PHP) server – which is very fast and great for background maps rendered with http://www.maptiler.com/ or alternatives.
Check: https://github.com/klokantech/tileserver-php/.
To be finished including UI a la: http://klokantech.github.com/tileserver-php/tileserver/ by summer and announced on ICC2013 in Dresden.
By Klokan Petr Pridal on Mar 21, 2013
I can not fully agree.
First point is, that WMTS IS part of INSPIRE TG on view services for years… And there is a TileMatrixSet defined on the base of GoogleCRS84Quad named INSPIRECRS84Quad.
You lined out correctly, that there is somehow a lack of usability regarding the different INSPIRE specifications. But I think the win INSPIRE makes possible is even greater. It is interoperability and availability! Never before there was a that widespread initiative which declares that OGC standards have to be used for providing geodata. It will just be a matter of time untill there is a huge coverage for most geospatial data provided by administrations all over europe.
I can understand your point regarding EPSG:3857. But you re wrong in saying, INSPIRE does not specify which SRS to be used. Implicitly specifications say, EPSG:4258 has to be used. And this ETRS89 based SRS does not need big reprojections to others. UTM, the most used projection type is also based on ETRS89 and reprojections are lightweight.
By Sebastian Goerke on Mar 21, 2013
@Klokan Petr Pridal:
You are saying you are providing an OGC compliant WMTS? I cannot believe that, as WMTS is not ready for compliance certification and there are no existing OGC certificates on WMTS yet…
So I think, you should better formulate “we are implementing OGC WMTS standard claiming compliance” ;-)
I will have a look at you project, as I am very interested in WMTS implementations (I am an active contributor of the deegree project)
By Sebastian Goerke on Mar 21, 2013
Thanks/Danke Sebastian, for your comments!
By Jachym Cepicky on Mar 22, 2013
For Flanders (northern part of belgium), you can get orthophotos tiled in EPSG:3857 http://www.agiv.be/gis/diensten/?artid=1671
Check The tms and wmts.
By Johan VdW on Mar 22, 2013
I was not able to keep my hands still with such a provocative title ;-)
And it is very interesting to get some input from a more or less users / web mapping view because INSPIRE is mostly discussed between specialiced geo-experts from the data providers. I see myself somehow inbetween both “worlds” and of course, your main issues stay as points of critiscism, especially reagarding usability!
By Sebastian Goerke on Mar 22, 2013
Oh yeah, the title was cheep and – as you practically tested on yourself – it worked ;-)
But the blogpost is just my $0.02 to the INSPIRE discussion. Or, as Arnulf pointed out, to the INSPIRE dialogue.
By Jachym Cepicky on Mar 22, 2013
Ok, that sucks, but that’s not fault of INSPIRE. That’s fault providers . INSPIRE is very benevolent in many ways and in many DS there’s only written: “you should provide it, when you can”. It’s logical. How could I provide 3D buildings, when I don’t have the data?
I think that a lot of providers have problems (not enough time or money) with basic implementation of INSPIRE GML data and they’re not even thinking about web services yet.
By Michal Med on Mar 22, 2013
Well, it’s always people’s fault, if something does not work. INSPIRE is as good, as people have created it. Concrete example is GML used in INSPIRE, which was not implemented anywhere in the time, it was published. Why was it made so complicated? KISS!
WMTS is just another distribution of the same data, compared to WMS – but in some cases more effective. As I said: it takes not more than a day to set it up (for the student in his first year at university). And it would be great in general, to support real-life use case.
This is really to be read as real-life example: I wanted to display ortophotos from some (all?) European countries on top of OpenStreetMap – is it really *that* extreme requirement?
By Jachym Cepicky on Mar 22, 2013
Yes, I know that you would like it in kml format and honestly, that’s not so bad idea. Unfortunatelly, it’s too late to complain about it. Maybe there could be added into INSPIRE specifications some possibility of providing light-weighted version of data, but honestly, that’s not so likely. In JRC are they quite busy at the moment (in my opinion).
You’re right about WMTS. As I said: it’s fault of providers. And maybe you’re little bit overestimating first year’s students :)
Big problem of INSPIRE nowadays is cooperation over borders. Accurately that there’s nothing like that. On the other side: INSPIRE should contain really HUGE amount of data. Some of the data isn’t available yet, some data are stored by thousands of providers in one country and INSPIRE is still in the beginning. Problems must be solved in sequence.
By Michal Med on Mar 22, 2013
I personally do not push KML as ideal format. Do not push KML at all. But it really is so simple, that it should be considered for INSPIRE purposes.
Too late to complain? C’mon – it’s never too late. Better late, than later.
I agree, that INSPIRE is at the beginning. It’s a huge project and certainly it will be better and it will change some components by the time. It should remain flexible for such proposals, otherwise, it will never be usable – accepted by large community and will remain “just another EU evil”.
By Jachym Cepicky on Mar 22, 2013
Jachym, regarding your described orthophoto use case, don’t you think it is a bit early for actually doing this with INSPIRE? Orthophotos are part of Annex II which has according to the original road map still not to be provided through those schemas.
So your issue is not that much an INSPIRE one ;-)
It is more about how providers configure their services which they also want to be used as their INSPIRE services.
I totally agree, that interoperability is still the big issue and this has also meeting points with usability.
Regarding the GML issue I would say, it has to be that complicated as INSPIREs original aim was to harmonize all geodata touching environmental themes. And harmonizing always means bringing different models together and create the least common factor of them. So GML is the best choice here.
By Sebastian Goerke on Mar 22, 2013