[Mapbender_dev] [Mapbender] #718: Non-transactional geometries are not visible during digitizing

Christoph Baudson christoph.baudson at wheregroup.com
Fri Nov 12 04:46:02 EST 2010


Thomas Baschetti wrote:
> On 12.11.2010 09:28, Christoph Baudson wrote:
>   
>> Christoph Baudson wrote:
>>     
>>> Thomas Baschetti wrote:
>>>       
>>>> On 11.11.2010 17:01, Mapbender wrote:
>>>>  
>>>>         
>>>>> #718: Non-transactional geometries are not visible during digitizing
>>>>> ------------------------+---------------------------------------------------
>>>>>
>>>>>       
>>>>>           
>>>> ...
>>>>  
>>>>         
>>>>> ------------------------+---------------------------------------------------
>>>>>
>>>>>  They should be displayed, but be uneditable
>>>>>       
>>>>>           
>>>> I disagree on this one, Non-transactional geometries should be
>>>> unsaveable to the server,
>>>> but editable in the client. I will present a use-case next week.
>>>>   
>>>>         
>>> Thanks for your input.
>>>
>>> Actually we supported both cases (always unsaveable, but both
>>> editable and uneditable), unfortunately the uneditable case broke,
>>> because it's rarely used. Typically, we use the uneditable case for
>>> snapping only. The editable case is for manipulating and then
>>> inserting into an actual WFS-T.
>>>       
>> This configuration is made in digitize_default.conf:
>>
>> nonTransactionalEditable = true/false
>>
>>     
>
> This is what i use at the moment, but then geometries seem to be
> deletable in the database (button is shown), which confuses some users.
>   

The workaround we use is to delete the transactional URL in the WFS table.

Then you need to update the WFS in Mapbender.

Let me know if this works.

Christoph


>
>   
>> I should create a wiki site that explains the configuration file.
>>
>>     
>
> yes, please ;-)
>
>   
>> Christoph
>>
>>
>>     
>>> Curious about your use case.
>>>
>>>       
> It's something like (i use german here)
> - Gebiet über auswählen (z.B. Wahlbezirk, Kindergarteneinzugsgebiet,
> mehrere Flurstück...)
> - Editieren und/oder puffern der Geometrien
> - mit dieser Geometrie Abfrage auf z.B. Einwohnerdaten, ALB-Daten usw.
> Zweck:
> - Ermitteln von Einwohner in Gebieten, wenn diese geändert werden sollen.
> - Ermitteln von Einwohnern in Gefahrenzonen (X Meter um Bombenfund)
> - Ermitteln von Grundstücksbesitzern
> ...
>
> I will explain in Detail and perhaps create a demo-site next week.
>
> Thomas
>
>   


-- 

********************************************
Where2B Konferenz 2010
09. Dezember 2010 in Bonn
www.where2b-conference.com
******************************************** 

----------------------------------

Aufwind durch Wissen!

Qualifizierte OpenSource-Schulungen
bei der www.foss-academy.eu

---------------------------------- 

_______________________________________

W h e r e G r o u p GmbH & Co. KG

Siemensstraße 8
53121 Bonn
Germany

Christoph Baudson
Anwendungsentwickler

Fon: +49 (0)228 / 90 90 38 - 15
Fax: +49 (0)228 / 90 90 38 - 11
christoph.baudson at wheregroup.com
www.wheregroup.com
Amtsgericht Bonn, HRA 6788
_______________________________________

Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm
_______________________________________ 



More information about the Mapbender_dev mailing list