Home | Trees | Indices | Help |
---|
|
django.db.models.Model --+ | PrivateKml
For presenting restricted-access KML datasets that don't belong to a particular user These can be either: * multi-file kml trees on disk (ie superoverlays) * single kml/kmz files Note that this is NOT a Feature so it doesn't have any of the sharing API, wont show in myshapes, etc Admin must upload data to server and place in settings.PRIVATE_KML_ROOT VERY IMPORTANT SECURITY CONSIDERATIONS... * PRIVATE_KML_ROOT should not be web accessible! * Each PrivateKml should have it's own subdirectory in PRIVATE_KML_ROOT! THIS IS IMPORTANT; Every file in and below the base kml's directory path is accessible if the user has proper permissions on the base kml. Sharing and permissions must be implemented one-off in the views using the sharing_groups many-to-many field.
|
|||
|
|
|||
priority = models.FloatField(help_text= "Floating point. Highe
|
|||
name = models.CharField(verbose_name= "Name", max_length= "255
|
|||
sharing_groups = models.ManyToManyField(Group, blank= True, nu
|
|||
base_kml = models.FilePathField(path= settings.PRIVATE_KML_ROO
|
|
priority
|
name
|
sharing_groups
|
base_kml
|
Home | Trees | Indices | Help |
---|
Generated by Epydoc 3.0.1 on Tue Oct 30 11:31:02 2012 | http://epydoc.sourceforge.net |