| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
input to GetLandObject()
This conforms to the existing ILandChannel.ParcelsNearPoint() method
|
| |
|
|
|
| |
However, the calls to the land management module to record prims need to remain, since they were also being used to return owner object lists, etc.
This is probably why prim counts were being done there in the first place.
|
| |
|
|
|
|
|
|
| |
parcels from the OAR.
The region spanning parcel shouldn't exist in this situation. If it does, when the land data is loaded it is repersisted with a local ID which comes after the ones loaded via the oar, which obliterates the oar loaded one.
Resaving the data we just loaded from the database is somewhat odd in itself (though this makes sense from the way that OAR loading was already using the same event).
|
| |
|
|
|
|
| |
of merged.
The --merge switch will still merge the old and new land parcelling.
|
| | |
|
| |
|
|
| |
joins parcels in an area, osParcelSubdivide splits parcels in an area, osParcelSetDetails sets parcel name, description, owner and group owner. Join and Subdivide methods in LandChannel are exposed.
|
| | |
|
| | |
|
|
|
* Moves the mono_metadata_token_from_dor message to a different module on loading.
|
