On opening the new gui for the first time, a default gui state is setup and stored in registry. This default state does not create appropriate docking relations between geodms windows.

table view op:
/Analysis/Ref_Abidjan_Ouagadougou/Indicators/TransportPerformance/Limit_90min_120kmEucl/TP_g

geeft na enkele seconden rode tabel met: Link_impedance: undefined values not allowed

Maar niet via F2 of detailpages te tracen naar probleem.

Door klikken naar:
/Analysis/Ref_Abidjan_Ouagadougou/Network/Combine_OrgDest/Imp_Original
Laat zien dat de not-flood (=Original) impedence wel rood is. Mogelijk vindt GeoDMS het leuk dat dat item rood is, terwijl deze ogenschijnlijk niet gebruikt wordt.

ovsrv6:
C:\ProjDir\Jip\geodms_africa_cusa2_issueGH82\trunk\cfg\africa.dms
/Analysis/Ref_Abidjan_Ouagadougou/Indicators/TransportPerformance/Limit_90min_120kmEucl/TP_g

geodms 8.6.3

OVSRV6:
C:\ProjDir\Jip\geodms_africa_cusa2_issueGH81\trunk\cfg\africa.dms
/Analysis/Ref_Praia_Dakar_Abidjan/Network/Network_Original/LinesToConnect/Speed

certain_arg[min|max][|_uint8|_uint16] -> arg[min|max]_alldefined[|_uint8|_uint16]

known_arg[min|max][|_uint8|_uint16] -> arg[min|max]_ifdefined[|_uint8|_uint16]

OVSRV6
C:\ProjDir\Jip\NetworkModel_EU_issueGH3\cfg\main.dms

ctr+D op /SourceData/Infrastructure/Read_Final_Network/Opschoning/ConnectedParts/PartNr
geeft crash

See #12 .

as poly2grid, but directly on shadow_tile.
Will take longer and use more memory, but less CPU time and results independent from actual tiling.

If it is your first time opening GeoDMS, this will create a loop that the software will try to reopen the xml file everytime you open the GUI. Only fixable by editing the registry.

A button in gui to release table/mapview selection.

Use case:
In RuimteScanner zien waar hij is in het proces.
Dus graag ook iets van pad informatie toevoegen.

The used should be able to create bookmarks on a specific configuration. These bookmarks could be implemented as buttons. When clicked, geodms state is changed to the state of the bookmark. The state encompasses:

• open views and their position
• for every view, the cursor position (tableview) or zoom and extent (mapview)
• DetailPages: active page

As explained in this issue the configuration file for libiconf is invalid, as: "libtool-2.4.6-9-x86_64.pkg.tar.xz is no longer available, updated version to libtool-2.4.7-3"

Likely to be resolved by a new version of vcpkg, to be tested.

Same style as TreeView:

ie. Alt-F, ALT-E as open

error: result of select_data is of type AbstrDataItem, expected type:

OVSRV6:
C:\ProjDir\Jip\IssueGH8.dms

/NUTS_selectie_many/geometry

attribute Geometry_BP (arc) := Geometry[BaseProjection];

resulteert in crash

OVSRV6:
C:\ProjDir\Jip\geodms_africa_cusa2_issueGH80\trunk\cfg\Africa.dms

map view of table view op:
/SourceData/Roads/OSM/Algeria/inFile/geometry_bp

in 8.6.3

OVSRV6
C:\ProjDir\Jip\BAG-Tools_issueGH10\cfg\BAG20_Xml2FSS.dms

crash bij ctrl+D op
/xml/ligplaats/ParsedXML/Objecten_ligplaats/gml_Polygon/srsDimension

In 8.6.3

Make use of implot to allow GeoDMS users to plot data in various ways and get more insight in how to best use (new) data in their models.

unit<spoint> monolith :=
	range(
		 gridset(
			 rdc_meter
			,point(-gridsize, gridsize, rdc_meter)
			,point(y_max, x_min, rdc_meter)
			,spoint
		)
		,point(0s, 0s)
		,point(nr_rows, nr_cols)
	),	DialogData = "rdc_meter";
	
// unit<spoint> tiled := TiledUnit(point(1024s, 1280s, monolith)); //25m
unit<spoint> tiled := TiledUnit(point(768s, 768s, monolith)); //100m
	
// unit<spoint> domain := tiled
unit<spoint> domain := monolith

poly2grid(geometry,domain) op item: /geography/RegioIndelingen/Gemeente2019_single/Per_AdminDomain

geeft bij tiled 1024x1280 tiles: Nr Values: 66,473,224
geeft bij tiled 768x768 tiles: Nr Values: 66,473,223
geeft bij untiled: Nr Values: 66,473,223

OVSRV6:
C:\ProjDir\Jip\RSLight2021_ontwikkel_3_regressietest_compacted_GH12\Runs\casus.dms

statistics op:
/geography/RegioIndelingen/Gemeente2019_single/Per_AdminDomain

aan en uitzetten van tiling varianten hier:
/geography/perGridsize/size_25m/Domain

OVSRV6
C:\ProjDir\Jip\Verdichting_issueGH9\cfg\verdichting.dms

Rood en error op:
/Analyse/RedevelopmentPaper/Export

OVSRV06:
C:\ProjDir\Jip\NetworkModel_EU_issueGH6\cfg\main.dms

mapview op /SourceData/RegionalUnits/NUTS/LEVL_CODE
geeft crash

rechtermuis knop > export > dbf and shp op attribuut, dan opslaan geeft freeze en error:

"device or resource busy: device or resource busy
/Desktops/Default/ViewData/DbfTable"

het is een vector attribuut, maar de geometry is niet daar geconfigureerd. Wanneer je het eerst een unit configureert, en dan rechtermuisknop op de unit werkt wel. Dat is mogelijk ook wenselijk gedrag. Desondanks zou de crash, error en freeze niet moeten komen.
Of wil je niet toestaan dat je een attribuut zo kunt exporteren?

OVSRV06:
C:\ProjDir\Jip\LUS_FTM_issueGH7\cfg\main.dms

export op: /Analysis/Allocatie/Per_AllocRegios/StartingState/RestClaim

gebeurt in 8.6.3

Wanneer je WGS84 arcs wilt visualiseren worden alle lijnen zeer dik.
Een work-around is om een PenWorldWidth in te stellen op:

attribute Geometry (arc)
{
parameter PenWorldWidth := 0.0001d , DialogType = "PenWorldWidth";
}

OVSRV6:
C:\ProjDir\Jip\geodms_africa_cusa2_issueGH78\trunk\cfg\Africa.dms

/SourceData/Roads/OSM/Algeria/inFile/Geometry

For new gui, see ocornut/imgui#2920

map view van /SourceData/Infrastructure/Infra_Unchecked/Connectiveness/NodeSet/PartNr
dan helemaal inzoomen naar een node, en dan met de maptools 'Select objects in the active layer by drawing a rectangle' op een enkele node. Dit resulteert na enkele seconden in een crash.

OVSRV6:
C:\ProjDir\Jip\NetworkModel_EU_GH14\cfg\main.dms

/SourceData/Infrastructure/Infra_Unchecked/Connectiveness/NodeSet/PartNr

Discussed in #73

In extra versie van 8.6.3. gemaakt door Erik op 6 januari geeft errors op alle .gdb's

GDAL Error: cannot open dataset D:/SourceData/Overig/Stads_en_Dorpsgezichten_2020.gdb D:/SourceData/Overig/Stads_en_Dorpsgezichten_2020.gdb: Permission denied

OVSRV6:
C:\ProjDir\Jip\Verdichting_issueGH17\cfg\verdichting.dms
/Brondata/Overig/StadsDorpsGezichten_src

Scenario: load luisa-bees, open in TableView (Ctrl-D):
/Geography/AdministrativeBoundaries/src/NUTS1_LUISA/inFile/geometry

and exit. About 28k memory leaks arise from sqllite3 etc.
This issue does only occur when Multi Threading is set on in the GeoDmsGui.exe (Windows 10-x64) with /S0 ... S3 and not when using /C0 ... /C3 (no multi threading).

The leaks result from a non-destroyed databaseContext_ as

OSRGetProjTLSContext() returns a TLS (a.k.a. Thread Local Static) OSRPJContextHolder& that holds a
pj_ctx* context that contains a
projCppContext* cpp_context that contains a
std:shared_ptr<osgeo::proj::io::DataBaseContext> databaseContext_

This all comes from
OGRLayer::GetSpatialRef() that holds a OGRShapeGeomFieldDefn->d: std::unique_ptr<OGRSpatialReference::Private, ...>
->... d->setPjCRS(proj_create_from_wkt(d->getPROJContext(), ...);
-> pj_ctx* getPROJContext() { return OSRGetProjTLSContext(); }

and similar paths from worker threads.
A non-solution is to call proj_context_create and proj_context_destroy for each worker thread frame that might call OSRGetProjTLSContext indirectly as they manage a separate copy aside from the TLS one that OSRPJContextHolder keeps.

Possible solution is clearing OSRPJContextHolder per worker thread frame that uses gdal or something similar.
See also: OSGeo/gdal#1838
void OSRCTCleanCache() in ogr_proj_p.h, also called from OSRCleanup

GeoDMS 8.6.2
9448 https://xxxxxxx/ruimtescanner/PBL/ProjDir/branches/RSLight2021_ontwikkel_3
9442 https://xxxxxxx/ruimtescanner/PBL/SourceData/Trunk/RSL

open casus.dms
Variant_name BAUZP
Casus_name WLO_hoog_BAUZP

oproepen:
/Analysis/Allocatie/Zichtjaren/Y2050/Impl/ReadStandWind/WindPolygoon/polydomain2/een
GeoDMS klapt eruit zonder enige melding bij opvragen in MapView

Let op: Allocatie dient te zijn uitgerekend voor de betreffende variant

ie. System: new configuration loaded

export naar csv met gdalwrite.vect geeft

OVSRV8:
C:\ProjDir\Jip\RVNL_GH15\Runs\casus.dms

ctrl+D op
/CaseIndicatoren/Export/Verharding/Result

v8.6.3

Wanneer je iets in WGS84 wilt visualiseren, bijvoorbeeld een wegnetwerk uit OSM, dan kun je niet verder inzoomen dan het hele land. Van bijvoorbeeld Algerije, zie hier:

OVSRV6:
C:\ProjDir\Jip\geodms_africa_cusa2_issueGH79\trunk\cfg\Africa.dms
/SourceData/Roads/OSM/Algeria/inFile/Geometry

Zonder de te genereren items expliciet te configureren, geeft de generate parameter direct 'Ready' aan, zonder iets uit te rekenen. Configureer je ze wel, dan werkt t wel.

Werkt niet:

unit<uint32> TomTom_Network_fss_select := TomTom_Network_gpkg
, StorageName = "%SourceDataProjDir%/Infrastructure/TomTom/NW2021_SP_streets.fss";

parameter<string> generate_relevant_items := 'Ready', ExplicitSuppliers = "TomTom_Network_fss_select/Geometry";

Werkt wel:

unit<uint32> TomTom_Network_fss_select := TomTom_Network_gpkg
, StorageName = "%SourceDataProjDir%/Infrastructure/TomTom/NW2021_SP_streets.fss"
{
	attribute<BaseProjection>     Geometry (arc) := TomTom_Network_gpkg/Geometry;
}

parameter<string> generate_relevant_items := 'Ready', ExplicitSuppliers = "TomTom_Network_fss_select/Geometry";

OVSRV6:
C:\ProjDir\Jip\NetworkModel_EU_GH13\cfg\main.dms
/SourceData/Infrastructure/TomTom/generate_relevant_items

Some button states should be synchronized to all active views (if applicable).