You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've a need for starting Vidi and when zoom to a feature and auto start editing of it.
Something like calling: http://127.0.0.1:3000/app/mydb/feature/?startedit=feature.polygon|1#osm/10/9.3137/56.817/v:feature.polygon
Where startedit=feature.polygon|1 is layername|pkey (primary key field is stored in the pkey property of Meta)
If a feature exists, when start editing it:
If it doesn't when start creating it. (In this case no zooming will be done). The key from the URL will be used as input. In this case a the new feature with value 1 in primary key field will be used. Something like this (normally we don't send primary key on INSERTS but in this case we have to do that)
the feature.polygon|12 is provided, the identifier 12 already exists, but the layer is dynamically loaded - ensure that feature with such identifier does not exist in the layer;
the provided identifier already exists in the layer - start editing;
check the possibility of inserting data with specified identifiers (gid's);
We've a need for starting Vidi and when zoom to a feature and auto start editing of it.
Something like calling:
http://127.0.0.1:3000/app/mydb/feature/?startedit=feature.polygon|1#osm/10/9.3137/56.817/v:feature.polygon
Where
startedit=feature.polygon|1
is layername|pkey (primary key field is stored in thepkey
property of Meta)If a feature exists, when start editing it:

If it doesn't when start creating it. (In this case no zooming will be done). The key from the URL will be used as input. In this case a the new feature with value
1
in primary key field will be used. Something like this (normally we don't send primary key on INSERTS but in this case we have to do that)The text was updated successfully, but these errors were encountered: