Hello Brian, I appreciate the standards and I know quite well GDAL GeoJSON driver which by the way is still having the GeoJSON 2008 as default. User must especially ask for RFC7946 with a layer creation option.
Why I still prefer the 2008 version is that I am mostly working with data that are not natively in EPSG:4326 and I am using WFS services a lot. From a WFS users point of view it makes a lot of sense to get exactly the same coordinates if only the outputformat is changing from GML into GeoJSON. http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs&version=1.0.0&request=getfeature&typename=lv:pks_juna_asemat&maxfeatures=1 http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs&version=1.0.0&request=getfeature&typename=lv:pks_juna_asemat&maxfeatures=1&outputformat=application/json I think that dropping the support for crs in GeoJSON was fixing something that was not really broken. I have changed friendly emails with misters Gillies and Daly and I know that they do not agree. I also know that rfc7946 allows use of other coordinate systems: "However, where all involved parties have a prior arrangement, alternative coordinate reference systems can be used without risk of data being misinterpreted." A self explaining, internal CRS element inside the GeoJSON file would have been the "a prior arrangement" for my mind. Otherwise the situation with non-EPSG:4326 GeoJSON will be the same that what we have with shapefiles which are missing the .prj part. When it comes to the GeoJSON driver of OpenJUMP, I do not believe that supporting only GeoJSON 2008 for writing is an critical issue. I do not believe that GeoJSON that is created with OpenJUMP is so often used directly by browser apps, heavier clients like GDAL can read 2008 version without problems, and OpenJUMP can read both versions. JTS and GEOS have been used for big data also before, and license change of JTS does not affect the GEOS port. -Jukka Rahkonen- ________________________________________ Lähettäjä: Brian M Hamlin <mapl...@light42.com> Lähetetty: 15. marraskuuta 2016 17:50 Vastaanottaja: Rahkonen Jukka (MML); jump-pilot-devel@lists.sourceforge.net Aihe: GeoJSON rfc7946 Hi OpenJUMP devs - from a user point of view, standards are valuable !! There is a massive increase in the use of GeoJSON in web development, and also (but less) in desktop GIS. OpenJUMP and users will benefit from emitting standard 4326 geoJSON. If you want to emit CRS geoJSON, you can, however please consider that as a clear user option only. Here is the current GDAL geoJSON driver for guidance. http://www.gdal.org/drv_geojson.html ps - I am using OpenJUMP 1.9 rev 4795 today and many days, to generate PostGIS summary geometry for a large project here in California. Also you may know that JTS license was changed last January, and new "bigdata" applications are now building geometry processing using JTS primitives. thank you very much and best wishes --Brian M Hamlin On Tue, 15 Nov 2016 11:38:02 +0000, "Rahkonen Jukka (MML)" wrote: edgar soldin wrote: >> " The geojsonhint project is at https://github.com/mapbox/geojsonhint. Releases before 2.0 (such as 1.2.1, from May 20016) will validate legacy GeoJSON." >> > what does that mean for us? sorry, there is no sun here today, so my batteries are very low. It means that if we instead of http://geojson.org/geojson-spec.html try to follow https://tools.ietf.org/html/rfc7946 we should re-project data into EPSG:4326 longitude-latitude and drop the crs member. However, people do continue to use other projections. If you feel yourself very kind you could make that selectable "Write GeoJSON 2008 with crs"/"Write rfc7946 GeoJSON". The latter requires that CRS plugin is installed. For my mind the newer specification is not better. -Jukka- ..ede ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
