Closed GabbySuwichaya closed 3 years ago
The problem is that the coordiantes in your CityGML file are in the order of latitude,longitude
. However, our Import/Export tool expects that the order shall be longitude,latitude
for geographic coordinate reference system (e.g. EPSG: 6697). To solve the issue, you need to enable the "Swap X/Y" option before database import. Please refer the online doc for more details.
If it is about the coordinates order, then also check out this link: https://postgis.net/2013/08/18/tip_lon_lat/. The longitude,latitude
order is required by the underlying spatial database.
@clausnagel...Thanks.... Could please tell me step by step how to make this change? I am using pgAdmin4.... I am so .... sorry. I am very new to this ...
@yaozhihang ...Thanks for the reply... I have enabled the "Swap X/Y" option before database import. However, I have received a very strange transformation. What should I do next ?
The calculated bounding box looks strange. Could you share your CityGML dataset or a subset of it?
Closing due to inactivity. @GabbySuwichaya, please provide an excerpt of your data if you still need support.
Hi, I have a problem with creating the database for an area in Tokyo, Japan.
I suspected that this is because I was using SRID = 2451 with the default height and gml:srsName ....Could you clarify how to properly assign SRID and the gml:srsName ?
First, Initially, I know that the area should have been defined as EPSG:6697. However, as I used SRID = 6697 and default gml:srsName, the resulting calculated bounding box in Database gives me the wrong bounding box area as both WGS 84 and my database system are showing the flipping x and y for latitude and long latitude.
However, I don't seem to get good results.
I got the following bounding box error from Database page (in which I get the bounding box by clicking
calculation
).