In order to create a valid GeoJSON file that can be used from Javascript libraries like d3, the GeoJSON objects included within the Dict created by geojson2dict (and hence included in the JSON objects themselves), cannot have the fully qualified Julia type information. Prior to this commit, when using Julia 0.4.5, the dictionaries created via geojson2dict for any GeoJSON object included the fully qualified type information, including the GeoJSON package name. This change ensures that only the geom entries in the tuple above are printed, but not the fully qualified type.
Coverage remained the same at 90.526% when pulling 5990d922ba65dc13c9212f59b2bb09226c1e7a21 on AndyGreenwell:name-qualification-patch into cf69b8d3449e9cbe1f356f01356ae42ebf7dd375 on JuliaGeo:master.
Coverage remained the same at 90.526% when pulling e4d752bfa440181e5951f430b82b005990a66a1c on AndyGreenwell:name-qualification-patch into cf69b8d3449e9cbe1f356f01356ae42ebf7dd375 on JuliaGeo:master.
In order to create a valid GeoJSON file that can be used from Javascript libraries like d3, the GeoJSON objects included within the Dict created by geojson2dict (and hence included in the JSON objects themselves), cannot have the fully qualified Julia type information. Prior to this commit, when using Julia 0.4.5, the dictionaries created via geojson2dict for any GeoJSON object included the fully qualified type information, including the GeoJSON package name. This change ensures that only the geom entries in the tuple above are printed, but not the fully qualified type.