Hi,
If I had to refactor the layer hierarchy to include datasets without
geometry, I would probably try something like that
(note that it would be a big refactoring, and I am not able to evaluate
the workload to achieve it)
Current layer hierarchy
Current layer hierarchy
Proposition to incl
Hi,
In GeoJSON FeatureCollection must have "properties" member even if there are no
attributes. This output from OpenJUMP r5186 does not validate
{
"type": "FeatureCollection",
"features": [
{ "type": "Feature", "geometry":
{"type":"Polygon","coordinates":[[[278,423],[483,505],[478,293],[278,4
from http://geojson.org/geojson-spec.html
"
A GeoJSON object with the type "Feature" is a feature object.
A feature object must have a member with the name "geometry". The value of the
geometry member is a geometry object as defined above or a JSON null value.
A feature object must have a member
Revision: 5188
http://sourceforge.net/p/jump-pilot/code/5188
Author: edso
Date: 2016-11-15 10:02:05 + (Tue, 15 Nov 2016)
Log Message:
---
GeoJSON spec expects properties object to written all the time, might be null
though
Modified Paths:
--
core/trunk/
Jukka,
please try r5188.. ede
On 15.11.2016 10:31, edgar.sol...@web.de wrote:
> from http://geojson.org/geojson-spec.html
> "
> A GeoJSON object with the type "Feature" is a feature object.
>
> A feature object must have a member with the name "geometry". The value of
> the geometry member is a
Hi,
DB Query plugin is attaching a fake GEOMETRYCOLLECTION EMPTY to all the lines
without a real geometry. For my purposes it has been a good solution but I
can’t say if it suits for other use cases.
-Jukka Rahkonen-
Stefan Steiniger wrote:
Hi,
i used empty geomcollection so far, to have so
GeometryCollection is afaik the only possibility to have an empty geometry as
all other geom types require either coordinates or sub geoms per definition.
..ede
On 15.11.2016 11:06, Rahkonen Jukka (MML) wrote:
> Hi,
>
> DB Query plugin is attaching a fake GEOMETRYCOLLECTION EMPTY to all the lin
Hi,
What do you mean? You did lot of work with empty geometries two years ago. In
December 1st, 2014 I answered you, probably after the final tests
"Hi Ede,
All this seems to work perfectly now:
- Different empty geometries are visualized with corresponding icons
- All kind of empty geometries
Hi,
According to this mail empty geometries in GeoJSON are {"geometry": null}
http://lists.geojson.org/pipermail/geojson-geojson.org/2013-October/000839.html
-Jukka-
-Alkuperäinen viesti-
Lähettäjä: edgar.sol...@web.de [mailto:edgar.sol...@web.de]
Lähetetty: 15. marraskuuta 2016 12:35
Jukka,
nothing to worry, my mind was w/ GeoJSON still and the only possibility to add
an empty geom there is to use GeometryCollection because of the constraints i
described.
my bad ..ede
On 15.11.2016 11:16, Rahkonen Jukka (MML) wrote:
> Hi,
>
> What do you mean? You did lot of work with emp
Hi,
One closing "}" seems to be missing. There is EPSG:0"}}} but should be one
more. Otherwise validates in jsonling.com and in geojsonlint.com.
{
"type": "FeatureCollection",
"features": [
{ "type": "Feature", "properties" : null, "geometry":
{"type":"Polygon","coordinates":[[[207,483],[343,
On 15.11.2016 12:02, Rahkonen Jukka (MML) wrote:
> Hi,
>
> One closing "}" seems to be missing. There is EPSG:0"}}} but should be one
> more. Otherwise validates in jsonling.com and in geojsonlint.com.
whooops a typo ;)
> {
> "type": "FeatureCollection",
>
> "features": [
> { "type": "Feature
right again,
and i even quoted the http://geojson.org/geojson-spec.html part to you wrt.
properties some mails ago ;(. obviously need more coffee still.
will patch the writer accordingly, even though OJ internally does not know null
geometries i implemented it just for completion.
i know i can
Revision: 5189
http://sourceforge.net/p/jump-pilot/code/5189
Author: edso
Date: 2016-11-15 11:31:49 + (Tue, 15 Nov 2016)
Log Message:
---
refine handling when geom or props are NULL
Modified Paths:
--
core/trunk/src/com/vividsolutions/jump/io/geojson/Geo
should be fixed in r5189 ..ede
On 15.11.2016 12:27, edgar.sol...@web.de wrote:
> On 15.11.2016 12:02, Rahkonen Jukka (MML) wrote:
>> Hi,
>>
>> One closing "}" seems to be missing. There is EPSG:0"}}} but should be one
>> more. Otherwise validates in jsonling.com and in geojsonlint.com.
>
> whoo
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
Mike,
i see your point. i'd vote to stick what we've got then and simply autocreate
empty geometries as we do now. just curious, can CSV writer ignore geoms if i
want to write a plain data table?
..ede
On 15.11.2016 09:02, Michaël Michaud wrote:
> Hi,
>
> If I had to refactor the layer hierar
would you mind packing it and maybe some summer heat on the side as well and
send it to cologne?
;).. ede de la Capital de los tontos
On 15.11.2016 14:29, Stefan Steiniger wrote:
> ede, got some sun for you on my metro ride to work.
>
> stefan
>
> -- Originalnachricht --
> *Von: *
> *D
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, h
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
Hi everybody
and thanks for the comments
@Ede >can CSV writer ignore geoms if i want to write a plain data table?
This is a good point. As CSV exporter also saves geometries in WKT.
I did a couple of tests (exporting large shapefiles of Italian
Regions/Provinces to csv), my LibreOffice speadsheet
maybe a panel to select the columns to be exported for the selected format
would be A. reusable B. fitting for several formats (eg. csv, json).
..ede
On 15.11.2016 18:44, Giuseppe Aruta wrote:
> Hi everybody
> and thanks for the comments
>
> @Ede >can CSV writer ignore geoms if i want to write
ok. A. equals B. there, i mean A. flexible B. reusable.. ede
On 15.11.2016 21:21, edgar.sol...@web.de wrote:
> maybe a panel to select the columns to be exported for the selected format
> would be A. reusable B. fitting for several formats (eg. csv, json).
>
> ..ede
>
> On 15.11.2016 18:44, Giu
Good idea. How about having an option to rename the columns to be exported by
the same? Would be handy for example when exporting columns with long names
into shapefiles when automatic truncation can create non-informative names.
-Jukka Rahkonen-
edgar soldin wrote:
> maybe a panel to select
Revision: 5190
http://sourceforge.net/p/jump-pilot/code/5190
Author: michaudm
Date: 2016-11-15 22:15:19 + (Tue, 15 Nov 2016)
Log Message:
---
Fix #353 Dialogs do not use preferred size on dual screen
Modified Paths:
--
core/trunk/ChangeLog
core/trunk
Hi,
Renaming attributes to be compatible with shapefile specification is a
common need.
I also had this need and decided to go through configuration files. With
layers having
20 to 30 attributes each, if you have to rename attributes more than one
or two times,
a graphical interface will not do
26 matches
Mail list logo
