If using the CLI add ‘epsg’ in StreamPipes environment file (.spenv) Running the pipeline-element
environment, your environment file should look like this
# Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional information regarding copyright ownership. # The ASF licenses this file to You under the Apache License, Version 2.0 # (the "License"); you may not use this file except in compliance with # the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. [environment:pipeline-element] backend extensions-all-jvm couchdb kafka ui zookeeper influxdb epsg
Coming soon
Coming soon
The database, in which the epsg data will be imported, is already included as a service (Postgres DB). The Only step the user has to do is to fill the database with the required scripts.
Therefore, the following empty scripts must be replaced in the streampipes/installer/scripts/epsg
folder
Due to license agreement, you have to create an account
to accept the term of use of the ‘EPSG Dataset’.
With an account, you can download the EPSG Dataset here
. Make sure you download the EPSG-v9_9_1-PostgreSQL.zip, which supports the 2007 data model release. Higher versions are not yet supported by the Apache SIS , which is used in StreamPipes to handle Geometry reprojections.
Unzip the folder and replace files
in the streampipes/installer/scripts/epsg
folder.
For indexing the imported data and get better performance, go to this file and replace it with the
in the streampipes/installer/scripts/epsg
folder.
Restart StreamPipes with streampipes up -d
Now check if the database scripts were executed with streampipes logs --follow epsg
If you already started StreamPipes before, the import was done with the empty scripts! You have to delete the corresponding docker volume. The scripts are only imported during the first start!
Therefore, make sure that StreamPipes is not running with streampipes down
.
Now execute docker volume rm streampipes_epsg
Then you can repeat Step 1) and 2)
Coming soon
Coming soon