Chart Object Search plug-in

[DavidBurch]

Thanks very much. I will try both. We have a training chart 18465TR which has a big chunk of Canada in it, and without those expensive CND ENC we need to add these by hand.

thanks again.

--david

Originally Posted by nohal

Yes, the plugin has it's data stored in a very simple SQLite database so you can use any client that can work with it to add, delete or modify the data.

You can also import any data on the Database Maintenence tab in the plugin preferences dialog using a CSV file with the following columns:
Latitude(floating point number),Longitude(floating point number),Object name(string),Feature name(string),Source name(string)

Pavel

[cagney]

Pavel

Downloaded and compiled your latest Git code.

Going to Options-Plugins-ObjSearch-Preferences, doing nothing and then click "OK" surprisingly changes OpenCPN's chart view to lat/long 0.0/0.0 .

Thomas

[DavidBurch]

Hi Pavel,

Can you please tell why this csv update is not working. It does put all of the items into the db, and in the right categories, but it can't find them. The categories show up, but new objects cannot be found. I must be doing something wrong as this did work at one point, but i cannot tell what is different.

thanks. I want to make a stand alone update file for a specific chart, which is why the csv file is attractive.

thanks.
--david

48.406745,-123.387455,Brotchie Ledge,Beacon lateral,18465
48.406745,-123.387455,Scroggs Rocks,Seabed area,3419
48.405219,-123.334868,Ross Bay,Sea area,18465
48.413961,-123.3937,Victoria Harbor Light,Light,18465

Originally Posted by nohal

Yes, the plugin has it's data stored in a very simple SQLite database so you can use any client that can work with it to add, delete or modify the data.

You can also import any data on the Database Maintenance tab in the plugin preferences dialog using a CSV file with the following columns:
Latitude(floating point number),Longitude(floating point number),Object name(string),Feature name(string),Source name(string)

Pavel

[nohal]

David...

The data currently must be sorted on the last column and the respective "chart"(source) must not exist in the database. I consider it a bug and will fix it, but for now this is how your data must look to import successfully.

Pavel

[DavidBurch]

Thanks Pavel, i will give it a try. --david

Originally Posted by nohal

David...

The data currently must be sorted on the last column and the respective "chart"(source) must not exist in the database. I consider it a bug and will fix it, but for now this is how your data must look to import successfully.

Pavel

[DavidBurch]

Thanks again Pavel. That works now. Not really an issue once you pointed out the rules. I will study some more then make an "objects patch" for our students for this unique US chart (18465) that has a missing ENC sector. Even on normal charts many land areas like points and headlands get missed as they are not encoded in the ENC. This makes your csv option all the more valuable for optimizing this neat plug in of yours. The next generation of ENC will be much better with terrain-based objects and their attributes. --david

[nohal]

I have released a new version of the plugin that should fix the crashes reported on Windows

You may get the installer from https://github.com/nohal/objsearch_p...ov50-win32.exe

Cheers

Pavel

[Gilletarom]

Hello Pavel,

I just installed the version for O5.0 of this plugin.

In the "preferences", the announcement says that it is the version 0.21 ... But, I have an old screenshot that already announced version 0.7 ...

Hum What about ?

[nohal]

Originally Posted by Gilletarom

Hello Pavel,

I just installed the version for O5.0 of this plugin.

In the "preferences", the announcement says that it is the version 0.21 ... But, I have an old screenshot that already announced version 0.7 ...

Hum What about ?

Gilletarom...

Where I live, 21 is more than 7. That's what it's about.

Pavel

[cagney]

Originally Posted by nohal

Gilletarom...

Where I live, 21 is more than 7. That's what it's about.

Pavel

Is it? Certainly 0.7 > 0.21, as Gilletarom says.

A bit of a nightmare to "explain".

Thomas

[nohal]

Originally Posted by cagney

Is it? Certainly 0.7 > 0.21, as Gilletarom says.

A bit of a nightmare to "explain".

Thomas

But we are not talking decimal number, we are talking semantic version.

[cagney]

Originally Posted by nohal

But we are not talking decimal number, we are talking semantic version.

Well, still not quite right then. The versioning should then be similar to 0.0.7/0.0.21 or 0.7.0/ 0.21.0. -https://semver.org/. As it is now it's confusing, which this exchange shows. Alternatively I and Gilletarom are confused

Thomas

[nohal]

Originally Posted by cagney

Well, still not quite right then. The versioning should then be similar to 0.0.7/0.0.21 or 0.7.0/ 0.21.0. -https://semver.org/. As it is now it's confusing, which this exchange shows. Alternatively I and Gilletarom are confused

Thomas

As usually, I will gladly consider accepting pull requests solving this "issue".

[Gilletarom]

Hello,


Anyway, there are so many details that have been settled here where the ... We can accept that detail. I would be surprised if many users come to complain.
You have to be plunged into OpenCPN, as I am, for seeing this detail.

It will be enough during the next update to choose as future version number 2.2.


In the meantime, this debate on the value of "<" and ">" and / or on the meaning of what is semantic or not ... I admit that he amused me.

[nohal]

Originally Posted by Gilletarom

Hello,


Anyway, there are so many details that have been settled here where the ... We can accept that detail. I would be surprised if many users come to complain.
You have to be plunged into OpenCPN, as I am, for seeing this detail.

It will be enough during the next update to choose as future version number 2.2.


In the meantime, this debate on the value of "<" and ">" and / or on the meaning of what is semantic or not ... I admit that he amused me.

The next version will be 0.22. At some moment there might be 1.0