mdb file uploaded, but the geometry gone.

connect via ODBC provider:

I use RawConnectionString and then this code to connect to my *.mdb file

Driver={Microsoft Access Driver (*.mdb, *.accdb)};Dbq=Partition:\DIrectory\*.mdb

however, there is a Problem. The geometry will not available. The data treated as non-spatial data.

when i validate the connection, those heads up coming out as result:

Information - OSGeo.MapGuide.ObjectModels.FeatureSource_1_0_0.FeatureSourceType: No primary key defined for class: Fdo:Langkawi_poi_Shape_Index, features will not be selectable and feature joins on this class may produce unexpected results

but its ok. i think, i will try to edit the xml coding as shown in Jackie's post entitled FDO Schema Overrides

and i will update the progress.

pee ass: i think, if these succeed, i can join both data and the mission accomplished! :)

how to load non-spatial table and then join it with spatial data in mapguide? (unresolved yet)

ok. here's the thing.

i want to do a map that has external table.

why? the data condition doesnt permit me to do one-one relationship mapping.

so, i want to it this way (look at image below. ive done it using arcgis)

i tried to imply the same concept in Opensource Mapguide, but it seems like i met with failure each way.

the 1st problem is, i failed to load dbf file using SHP provider. the program recognize the absence of geometry as error.

so, i try to convert the data into *.mdb and manage to connect the data.

however the geometry properties is gone, gone and gone. aarrghh the sky is falling.

but nvm lah. i think i jz can re-load the with-geometry data using shp provider and relate both data.

so, i move on to create layer for the external table.

another road-block. error again since the data doesnt hv geometry.

get it? layer = geometry properties.

owh. so how? is there any resource in mapguide that allow user to create "table", or anything that allow the non-spatial table to be view and joined with spatial data?

i've already sent an email to jackie ng. I hope he is in a good mood and reply to my email :(

import mysql file

this is one part of my mysql lesson.

if copy-paste the database folder from directory of c:xampp/mysql/data/destinationfolder is not working for other laptop, try to export the database into .mysql using localhost/phpmyadmin

-end-

Spatial Data Connection in Mapguide

this is my findings during my research of publishing marine physical oceanography of web using Mapguide.

here's the thing. it is so hard to load a geodatabase (.mdb) perfectly into mapguide. mapguide only able to support shapefile (via load data procedure) in default. however, the aims of our research is to create a centralized database, not a file-based data compilation on a web server.

here's the research that i've done in a way to achieve the objective of publishing centralized database on the web using open source mapguide.

mdb file actually can be loaded into mapguide using a little customization of the software. all you need is OGR provider that can be downloaded in OSGEO website..

extract the file and paste the .dll file into opensource FDO directory that usually found in:

c:/program files/osgeo/bin/fdo

but, this provider is still need to be revised since it only load spatial data (with geometry properties). in a normal centralized database, not all data are spatially georeferenced. supported non-spatial data such as land parcel owner is still needed to create a meaningful database!

ok, here's the summary of my finding.

Data format	Provider used	Findings
*.mdb	OGR Provider	Only load spatial data. Non-spatial data that implemented in the database is not included during data loading.
*.mdb	ODBC Provider with system DSN setting	Load all data in the geodatabase, but it neglect the geometry (spatial) properties of the data
*.shp	default	Load the Shapefile data, but doesn’t has ability to load external non spatial data (*.dbf file)
postgis	Postgis Provider	Data need to be converted into postgis format using FME. The spatial extend need to be specified to view the geometry of the data. No issues of spatial – non spatial table.
*.kml	KML FDO Provider	Installed the .dll file, but it is still not appear in the menu of data connection. Duh!!

niu werk

its been a long time since my last update..

however,my data model was implemented n now we're working on publishing the thingy on internet server...

actually its nabil's work... but he's quitting n i have to do every single thing, including hadi's ontology....

i really hope that Rosddi can come out with useful data catalogue since it will use it in my annotation and ontology.

ontology is a semantic, synonymous, antonymous, and meronim database that related to certain keyword that exist in MyNODC database.

in other hand, annotation is the evidence. evidence of the relationship, or in this case, the evidence of relationship between the keyword with related words. the evidence is in form of trusted journal, organization and formal documentation...

cruise

A Customization of the Arc Marine Data

Model to Support Whale Tracking via

Satellite Telemetry (Brett Lord Castillo)

The Operations group is divided into two areas,

Cruise and Approaches (Figure 7).

Cruise involves a small number of generic object classes to link field observations to the

person making the observation.

Approaches handle the specific operational situation of

approaching an animal and deploying a tag.

Cruise is essentially a customization of the Arc Marine SurveyInfo object class tables.

SurveyInfo links an InstantaneousPoint to a unique survey operation.

This point may

represent a sighting, photograph, deployment, telemetry location, or a wide variety of

other features.

When this point is linked to a survey though, that survey has a specific

crew, identified by CrewKey, and specific crew members in that crew, identified by the

Crew class object.

Thus, a crew has crew members and carries out one unique survey.

SurveyInfo is also a dimension of the ApproachEvent, a linking dimension table for the

Approach object group.

IHO s-100

Goals for S-100

S-100 will support items such as imagery and gridded data, 3D and time-varying data (x, y, z, and time), and new applications that go beyond the scope of traditional hydrography; for example, high-density bathymetry, sea floor classification and marine GIS. It will also enable the use of web-based services for acquiring, processing, analysing, accessing and presenting data. It is important to recognise that S-100 is not an incremental revision of the current Edition 3.1 of S-57. S-100 will be a new standard that includes additional content and support of new data exchange formats.
S-100 was released as a draft version in February 2008 and is in its development phase.