Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

I have found a very interesting paper here related to this topic.

I just want to have views/ideas from other professional about how we can protect GIS data using Cryptography or Digital Watermarking?

Any suggestions, especially for Administrative layers of a country where source of layers is same for every company so output is also same more or less.

I am interested in some methods like one suggested here

share|improve this question
2  
Might be useful for a bit more info. I assume you are a data provider. Are you trying to protect data that's stored online, or somehow retrict data files to access by your end-users? Or are you just looking to make the data identifiable if it does get copied? Or all of these? –  Mark Ireland Dec 5 '11 at 18:10
    
I will say all of these –  iRfAn Dec 6 '11 at 8:03
    
I wrote an answer, then decided my answer was more of a debate, so sent it to chat instead: chat.stackexchange.com/transcript/message/2637119#2637119 –  matt wilkie Dec 7 '11 at 19:10
1  
I am the author for this paper. for any help contact me aft1972@yahoo.com Regards Dr. Ashraf Tammam –  user25608 Jan 9 at 6:51

3 Answers 3

up vote 8 down vote accepted

Fake features - fake roads or trap street - http://en.wikipedia.org/wiki/Trap_street can be easily spotted - fines up-to £20 million have been applied for reproduction without license to from digital data.

Open Street Map is highly aware of this 'A Copyright Easter Egg' in terms of mapping, is a feature that is drawn in a distinctive way in order to help identify its original author. It may be a nonexistent, or slightly or heavily distorted, map feature, or its name may be wrongly or unusually spelt.

share|improve this answer
    
Thanks for nice links. Our Administrative and postal code maps generally of 10K scale and maps for that scale we have really less options for adding any fake feature (like fake street in OSM) or road length as in example of ordinance survey. –  iRfAn Dec 5 '11 at 15:23

At a slightly lower level, you may want to have a look at this presentation about securing GIS data, a variation of which was given at FOSS4G in Denver earlier this year.

Before going to very advanced scheme to prevent data theft, you should first make sure that the data is only available to the authorized users and prevent others to gain unauthorized access. Many of the commonly used solutions are reasonably weak in this area. A framework like Geomajas has a client-server architecture which allows you secure your GIS data in a few ways. Some of the advantages include:

  • Data can be filtered on the server (fine grained, including filtering features or even attributes of features). This assures unauthorized data cannot be discovered at the client.

  • It prevents leaking credentials to the data sources by acting as a security proxy. By putting the Geomajas server in the demilitarized zone, you can completely shield your data sources from the internet (like WMS/WFS servers).

  • It allows single sign-on with other services.

  • The security can be integrated in the application (adding custom policies).

Admittedly, such schemes do not prevent authorized users to copy data and distribute to unauthorized users. Schemes like watermarking can help in such cases to be able to find the source of the data leak.

share|improve this answer
    
Thanks for nice link, but our data is not only available as WMS but also available in all popular GIS formats like TAB/shp or FileGeoDB. Our data only available to authorized user but you never know that out of 40 thousand users which one has violated copyrights. –  iRfAn Dec 6 '11 at 9:39
    
I would say there is no way you can prevent users from copying the data and sending it on unauthorized. Making sure the data is only available as images on the client is one solution, but they could still take a screenshot and distribute that. The approach from the article seems overkill in most cases (they indicate themselves that it is slow - I guess plain SSL is a lot faster). In any case, I see no possibility to automatically enforce a limited use of data, contracts only. In that sense watermarking can help trace who distributed the file if you include a different watermark for each user. –  Joachim Van der Auwera Dec 7 '11 at 21:25

As @Mapperz said road data can include easter eggs to prove copyright violation. (I am aware of a case where this was used to show violation but I cannot find it now after searching.) However, this does not help with polyline data.

You can approach this using digital watermarking. There are a large number of papers on this. I have two examples which you can find on IEEE or ACM.

Michael Voigt and Christoph Busch, "Feature-based watermarking of 2D vector data", Proc. SPIE 5020, 359 (2003); doi:10.1117/12.476815

Michael Voigt, "Watermarking geographic vector-data using a variable strip-size scheme", Proc. SPIE 6505, 65051V (2007); doi:10.1117/12.704557

I would recommend Google searches for "polyline digital watermarking", "GIS digital watermarking" and other variations. Secondly, if you follow citations to the Voigt papers you will find more. A large number of them are written by Chinese or Japanese researchers so the English translation can be difficult and the heavy maths involved make it worse.

Being simplistic, the watermarking techniques involve moving some of the points in special ways such that there is a signal in the points which can be detected if you know how to look for it but the changes are less than the noise error. Some of the techniques are "blind" - this means that the watermark can be detected without the original data.

share|improve this answer
    
Wow! That is so cool. Who knew? –  Mark Ireland Dec 12 '11 at 23:03

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.