We already make efforts to ensure that the official data contains entries that are unlikely to conflict with user-supplied data. However I'm sure you'll appreciate that the one item in which we cannot do this is and airport's ICAO identifier.

I must admit I don't understand the problem here; once SkyDemon release full or limited charts for a country, you would therefore no longer need any of your own custom airport data for that country, at least not for the public airports that will be covered by our own data and will include ICAO identifiers.

Have now removed my manually entered ICAO airports. That also removed the conflict.

I tried first to rename the airports, but the software will only accept the ICAO designator - not a C before or anything to separate it.

I have understood that the new version will come with an import function. I plan to import some information but it will be difficult not to end up with some duplicates. Would it not be an idea either to present the duplicate error on activation of the map or to add a letter to all the custom data, so it does not interfere with the Skydemon official data?

The most likely confliction is an ICAO identifier for an airfield, which we require to be unique in all loaded data.

Thanks for the answer.

It is clear for me the two data sets are in conflict. What kind of name convetion do I need to follow not to have this to happen again? I thought the custom data was given special names to avoid risk of overlap.

If you're getting a conflict because you've created your own custom data for Poland and you have now loaded our own Poland chart, you will need to resolve the conflict yourself by getting rid of your own conflicting Poland data. There really isn't anything we can do to resolve this for you.

Got exactly same error for some time.

I was in Poland a few month back and installed some zones and points for that use.

It now found that loading the Polish map will give the same error as you got with the Italian. Propably I named a place that is now already named in the new Polish map.

Removing the polish map removes the error.

Update: this has been narrowed down to an issue with the Italy chart published last week. If you run the chart manager from your start menu, it will automatically update the Italy chart with a corrected version we published this morning, and this will solve the problem.

Thanks for reporting it!

Hi Lufty

Any chance you can email me the zipped up charts and SkyDemon program files you're using and that give you the error? We haven't heard of anyone else running into it so I'm keen to discover what's wrong with that particular configuration.

Hi Tim

I had already upgraded the charts using the Data Manager which worked fine.

By the way if you click the OK button on the SkyDemon warning message you can then click continue on the .net framework error and everything works fine.

Regards

Lufty

It checks when the chart manager is opened. At some point in the future it'll also check in the background after the software is started.