Hi Stefan, > now that you are back, I would like to ask you something: > I had to write 2 weeks ago, based on the "Join table" from text files > code from SIGLE(?), a plugin to import some CSV data. > Important was, that I did not have any geometry info/coordinates and > just table data. For that reason I could not your plugin. (I actually > needed to match the bus stop IDs of that table with another CSV table > contained all bus stops, that I could load with your plugin). > > I would have liked to basically put/add an option to your plugin that > allows me to say that there are no coordinates - and create a null > geometry instead (or so). But I could not, as the plugin - well - is > your plugin. > Hence, I was wondering if you could merge your plugin code into the SF > code repository? (even integrate it with the core - not just as plugin?) You're right, I must provide the source. I add that to my todo list. The plugin has two modes : automatic structure detection and manual setting. I suggest to add the feature you ask in the automatic mode : no geometry found -> create empty GeometryCollection (null is not an option as it will throw exception sooner or later...) > Btw., I actually figured that the jml export/saving requires a geometry > of some type - so an exception was thrown. Exporting to shp did work. > Maybe something to change? What do you mean ? I can save a layer with no feature in JML and I can save a layer with a single GEOMETRYCOLLECTION EMPTY. Did you try to save a feature with a null geometry ? How did you create it ? I don't think we should authorize it. > However, using the CSV import and export option from your plugin was of > great help. I got my processed Google Transit Feed data back the way I > needed it!!! Nice to hear. > Ah.. and another note: in the SIGLE plugin there is actually a detection > for the attribute type (Integer or Double). While yours just puts/leaves > "Strings" as attribute type ... for later maybe? Yes, it is a possible improvement. There are some reasons why it is not already done : - difficult to guess the type in a 100% safe way without a complete reading - code simplicity - type casting is already available in OpenJUMP so that post-process is easy to do in a safe way (with option to rollback or to nullify in case of type mismatch). But of course, there are also argument to add it (especially in the automatic mode which is there to make user life as easy as possible and which is supposed to work in 99% of casesnot 100%).
Michaël > > cheers, > stefan > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Jump-pilot-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
